Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- About the capacity licensing model
- 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 selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
About multiple media servers with one master server
A protection domain refers collectively to the NetBackup master server, its NetBackup media servers, and its NetBackup clients. In a group of NetBackup servers, a client can have backups directed to any device on any server in the group.
Set up a NetBackup protection domain as follows:
One master server, which controls all backup scheduling.
Multiple media servers, which write the backup images to disk or removable media. They can have peripheral devices to provide additional storage.
Multiple protected NetBackup clients, which send their data to the media servers.
A common alternative strategy is to install extra peripherals on the clients that produce large amounts of data. The master server directs the data from the client to the client's peripherals, which reduces network traffic because the data does not traverse the network. This strategy also distributes the backup load between the master and the media servers.
Important factors to remember about master and media servers are as follows:
There can be only one master server in a group.
A NetBackup master server is a media server for itself but cannot be a media server for another master server.
Figure: Catalog location using multiple media servers shows where software is installed and where the NetBackup catalogs are located (by default).
Install NetBackup server software on each NetBackup server that has a peripheral that you want to include in a storage unit. The NetBackup installation program has choices for master and media server installation.
The master server is the default location for the NetBackup catalogs. The catalogs include the media and the volume database (
emm_data.db). The volume database contains the media usage information and the volume information that are used during the backups.