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. NetBackup™ Logging Reference Guide
  3. Using logs
  4. Logging options with the Windows Event Viewer
NetBackup™ Logging Reference Guide

Logging options with the Windows Event Viewer

You can configure a NetBackup Windows primary server to also write logging application and diagnostic messages to the Windows Event Viewer Application Event log.

For details on vxlogcfg, see the NetBackup Commands Reference Guide.

To write unified logging messages to the Windows Event Viewer for an originator

  1. Use the vxlogcfg command to set the LogToOslog value to true for the originator.

    For example:

    # vxlogcfg -a -o nbrb -p NB -s "LogToOslog=true"
  2. Restart the NetBackup services.

 

To write legacy logging messages to the Windows Event Viewer

  1. Create the eventlog file on the NetBackup primary server.
    install_path\NetBackup\db\config\eventlog
  2. Optionally, add an entry to the eventlog file. For example:
    56 255

    "56" produces a log with the messages that have a severity of warning, error, and critical (56 = 8 + 16 + 32). "255" produces a log with messages for all types (255 = 1 + 2 + 4 + 8 + 16 + 32 + 64 +128).

  3. Restart the NetBackup services.
Event log parameters

The parameters in the eventlog represent severity and type. Both parameters are specified as decimal numbers and equate to a bitmap for the values below.

Severity

  • Listed as the first parameter.

  • Controls the messages that NetBackup writes to the Application log.

  • If the file is empty, the default severity is Error (16).

  • If the file has only one parameter, it is used for the severity level.

1 = Unknown

2 = Debug

4 = Info

8 = Warning

16 = Error

32 = Critical

Type

  • Listed as the second parameter.

  • Controls the type of messages that NetBackup writes to the Application log.

  • If the file is empty, the default type is Backup Status (64).

1 = Unknown

2 = General

4 = Backup

8 = Archive

16 = Retrieve

32 = Security

64 = Backup Status

128 = Media Device

In the logs, the messages are formatted as follows:

<Severity>  <Job type>  <Job ID>  <Job group ID>  <Server>  <Client>  <Process>  <Text>

For example:

16 4 10797 1 cacao bush nbpem backup of client bush exited with status 71

Feedback

Was this page helpful?
Previous

UNIX logging with syslogd

Next

Backup process and logging

Feedback

Was this page helpful?