NetBackup™ Snapshot Client Administrator's Guide
- Introduction
- Installation
- Policy configuration
- Selecting the snapshot method
- About using alternate client backup
- Configuring alternate client backup
- Policy configuration tips
- About disabling snapshots
- NAS snapshot configuration
- Dynamic data streaming for D-NAS workloads
- Setting up a NAS-Data-Protection policy
- FlashBackup configuration
- Instant Recovery configuration
- About Instant Recovery
- About sizing the cache for Instant Recovery copy-on-write snapshots
- 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
- 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
- Snapshot management
- 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
Configuring FlashBackup policy for backward compatibility (UNIX only)
Before NetBackup 5.0, FlashBackup was a separate product with two built-in snapshot methods: snapctl driver (nbu_snap) for Solaris clients and a VxFS snap driver for HP clients. The configuration procedure for a pre-5.0 FlashBackup policy was different from the procedure in 5.0 and later, as follows:
Unless FlashBackup was combined with NetBackup 4.5 ServerFree Agent, the snapshot methods were preset to the snapctl driver (Solaris) and VxFS snap driver (HP).
The cache partition for the snapctl driver and VxFS snap driver had to be specified as a CACHE= entry in the policy's file list.
To use multiple data streams, other directives had to be added to the policy's
(file) list.
The following procedure and related topics explain how to configure a FlashBackup policy with a CACHE= entry in the policy's
list. This means of configuration is provided for backward compatibility.To configure FlashBackup policy for backward compatibility (UNIX only)
- Leave Perform snapshot backups deselected on the policy Attributes tab. NetBackup uses nbu_snap (snapctl driver) for Solaris clients or VxFS_Snapshot for HP.
- On the policy's Backup Selections tab, specify at least one cache device by means of the CACHE directive. For example:
CACHE=/dev/rdsk/c0t0d0s1
This cache partition is for storing any blocks that change in the source data while the backup is in progress. CACHE= must precede the source data entry. Note the following:
Specify the raw device, such as /dev/rdsk/c1t0d0s6. Do not specify the block device, such as /dev/dsk/c1t0d0s6.
Do not specify the actual device file name. For example, the following is not allowed:
/devices/pci@1f,0/pci@1/scsi@3/sd@1,0:d,raw
Wildcards (such as /dev/rdsk/c0*) are not allowed.
The CACHE entry must precede the entry for the source data you want to back up.
All entries in the Backup Selections list, including the source data, must be the full path name of a raw device in the form:
On Solaris: /dev/rdsk/cxtxdxsx
On HP: /dev/rdsk/cxtxdx
where x is an integer.
For multiple data streams, you can include multiple entries in the Backup Selections list.
For example:
CACHE=/dev/rdsk/c1t4d0s0 /dev/rdsk/c1t4d0s7 CACHE=/dev/rdsk/c1t4d0s1 /dev/rdsk/c1t4d0s3 /dev/rdsk/c1t4d0s4