How to access media and devices on other hosts
Note:
This topic is not applicable for NetBackup 8.1 or later versions.
Starting with NetBackup 8.1, the Volume Manager service (vmd) validates all requests from remote hosts against the primary servers and the media servers for the domain, as known to nbemm. The vm.conf entries are no longer used for this determination, and requests from hosts in other NetBackup domains are no longer allowed.
For NetBackup to access media and device management functionality on a remote NetBackup host, you may need to add a SERVER entry to the vm.conf file on the remote host.
The SERVER entries are used in the NetBackup bp.conf and vm.conf files for security. You can add the entries that allow only specific hosts to access those capabilities remotely.
If the vm.conf file on a remote host contains no SERVER entries, a host can manage media and devices on the remote host if it's added to the bp.conf file of the server you logged into. You do not need to add a SERVER entry to the vm.conf file.
If the vm.conf file on a remote host contains any SERVER entries, add a SERVER entry for the host on which the NetBackup Administration Console is running (the server you logged into) to that vm.conf file.
Assume that you have three hosts named eel, yak, and shark. You want to centralize device management on host shark and also permit each host to manage its own devices.
The following example scenario applies:
The vm.conf file on shark contains the following:
SERVER = shark
The vm.conf file on shark does not require any additional SERVER entries, because all device management for shark is performed from shark.
The vm.conf file on eel contains the following, which lets eel manage its own devices and permits shark to access them:
SERVER = eel SERVER = shark
The vm.conf file on yak contains the following, which lets yak manage its own devices and permits shark to access them:
SERVER = yak SERVER = shark