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
Configuring the NetBackup master server in a cluster using multiple interfaces
Perform the following steps to allow communication over an additional network interface.
To configure the NetBackup master server in a cluster using multiple interfaces
- For each additional interface, add a virtual name and IP address resource in the NetBackup cluster group.
This virtual name is the master server name the clients is referenced on their particular network.
- Configure the ANY_CLUSTER_INTERFACE parameter.
On Windows, perform the following steps.
In regedit, go to the following.
Create a new DWORD value that is called ANY_CLUSTER_INTERFACE.
Change the Value Data to 1.
- On UNIX/Linux, add the following entry to the bp.conf.
ANY_CLUSTER_INTERFACE = 1
- For example, to configure the master server in an environment with multiple network interfaces, add the following: NBUV168, NBUV192, NA168, NA192, NB168, NB192.
Add the following to the server list of the master server.
The node names of the master server, for each network interface.
The virtual name of the master server, for each network interface.
- Add the node name of each media server to the media server list on the master server.
For example, add Media168 and Media192.
- Repeat step 2 through step 6 for all nodes where the NetBackup master server is installed.
- Update the server list for all NetBackup clients.
The list must include all the possible names for the master server on their network. For example, for clients on the 168.1 network, include the server names NBUV168, NA_168, and NB_168. For clients on the 192.1 network, include the server names NBUV192, NA_192, and NB_192.