For a given issue, it may be necessary to gather multiple logs. This MUST cover the time the issue happens.
If an additional log is required, that has to be created, then ALL the logs must be supplied again.
There are two types of logs in NetBackup. Legacy logs and VX logs.
1) Creating Legacy Logs
2) Setting Verbose Level for Legacy Logs
3) Collecting Legacy Logs
4) Creating VX Logs and setting the log level
5) Collecting VX logs
6) Volmgr Logs
1) Creating Legacy Logs
************************
These are created in either
Unix
/usr/openv/netbackup/logs/
/usr/openv/volmgr/debug/
Windows
<install path>veritas etbackuplogs
<install path>veritasvolmgrdebug
For example to create bptm log, simply create a directory called the <process> name.
mkdir /usr/openv/netbackup/logs/bptm
A newly created log will not log anything /detect a change of verbose level until the process is restarted. For logs such as bptm, this will be when the next backup runs. Other logs such as bprm and bpdm may require a restart of the NBU services. I say 'may', if the process starts a child process, then this would write to a newly created log or pick up a verbose level change.
2) Setting Verbose Level for Legacy Logs
****************************************
There are two ways this can be done :
(Unix)
To increase the verbose level of all logs (except vault)
Add the entry VERBOSE = <level> into /usr/openv/netbackup/bp.conf. <level> is a value between 0 and 5, with 5 being the highest.
(Windows)
On the server you are gathering the logs from, run the BAR GUI
From the File menu, select Client Properties and in the pop-up window, goto the Troubleshooting tab.
Set General to 2 and Verbose to 5
3) Collecting Legacy Logs
*************************
The log file is simply found in the <process> name directory. There is one log per day.
The name of the log file will be log.<date>
If you are sending multiple log files in, they will all have the same name. Please therefore rename the log files to :
<process>.log.<date>
4) Creating VX Logs and setting the log level
**********************************************
These are more complex, and have to be set with specific commands. NOTE: Some of these logs, for example, 'mds' do NOT create a log file. Instead the lines are entered in to other log files. In the case of mds (143), it logs into EMM (111).
The vxlogs cover various processes, for example, nbemm, nbrb, nbjm, nbrb, mds
To set these up on either Unix or Windows, use this command :
vxlogcfg -a -p 51216 -o <oid> -s DebugLevel=<1-6> -s DiagnosticLevel=<1-6>
For example, to set the EMM and MDS logs to levels 6 and 6 use
vxlogcfg -a -p 51216 -o 111 -s DebugLevel=6 -s DiagnosticLevel=6
vxlogcfg -a -p 51216 -o 143 -s DebugLevel=6 -s DiagnosticLevel=6
To confirm the log level has been set, simply look in the nblog.conf file, which is located in the netbackup diorectory.
(NOTE: DO NOT EDIT THIS FILE MANUALLY)
5) Collecting VX Logs
*********************
To collect the vx logs, use the nbcplogs command. This copies the raw logs, which is the preference of Technical Support.
NOTE: The destination directory MUST be empty.
nbcplogs --no-nbsu -d 2hrs --logs nbemm,nbjm /tmp/logs (Ex. Coleect the past 2 hrs of logs, RELATIVE, to when the command is run )
nbcplogs --no-nbsu -s 07/11/2012-10:17:58 -e 07/11/2012-12:17:58 --logs nbjm,nbpem /tmp/logs (Collect the logs between two times -s <start> -e <end> )
In these examples, the nbpem and nbjm logs would be copied to /tmp/logs
For details of using vxlogview please see TN: http://www.symantec.com/docs/TECH75805
6) Volmgr Debug Logs
********************
These are very similar to legacy logs, the difference being the location and the verbose setting.
There is no value for verbose level, simply it is turned up by adding the work VERBOSE to a line in the vm.conf file.
To turn on Media Manager logging:
UNIX:
Add VERBOSE to the /usr/openv/volmgr/vm.conf file. If this file does not exist, just create it.
If necessary, create the directory /usr/openv/volmgr/debug
mkdir /usr/openv/volmgr/debug/acssi
mkdir /usr/openv/volmgr/debug/acsd
mkdir /usr/openv/volmgr/debug/robots
mkdir /usr/openv/volmgr/debug/daemon
mkdir /usr/openv/volmgr/debug/ltid
mkdir /usr/openv/volmgr/debug/oprd
mkdir /usr/openv/volmgr/debug/reqlib
mkdir /usr/openv/volmgr/debug/tpcommand
The following empty files increase the details logged further
touch /usr/openv/volmgr/DRIVE_DEBUG
touch /usr/openv/volmgr/ROBOT_DEBUG
touch /usr/openv/volmgr/AVRD_DEBUG
touch /usr/openv/volmgr/SSO_DEBUG
Restart ltid :
/usr/openv/volmgr/bin/stopltid
/usr/openv/volmgr/bin/ltid -v
Windows:
Add VERBOSE to the <install path>veritasvolmgrvm.conf file. If this file does not exist, just create it.
If necessary, create the directory /usr/openv/volmgr/debug
<install path>veritasvolmgrdebug/acssi
<install path>veritasvolmgrdebug/acsd
<install path>veritasvolmgrdebug/robots
<install path>veritasvolmgrdebug/daemon
<install path>veritasvolmgrdebug/ltid
<install path>veritasvolmgrdebug/oprd
<install path>veritasvolmgr eqlib
<install path>veritasvolmgrdebug pcommand
Create the following empty files to increase the details logged further
Ensure that windows does not craete a 'suffix', for example .txt
<install path>veritasvolmgrDRIVE_DEBUG
<install path>veritasvolmgrROBOT_DEBUG
<install path>veritasvolmgrAVRD_DEBUG
<install path>veritasvolmgrSSO_DEBUG
Restart ltid :
<install path>veritasvolmgrin/stopltid
<install path>veritasvolmgrin/ltid -v
NOTE:
The 'OIDs' for the Unified /VX logs can be determined by looking in the nblog.conf file in the /usr/openv/netbackup directory. Be careful not to edit the file.
The default logs levels for the Unified /VX log levels can be found in the nblog.conf. These are set as follows:
NetBackup Server : Default.DiagnosticLevel=6 / Default.DebugLevel=1
NetBackup Appliance : Default.DiagnosticLevel=6 / Default.DebugLevel=5