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
Restoring the entire snapshot on UNIX
You can recover data from the disk snapshot in several ways, depending on your hardware configuration and the snapshot method that the policy used.
To restore the entire snapshot if the snapshot method was FlashSnap
- Unmount the snapshot source (original file system) and the snapshot file system on the alternate client:
umount original_file_system umount snapshot_image_file_systemTo locate the file systems:
Deport the snapshot on the alternate-client:
vxdg list
The format of the disk group name is as follows:
SPLIT-primaryhost_diskgroup
If vxdg list does not show the disk group, the group might have been deported. You can discover all the disk groups, including deported ones, by entering:
vxdisk -o alldgs list
The disk groups in parentheses are not imported on the local system.
Deport the VxVM disk group:
vxdg deport SPLIT-primaryhost_diskgroup
- Import and join the VxVM disk group on the primary (original) client:
vxdg import SPLIT-primaryhost_diskgroup vxrecover -g SPLIT-primaryhost_diskgroup -m vxdg join SPLIT-primaryhost_diskgroup diskgroup - Start the volume and snap back the snapshot volume as follows, using the -o resyncfromreplica option:
vxvol -g SPLIT-primaryhost_diskgroup start SNAP_diskgroup_volume vxassist -g SPLIT-primaryhost_diskgroup -o resyncfromreplica snapback SNAP_diskgroup_volume
To restore the entire secondary disk if the snapshot was made on an EMC, Hitachi, or HP disk array
- WITH CAUTION, you can use hardware-level restore to restore the entire mirror or secondary disk to the primary disk.
If the disk is shared by more than one file system or VxVM volume, there may be unintended results. Read the following:
Warning:
This overwrite can be a problem if you attempt to restore a snapshot of one of the file systems or one of the VxVM volumes that share the same disk. The other file systems or volumes sharing the disk may have older data that you do not want to write back to the primary. When the hardware-level disk-restore takes place, the older data replaces the newer data on the primary disk.