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 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 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
Generating reports by using the vlteject command
You can use the vlteject command with the -report option to generate reports from the command line. The following is the syntax for the command that generates all reports that are not yet generated:
vlteject -report
You also can specify a robot, vault, profile, or session for which to generate reports.
If the corresponding eject process has completed, pending reports from the selected sessions are generated and distributed. The reports are not generated again if vlteject is run again. If the ejection has not been completed, the subset of reports that do not depend on completion of eject are generated. These reports are generated again if vlteject -report is run again after eject has been completed.
The following is the format of the vlteject command:
vlteject -eject -report -preview [-profile profile_name] [-profile robot_no/vault_name/profile_name] [-robot robot_no] [-vault vault_name [-sessionid id]] [-auto y|n] [-eject_delay seconds] [-legacy]
The vlteject command resides in the following directory:
UNIX: /usr/openv/netbackup/bin
Windows: install_path\NetBackup\bin
See the NetBackup Commands Reference Guide.
To generate reports by using the vlteject command
- In a terminal window or command window, change to the directory in which the vlteject command resides.
- Run the command, using the appropriate options and parameters.
Note:
In case of non-administrative users using NBAC, a specially privileged user in Vault Operator group is authorized to run the command vlteject -report. This privileged user only can generate the reports for detail.log and session.log files, on demand.