NetBackup™ Clustered Primary Server Administrator's Guide
- Introduction to NetBackup primary server clustering
- NetBackup in a Windows Server Failover Clustering
- NetBackup in a Veritas Cluster Server on Linux
- About preinstallation checklist for a NetBackup failover server installation on VCS on Linux
- NetBackup in a Veritas Cluster Server on Windows
- NetBackup on RedHat Pacemaker (PCS) on Linux
- Configuring NetBackup
- Operational notes
- Appendix A. NetBackup primary server in a cluster using multiple interfaces
NetBackup configuration guidelines
Review the following guidelines before you configure NetBackup:
To ensure that all nodes in the NetBackup failover group are properly registered in the EMM database, you must failover the NetBackup Group to all nodes in the NetBackup cluster group.
The NetBackup server list must be set up correctly on each node where NetBackup is configured as a failover server. For NetBackup in a clustered environment, the virtual server name must appear first. After that name, include the node names within the NetBackup group.
For each NetBackup server that runs outside of the cluster, the server list must contain the name of each node where NetBackup can run. The list must also contain the name of the virtual server.
NetBackup depends on names to route information between participants in the backup and restore process. Therefore, the use of names must be consistent within a NetBackup configuration. Specific node names and virtual names should not be used interchangeably.
CLIENT_NAME should be set to the name of the node.
CLUSTER_NAME should be the virtual server name that is dedicated to the NetBackup Application that runs on the cluster.
When you make changes to the NetBackup configuration on the active node, be sure to apply the same changes to each node in the cluster.
NetBackup server host properties in a cluster
NetBackup obtains node information from the EMM database. Therefore, changes to the host properties only affect the nodes that are already registered in the EMM database. (You change the host properties only when you fail over to the NetBackup Group to each node.)
You can update the properties for all hosts that are listed in host properties. The exception is the Authorization host property, which is only updated on the active node.
Configuration information is stored on the shared disk and cannot be configured separately for each node. (This information includes backup policies, storage units, and the NetBackup catalog backup.) All other configuration changes must be applied by moving the NetBackup server to each node.
By default, NetBackup tries to complete a backup job two times (within a 12-hour window) before it allows the job to fail. Backup attempts may be exhausted before the failover of the NetBackup media server completes. If this situation happens, increase the
setting to 6. You can also avoid this problem; set the setting to a lower value.The
setting should be set lower to increase the likelihood that NetBackup is able to initiate all scheduled backups.The server list for each client you want to back up should contain the name of each node where NetBackup can run. This list should also contain the name of the virtual server.