Veritas NetBackup™ Vault™ Administrator's Guide
- About Vault
- About the Vault process
- Installing Vault
- About installing and configuring Vault on UNIX and Linux systems
- About installing and configuring Vault on Microsoft Windows systems
- 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 two processes trying to use the same drive
- About load balancing
- About how to avoid sending duplicates over the network
- About increasing duplication throughput
- About organizing reports
- Configuring NetBackup for Vault
- About off-site volume pools
- About creating catalog backup schedules for Vault
- About setting master server properties for Vault
- Configuring Vault
- About Vault configuration
- About configuring Vault Management Properties
- General tab (Vault Management Properties)
- Alternate Media Server Names tab (Vault Management Properties)
- Retention Mappings tab (Vault Management Properties)
- Reports tab (Vault Management Properties)
- About creating a vault
- About creating profiles
- Configuring a profile
- Duplication tab
- Catalog backup tab (Profile dialog box)
- Eject tab (Profile dialog box)
- Reports tab (Profile dialog box)
- 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 media in containers
- About managing containers and media
- About vaulting additional volumes
- About using notify scripts
- Creating originals or copies concurrently
- About the continue or fail for concurrent copies
- About creating duplicate images concurrently
- About generating reports
- About consolidating reports
- Vault report types
- Reports for media going off site
- Reports for media coming on-site
- Inventory reports
- Administering Vault
- About administering access to Vault
- About NetBackup Vault session files
- Using the menu user interface
- Debug logs
- Appendix A. Recovering from disasters
- About disaster recovery
- Appendix B. Vault file and directory structure
About NetBackup Vault session files
The directory that is generated for each vault session collects information for the session in 2 log files. The detail.log file contains a record of each action that is performed for the session. Some of the information in detail.log is also recorded in the NetBackup log files. The summary.log file contains a brief description of the vault session, and the results of the session. If email notification is enabled, the information in this file is appended to the email.
The detail.log has information about the number of images that are selected by a particular session. In addition, it should record information (during the duplication step) about the total number of images and the number of images duplicated. If these numbers do not match, it means that some images were not duplicated. The log should contain information about which images were not duplicated, either because they were duplicated in a previous session or because the duplication failed for some reason. The actual images that are selected by the session show only if a higher debug level (level 5) is used.
The session log files are located in the following path:
On a NetBackup cluster, the vault/sessions directory is present in the shared location:
On a NetBackup cluster, the vault\sessions directory is present in the shared location.
The name of the vault is vault_name and it is used for the session. The unique session identifier xxx is the identifier that Vault assigns to each vault session. The session ID starts at 1 the first time that Vault runs and increments by 1 for each new session. The session identifier for a Vault session can be found by viewing the Activity Monitor entry for that session.
By default, the session log files are created using the following naming convention, on Windows and UNIX platforms.
For Windows administrative users, the user name ALL_ADMINS gets appended in the log file name. In case of UNIX administrative users, the user name root gets appended in the log file name. For non-administrative users, only for the NBAC, with a specially privileged user in Vault_Operator group who is authorized to run vlteject -report, generates the session logs on demand. For more information on legacy logging, refer to the Legacy Logging section in NetBackup Logging Reference Guide.
Directory names are not case-sensitive on Microsoft Windows systems. Therefore, session directories are created in the same vault\sessions\vault_name directory for two or more vaults that have names difference only in the letter-case.
Table: Vault session log names describes the Vault session logs.
Table: Vault session log names
Progress information for duplication operations; generated by the -L option of the bpduplicate command.
Summary of images to be duplicated if Duplication step is configured or ejected if Eject step is configured and Duplication step is not.
Lists all images and partial images for a session.
Summary of each action that is performed for a Vault session.
Brief description of the Vault session and its results. If email notification is enabled, data in this log file is appended.