How to enable debug logs for NetBackup Java Administration GUI in NetBackup.

Description

This document applies to Windows systems without NetBackup Server or Client software installed.

Veritas Support may require a customer to send logs to troubleshoot issues with the JAVA Administration GUI to troubleshoot an issue. 

The NetBackup JAVA Administration GUI does not create a log file by default. Instead, it will create a Command Window showing the commands as they are executed by the GUI. Understanding how the JAVA GUI log file is created can help the process of enabling the log file.

When started, the JAVA GUI reads two values from the configuration file called setconf.bat to set the full log file path.

The base path variable is set by "NB_INSTALL_PATH".
The Log file variable path is set by "logFile"

The defaults for both variables are:

SET NB_INSTALL_PATH=C:\\Program Files\\Veritas\\NetBackup

set logFile=%NB_INSTALL_PATH%\logs\user_ops\nbjlogs\%nbjLogFileName%

The path created by the two variables would result in:

C:\Program Files\Veritas\NetBackup\logs\user_ops\nbjlogs

On Windows System running the NetBackup JAVA GUI

1.  Enable JAVA GUI Debug Levels

In the <install_path>\VERITAS\\java, modify the Debug.properties file as follows:

Remove the comments from the following lines if they exist:

printcmds=true
printCmdLines=true

Then add the following lines to the bottom of the file:

Save the file and make sure it does NOT have a .txt file extension.

2. Enable JAVA GUI Log file Location

Make a copy of the file <install_path>\Veritas\Java\setconf.bat

A) At the top of the file, locate and change the following line to remove the REM statement:

REM      SET NB_INSTALL_PATH=<netbackup install path>
to
SET NB_INSTALL_PATH= < full path to NBU java install>

Example :   

        SET NB_INSTALL_PATH=C:\\Program Files\\Veritas\\NetBackup

B) Manually create the log folder path

** Note: You must have Local Administrator rights to create the folder.

Option #1 - Use an Administrator Command Prompt

mkdir "C:\Program Files\Veritas\NetBackup\logs\user_ops\nbjlogs"

Option #2 - Use Windows Explorer to manually create the folder path.

If customers need to modify the location of the JAVA GUI logs, this can be done by changing the NB_INSTALL_PATH and/or logfile variables in the setconf.bat.

Example:

SET NB_INSTALL_PATH=D:\\VERITAS\Netbackup\Java

The path created by the updated variable would result in:

D:\Veritas\NetBackup\logs\user_ops\nbjlogs

Once the log path is created, close all instance of the JAVA GUI on the client.

The next time the console is run (using nbjava.bat) it will log to the location specified in logs with a name similar to jbp.yyyymmddhhmmss**.log where

Enable JAVA GUI Logging on the NetBackup Master

On the target master server being logged into by the Java GUI, complete the following:

 -  Increase the log file debug/verbose settings to 5.
 -  Create the following log file directories:

Start the JAVA Admininstration GUI to recreate the problem

When the problem has been recreated, collect the logs:

Master -  bpjava-msvc, bpjava-susvc 

Windows System - <install_path>\Veritas\NetBackup\logs\user_ops\jbp.yyyymmddhhmmss**.log
 

Note:  If debugging device monitor, storage unit, media management, volume pools, etc., areas of the Java console, nbsl logging should also be increased on the master server.  A recycle WILL BE REQUIRED in that case before logging increases will take effect.

To increase nbsl logging complete the following on the master server from netbackup/bin:

        vxlogcfg -a -p 51216 -o 132 -s DiagnosticLevel=6 -s DebugLevel=6

vxlogcfg -a -p 51216 -o 156 -s DiagnosticLevel=6 -s DebugLevel=6

vxlogcfg -a -p 51216 -o 137 -s DiagnosticLevel=6 -s DebugLevel=6

*** After the recreation is complete, revert the logging to default by running the following:

vxlogcfg -r -p 51216 -o 132 -s DiagnosticLevel=6 -s DebugLevel=1

vxlogcfg -r -p 51216 -o 156 -s DiagnosticLevel=6 -s DebugLevel=1

vxlogcfg -r -p 51216 -o 137 -s DiagnosticLevel=6 -s DebugLevel=1

Gather up the /usr/openv/logs/nbsl/ log files from the affected time frame in addition to other information.