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
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.
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.
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
The NetBackup Administration Console 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.)
All host names that are listed in the Properties panel can have their host properties updated with the Host Properties user interface. The exception is the Authorization host property, which is only updated on the active node.
The "Add to All" hosts functionality is applicable only for a clustered master server and not for clustered media servers. To update Host Properties on clustered media servers, the user needs to update each node individually or select multiple nodes of the clustered media server.
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 thesetting to 6. You can also avoid this problem; set the setting to a lower value.