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 advanced duplication
Advanced duplication lets you specify more than one duplication rule. Vault determines which media server wrote each backup image and then applies the duplication rule corresponding to that media server to that image. In this context, the media server does not have any effect other than to identify which rule to apply to each image.
Note:
Alternate read servers and multiple media servers apply to NetBackup Enterprise Server only.
If a duplication rule does not specify an alternate read server, the media server that originally wrote the backup image is used to read the original backup image during the duplication process.
Use advanced configuration only if you need to control exactly how to assign the backup images to be duplicated.
The following statements may help you understand why you should use advanced configuration:
Note:
You do not need to configure advanced options if your profile duplicates images that are backed up by a single media server.
Your robot has different types of drives or media so that you have different storage units to use as destinations for the duplication process. In this case, you may want to balance the duplication job between multiple storage units. For example, you may want to send the duplicate copies of all backup images that are written by one media server to a storage unit of one density and all backup images that are written by another media server to a storage unit of another density.
Your profile is duplicating backup images to different media servers, each writing different types of data that require different retention periods. For example, if media server A backs up your customer database and media server B backs up warehouse inventory data, you may want to keep your customer database in off-site storage for a longer period of time (a different retention) than your warehouse inventory data.
You have one media server that you need reserved for other operations. For example, you use multiple media servers for duplication but dedicate one media server for backups. For that one media server you specify an alternate read server, and you let the rest of the media servers handle their own duplication.
Note:
You do not need to configure advanced options if your profile duplicates images that are backed up by a single media server.
To avoid sending data over the network, do the following:
For each duplication rule that does not specify an alternate read server, ensure that the media server controls both the source volumes and the destination storage units.
For each duplication rule that specifies an alternate read server, ensure that
The alternate read server is connected to all robots that have backup images written by the media server specified for this rule.
The alternate read server is the same server as the media server of the destination storage unit.