Veritas NetBackup™ Vault™ Administrator's Guide
- About Vault
- Installing Vault
- Best Practices
- About best practices
- About vaulting paradigms
- About preferred vaulting strategies
- About how to ensure that data is vaulted
- About not Vaulting more than necessary
- About preparing for efficient recovery
- About media ejection recommendations
- About avoiding resource contention during duplication
- About how to avoid sending duplicates over the network
- About increasing duplication throughput
- About maximizing drive utilization during duplication
- About scratch volume pools
- About organizing reports
- About generating the lost media report regularly
- Configuring NetBackup for Vault
- Configuring Vault
- About configuring Vault
- About Vault configuration
- About configuration methods
- About configuring Vault Management Properties
- Configuring robots in Vault
- Vault Robot dialog box options
- About creating a vault
- Media access ports dialog box
- Creating retention mappings
- About creating profiles
- Creating a profile
- Configuring a profile
- Vaulting and managing media
- About Vault sessions
- About previewing a Vault session
- Stopping a Vault session
- About resuming a Vault session
- About monitoring a Vault session
- About the list of images to be vaulted
- About ejecting media
- About injecting media
- About using containers
- Assigning multiple retentions with one profile
- About vaulting additional volumes
- Revaulting unexpired media
- About tracking volumes not ejected by Vault
- Vaulting VSM media
- Vaulting non-NetBackup media managed by media Manager
- About notifying a tape operator when an eject begins
- About using notify scripts
- About clearing the media description field
- Restoring data from vaulted media
- Replacing damaged media
- Creating originals or copies concurrently
- Reporting
- Administering Vault
- About setting up email
- About administering access to Vault
- About printing Vault and profile information
- Copying a profile
- About moving a vault to a different robot
- About changing volume pools and groups
- About NetBackup Vault session files
- Operational issues with Vaulting Storage migrator files
- Operational issue with disk-only option on Duplication tab
- Operational issues with the scope of the source volume group
- Using the menu user interface
- Troubleshooting
- About troubleshooting Vault
- About printing problems
- About errors returned by the Vault session
- About media that are not ejected
- About media that is missing in robot
- Reduplicating a bad or missing duplicate tape
- About the tape drive or robot offline
- No duplicate progress message
- About stopping bpvault
- About ejecting tapes that are in use
- About tapes not removed from the MAP
- Revaulting unexpired tapes
- Debug logs
- Appendix A. Recovering from disasters
- Appendix B. Vault file and directory structure
About using advanced duplication configuration
If each media server has access to at least one unique drive in the destination robot, you can use advanced duplication to process each media server independently and concurrently. (Note: all media from a single profile are ejected from the same robot.) You can do the same thing by configuring a separate profile for each media server rather than using advanced duplication configuration. However, multiple profiles within a single vault must run consecutively, so this may not allow you sufficient bandwidth.
Note:
More than one media server applies to NetBackup Enterprise Server only.
Figure: Each media server reads and duplicates its own backup image shows that no alternate read server is used and each media server reads and duplicates its own backup images.
You should use caution when you are specifying . For example, if you specify on the Choose Backups tab of a profile and also use on the Duplication tab, create an entry for each media server on the Duplication tab advanced configuration view.
If you list more media servers on the Choose Backups tab than on the Duplication tab, Vault assigns the images that are written by media servers that are not listed in the advanced view to the first media server that finishes its duplication job. If the first available media server is across the network, a large amount of data is sent over the network.
Another possible, though less problematic, consequence is that backup images from the media servers that are not configured for duplication may be duplicated by a different media server each time the profile is run.