Please enter search query.
Search <book_title>...
Veritas NetBackup™ Vault Administrator's Guide
Last Published:
2021-01-01
Product(s):
NetBackup (9.0.0.1, 9.0)
- 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 extended error codes
Vault jobs may exit with exit status values greater than 255. These values are called extended error codes because they extend beyond the standard 255 NetBackup error codes. If a vault job exits with an extended error code, the exit status that is returned to the shell is 252. NetBackup adopted the convention that the exit status 252 means that an extended error code is returned by using stderr, in the following message:
EXIT status = extended error code
The Activity Monitor displays the extended error code rather than the value 252 returned to the shell in this case.