NetBackup™ Snapshot Client Administrator's Guide
- Introduction
- Installation
- Policy configuration
- Notes on policies
- Configuring a policy
- Backup Selections tab options when configuring a policy
- Off-host backup configuration options
- Selecting the snapshot method
- Configuring backup scripts
- About using alternate client backup
- Configuring alternate client backup
- Policy configuration tips
- About disabling snapshots
- NAS snapshot configuration
- About NAS snapshot overview
- Dynamic data streaming for D-NAS workloads
- Prerequisites for NetBackup DNAS configuration
- Configuring dynamic data streaming with backup host pool
- Configuring a backup host pool
- Discover plugins
- Minimum supported backup host versions for different features
- Limitations and considerations
- Setting up a NAS-Data-Protection policy
- FlashBackup configuration
- Instant Recovery configuration
- About Instant Recovery capabilities
- Instant Recovery requirements
- Instant Recovery restrictions
- Giving full server privileges to the media server
- About Instant Recovery
- Configuring a policy for Instant Recovery
- About sizing the cache for Instant Recovery copy-on-write snapshots
- Instant Recovery for databases
- About storage lifecycle policies for snapshots
- Configuration of software-based snapshot methods
- Support for Cluster Volume Manager Environments (CVM)
- Configuration of snapshot methods for disk arrays
- OS-specific configuration tasks
- About IBM DS6000 and DS8000 arrays
- IBM DS6000 and DS8000 software requirements
- Preconfiguration for IBM arrays
- Configuring NetBackup to access the IBM DS6000 or DS8000 array
- Configuring the IBM array for NetBackup
- Using DSCLI commands to obtain unique IBM identifiers
- Configuring a NetBackup policy for IBM_DiskStorage_FlashCopy
- For further reference on IBM arrays
- About IBM DS4000 array
- About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
- Hitachi array software requirements
- Preconfiguration for Hitachi
- About communication between NetBackup and the Hitachi array
- Determining if the Hitachi command devices are visible
- About configuring the Hitachi array for NetBackup
- Obtaining the Hitachi array serial number and the unique device identifiers
- Configuring a NetBackup policy for Hitachi_ShadowImage or Hitachi_CopyOnWrite
- About HP-XP arrays
- HP-XP array software requirements
- Preconfiguration for HP-XP
- About communication between NetBackup and the HP-XP array
- Determining if the HP-XP command devices are visible
- About configuring the HP-XP array for NetBackup
- Obtaining the array serial number and unique HP-XP identifiers
- Configuring a NetBackup policy for HP_XP_BusinessCopy and HP_XP_Snapshot
- About array troubleshooting
- Notes on Media Server and Third-Party Copy methods
- Disk requirements for Media Server and Third-Party Copy methods
- Directives for Media Server and Third-Party Copy methods
- Storage units for Media Server and Third-Party Copy methods
- Preventing multiplexing on a third-party copy backup
- Raw partition backups
- Increasing the client read timeout for all clients
- Further information on off-host data mover backups
- Backup and restore procedures
- Snapshot management
- Troubleshooting
- About gathering information and checking logs
- Logging directories for UNIX platforms
- Logging folders for Windows platforms
- Customer support contact information
- Latest patches and updates
- Snapshot provider information
- Important notes on &newProductName;
- &newProductName; installation problems
- FlashBackup and status code 13
- Single file restore from a FlashBackup Instant Recovery snapshot of a file protected by Windows VSS writer fails
- Identifying and removing a left-over snapshot
- Removing a VxVM volume clone
- Alternate client restore and backup from a snapshot fails
- Restore from a snapshot fails with status 2800
- Raw Partition restore fails with the message 'FlashBackup-Windows policy restore error'
- Snapshot creation fails with error 156
- Snapshot fails with error 20
- Restore from a snapshot fails with status 133
- Backup from snapshot fails with error 50
- Backup from snapshot parent job fails with error 4213: Snapshot import failed
- Snapshot job fails and the snapshot command does not recognize the volume name
- Snapshot creation fails with error 4220
- Snapshot creation fails when the same volume is mounted on multiple mount points of the same host
- Snapshot-based backup and restore failure
- Multiple snapshot jobs fail with code 156 or 1541.
- FlashBackup policy fails, with multiple backup selections [Cache =]
- Partial backup failure with 'Snapshot encountered error 156'
- Backup of file system validation fails with error 223
- Policy validation fails if the specified CIFS share path contains a forward slash
- Policy validation fails with status code 223
- An NDMP snapshot policy for wildcard backup fails with error 4201
- Troubleshooting with bpfis log
- Limitations of using HP-UX 11.31
- While configuring a policy for snapshot operations, the NetBackup Administration Console hangs
- Accelerator enabled incremental backup of NetApp NAS volume
- Snapshot method: Auto
- Appendix A. Managing nbu_snap (Solaris)
- Appendix B. Overview of snapshot operations
- Index
Testing volumes for FlashSnap
Before you run an alternate client backup with the FlashSnap snapshot method, test your FlashSnap volume configuration as described in this section. You must ensure that the disk(s) containing the volume can be moved (deported and imported) to the alternate client without errors.
For instance, the backup disks cannot be split off into a new disk group and deported, if the disks containing the backup volumes contain some part of a volume that has another part on a disk that is not in the backup disks. Deporting a disk group means disabling access to that disk group.
See the Volume Manager Administrator's Guide for more information on deporting disk groups.
The following steps are described in more detail in the Veritas FlashSnap Point-In-Time Copy Solutions Administrator's Guide.
To test volumes for FlashSnap on UNIX
On the primary host:
vxassist -g diskgroup addlog volume logtype=dco
Enable FastResync on the volume:
vxvol -g diskgroup set fastresync=on volume
vxassist -g diskgroup -b snapstart volume
Create a snapshot volume from the primary volume:
For disk groups that were created with VxVM 5.x:
vxassist -g diskgroup snapshot volume snap_volume
Note:
Choose a volume name that is fewer than 15 characters. Volume names are prefixed or suffixed with characters, which increases the volume name. Lengthy volume names can cause snapshot jobs to fail.
For disk groups that were created with VxVM 4.x:
vxsnap -g diskgroup snapshot volume snap_volume
For disk groups that were created with VxVM 3.x:
vxassist -g diskgroup snapshot volume snap_volume
Move the disks containing the snapshot volume to a separate (split) disk group:
vxdg split diskgroup split_diskgroup snap_volume
If the volume has not been properly configured, you may see an error similar to the following:
host-name# vxdg split lhdvvr lhdvvr_split SNAP-emc_concat vxvm:vxdg: ERROR: vxdg split lhdvvr lhdvvr_split failed vxvm:vxdg: ERROR: emc_dis05 : Disk moving, but not all subdisks on it
Re-examine the layout of the disks and the volumes that are assigned to them, and reassign the unwanted volumes to other disks as needed.
Consult the Veritas FlashSnap Point-In-Time Copy Solutions Administrator's Guide for examples of disk groups that can and cannot be split.
vxdg deport split_diskgroup
On the secondary host:
After this test, you must re-establish the original configuration to what it was before you tested the volumes.
Deport the disk group on the alternate client.
Import the disk group on the primary client.
Recover and join the original volume group.
To test volumes for FlashSnap on Windows
On the primary host:
If not already done, create a snapshot mirror:
vxassist snapstart \Device\HarddiskDmVolumes\diskgroup\volume
Create a snapshot volume from the primary volume:
vxassist snapshot \Device\HarddiskDmVolumes\diskgroup\volume DrivePath=C:\Temp\Mount SNAP-VolumeMove the disks containing the snapshot volume to a separate (split) disk group.
The disk group is also deported after this command completes:
vxdg -g DskGrp -n SPLIT-DskGrp split \Device\HarddiskDmVolumes\diskgroup\snap_volume
On the secondary host:
Rescan to make the deported disk group visible on the secondary host:
vxassist rescan
Import the disk group that was deported from the primary:
vxdg -g split_diskgroup import
Assign the snapshot volume to an empty NTFS directory.
This example uses
C:\Temp\Mount.vxassist assign \Device\HarddiskDmVolumes\split_diskgroup \snap_volume DrivePath=C:\Temp\MountIf these commands execute successfully, the volume setup is correct.