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
Alternate client backup requirements
Before you configure a policy for alternate client backup, make sure the following have been done:
The client data must be configured as required by the snapshot method. The alternate client must have access to the snapshot devices.
User and group identification numbers (UIDs and GIDs) for the files to back up must be available to the primary client and the alternate client.
The primary client and alternate client must run the same version of NetBackup. For example, the use of a later version of NetBackup on the primary client and an earlier version on the alternate client is not supported.
The primary client and alternate client must run the same operating system, volume manager, and file system. For each of these I/O system components, the alternate client must be at the same level as the primary client, or higher level.
Table: Alternate client requirements lists the supported configurations.
Table: Alternate client requirements
If primary client is: | Alternate client must be: |
---|---|
Solaris | Solaris, at same level as primary client or higher |
HP | HP, at same level as primary client or higher |
AIX | AIX, at same level as primary client or higher |
Red Hat | Red Hat, at same level as primary client or higher |
SUSE | SUSE, at same level as primary client or higher |