Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- nbdeployutil utility options
- Creating and viewing the licensing report
- After creating a traditional licensing report
- After creating a capacity licensing report
- Reconciling the capacity licensing report results
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- About the NetBackup Disk Configuration Utility
- Reference topics
- Host name rules
- About reading backup images with nbtar or tar32.exe
- Factors that affect backup time
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About Tape I/O commands on UNIX
How to access media and devices on other hosts
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