Veritas NetBackup™ Clustered Master Server Administrator's Guide
- Introduction to NetBackup Master Server Clustering
- About NetBackup clustering
- NetBackup in a Windows Server Failover Clustering
- NetBackup in a Veritas Cluster Server on UNIX/Linux
- About preinstallation checklist for a NetBackup failover server installation on VCS on Unix\Linux
- NetBackup in a Veritas Cluster Server on Windows
- NetBackup in a Solaris Cluster
- NetBackup on HP Service Guard cluster
- NetBackup on PowerHA cluster for AIX
- Configuring NetBackup
- Operational notes
- Appendix A. NetBackup master server in a cluster using multiple interfaces
Device configuration guidelines
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 for more information on how to reset a drive and on thesetting.
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 master 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 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.