Veritas NetBackup™ Snapshot Client Administrator's Guide
- Introduction
- Snapshot Client features
- About snapshot basics
- Off-host backup overview
- Off-host backup methods
- Snapshot Client requirements
- Installation
- 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
- 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
- Notes on Media Server and Third-Party Copy methods
- Backup and restore procedures
- About restores from a FlashBackup backup
- Instant Recovery restore features
- About configurations for restore
- About restoring from a disk snapshot
- 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
- Appendix C. NetBackup integration with CloudPoint for snapshot managment
Backup Selections tab options when configuring a policy
Note the following about the options on the Backup Selections tab:
Snapshot Client policies do not support the ALL_LOCAL_DRIVES entry in the
list (except for the VMware and Hyper-V snapshot methods).For snapshots, the maximum pathname length is approximately 1000 characters (as opposed to 1023 characters for backups that do not use a snapshot method).
The NetBackup Administrator's Guide, Volume I, describes other file-path rules.
When you configure a snapshot method in a MS-Windows policy, the backward slash (\) must be entered in the Backup Selections list after the drive letter.
If the backward slash is not included, the snapshot image does not appear in the NetBackup catalog.
Wildcards are permitted if the wildcard does not correspond to a mount point or a mount point does not follow the wildcard in the path.
Note:
This is applicable to a Storage Lifecycle Policy that has snapshot as the first operation and does not contain any backup or replicate operation.
For example, in the path /a/b, if /a is a mounted file system or volume, and /a/b designates a subdirectory in that file system: the entry /a/b/*.pdf causes NetBackup to make a snapshot of the /a file system and to back up all pdf files in the /a/b directory. But, with an entry of /* or /*/b, the backup may fail or have unpredictable results, because the wildcard corresponds to the mount point /a. Do not use a wildcard to represent all or part of a mount point.
In another example, /a is a mounted file system which contains another mounted file system at /a/b/c (where c designates a second mount point). A Backup Selections entry of /a/*/c may fail or have unpredictable results, because a mount point follows the wildcard in the path.
Information is available on the
policy attribute.See Snapshot tips.
For a raw partition backup of a UNIX client, specify the /rdsk path, not the /dsk path. You can specify the disk partition (except on AIX) or a VxVM volume.
Examples:
On Solaris:
/dev/rdsk/c0t0d0s1 /dev/vx/rdsk/volgrp1/vol1
On HP:
/dev/rdsk/c1t0d0 /dev/vx/rdsk/volgrp1/vol1
On AIX and Linux:
/dev/vx/rdsk/volgrp1/vol1
On Linux:
/dev/sdc1
On AIX clients, backing up a native disk partition is not supported. A raw partition backup must specify a VxVM volume, such as /dev/vx/rdsk/volgrp1/vol1.
Note that /dev/vx/dsk/volgrp1/vol1 (without the "r" in /rdsk) does not work.
More Information