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
Snapshot Client restrictions
For detailed support information, refer to the following:
For a complete list of supported platforms, snapshot methods, data types, and database agents, and supported combinations of platform and snapshot methods, see NetBackup 7.x Snapshot Client Compatibility:
Further information is also available.
For the NetBackup media server or Third-Party Copy Device methods, the client disk must be either a SCSI or Fibre Channel device.
For off-host backup that uses a data mover with the nbu_snap, VxFS_Checkpoint, or VxVM snapshot methods: The NetBackup media server must have access to all the disks that make up the snapshot. The disk(s) can be connected to a SAN. For each of these snapshot methods, note the following:
: Media server requires access to the active disk and the cache disk.
: Media server requires access to the primary or an active disk.
: Access requirements depend on layout of the volume group. Media server must be able to access all disks that make up the SnapMirror volume.
Backup of an AIX 64-bit client with the NetBackup media server (data mover) method and the VxVM or VxFS_Checkpoint snapshot method may fail with NetBackup status code 11. This failure may occur if the client volumes are configured with Storage Foundation 5.0 MP3. A NetBackup message similar to the following appears in the job's Detailed Status tab:
12/09/2010 23:23:23 - Error bpbrm (pid=458874) from client p5201: ERR - bp_map_open, err 2059
This error occurs because the required VxVM libraries for 64-bit AIX are not installed in the correct location. The libraries should be installed in /opt/VRTSvxms/lib/map/aix64/.
cp /usr/lpp/VRTSvxvm/VRTSvxvm/22.214.171.124/inst_root/ opt/VRTSvxms/lib/map/aix64/* /opt/VRTSvxms/lib/map/aix64/
This issue is fixed in Storage Foundation versions starting with 5.0MP3RP3, 5.1RP1, and 5.1SP1.
For off-host backups that use the NDMP data mover option to replicate snapshots, see the NetBackup Replication Director Solutions Guide for a list of limitations.
In a clustered environment, Instant Recovery point-in-time rollback is not supported for the backups that were made with a disk array snapshot method. The disk array snapshot methods are described in the chapter titled Configuration of snapshot methods for disk arrays.
For the TimeFinder, ShadowImage, or BusinessCopy legacy snapshot methods (when you use the NetBackup media server or Third-Party Copy Device backup methods): The NetBackup clients must have access to the mirror (secondary) disk containing the snapshot of the client's data. The NetBackup clients must also be able to access the primary disk. The NetBackup media server only needs access to the mirror (secondary) disk.
For the TimeFinder, ShadowImage, or BusinessCopy legacy snapshot methods, a Volume Manager disk group must consist of disks from the same vendor.
The NetBackup media server off-host backup method does not support the clients that use client deduplication. If the client is enabled for deduplication, you must select Attributes tab.on the policy
For the NetBackup media server or Third-Party Copy Device backup method: The disk must return its SCSI serial number in response to a serial-number inquiry (serialization), or the disk must support SCSI Inquiry Page Code 83.
For alternate client backup: The user and the group identification numbers (UIDs and GIDs) for the files must be available to the primary client and the alternate backup client.
Clients must be Solaris, HP, or AIX.
Requires the use of tape or disk LUNs to send the Extended copy commands for backup.
The tape must be behind a third-party-copy-capable FC-to-SCSI router. The router must be able to intercept Extended Copy commands that are sent to the tape LUNs.