Collecting from NetBackup Clusters
Regardless of your NetBackup data collection architecture—either Centralized or Distributed collection—if your Master Servers belong to a cluster, the Data Collector will communicate with the cluster to gather data from the active Master Server.
Best Practices for Collecting from NetBackup Clusters
• Install the Data Collector on both Master Servers in the cluster, but only run the collector on one of them. This enables one server to be the active node while the other server is the failover node.
• Enable the Data Collector only on the active node of the cluster.
• If a Master Server belongs to a cluster, when you add the Data Collector server via the IT Analytics Portal, enter the
NetBackup Cluster Name for the Internal Name (see
Adding or Editing NetBackup Master Servers) along with the cluster’s Virtual IP address.
Clustered NetBackup Upgrade Procedure
For Distributed NetBackup deployments only (Data Collector software is installed on each NetBackup Master Server)
Clustered NetBackup Nodes require a unique upgrade strategy in order to keep their Data Collector versions in synch:
• The active node automatically updates during the Portal upgrade process.
• The passive node requires a manual update.
To ensure that both the active and passive nodes in a clustered pair are operating with the same version of the Data Collector, take the following steps:
1. After a Portal upgrade, the Data Collector automatically updates the NetBackup Master active node to the latest aptare.jar version. This process then pushes the update to all the collectors in the policy.
2. Fail over to the passive node in order to make it the active node.
3. At the command line of the newly active node, use the downloadlib utility to manually download and update aptare.jar.
Windows: <Home>\mbs\bin\downloadlib.bat
Linux: <Home>/mbs/bin/downloadlib.sh
Note: Check with your Veritas representative to determine if anything needs to be disabled prior to taking this step on the newly active node so that the upgrade does not trigger an event.
