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:
UNIX
/usr/openv/netbackup/vault/sessions/vault_name/sidxxx
/usr/openv/netbackup/vault/sessions/vault_name/sidxxx/logs
On a NetBackup cluster, the vault/sessions directory is present in the shared location:
Example: /opt/VRTSnbu/netbackup/vault/sessions/vault_name/sidxxx/
Windows
install_path\NetBackup\vault\sessions\vault_name\sidxxx
On a NetBackup cluster, the vault\sessions directory is present in the shared location.
Example: <shared-path>\NetBackup\vault\sessions\vault_name\sidxxx\
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.
/usr/openv/netbackup/logs/vault/<vault>/<session-id>/logs/<username>.detail.log
/usr/openv/netbackup/logs/vault/<vault>/<session-id>/logs/<username>.session.log
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.
Note:
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
Name | Purpose |
|---|---|
duplicate.log.nn | Progress information for duplication operations; generated by the -L option of the bpduplicate command. |
preview.list | Summary of images to be duplicated if Duplication step is configured or ejected if Eject step is configured and Duplication step is not. |
image.list | Lists all images and partial images for a session. |
detail.log | Summary of each action that is performed for a Vault session. |
summary.log | Brief description of the Vault session and its results. If email notification is enabled, data in this log file is appended. |