Veritas NetBackup™ Commands Reference Guide
- Appendix A. NetBackup Commands
backupdbtrace — trace debug logs of backupdb (image catalog backup) jobs
[-server name] [-job_id number] [-start_time hh:mm:ss] [-end_time hh:mm:ss] mmddyy [mmddyy ...]
On UNIX systems, the directory path to this command is /usr/openv/netbackup/bin/admincmd/
On Windows systems, the directory path to this command is install_path\NetBackup\bin\admincmd\
The backupdbtrace utility consolidates the debug log messages for the specified backup database jobs and writes them to standard output. It then sorts them by time. backupdbtrace tries to compensate for time zone changes and the clock drift between remote servers and clients.
At a minimum, you must enable debug logging for the administrator on the master server and for bptm and bpbkar on the media server. For best results, set the verbose logging level to 5. Then enable the debug logging for the following in addition to the processes already identified:
bpdbm on the master server
bpcd on all servers
backupdbtrace uses the -job_id option as the sole criterion for selecting the backupdb job to trace. If -job_id is not used, then backupdbtrace selects all the backupdb jobs that started on the days that the day stamps (mmddyy) specified. Use the -start_time and -end_time options to examine the debug logs on the specified time interval.
The backupdbtrace utility writes error messages to standard error.
Name of the media server where the backupdb command is initiated. The default is the local host name.
Job ID number of the backupdb job to analyze. Default is any job ID.
Earliest timestamp to start analyzing the logs. Default is 00:00:00.
Latest timestamp to finish analyzing the logs. Default is 23:59:59.
One or more day stamps. This option identifies the log file names (log.mmddyy for UNIX, mmddyy.log for Windows) to analyze.
The following is the format of an output line:
daystamp.millisecs.program.sequence computer log_line
The day that the log is generated in yyyymmdd format.
The number of milliseconds since midnight on the local computer.
The name of the program (for example, BPBKAR) being logged.
Line number within the debug log file.
The name of the NetBackup server or client.
The line that appears in the debug log file.
Example 1 - Analyze the log of a backupdb job with job ID 5 that is run on May 6, 2013.
# backupdbtrace -job_id 5 050613
Example 2 - Analyze the log of all the backupdb jobs that were run on August 5, 2012 and August 17, 2013.
# backupdbtrace 080512 081713