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
  3. Veritas NetBackup™ Logging Reference Guide
  5. NetBackup secure communication logging
  7. Sending secure communication logs to Veritas Technical Support
Veritas NetBackup™ Logging Reference Guide

Sending secure communication logs to Veritas Technical Support

If you encounter a issue that is due to certificate deployment or secure communication, you can send a problem report and the relevant logs to Veritas Technical Support for assistance. Table: Logs to gather for secure communication issues provides a list of logs and the recommended logging levels that Veritas Technical Support may need to diagnose certain secure communication issues.

Table: Logs to gather for secure communication issues

Type of issue

Logs to gather

Java console login failure

From the master server:

  • The bpjava-msvc log at verbose 5

  • The bpjava-susvc log at verbose 5

  • The nbsl log at debug level 6

    • Enable the OIDs 156 (ACE\TAO) and 137 (NB libraries) at debug level 6. They will write to the calling process.

    • Enable the Embeddable Authentication Client (EAT) logging

  • The nbatd log (from the AT logging section)

  • vssat.log (see the vssat log)

  • The PBX log files

  • The NetBackup support utility nbsu

From the entity on which the console was started:

  • nbj or jbp log file

Starting or unexpected termination of nbwmc on the master server

All of the logs are located on the master:

  • The nbwebservice logs (see the web services logs)

  • The nbwmc logs, the webserver logs, and all of the files from the data of the issue, including any hs_err.* or *.hprof files

  • Installation log files

    • Gather an nbsu as it automatically collects the installation logs

  • The nbcert log

  • The PBX log files

Certificate deployment during installation

From the server on which the certificates cannot be deployed:

  • The nbcert log

  • Installation logs

    • Gather an nbsu as it automatically collects the installation logs

  • The nbpxyhelper log files at debug level 4 or greater

From the master server:

  • The nbcert log

  • The nbpxyhelper log files at debug level 4 or greater

Backup failures due to failure to establish a secure connection

From the problem client or media server:

  • The nbcert log

  • The nbpxyhelper log files at debug level 4 or greater

From the master or media server rejecting the connection:

  • The nbpxyhelper log files at debug level 4 or greater

  • Any process logs that are involved in the communication, such as bprd, bptm, and bpbrm.

From the master:

  • The job details

Note:

Ensure that cURL logging is enabled.

Disaster recovery (DR) package creation during catalog backup

From the master server:

  • The bpdbm log at verbose 5

Web server tunnel (media) or web server router (client)

From the media server acting as the tunnel:

  • The nbpxytnl log files at debug level 6

  • The nbpxyhelper log files at debug level 4 or greater

From the client/router:

  • The nbcert log file

  • The bpcd log file

  • The nbproxyhelper log files at debug level 4 or greater

From the master server:

  • The nbproxyhelper log files at debug level 4 or greater.

Note:

Ensure that cURL logging is enabled.

Feedback

Was this page helpful?
Previous

PBX logging

Next

Snapshot technologies

Feedback

Was this page helpful?