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™ for OpenStack Administrator's Guide
  3. Troubleshooting
  4. Important log files
  5. NetBackup for OpenStack Datamover service logs on RHOSP
NetBackup™ for OpenStack Administrator's Guide

NetBackup for OpenStack Datamover service logs on RHOSP

Following are the NetBackup for OpenStack Datamover service logs on RHOSP:

  • nbosdmapi log

    The log for the NetBackup for OpenStack Datamover API service is located on the nodes, typically controller, where the NetBackup for OpenStack Datamover API container is running under:

    /var/log/containers/nbosdmapi/nbosdmapi.log

  • nbosdm log

    The log for the NetBackup for OpenStack Datamover service is located on the nodes, typically compute, where the NetBackup for OpenStack Datamover container is running under:

    /var/log/containers/nbosdm/nbosdm.log

    In case of S3 being used in the log for the S3 Fuse plug-in that is located on the same nodes under:

    /var/log/containers/nbosdm/nbos-object-store.log

For VxMS-supported Linux file systems, VxMS logs for the incremental backups are stored at the following location: /usr/openv/netbackup/logs/vxms/

VxMS log level is defined in /usr/openv/netbackup/bp.conf file and it is configured to 3 by default.

VXMS_VERBOSE = 3

You can configure the log level from 0 to 5. Higher number results in more verbose logs.

Note:

VxMS log may take significant disk space when the log verbosity is set to high. Ensure that you clean up the VxMS log files periodically to avoid any disk space-related issues.

Table: VxMS log levels

Log level

Description

0

No logging

1

Error logging

2

Level 1 + warning messages

3

Level 2 + informative messages

4

Same as level 3.

5

Highly verbose (includes level 1) + auxiliary evidence files (.MMF, .DUMP, .XML, .RVPMEM)

Feedback

Was this page helpful?
Previous

On the NetBackup for OpenStack Nodes

Next

NetBackup for OpenStack Datamover service logs on Ansible OpenStack

Feedback

Was this page helpful?