Symantec NetBackup 5220 - Enabling and Disabling Vxms Logging

The following example describes how you can gather troubleshooting data for
Symantec Technical Support to analyze.
Wait for several minutes before you assume that the operation
is hung. Some operations can take quite a while to complete,
especially operations in the Activity Monitor and Reports
applications.
An application does not
respond.
Run /usr/openv/java/get_trace under the account
where you started the Java application. This script causes a
stack trace to write to the log file.
For example, if you started jnbSA from the root account, start
/usr/openv/java/get_trace as root. Or else, the
command runs without error, but fails to add the stack trace to
the debug log. This failure occurs because root is the only
account that has permission to run the command that dumps
the stack trace.
Still no response after
several minutes.
Run /usr/openv/netbackup/bin/goodies/support. Run
this script after you complete the NetBackup installation and
every time you change the NetBackup configuration.
Get data about your
configuration.
Provide the log file and the output of the support script for
analysis.
Contact Symantec
Technical Support
See “About working with log files” on page 48.
Enabling and disabling VxMS logging
The following procedures explain how to enable or disable VxMS logging from the
NetBackup Appliance Shell Menu.
Note: Due to the size of the VxMS logs, Symantec recommends that you only enable
VxMS logging when it is necessary to troubleshoot an issue. Disable VxMS logging
again when the issue is resolved.
Use the Support > Logs > GetLevel command to check your current VxMS log
setting.
57Working with log files
Enabling and disabling VxMS logging