NetBackup™ Clustered Primary Server Administrator's Guide
- Introduction to NetBackup primary server clustering
- NetBackup in a Windows Server Failover Clustering
- About NetBackup on Windows Server Failover Clustering
- Installation prerequisites for NetBackup on WSFC cluster
- Installing a NetBackup failover server on WSFC cluster
- Configuring a NetBackup server on WSFC cluster
- Upgrading a NetBackup failover server on WSFC cluster
- Restoring the cluster quorum
- Restoring the cluster quorum to a node with directory services
- Preparation for disaster recovery of WSFC
- Disaster recovery of WSFC
- Recovering the entire WSFC cluster
- Recovering all shared disks
- About recovering NetBackup data on a shared disk
- NetBackup in a Veritas Cluster Server on Linux
- About NetBackup on a Veritas Cluster Server on Linux
- Installation prerequisites for NetBackup on VCS on Linux
- About preinstallation checklist for a NetBackup failover server installation on VCS on Linux
- Installing a failover NetBackup server on VCS on Linux
- Configuring a failover NetBackup server on VCS on Linux
- About adding a node to existing cluster
- Installing or upgrading NetBackup options on VCS on Linux
- Upgrading a NetBackup failover server on VCS on Linux
- NetBackup in a Veritas Cluster Server on Windows
- About NetBackup in a Veritas Cluster Server on Windows
- About NetBackup agent for VCS on Windows
- Installation prerequisites for NetBackup on VCS on Windows
- Installing a NetBackup failover server on VCS on Windows
- Configuring a NetBackup server on VCS on Windows
- Upgrading a NetBackup failover server on VCS on Windows
- Setting up a detailed monitoring script for the NetBackup server on VCS on Windows
- Enabling detailed monitoring in VCS Cluster Manager for the NetBackup server
- Disabling detailed monitoring in VCS Cluster Manager for the NetBackup server
- NetBackup on RedHat Pacemaker (PCS) on Linux
- Configuring NetBackup
- NetBackup configuration overview
- NetBackup configuration guidelines
- Device configuration guidelines
- Configuring devices
- Configuring NetBackup catalog backups in a cluster
- About configuring backup policies for a NetBackup clustered server
- What to back up
- Guidelines for backing up local disks in a cluster
- Guidelines for backing up the shared disks
- Verifying NetBackup configuration
- Configuring robotic daemons for monitoring (UNIX/Linux clusters)
- Configuring additional services (UNIX/Linux clusters)
- Configuring add-ons for monitoring (UNIX/Linux clusters)
- Configuring additional services (Windows)
- Configuring add-ons for monitoring (Windows)
- About adding license keys
- Operational notes
- Appendix A. NetBackup primary server in a cluster using multiple interfaces
Device configuration guidelines
The following are guidelines for configuring the devices for a clustered NetBackup server:
Choose the protection option, if possible. The use of persistent reserve is recommended, but take care to ensure that your hardware supports it correctly. See the NetBackup Administrator's Guide, Volume II for more information.
With this option, NetBackup can recover and use a reserved drive after a failover (if NetBackup owns the reservation). If you use SPC-2 SCSI reserve, a drive reset usually is required because the reservation owner is inoperative. Consult the NetBackup Administrator's Guide, Volume I for more information on how to reset a drive and on the setting.
Devices that are attached to one node but not to the other node are available only when the node where they are attached is online. For a NetBackup failover primary server, attach all of the devices to each node where NetBackup is installed. Use shared SCSI or Fibre Channel connections as necessary to share the devices.
For a NetBackup media server failover configuration, configure devices from the NetBackup primary server with the active node name as the NetBackup media server name.
For any tape devices that are in a robotic library, ensure that the robot drive number field is set correctly. Use the drive numbering scheme that the manufacturer of the robotic library has implemented. NetBackup considers the first drive in the robot as robot drive number 1. If the manufacturer's drive numbering scheme starts with a different number such as 0, adjust it accordingly.
Ensure that the robot numbers the failover server uses are consistent on all servers that use that robot. If the robot number that is defined on one node, does not match the number that is defined on another node, backups may fail.
When you create the storage units that reside on the cluster, select the virtual name of the failover NetBackup server for the setting.
If you choose for the media server when you create a storage unit, NetBackup selects the virtual NetBackup server when it performs any backup and restore operations.