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
Performing snapshot rollback
The following procedure requires root access (UNIX) or Administrator privilege (Windows).
To perform snapshot rollback (UNIX)
- Start the Backup, Archive, and Restore interface.
/usr/openv/netbackup/bin/jbpSA &
- Click the Restore Files tab.
- Click Actions > Specify NetBackup Machines to specify the server, source client, policy type, and destination client.
- For the Restore Type, select Point in Time Rollback.
The Browse directory field is grayed out, with root (/) as default.
Instant Recovery backups are displayed in the Backup History window, for all dates (you cannot set a range).
- Select an image from the list and click OK.
The image contents are displayed in the Directory Structure pane of the Restore Files tab.
You can select root level or mount points (file systems or volumes), but not folders or files at a lower level.
- In the Directory Structure list, click the check box next to the root node or a mount point beneath root.
You can select a file system or volume, but not lower-level components.
- Click the Restore option.
If the volume that you have selected, belongs to a storage array consistency group or volume set, you can see a list of volumes that are restored along with the selected volume, as they belong to the same array volume set or consistency group. In the open dialog,
To recover all the listed volumes, click OK.
To cancel, and select another restore method for single volume recovery, click Cancel.
For more details refer to NetBackup status code: 4311, in the NetBackup Status Codes Reference Guide
The only available destination option is Restore everything to its original location.
- For file systems, you can choose to skip file verification by placing a check in the Skip verification and force rollback option.
Warning:
Click Skip verification and force rollback only if you are sure that you want to replace all the files in the original location with the snapshot. Rollback deletes all files that were created after the creation-date of the snapshot that you restore.
If Skip verification and force rollback is not selected, NetBackup performs checks on the file system.
See Notes on rollback.
If the checks do not pass, the rollback aborts and the Task Progress tab states that rollback could not be performed because file verification failed.
- For volumes belonging to consistency group or volume set, select Force rollback even if it destroys the consistency group's state on the storage array option, to ignore any mismatch in consistency group configuration on the storage arrays during the restore. NetBackup completes the restore with warning messages.
Note:
Select this option only when it is safe to rollback all the devices on the concerned storage array consistency group.
To understand the concept of forced rollback, refer to the following examples.
The above figure shows a simple application server where the application data (/mnt1 and /mnt2) resides on five storage array devices (D1, D2, D3, D4 and D5), which are a part of storage array consistency group. Consider that your NetBackup policy is configured such that you are using VSO snapshot method and backup selection leads to /mnt1 and /mnt2. Once the snapshot is conducted, it will be conducted at consistency group level. So, now at the time of PIT Rollback Restore if you choose only /mnt1 for such a restore, you will get a warning stating partial selection. This is because of the fact that the snapshot being referred for restore has information about group snapshot consisting of devices D1, D2, D3, D4 and D5 where /mnt1 resides on D1, D2 and D3 only; and reverting back at consistency group will affect all devices in this group.
The above figure shows a simple application server where the application data (/mnt1 and /mnt2) resides on three devices (D1, D2, D3) which are part of a storage array consistency group. The consistency group is comprised of four devices (D1, D2, D3 and D4). Consider that your NetBackup policy is configured such that you are using VSO snapshot method and backup selection leads to /mnt1 and /mnt2. Once the snapshot is conducted, it will be conducted at consistency group level. So, now at the time of PIT Rollback Restore if you select both /mnt1 and /mnt2 for such a restore, the restore will fail due to mis-match of the devices. Because, the group consists of four devices whereas the devices being asked for restore are only three. Reverting back at consistency group will affect all devices in this group.
The rest of the procedure is identical to a normal restore as explained in the NetBackup Backup, Archive, and Restore Getting Started Guide and help.