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
Directives for multiple data streams
For multiple data streams, certain directives must be added to the policy's Backup Selections tab.
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 .
Note:
Only one data stream is created for each physical device on the client. You cannot include the same partition more than once in the list.
The directives that you can use in the list for a FlashBackup policy are as follows:
Each backup begins as a single stream of data. The start of the list up to the first NEW_STREAM directive (if any) is the first stream. Each NEW_STREAM entry causes NetBackup to create an additional stream or backup.
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
Example | On Solaris systems: | On HP systems: |
|---|---|---|
1 | CACHE=/dev/rdsk/c1t3d0s3 /dev/rdsk/c1t0d0s6 | CACHE=/dev/cache_group/rvol1c /dev/vol_grp/rvol1 |
2 | NEW_STREAM /dev/rdsk/c1t1d0s1 | NEW_STREAM UNSET CACHE CACHE=/dev/cache_group/rvol2c /dev/vol_grp/rvol2 |
3 | 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 |
4 | 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.