Veritas NetBackup™ Snapshot Client Administrator's Guide
- Introduction
- Snapshot Client features
- About snapshot basics
- Off-host backup overview
- Off-host backup methods
- Snapshot Client requirements
- Installation
- Policy configuration
- Selecting the snapshot method
- Configuration parameters for Snapshot Client
- About using alternate client backup
- Configuring alternate client backup
- Policy configuration tips
- About disabling snapshots
- FlashBackup configuration
- Instant Recovery configuration
- About Instant Recovery
- About sizing the cache for Instant Recovery copy-on-write snapshots
- About configuring VxVM
- About storage lifecycle policies for snapshots
- Network Attached Storage (NAS) snapshot configuration
- Configuration of software-based snapshot methods
- Support for Cluster Volume Manager Environments (CVM)
- Configuration of snapshot methods for disk arrays
- About the new disk array snapshot methods
- Disk array configuration tasks
- OS-specific configuration tasks
- About VSS configuration (Windows)
- About EMC CLARiiON arrays
- Configuring NetBackup to access the CLARiiON array
- Configuring a NetBackup policy for a CLARiiON array method
- About EMC Symmetrix arrays
- About configuration for EMC_TimeFinder_Mirror
- About configuration for EMC_TimeFinder_Clone
- About HP EVA arrays
- Verifying connectivity from clients to array using SSSU 5.0
- About IBM DS6000 and DS8000 arrays
- Configuring NetBackup to access the IBM DS6000 or DS8000 array
- About IBM DS4000 array
- About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
- Hitachi array software requirements
- About HP-XP arrays
- About array troubleshooting
- Notes on Media Server and Third-Party Copy methods
- Backup and restore procedures
- About restores from a FlashBackup backup
- Instant Recovery restore features
- About configurations for restore
- About restoring from a disk snapshot
- Troubleshooting
- Logging directories for UNIX platforms
- Logging folders for Windows platforms
- FlashBackup and status code 13
- Appendix A. Managing nbu_snap (Solaris)
- Appendix B. Overview of snapshot operations
- Appendix C. NetBackup integration with CloudPoint for snapshot managment
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_system
To 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.