Veritas NetBackup™ Vault Administrator's Guide
- About Vault
- Installing Vault
- 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 how to avoid sending duplicates over the network
- About increasing duplication throughput
- About organizing reports
- Configuring NetBackup Vault
- Configuring Vault
- About Vault configuration
- About configuring Vault Management Properties
- About creating a vault
- About creating profiles
- Configuring a profile
- 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 additional volumes
- About using notify scripts
- Creating originals or copies concurrently
- Reporting
- Administering Vault
- About administering access to Vault
- About NetBackup Vault session files
- Using the menu user interface
- Troubleshooting
- Debug logs
- Appendix A. Recovering from disasters
- Appendix B. Vault file and directory structure
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.