Veritas NetBackup™ Clustered Master Server Administrator's Guide
- Introduction to NetBackup Master 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 UNIX/Linux
- About NetBackup on a Veritas Cluster Server on UNIX/Linux
- Installation prerequisites for NetBackup on VCS on UNIX/Linux
- About preinstallation checklist for a NetBackup failover server installation on VCS on Unix\Linux
- Installing a failover NetBackup server on VCS on UNIX/Linux
- Configuring a failover NetBackup server on VCS on UNIX/Linux
- About adding a node to existing cluster
- Installing or upgrading NetBackup options on VCS on UNIX/Linux
- Upgrading a NetBackup failover server on VCS on Unix/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
- About detailed monitoring for the NetBackup server
- 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 in a Solaris Cluster
- About NetBackup on Solaris Cluster
- Installation prerequisites for NetBackup on Solaris Cluster
- Preinstallation checklist for a NetBackup failover server installation on Solaris Cluster
- Installing NetBackup on Solaris Cluster
- Configuring NetBackup on Solaris Cluster
- Installing or upgrading NetBackup options on Solaris Cluster
- Upgrading a NetBackup failover server on Solaris Cluster
- Solaris Cluster commands for bringing the resource group online or offline
- 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
- General notes on clustered master server administration
- About delay in detecting of loss of connection (WSFC and VCS on Windows)
- About WSFC clusters
- About NetBackup cluster application management
- Logging information
- About the support for multiple IP addresses in NetBackup
- Log on to server using virtual name
- Increase resource offline timeout after installing or upgrading on non-Solaris UNIX clusters
- Normal error messages when upgrading clustered servers to 8.1.2
- NetBackup resource group tuning parameters for Solaris Cluster
- Appendix A. NetBackup master server in a cluster using multiple interfaces
General notes on clustered master server administration
Consider the following operational issues to consider when you use NetBackup as a failover server:
If a NetBackup server fails over and backup jobs are running, one of the following things happen:
If checkpoint restart is enabled for backup jobs for the policy, any backups that were running are resumed at the last checkpoint. Note that the schedule window must permit the job to be resumed.
If checkpoint restart is not enabled for backup jobs, any backup jobs that were running fail. These jobs show up as failed jobs in the Activity Monitor or NetBackup reports. Scheduled backup jobs are retried according to the normal retry logic. (See the and the attributes). The schedule window and so on must permit the retry of the job. After a failover occurs, the user must restart user-directed backups and manual backups.
Refer to the NetBackup Administrator's Guide, Volume I, for more information on checkpoint restart , Job retry delay, and Scheduled backup attempts.
After a failover occurs on a NetBackup failover server, it takes time for the tape devices and media servers to be reset. For example, a tape may have to be rewound before it is made available. Until the device is again ready for use, you may see errors. For example, you may see error 213 (no storage units available for use) or error 219 (the required storage unit is unavailable).
After a failover, NetBackup may change the status of a drive that is required for a backup or restore to PEND. More information is available about how to use the NetBackup Administration Console Device Monitor to resolve a pending request or action.
See the NetBackup Administrator's Guide, Volume I.
If you have the NetBackup Administration Console open when a failover occurs, you need to refresh the display. This refresh ensures that the services on the active node are displayed correctly. In the NetBackup Administration Console (from the View menu) click .
The backup and restore process is the same whether you are in a cluster or a non-cluster environment. See the NetBackup Troubleshooting Guide, for further information on backup and archive processes and on restore processes.
TIR is not supported for clustered shared drives.