Log setup for NBAC issues

Log setup for NBAC issues

Article: 100038301
Last Published: 2013-12-23
Ratings: 0 0
Product(s): NetBackup

Description

The following logs may be required when troubleshooting NBAC issues.

1. admin, bprd, bpcd legacy logs

Location of log files:
UNIX:   /usr/openv/netbackup/logs
Windows:   %INSTALL_PATH \netbackup\logs

How to change logging level:
UNIX:   change VERBOSE property filed in Host Properties > Logging or VERBOSE entry in bp.conf 
Windows:   change VERBOSE property filed in Host Properties > Logging 

2. nbatd unified logs

Location of log files:
UNIX:   /usr/openv/logs/nbatd
Windows:   %INSTALL_PATH \NetBackup\logs\nbatd 
             

How to change debug level:
UNIX:   vxlogcfg -a -p 51216 -o 18 -s DebugLevel=<0-6> 
Windows:   vxlogcfg -a -p 51216 -o 18 -s DebugLevel=<0-6>

3. Authentication Service log

Use the following command to set the location and log level:

UNIX:   /usr/openv/netbackup/se/at/bin/vssat setloglevel -l <0-4> -f <filename>
Windows:   %INSTALL_PATH\netbackup\sec\at\bin\vssat.exe setloglevel -l <0-4> -f <filename>

e.g.)
vssat setloglevel -l 4 -f /export/home/at_log.txt (on UNIX)
vssat setloglevel -l 4 -f E:\NBAC_Logs\at_log.txt (on Windows)
 
4. Authorization Service logs

Location of log files:
UNIX:   /usr/openv/netbackup/logs/nbazd/debug/vxazd_debug.log, 
            /usr/openv/netbackup/logs/nbazd/vxazd.log
Windows:   %INSTALL_PATH \NetBackup\logs\nbazd\debug\vxazd_debug.log, 
                 %INSTALL_PATH \NetBackup\logs\nbazd\vxazd.log

How to change debug level:
Open VRTSaz.conf and change the number of "DebugLevel"=, the number should be 0 to 4.
The location of VRTSaz.conf is as follows.
UNIX:   /usr/openv/netbackup/sec/az/bin
Windows:   %INSTALL_PATH\netbackup\sec\az\bin

e.g.) 
VRTSaz.conf appears as follows.
On UNIX
[Security]
[Security\Authorization]
"InstallDir"="/usr/openv/netbackup/sec/az"
"DebugLevel"="0"   →  change to "DebugLevel"="4"

On Windows
[Security]
[Security\Authorization]
"InstallDir"="C:\Program Files\Veritas\NetBackup\sec\az"
"DebugLevel"="0"   →  change to "DebugLevel"="4"

5. AT Client Side Debugging

Client side debugging/logging can be turned on as follows:

On UNIX
In Bourne or Korn shell,

$ AtClientDebugLog=4:<log file>
$ export AtClientDebugLog
In C shell,
$ setenv AtClientDebugLog 4:<log file>

On Windows
set AtClientDebugLog=4:<log file>

Two more environment variables generate debug output from the shared library 
loader module. They can be turned on as shown below:

On UNIX
In Bourne or Korn shell,

$ VRTSat_API_DEBUG_LEVEL=4
$ VRTSat_API_DEBUG_FILE=<log file>
$ export VRTSat_API_DEBUG_LEVEL
$ export VRTSat_API_DEBUG_FILE
In C Shell,
$ setenv VRTSat_API_DEBUG_LEVEL=4
$ setenv VRTSat_API_DEBUG_FILE=<log file>

On Windows
set VRTSat_API_DEBUG_LEVEL=4
set VRTSat_API_DEBUG_FILE=<log file> 

 

Note for Choosing Log/Debug Levels  3,4,5.

The log/debug levels are as follows. To stop logging/debugging messages, choose "0".
■ 0 - No logging
■ 1 - Log errors
■ 2 - Log warnings
■ 3 - Log debug messages
■ 4 - Log Info messages

Was this content helpful?