Veritas NetBackup™ Vault™ Administrator's Guide
- About Vault
- About the Vault process
- Installing Vault
- About installing and configuring Vault on UNIX and Linux systems
- About installing and configuring Vault on Microsoft Windows systems
- Best Practices
- About preferred vaulting strategies
- About how to ensure that data is vaulted
- About not Vaulting more than necessary
- About preparing for efficient recovery
- About avoiding resource contention during duplication
- About two processes trying to use the same drive
- About load balancing
- About how to avoid sending duplicates over the network
- About increasing duplication throughput
- About organizing reports
- Configuring NetBackup for Vault
- About off-site volume pools
- About creating catalog backup schedules for Vault
- About setting master server properties for Vault
- Configuring Vault
- About Vault configuration
- About configuring Vault Management Properties
- General tab (Vault Management Properties)
- Alternate Media Server Names tab (Vault Management Properties)
- Retention Mappings tab (Vault Management Properties)
- Reports tab (Vault Management Properties)
- About creating a vault
- About creating profiles
- Configuring a profile
- Duplication tab
- Catalog backup tab (Profile dialog box)
- Eject tab (Profile dialog box)
- Reports tab (Profile dialog box)
- Vaulting and managing media
- About Vault sessions
- About monitoring a Vault session
- About the list of images to be vaulted
- About ejecting media
- About injecting media
- About using containers
- About vaulting media in containers
- About managing containers and media
- About vaulting additional volumes
- About using notify scripts
- Creating originals or copies concurrently
- About the continue or fail for concurrent copies
- About creating duplicate images concurrently
- About generating reports
- About consolidating reports
- Vault report types
- Reports for media going off site
- Reports for media coming on-site
- Inventory reports
- Administering Vault
- About administering access to Vault
- About NetBackup Vault session files
- Using the menu user interface
- Debug logs
- Appendix A. Recovering from disasters
- About disaster recovery
- 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 Choose Backups tab than in the advanced configuration view on the Duplication tab.list on the
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.
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.