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™ OpsCenter Administrator's Guide
  3. Administering OpsCenter
  4. About OpsCenter log files
  5. VxUL log files
Veritas NetBackup™ OpsCenter Administrator's Guide

VxUL log files

VxUL creates log files in a format that is standardized across all OpsCenter components. These messages use VxUL IDs (a product ID and an originator ID) that identify the component that wrote the log message.

OpsCenter components create most log messages in VxUL format.

Table: VxUL IDs used by OpsCenter components shows the originator IDs used by OpsCenter and key shared components.

Table: VxUL IDs used by OpsCenter components

VxUL originator ID

Originator name

103

Veritas Private Branch Exchange service (PBX)

132

NetBackup Service Layer (NBSL)

146

OpsCenter Agent

147

OpsCenter Web GUI

148

OpsCenter Server

423

Application log file

18

OpsCenter AT

In Windows, OpsCenter writes VxUL logs to the following directory:

INSTALL_PATH\OpsCenter\server\logs

In UNIX, OpsCenter writes VxUL logs to the following directory:

INSTALL_PATH/SYMCOpsCenterServer/logs

You can control how OpsCenter writes log files for OpsCenter Server, OpsCenter Agent, OpsCenter Web GUI, and also application log files.

The following OID values must be used for OpsCenter Server, OpsCenter Agent, OpsCenter Web GUI, and application logging.

OpsCenter Server

148

OpsCenter Agent

146

OpsCenter Web GUI

147

Application logging

423

Table: Control logging on Windows lists the commands by which you can control logging on Windows.

Table: Control logging on Windows

Control Logging

Command

To change the log directory destination (default value is

<INSTALL_PATH>\OpsCenter\server\logs)

INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe -a -p 58330 -o <OID> -s LogDirectory="<New log directory location>"

Note:

58330 is the OpsCenter product ID.

To configure the verbosity level (default value is 1)

INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe -a -p 58330 -o <OID> -s DebugLevel=1

To configure the diagnostic level (default value is 1)

INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe -a -p 58330 -o <OID> -s DiagnosticLevel=1

To configure the number of log files that are created (default value is 100)

INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe -a -p 58330 -o <OID> -s NumberOfLogFiles=100

Table: Control logging on UNIX lists the commands by which you can control logging on UNIX.

Table: Control logging on UNIX

Control logging

Command

To change the log directory destination (default value is <INSTALL_PATH>/SYMCOpsCenterServer/logs)

<INSTALL_PATH>/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o <OID> -s LogDirectory="<New log directory location>"

Note:

58330 is the OpsCenter product ID.

To configure the debug level (default value is 1)

<INSTALL_PATH>/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o <OID> -s DebugLevel=<New debug level>

To configure the diagnostic level (default value is 1)

<INSTALL_PATH>/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o <OID> -s DiagnosticLevel=<New diagnostic level>

To configure the number of log files that are created (default value is 100)

<INSTALL_PATH>/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o <OID> -s NumberOfLogFiles=<New number>

Feedback

Was this page helpful?
Previous

About OpsCenter log files

Next

OpsCenter application log files

Feedback

Was this page helpful?