This error can occur because the machine being used as the remote administration console does not have a server entry on the Master Server that allows it to perform server level operations. In some cases, when this server entry on the Master Server is already in place, name resolution issues can still cause this error.
Note: The remote administration console machine may be also be an actual Media Server, a client, or simply a standalone console machine that isn’t an active client or server otherwise.
There are 2 potential resolutions to this error. Follow them in order.
1. Place remote console machine name in the Master’s Server List
Windows Master Servers
* Open a Java or Windows Administration console and expand the Host Properties section in the left pane.
* Click Master Server in the left pane.
* In the right pane, double-click the name of the Master Server to pull up its properties.
* Within this properties screen, click to display the Servers section.
* In this Servers section, add the name of every machine that will be used as a remote administration console in the NetBackup configuration under additional servers.
* Click OK to exit the Properties screen.
* Restart NetBackup services on the Master Server when possible. Ensure that no jobs are running when this is done.
UNIX Master Servers
Edit the /usr/openv/netbackup/bp.conf file on the Master Server and ensure that there is a “SERVER=” line for any machines being used as a Console in the NetBackup Environment. The Master Server name should be the first SERVER entry in the server list, followed by an entry for whatever other Servers (such as a remote console) will connect to the Master Server.
Example bp.conf excerpt:
SERVER = NBUMASTER
SERVER = NBUMEDIA01
Then, restart NetBackup daemons on the Master Server when possible. Ensure that no jobs are running when this is done.
2. Name Resolution
Name resolution should be closely analyzed if the console’s machine name appears in the Master Server’s server list, but the Status 37 is still seen. In this case, host name comparisons are not matching.
“bpclntcmd” is a useful utility that can be run from the Master Server or from the remote console machine. It will help determine if name resolution is working properly from NetBackup’s perspective between the two hosts.
Windows command location: %install_path%\VERITAS\NetBackup\bin\
UNIX command location: /usr/openv/netbackup/bin
Switches and variations:
bpclntcmd -hn <hostname_of_masterserver>
bpclntcmd -hn <hostname_of_machine_used_for_console>
bpclntcmd -ip <ip_of_masterserver>
bpclntcmd -ip <ip_of_machine_used_for_console>
The goal of these commands is to make sure the host name is consistently seen the same way after each command. Below is an explanation of what each switch does:
-pn – The client process on the host connects to the Master Server and asks the question “Who am I?”. The second line of the output is the result. This is how the client process on the host is being seen by the Master Server.
-self – Checks how this host can be resolved. Ideally, there should be only 1 unique host name and 1 unique IP address.
-hn – Checks the given host name and returns an IP.
-ip – Checks the given IP and returns a host name.
If there is any inconsistency in the results of these commands, correct the host name to IP resolution by either editing the local hosts table or by updating the DNS database.