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 to a node with directory services
To restore the quorum to a node that is either running Active Directory or that is currently a domain controller, the node must be in Directory Services Restore Mode. The cluster services cannot run in this mode. So the cluster quorum must be restored separately, after the System State or the Shadow Copy Components are restored and after the node is restarted.
To restore the cluster quorum to a node running Active Directory or that is currently a domain controller
- In the NetBackup Backup, Archive, and Restore interface, open a Restore window.
- Select the backup image (or range of images) that contains the backup you want to restore.
Exclude the cluster quorum from the restore, as follows:
Expand System_State and then deselect Cluster_Database.
Expand Shadow Copy Components > System State and then deselect Cluster_Quorum.
- Continue the restore.
- When the restore operation is complete, restart the cluster node in Safe (repair) mode. Then select Directory Services Restore Mode.
- Start the NetBackup service(s).
- Open the NetBackup Backup, Archive, and Restore interface.
Select only the cluster quorum, as follows:
Expand System_State and select only Cluster_Database.
Expand Shadow Copy Components > System State and select only Cluster_Quorum.
- If the disk where the cluster quorum previously resided is changed, you may have to 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 is complete, restart the target node.
- Use Failover Cluster Manager to restart the cluster service on any nodes where it was stopped.