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 VMware Administrator's Guide
  3. Troubleshooting
  4. Configuring VxMS logging
NetBackup™ for VMware Administrator's Guide

Configuring VxMS logging

The following procedures describe how to configure VxMS logging for NetBackup.

Except as noted in this topic, you can also use the Logging Assistant (in the NetBackup Administration Console) to configure VxMS logging.

Note:

VxMS logging may require significant resources on the VMware backup host.

VxMS logging on a Linux backup host

To configure VxMS logging on a Linux backup host

  1. Create the VxMS log directory:

    /usr/openv/netbackup/logs/vxms

    Note:

    For logging to occur, the VxMS directory must exist.

    Note:

    If you have run the NetBackup mklogdir command, the VxMS log directory already exists.

    See NetBackup logging for VMware.

  2. Add the following to the /usr/openv/netbackup/bp.conf file:

    VXMS_VERBOSE=<numeric value of 0 or greater>

    See Table: VxMS logging levels for the available logging levels.

  3. To change the log location, enter the following in the bp.conf file:

    vxmslogdir=path to new log location

    Note:

    If the VxMS log location is changed, the Logging Assistant does not collect the logs.

VxMS logging on a Windows backup host

To configure VxMS logging on a Windows backup host

  1. Create the VxMS log directory:

    install_path\NetBackup\logs\vxms

    Note:

    For logging to occur, the VxMS folder must exist.

    Note:

    If you have run the NetBackup mklogdir.bat command, the VxMS log directory already exists.

    See NetBackup logging for VMware.

  2. In the Windows registry, create the DWORD registry entry VXMS_VERBOSE in the following location:

    HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup > CurrentVersion > Config

  3. To configure the logging level, set the numeric value of VXMS_VERBOSE to 0 or greater. Larger numbers result in more verbose logs.

    See Table: VxMS logging levels for the available logging levels.

  4. To change the log location:
    • Open regedit and go to the following location:

      HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup > CurrentVersion

    • Create the registry entry vxmslogdir with a string value (REG_SZ). For the string value, specify the full path to an existing folder.

    Note:

    You can use NTFS compression on VxMS log folders to compress the log size. The new logs are written in compressed form only.

    Note:

    If the VxMS log location is changed, the Logging Assistant does not collect the logs.

VxMS logging levels

Table: VxMS logging levels lists the VxMS logging levels.

Note:

Logging levels higher than 5 cannot be set in the Logging Assistant.

Note:

Logging levels higher than 5 should be used in very unusual cases only. At that level, the log files and metadata dumps may place significant demands on disk space and host performance.

Table: VxMS logging levels

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, VDDK logs, .xml, .rvpmem).

You can set the logging level for the VDDK messages.

6

VIX (VMware virtual machine metadata) dumps only.

7

VHD (Hyper-V virtual machine metadata) dumps only.

> 7

Full verbose + level 5 + level 6 + level 7.

Feedback

Was this page helpful?
Previous

NetBackup logging for VMware

Next

Format of the VxMS core.log and provider.log file names

Feedback

Was this page helpful?