Changes to Session Log Information for 7.0 NetBackup Vault

  • Modified Date:
  • Article ID:000002377


Beginning in NetBackup Vault 7.0, the structure of the session folders has changed slightly.    In previous releases, all session files were located in:

Unix:  /usr/openv/netbackup/vault/sessions/<vault_name>/sidXXX
Windows:  \<install_path>\netbackup\vault\sessions\<vault_name>\sidXXX

In 7.0 Vault this was changed.    The only files remaining in the sidXXX directory are the preview.list and eject.list.   There is a new folder named "logs" in the sidXXX directory which houses the remaining logs, such as the detail.log, the duplication logs and summary.log.

The report files (.rpt files) generated during a vault session have been moved.    Starting in 7.0 the .rpt files, by default, are created in /usr/openv/netbackup/logs/user_ops/vault.  They are given an arbitrary name  which is totally unrelated to the session number or vault name.  They are divided into three folders, determined by pre-eject, post-eject, and inventory.



The 7.5 Vault Administrators Guide, under 'Configuring a profile', describes it this way:

 Reports tab (Profile dialog box)
 Use the Reports tab to select which reports to generate for the profile, where to distribute them, and when to generate them (immediately when the profile runs or deferred until later).
 You and your off-site storage vendor can use the reports to determine which media should be moved between your site and the off-site storage location and the timing of the moves. Reports can be generated for one session or for multiple sessions (known as consolidating your reports and ejections).
 Note: You must specify a destination so that reports are generated.     

The reports WILL be generated but, by setting the destination path, you can control to where they are written.
If the profile Reports tab DOES NOT specify an output destination directory, you will need to locate the user_ops/vault directory names from the vault log. 
If the profile Reports tab DOES specify an output destination directory, then the .rpt files are written here and are identified with a sid value, but will contain no indication from which vault or profile the report originated.

An example:


To enhance this name, it is recommended that you add the vault and/or profile name to your destination pathname.

An example:


The results of this would then be:



Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)