Configuring a primary server or appliance primary server for server access and data collection by OpsCenter
Use the following procedures to configure a primary server or an appliance primary server for data collection by OpsCenter on Windows and UNIX. This procedure applies to both NBAC and non-NBAC primary servers.
In case of a clustered NetBackup setup, use this procedure on each node of the cluster.
You can use an alternate procedure to configure an appliance primary server for data collection by OpsCenter.
See Adding a primary server or an appliance primary server in the OpsCenter console.
To configure a primary server or appliance primary server for server access and data collection on Windows and UNIX
- Log on to the managed primary server or the appliance primary server as Administrator or root on Windows and UNIX respectively.
- Start the NetBackup Administration Console.
- Expand NetBackup Management > Host Properties > Primary Servers.
- Double-click the primary server name to view its properties. The Primary Server Properties dialog box appears.
- For a NetBackup server, select the Servers tab and then the OpsCenter servers tab from the Primary Server Properties dialog box. The OpsCenter servers tab displays all of the OpsCenter servers that can access the currently selected NetBackup primary server.
Note:
In a clustered OpsCenter setup, ensure that you add the host names of all clustered OpsCenter nodes and the virtual name in the OpsCenter Servers tab.
- To add the OpsCenter server to the server list, click Add. The Add a New Server Entry dialog box appears.
- Type the OpsCenter server name in the field and click Add to add the server to the list.
Ensure that the OpsCenter server name that you add is reachable from the NetBackup server.
- Click Close.
- In the Primary Server Properties dialog box, click OK.
- Ignore this step for primary servers on which NBAC is not configured.
If the primary server is NBAC-enabled, a bi-directional trust relationship must be established between the authentication broker of the OpsCenter server and the authentication broker(AB) of each managed NetBackup server. OpsCenter cannot monitor NetBackup servers if the trust relationship has not been set up between OpsCenter and NetBackup server (NBAC enabled).
To set up these trust relationships, use the vssat command in Veritas Product Authentication Service. Run this command from
%Program Files%\Veritas\Security\Authentication\bindirectory in Windows or INSTALL_PATH/VRTSat/bin in UNIX.On the NetBackup primary server or the appliance primary server host, run the following command:
vssat setuptrust --broker OpsCenter hostname:1556:OPSCENTER_PBXSSLServiceID --securitylevel high
where <OpsCenterABhost> is same as the host where OpsCenter server is installed. However if OpsCenter is installed in a clustered mode, then <OpscenterAB> is the host name that is provided as the remote authentication broker host during the OpsCenter installation.
Similarly, log on as Administrator or root on the OpsCenter server host and run the following command depending on your specific primary server version:
In case of NetBackup 7.6 primary server and of later versions, this is an optional step.
7.0 and 7.0.1 primary server
vssat setuptrust --broker <PrimaryServerhost:2821> --securitylevel high
7.1 or later primary server
vssat setuptrust --broker <PrimaryServerhost:13783> --securitylevel high
where <PrimaryServerhost> is the name of the primary server.
- Restart all the NetBackup services.
- Add this primary server to the OpsCenter console, so that it can be monitored.
See Adding a primary server or an appliance primary server in the OpsCenter console.