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. NetBackup secure communication logging
  4. NetBackup web services logging
Veritas NetBackup™ Logging Reference Guide

NetBackup web services logging

The NetBackup web services logs are as follows (on the master server only):

UNIX: /usr/openv/logs/nbwebservice

Windows: install path\netbackup\logs\nbwebservice

This log directory contains the web services originator log files. They include, but are not limited to, the following log files:

Table: Web services OIDs and log files

Originator ID

Log file

Description

439

nbwebservice\nbwebservice

NetBackup Web Service

466

nbwebservice\security

NetBackup Security Service (security web app)

482

nbwebservice\hosts

NetBackup Hosts Webservice (hosts web app)

483

nbwebservice\nbconfigmgmt

NetBackup Configuration Management Service (web app)

484

nbwebservice\nbgateway

NetBackup Gateway Service (web app)

485

nbwebservice\nbwss

NetBackup WebSocket Service (NBWSS) (web app)

487

nbwebservice\nbcatalogws

NetBackup Catalog Web Service (web app)

488

nbwebservice\nbrbac

NetBackup Role-based Access Control (RBAC) Web Service (web app)

489

nbwebservice\nbadminws

NetBackup Admin Web Service (web app)

The logging for processes with originator IDs (OIDs) can be increased and decreased using the vxlogcfg command located in NetBackup\bin. This command can be used to add and remove logging for each of the previous processes. See the following examples that use OID 439:

To add logging, use the following command with the -a (add) option:

vxlogcfg -a -p NB -o 439 -s DebugLevel=6

To remove logging, use the following command with the -r (remove) option:

vxlogcfg -r -p NB -o 439 -s DebugLevel=6

If an issue can be easily or quickly reproduced, it can be easier to configure the default log file setting to 6, and then decrease it to the out-of-the-box setting of 1. See the following examples:

To increase logging, use the following command:

vxlogcfg -a -p NB -o Default -s DebugLevel=6

To decrease logging, use the following command:

vxlogcfg -a -p NB -o Default -s DebugLevel=1

Note:

In the previous examples, the -a option was added to both commands because we do not want to remove the default logging, but only change the debug level to the out-of-the-box default level.

Caution:

Always wait at least 1 full minute after changing the log file logging levels as it may take a minute for the changes to be implemented.

Do not leave a high level of logging in place for a long period of time as it can cause the file systems to fill up with logs.

If the OIDs are set to 0 by default, they are not affected when the default logging levels are changed. These OIDs are as follows:

  • 156 - NetBackup ACE/TAO; this logs to any process that needs to utilize an ACE/TAO call

  • 486 - NetBackup proxy helper; this logs to the unified nbpxyhelper log file. See NetBackup proxy helper logging.

Feedback

Was this page helpful?
Previous

Tomcat logging

Next

Command-line logging

Feedback

Was this page helpful?