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 the treatment of images without a corresponding duplication rule
In some cases, the profile may list more media servers in the list on the Choose Backups tab than in the advanced configuration view on the Duplication tab.
Figure: Media servers listed on Choose Backup and Duplication tabs shows that the number of media servers that appear in the Choose Backup tab can differ from the number of media servers that appear in the Duplication tab.
Note:
More than one media server applies to NetBackup Enterprise Server only.
If this happens, images that are written by media servers that have no corresponding duplication rule must also be duplicated. Vault duplicates those images but tries to minimize total duplication time by keeping as many drives as possible busy writing data until all images are duplicated.
This situation is handled as follows:
All images that are written by media servers that have a duplication rule are assigned to the appropriate duplication rule.
As soon as one duplication rule finishes processing the images that are assigned to it, Vault begins to assign images written by other media servers (media servers that have no rule of their own) to the duplication rule that finished processing.
As other rules complete the duplication of their assigned images, they too are assigned images written by other media servers that have no rule of their own.
Eventually all images that are written by all media servers that are listed on the Choose Backups tab are duplicated and the duplication step is complete. If you have more media servers listed on the Choose Backups tab than on the Duplication tab, there is only one way to ensure that large amounts of duplication data do not get sent over the network.
Every duplication rule must specify an alternate read server. For each duplication rule, the alternate read server must be the same as the media server of the destination storage unit(s).
All alternate read servers must be connected to all robots that have images written by any media server listed on the Choose Backups tab but not on the Duplication tab.
The previous configurations are best suited for a SAN environment where all media servers are visible to all robots.