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™ Deduplication Guide
  3. S3 Interface for MSDP
  4. Logging and troubleshooting
NetBackup™ Deduplication Guide

Logging and troubleshooting

S3 interface for MSDP log is saved at <storage>/log/vxs3. You can also find the errors that are related to S3 API at this location. Some errors can be found under spad/spoold.

Configuring the logging

  1. Configure the log level manually.

    Edit S3 server configuration file <storage>/etc/puredisk/s3srv.cfg

    ; None: 0; Error: 1; Warning: 2; Info: 3; Debug: 4
    
     ; @restart
    
     LogLevel=<log level>
  2. Restart the S3 server.

    systemctl restart pdde-s3srv

NGINX forwards request to the S3 server. NGINX logging is disabled by default. If you want to use it, you must enable NGINX log in S3 NGINX configuration.

Enabling NGINX logging

  1. Edit /etc/<nginx server name>/conf.d/s3srvbyo.conf.
  2. Change access and error part as follows:
            access_log <access log path> main;
    
            error_log <error log path> debug;
  3. Reload the NGINX configuration.

    systemctl reload <nginx server name>

Feedback

Was this page helpful?
Previous

Limitations in S3 interface for MSDP

Next

Best practices

Feedback

Was this page helpful?