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 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 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 alternate media server names considerations
Be aware of the following concerns associated with alternate media server names:
You must have enough drives in the specified destination storage unit to keep up with the demand for duplication. If you do not, you risk a deadlock situation.
The specified media servers must have access to the destination storage unit. If not, you risk a deadlock situation and your Vault job fails. To prevent this situation, use the criterion on the Choose Backups tab to ensure that only backups from certain media servers are selected.
If multiple duplication rules use different media server names that are part of a server name group, Vault processes only the first duplication rule. Successive rules do not get processed. Also, because the media server name for the duplication rule is expanded to include all media server names in the group, all images written by all storage units that use those media server names are processed by the first duplication rule that uses any name from the group. All images are processed, but by the first duplication rule only.
Your configuration can send data over the network, depending on the media server(s) in use.
Veritas recommends that you specify only one destination storage unit per server. If you specify more than one, you may create a problem because Vault does not have a mechanism to choose to which destination storage unit to send the duplicate images.