If You Cannot Access a Remote Server

In order to administer a server from another master server make sure that the following conditions are true:

• The destination server is operational.
• NetBackup daemons are running on both hosts.
• There is a valid network connection.
• The user has administrative privileges on the destination host.
• The current host is listed in the server list of the destination host as explained in Adding a NetBackup Server to a Server List. This is not required for a media server, client, media and device management, or device monitoring.

To ensure that the new server entry is used by all NetBackup processes that require it, stop and restart:

• The NetBackup Database Manager and NetBackup Request Manager services on the remote server if it is Windows.
• The NetBackup Database Manager (bpdbm) and NetBackup Request Manager (bprd) on the remote server if it is UNIX.
• Authentication is set up correctly, if used.
• If you have problems changing servers when configuring media or devices or monitoring devices:
• If the remote server is Windows, verify that the NetBackup Volume Manager service is running on that server and start it if necessary.
• If the remote server is UNIX, verify that the Media Manager Volume daemon is running on that server and start it if necessary.
• 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 Media Manager System Administrator's Guide for instructions.