Veritas NetBackup™ Snapshot Client Administrator's Guide
- Snapshot Client features
- About snapshot basics
- Off-host backup overview
- Off-host backup methods
- About alternate client backup
- Snapshot Client requirements
- 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
- Software-based snapshot methods
- Cache device requirements
- About VxFS_Checkpoint
- About VxVM
- About FlashSnap
- About VVR
- About VSS
- 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
- Troubleshooting issues pertaining to all arrays
- Troubleshooting IBM DS6000 and DS8000 arrays
- Troubleshooting IBM4000 arrays
- Troubleshooting Hitachi arrays
- Notes on Media Server and Third-Party Copy methods
- Backup and restore procedures
- About restores from a FlashBackup backup
- Instant Recovery restore features
- About Instant Recovery: block-level restore
- About Instant Recovery: file promotion
- About Instant Recovery: Fast File Resync (Windows clients only)
- About Instant Recovery: point in time rollback
- About configurations for restore
- About restoring from a disk snapshot
- 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
Notes on rollback
Note the following.
Rollback deletes all files that were created after the creation-date of the snapshot that you restore. Rollback returns a file system or volume to a given point in time. Any data changes or snapshots that were made after that time are lost.
Also, if there are multiple logical volumes on a single disk or volume group and if you perform a Point in Time Rollback of a specific logical volume, the entire disk or volume group is restored to the point in time.
Rollback can be done only from the backups that were enabled for Instant Recovery and made with one of the following methods: VxFS_Checkpoint, VxVM, FlashSnap, NAS_Snapshot, or the disk array methods.
To verify that the clone is complete before you do a rollback:
For the backups that were made with the VxFS_Checkpoint method, rollback requires the VxFS File System 4.0 or later and Disk Layout 6. For NAS_Snapshot, the file system requirements depend on the NAS vendor.
Rollback deletes any VxFS_Checkpoint snapshots or NAS_Snapshot snapshots (and their catalog information) that were created after the creation-date of the snapshot that you restore.
If the primary file system is mounted and the snapshot resides on a disk array, the rollback attempts to unmount the file system. Any I/O on the primary device is forcibly stopped if the unmount succeeds. To be safe, make sure that no I/O occurs on the primary device before a rollback.
If the attempt to unmount the primary file system fails, the rollback does not succeed. You should halt I/O on the device and retry the rollback. For example, if a terminal session has accessed the file system through the cd command, change to a directory outside the file system and retry the rollback.
Rollback is available only when you restore the file system or volume to the original location on the client.
When a file system rollback starts, NetBackup verifies that the primary file system has no files that were created after the snapshot was made. Otherwise, the rollback aborts.
Rollback from OST_FIM type snapshot can be done from copy one only.
For the rollback from OST_FIM type snapshot, refer to the NetBackup Replication Director Solutions Guide.