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 Deduplication logging
  4. Media server deduplication/pdplugin logging
Veritas NetBackup™ Logging Reference Guide

Media server deduplication/pdplugin logging

This topic describes the media server deduplication/pdplugin logging.

  • Unless you are troubleshooting the Private Branch Exchange (PBX) communication between the client direct and its media server, reduce the unnecessary CORBA/TAO to zero (0) for deduplication logging by using the following command:

    # vxlogcfg -a -p NB -o 156 -s DebugLevel=0 -s DiagnosticLevel=0

For backups:

  • Enable verbose 5 bptm on the media servers to read/write backups

  • Uncomment LOGLEVEL = 10 in the media server pd.conf file

For duplications or replications:

  • Enable verbose 5 bpdm on the media server(s) to read/write duplications

  • Uncomment LOGLEVEL = 10 in the media server pd.conf file

    Caution:

    If you enable verbosity, it can affect performance.

  • Enable trace level spad and spoold logging so that the failing duplication or replication job can be traced across bpdm/pdvfs > source spad/spoold session log > source replication.log > target spad/spoold session logs

Feedback

Was this page helpful?
Previous

Deduplication configuration logs

Next

Disk monitoring logging

Feedback

Was this page helpful?