Troubleshooting remote server administration
To administer a server from another master server, make sure that the following conditions are met:
NetBackup daemons are running on both hosts.
The network connection is valid.
The user has administrative privileges on the destination host.
To perform a Change Server operation, all servers should be at the same version.
The current host is listed in the server list of the destination host.
See Allow access to another server.
The host does not need to be listed if the host is a media server or a client. Or, it does not need to be listed if only media and device management or monitoring is to take place.
If you change the master server list, stop and restart the NetBackup Database Manager (bpdbm) and NetBackup Request Daemon (bprd) to ensure that all appropriate NetBackup processes use the new server entry.
Authentication is set up correctly, if used.
To perform a Change Server operation to a media server or client, the media server or client must have a security certificate installed.
For problems changing servers to configure media or devices or monitor devices, verify that the NetBackup Volume Manager is running on that server.
If you cannot access devices on the remote host, it may be necessary to add a SERVER entry to the vm.conf file on that host.
See the NetBackup Administrator's Guide, Volume II for instructions.
If you cannot start or stop processes or services through the Activity Monitor, verify the following:
The remote server is a Windows system. Only on other Windows systems can processes be monitored and controlled.
You have the required permissions on the remote server. Windows security must allow access to the user that is running the Activity Monitor.