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
Directives for multiple data streams
The number of backups that are started depends on the directives in the Backup Selections tab.
The maximum number of concurrent backups depends on the number of available drives in the storage units and the maximum jobs parameters. An example of a maximum jobs parameter is.
Only one data stream is created for each physical device on the client. You cannot include the same partition more than once in thelist.
Note that all file paths that are listed between NEW_STREAM directives are in the same stream.
Table: Example of Backup Selections list shows a list that generates four backups:
Table: Example of Backup Selections list
On Solaris systems:
On HP systems:
NEW_STREAM UNSET CACHE CACHE=/dev/cache_group/rvol2c /dev/vol_grp/rvol2
NEW_STREAM UNSET CACHE CACHE=/dev/rdsk/c1t3d0s4 /dev/rdsk/c1t2d0s5 /dev/rdsk/c1t5d0s0
NEW_STREAM UNSET CACHE CACHE=/dev/cache_group/rvol3c /dev/vol_grp/rvol3 /dev/vol_grp/rvol3a
NEW_STREAM UNSET CACHE CACHE=/dev/rdsk/c0t2d0s3 /dev/rdsk/c1t6d0s1
NEW_STREAM UNSET CACHE CACHE=/dev/cache_group/rvol4c /dev/vol_grp/rvol4
The backup streams are issued as follows. The following items correspond in order to the numbered items inTable: Example of Backup Selections list:
The first stream is generated automatically and a backup is started for /dev/rdsk/c1t0d0s6 (Solaris) or /dev/vol_grp/rvol1 (HP). The CACHE= entry sets the cache partition to /dev/rdsk/c1t3d0s3 (Solaris) or /dev/cache_group/rvol1c (HP).
The first NEW_STREAM directive (2) starts a second stream to back up /dev/rdsk/c1t1d0s1 (Solaris) or /dev/vol_grp/rvol2 (HP). On Solaris systems, this backup uses the same cache partition. On HP systems, a different cache partition must be defined for each stream (CACHE=/dev/cache_group/rvol2c).
The second NEW_STREAM directive (3) starts a backup for /dev/rdsk/c1t2d0s5 and /dev/rdsk/c1t5d0s0 (Solaris) or /dev/vol_grp/rvol3 and /dev/vol_grp/rvol3a (HP). These two partitions are backed up serially within the stream. In addition, the UNSET CACHE directive unsets the previous cache setting and the CACHE= directive sets a new cache partition for this backup.
The last NEW_STREAM directive (4) starts a backup for /dev/rdsk/c1t6d0s1 (Solaris) or /dev/vol_grp/rvol4 (HP). Like the third stream, this one also unsets the cache directive and defines a new cache partition.
Policy-specific directives such as CACHE are passed to the client with the current stream and all subsequent streams, until the directive is redefined or unset.
If the directive is encountered again, its value is redefined.
An UNSET or UNSET_ALL directive unsets a directive that was previously defined in the list. Note the following:
UNSET unsets a policy-specific directive so it is not passed with additional streams. The directive that was unset can be defined again later in the list to be included in the current or a later stream.
UNSET_ALL has the same effect as UNSET but affects all policy-specific directives that have been defined up to this point in the list. If you use it, UNSET_ALL must appear immediately after the second or later NEW_STREAM directive.