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™ Logging Reference Guide
  3. Using logs
  4. About global logging levels
Veritas NetBackup™ Logging Reference Guide

About global logging levels

Global logging levels refer to unified logging and legacy logging. The logging level determines how much information is included in the log message. The higher the level number, the greater the amount of detail is in the log messages.

Table: Global logging levels describes all of the logging levels and the details that are included in each level.

Table: Global logging levels

Logging level

Description

Minimum logging

Includes very important, low-volume diagnostic messages and debug messages.

The Host Properties Logging page or the Logging Assistant can set minimum logging.

Legacy logs use the following values to represent minimum logging:

  • Windows: Registry displays the following hexadecimal value: 0xffffffff

  • UNIX: The bp.conf file displays VERBOSE = 0 (global). processname_VERBOSE = 0 represents using the global default for an individual process.

    If the global VERBOSE value is set to a value other than 0, an individual process can be decreased by using the value -1. For example, processname_VERBOSE = -1.

Unified logging uses the value 1 to represent minimum logging.

Disable logging

The Host Properties Logging page or the Logging Assistant can set disable logging.

Legacy logs use the following values to represent disabled logging:

  • UNIX: The bp.conf file displays VERBOSE=-2 (global) or processname_VERBOSE = -2 for an individual process.

  • Windows: Registry displays the following hexadecimal value: 0xfffffffe

Unified logging uses the value 0 to represent disabled logging.

1

Adds verbose diagnostic messages and debug messages to the low-volume diagnostic messages that are associated with minimum logging.

2

Adds the progress messages.

3

Adds the informational dumps.

4

Adds the function entry and exits.

5

Includes everything. The finest detail of messages.

Unified logging is enabled by default to log debug messages at level 0 and application messages at level 5.

The following actions affect logging levels:

  • In the Global logging level list, a zero (0) level specifies the minimum level of logging for both legacy and unified logging. However, for diagnostic and debug messages in unified logging, the logging level can be turned off completely. No diagnostic messages or debug messages are logged. This level cannot be set with the Global logging level list in the NetBackup Administration Console. You can set it with the vxlogcfg command or the Logging Assistant.

    See Changing the logging level.

    See Examples of using vxlogcfg to configure unified logs.

  • A change to the Global logging level list affects the logging level of all NetBackup and Enterprise Media Manager (EMM) processes on the server or client. (The exceptions are PBX and media and device management logging.) This setting overrides any previous settings.

  • If you make a change to the VERBOSE entry (or entries) in the bp.conf file or entry in the vm.conf file, it only affects the legacy logging.

    See How to control the amount of information written to legacy logging files.

  • If you make a change with the vxlogcfg command, it only affects the unified logging level.

A change to the Global logging level list does not affect the level of the following logging processes:

  • PBX logging

    See the NetBackup Troubleshooting Guide for more information on how to access the PBX logs.

  • Media and device management logging (vmd, ltid, avrd, robotic daemons, media manager commands)

    See Directory names for legacy debug logs for media and device management.

  • Any unified logging process whose debug level has been changed from the default setting

Feedback

Was this page helpful?
Previous

Configuring the legacy log rotation

Next

Changing the logging level

Feedback

Was this page helpful?