Name
duplicatetrace — trace debug logs for duplicate job(s)
SYNOPSIS
[-master_server name] -job_id number [-start_time hh:mm:ss] [-end_time hh:mm:ss] mmddyy [mmddyy ...]
[-master_server name] -backup_id id [-start_time hh:mm:ss] [-end_time hh:mm:ss] mmddyy [mmddyy ...]
[-master_server name] [-policy_name name] [-client_name name] [-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\
DESCRIPTION
duplicatetrace consolidates the debug logs for duplicate jobs and writes them to standard output. The messages sort by time. It tries to compensate for time zone changes and clock drift between remote servers and clients.
At a minimum, you must enable debug logging for bptm and bpdm on the media server and for the following directory on the master server:
UNIX systems:
/usr/openv/netbackup/admin
Windows systems:
install_path\NetBackup\admin
For best results, set the verbose logging level to 5. Enable debug logging for bpdbm on the master server and bpcd on all servers, clients, and the processes that are already identified.
duplicatetrace uses the -job_id or -backup_id option as the sole criteria for selecting the duplicate jobs it traces. The -policy_name option or the -client_name option cannot be used with -job_id or -backup_id. If neither option is specified, then all duplicate jobs that match the selection criteria are selected. If none of the following options are specified, all the duplicate jobs that are activated on the days that day stamps (mmddyy) specify are traced: -job_id, -backup_id, -policy_name, or -client_name. If -start_time and -end_time options are used, then the debug logs that reside in the specified time interval are examined.
If duplicatetrace starts with -backup_id bid, it looks for the duplicate jobs that bpduplicate started with -backup_id bid where the backup IDs (bid) match.
duplicatetrace -policy_name policy looks for the duplicate jobs that it started with the -policy policy option, where the policy names match.
duplicatetrace -client_name client looks for the duplicate jobs that it started with the -client option where the client names (client) match.
duplicatetrace writes error messages to standard error.
You must have administrator privileges to run this command.
OPTIONS
- -master_server
Name of the master server. Default is the local host name.
- -job_id
Job ID number of the duplicate job to analyze. Default is any job ID.
- -backup_id
Backup ID number of the backup image that the duplicate job uses to analyze duplicates. Default is any backup ID.
- -policy_name
Policy name of the duplicate jobs to analyze. Default is any policy.
- -client_name
Client name of the duplicate jobs to analyze. Default is any client.
- -start_time
Specifies the earliest timestamp to start analyzing the logs. Default is 00:00:00.
- -end_time
Specifies the latest timestamp to finish analyzing the logs. Default is 23:59:59.
- mmddyy
One or more "day stamps". This option identifies the log file names (log.mmddyy for UNIX, mmddyy.log for Windows) that is analyzed.
OUTPUT FORMAT
The format of an output line is: daystamp.millisecs.program.sequence machine log_line
- daystamp
The day of the log that is displayed in yyyymmdd format.
- millisecs
The number of milliseconds since midnight on the local computer.
- program
The name of program (ADMIN, BPTM, BPCD, etc.) being logged.
- sequence
Line number within the debug log file.
- machine
The name of the NetBackup server or client.
- log_line
The line that appears in the debug log file.
EXAMPLES
Example 1 - Analyze the log of duplicate job with job ID 3 activated on May 1, 2010.
# duplicatetrace -job_id 3 050110
Example 2 - Analyze the log of duplicate jobs that duplicate backup image with backup ID pride_1028666945 executed on May 20, 2010. It analyzes only those jobs that were activated with option -backupid pride_1028666945.
# duplicatetrace -backup_id pride_1028666945 052010
Example 3 - Analyze the log of duplicate jobs that are activated on policy Pride-Standard and client pride on May 1, 2010 and May 3, 2010. It analyzes only the duplicate jobs that were activated with options -policy Pride-Standard and -client pride.
# duplicatetrace -policy_name Pride-Standard -client_name pride 050110 050310
Example 4 - Analyze the log of all duplicate jobs that are activated on August 5, 2010 and August 23, 2010.
duplicatetrace 080510 082310