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 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
- Index
About creating duplicate images concurrently
You can create multiple duplicate backup images concurrently either by using the NetBackup Catalog node or by configuring the Duplication tab of a Vault profile. Duplication is not always possible, so you must understand when you can use duplication in NetBackup.
See Creating concurrent copies through the catalog node.
See Creating concurrent copies using the basic duplication tab.
See Creating concurrent multiple copies using the advanced duplication options.
Table: Possible circumstances for duplicating a Vault profile describes when duplication is and is not possible in NetBackup.
Table: Possible circumstances for duplicating a Vault profile
Possible to duplicate backups | Not possible to duplicate backups |
|---|---|
|
|
If you do multiplexed duplication, be aware of the following:
When you duplicate multiplexed SQL-BackTrack backups with multiplex mode enabled, it is necessary to duplicate all of the backups in the multiplexed group. This ensures that the fragment order and size are maintained in the duplicate. Otherwise, it is possible that restores from the duplicated backups will not work. A multiplexed group is a set of backups that were multiplexed together during a single multiplexing session.
When you duplicate multiplexed backups, the multiplex settings of the destination storage unit and the original schedule are ignored. However, if multiple multiplexed groups are duplicated, the grouping within each multiplexed group is maintained. This means that the duplicated groups have a multiplexing factor that is no greater than that used during the original backup.
If all backups in a multiplexed group are duplicated to a storage unit that has the same characteristics as the one where the original backup was created, the duplicated group is identical, with the following exceptions:
If end of media (EOM) is encountered on either the source media or destination media.
If any of the fragments in the source backups are zero length (which can occur if many multiplexed backups start at the same time), during duplication these zero-length fragments are removed.