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 for 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 VSM media
- 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 issues with Vaulting Storage migrator 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
Vault fields in bpdbjobs output
The NetBackup activity monitor utility, bpdbjobs, displays Vault jobs by default.
Table: Vault fields in bpdbjobs output shows the Vault-specific fields that you receive if you run the bpdbjobs command and use the -vault option.
Table: Vault fields in bpdbjobs output
Field | Description |
|---|---|
| The name of the robot with which the vault is associated. |
| The name of the vault under which the session is running. |
| The name of the profile that holds the configuration information for the vault session. |
| The session ID is a unique numeric value for the vault job. Session ID assignment starts at 1 the first time a vault job is run after vault has been installed. The value increments by 1 every time a new vault job runs. |
| The number of tapes to be ejected for a vault session. If the profile is configured for deferred eject, the tapes may not be ejected yet. |
| For Vault jobs, the field contains one of the following values. These values progress from the first value to the last as the Vault job progresses as follows: |
If a Vault job completes successfully (with exit status = 0), the field and the field both contain the value . If a vault job fails, the Operation field contains the operation occurring at the time the job failed.