Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ AdvancedDisk Storage Solutions Guide
  3. Toubleshooting AdvancedDisk
  4. NetBackup AdvancedDisk log files
Veritas NetBackup™ AdvancedDisk Storage Solutions Guide

NetBackup AdvancedDisk log files

You can monitor NetBackup AdvancedDisk activity and status by viewing the NetBackup log files.

Some NetBackup commands or processes write messages to their own log files. For those commands and processes, the log directories must exist so that the utility can write log messages.

See Creating NetBackup log file directories for AdvancedDisk.

Other processes use Veritas unified log (VxUL) files. Each process has a corresponding VxUL originator ID. VxUL uses a standardized name and file format for log files. To view VxUL log files, you must use the NetBackup vxlogview command.

More information about how to view and manage VxUL log files is available. See the NetBackup Logging Reference Guide:

http://www.veritas.com/docs/DOC5332

The following are the component identifiers for log messages:

  • An sts_ prefix relates to the interaction with the plug-in that writes to and reads from the storage.

  • An encrypt prefix relates to interaction with the encryption plug-in.

  • A KMSCLIB prefix relates to interaction with the NetBackup Key Management Service.

Most interaction occurs on the NetBackup media servers. Therefore, the log files on the media servers that you use for disk operations are of most interest.

Warning:

The higher the log level, the greater the affect on NetBackup performance. Use a log level of 5 (the highest) only when directed to do so by a Veritas representative. A log level of 5 is for troubleshooting only.

Specify the NetBackup log levels in the Logging host properties on the NetBackup master server. The log levels for some processes specific to certain options are set in configuration files as described in Table: NetBackup logs.

Table: NetBackup logs describes the logs.

Table: NetBackup logs

Activity

OID

Processes

Backups and restores

N/A

Messages appear in the log files for the following processes:

  • The bpbrm backup and restore manager.

  • The bpdbm database manager.

  • The bpdm disk manager.

  • The bptm tape manager for I/O operations.

The log files reside in the following directories:

  • UNIX: /usr/openv/netbackup/logs/

  • Windows:install_path\NetBackup\logs\

Backups and restores

117

The nbjm Job Manager.

Image cleanup, verification, import, and duplication

N/A

The bpdbm database manager log files.

The log files reside in the following directories:

  • UNIX: /usr/openv/netbackup/logs/bpdbm

  • Windows:install_path\NetBackup\logs\bpdbm

Device configuration

111

The nbemm process.

Device configuration

178

The Disk Service Manager process that runs in the Enterprise Media Manager (EMM) process.

Device configuration

202

The Storage Server Interface process that runs in the Remote Manager and Monitor Service. RMMS runs on media servers.

Device configuration

230

The Remote Disk Service Manager interface (RDSM) that runs in the Remote Manager and Monitor Service. RMMS runs on media servers.

Feedback

Was this page helpful?
Previous

Creating NetBackup log file directories for AdvancedDisk

Next

AdvancedDisk troubleshooting

Feedback

Was this page helpful?