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 resuming a Vault session
If a vault job fails, first consult the NetBackup Administration Console Activity Monitor or the notification of session status (the session's summary.log). If they do not provide enough information to determine the cause of the problem, examine the other log files.
See Debug logs.
After you determine the cause, you can do one of the following:
If the session reached the Eject step or attempted to generate reports before encountering problems, you can use vltopmenu (or vlteject) to finish the eject or reporting for the session.
Start a new session for your profile. If you are doing duplication, Vault does not duplicate any images it already duplicated, but it does eject those images if the profile is configured to eject. (This behavior is similar to checkpoint and restart.)