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
Restoring the cluster quorum
The cluster quorum is backed up as part of System State or Shadow Copy Components for each node. To restore the cluster quorum, other nodes in the cluster must be offline. If you cannot take the other nodes in the cluster offline before you restore the cluster quorum, follow the instructions in the next procedure.
To force the restore of the cluster quorum when other nodes are online
- Create the following registry entry:
HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\ Config\Cluster_Database_Force_Restore
The actual registry entry must be on a single line. If required, create this registry value as data type REG_SZ with a value of YES. When this value is set, the cluster service is stopped for any nodes that are online.
- If Active Directory is running on the target server or the target server is currently a domain controller, the restore procedure is different.
To restore the cluster quorum
- If the other nodes in the cluster are online, create the registry entry as described in the previous procedure.
- In the NetBackup Backup, Archive, and Restore interface, open a Restore window.
- Select the backup image (or range of images) that contains the backup of the System State or Shadow Copy Components for this node of the cluster.
- In the All Folders pane, select System_State or Shadow Copy Components.
- If the disk where the cluster quorum previously resided is changed, set the registry entry. This action forces the restore to continue.
The disk may have been replaced with a new one. Or the disk configuration may have been changed so that the cluster quorum now resides on a different disk. In the latter case, the drive letter can remain the same for the disk that contained the cluster quorum. The drive letter can remain the same even if the configuration has changed. It can also remain the same if the disk signatures in the restore media do not match the signatures in the cluster quorum.
- Continue the restore.
- When the restore operation is complete, restart the cluster node. Or use the Failover Cluster Manager to restart the cluster service on any nodes where it was stopped.