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 for 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 using alternate read server
An alternate read server is a server used to read a backup image originally written by a different media server.
You can avoid sending data over the network during duplication by specifying an alternate read server if the alternate read server is as follows:
Connected to the robot that has the original backups (the source volumes).
Connected to the robot that contains the destination storage units.
Note:
Alternate read servers apply to NetBackup Enterprise Server only.
Note:
If the destination storage unit is not connected to the alternate read server, you send data over the network.
Figure: Tapes written by one media server can be read by another shows non-disk images that are written by media servers A, B, C, and D and are read by the alternate read server.