SYNOPSIS
/usr/openv/netbackup/bin/admincmd/bperror {-S | -statuscode status_code}
[-r|-recommendation] [[-p Unx | NTx]|[-platform Unx | NTx]] [-v]
/usr/openv/netbackup/bin/admincmd/bperror [-all | -problems |-media | {-backstat
[-by_statcode]}] [-L | -l | -U] [-columns ncols] [-d date | -hoursago
hours] [-e date] [-client client_name] [-server server_name] [-jobid
job_id] [-M master_server,...] [-v]
/usr/openv/netbackup/bin/admincmd/bperror [-s {severity[+]}|severity ...] [-t
type ...] [-L | -l|-U] [-columns ncols] [-d date | -hoursago hours] [-e
date] [-client client_name] [-server server_name] [-jobid job_id] [-M
master_server,...] [-v]
DESCRIPTION
bperror displays information from either the same source as the online trou-
bleshooter (in the Activity Monitor or Reports applications) or from the Net-
Backup error catalog. bperror provides the following types of displays:
· A display of the message that corresponds to a status code and, option-
ally, a recommendation on how to troubleshoot the problem. In this case,
the display results come from the same source as the online trou-
bleshooter for the local system.
· A display of the error catalog entries that satisfy the command-line
options. For instance, bperror can display all the problem entries for
the previous day.
· A display of the error catalog entries that correspond to a particular
message severity and/or message type.
For information on details of the displays, see DISPLAY FORMATS later in this
command description.
bperror writes its debug log information to the /usr/openv/netbackup/logs/admin
directory. You can use the information in this directory for troubleshooting.
The output of bperror goes to standard output.
This command can be executed by authorized users. For more information about
NetBackup authorization, refer to "Enhanced Authorization and Authentication" in
the NetBackup System Administrator's Guide.
OPTIONS
-all
-backstat [-by_statcode]
-media
-problems These options specify the type and severity of log messages to dis-
For -problems: The type is ALL, and severity is the union of WARNING,
ERROR, and CRITICAL. Running bperror with this option and -U produces
a Problems report.
-client client_name
Specifies the name of a NetBackup client. This name must be as it
appears in the NetBackup catalog. By default, bperror searches for all
clients.
-columns ncols
For the -L and -U reports, -columns provides an approximate upper
bound on the maximum line length. bperror does not attempt to produce
lines exactly ncols characters in length.
-columns does not apply to the -l report.
ncols must be at least 40. The default is 80.
-d date
-e date Specifies the start and end date range for the listing.
-d specifies a start date and time for the listing. The resulting list
shows only images in back ups or archives that occurred at or after
the specified date and time. The format of date depends on the user's
locale setting. See the NOTES section for more information. For the C
locale, the date syntax is as follows:
mm/dd/yy [hh[:mm[:ss]]]
The valid range of dates is from 01/01/1970 00:00:00 to 01/19/2038
03:14:07. The default is 24 hours before the current date and time.
The method you use to specify the date and time is dependent on the
locale setting for your system. See NOTES.
-e specifies an end date and time for the listing. The resulting list
shows only files from backups or archives that occurred at or before
the specified date and time. Use the same format as for the start
date. The default is the current date and Time. The end date must be
greater than or equal to the start date.
-help Prints a command line usage message when -help is the only option on
the command line.
-hoursago hours
Specifies a start time of this many hours ago. This is equivalent to
specifying a start time (-d) of the current time minus hours. Hours is
an integer. The default is 24, meaning a start time of 24 hours before
the current time.
tem issuing the command. If an error occurs for any master server,
processing stops at that point in the list. The default is the master
server for the system where the command is entered.
-p Unx | NTx
-platform Unx | NTx
Display the message that applies to the platform (UNIX or Windows) for
the specified status code. The default is to display the message for
the platform on which bperror is running. The -S or -statuscode option
must be specified when using this option.
-r | -recommendation
Display the recommended action for the specified status code from the
troubleshooting guide. The default is not to display the recommended
action. The -S or -statuscode option must be specified when using this
option.
-S status_code
-statuscode status_code
Display the message that corresponds to the status code. There is no
default for this option.
-s severity
-s severity+
Specifies the severity of log messages to display. The defined values
are ALL, DEBUG, INFO, WARNING, ERROR, and CRITICAL.
There are two ways to specify severity. The first way is a list of one
or more severity values. For instance, "-s INFO ERROR" displays the
messages with either severity INFO or severity ERROR. The delimiter
between the elements in the list must be a blank (" "). The second way
is a single severity value with "+" appended, meaning this severity or
greater. For instance "-s WARNING+" displays the messages with sever-
ity values WARNING, ERROR, and CRITICAL.
The default is ALL. The severity value can be in either upper or
lower case.
-server server_name
Specifies the name of a NetBackup server. This name must be as it
appears in the NetBackup catalog. The display is limited to messages
logged for this server, which also satisfy the other criteria speci-
fied by bperror options. For instance, if -server plim and -hoursago 2
are bperror options, the display contains messages logged for the
media server plim in the past two hours.
The server name must match the server name recorded in the log mes-
sages. For instance, if the logs record the server name as
plim.null.null.com, specifying -server plim will not display the logs,
type BACKSTAT or type MEDIADEV. The delimiter between the elements in
the list must be a blank (" ").
-U Report in user format. This is the report format used by NetBackup
report-generating tools such as the NetBackup-Java Reports applica-
tion.
-v Selects verbose mode. This option causes bperror to log additional
information for debugging purposes. The information goes into the Net-
Backup-administration daily debug log. This option is meaningful only
when NetBackup has debug logging enabled (/usr/openv/net-
backup/logs/admin directory defined). The default is not to be ver-
bose.
DISPLAY FORMATS
· Status code display (for example, bperror -S status_code):
bperror queries the NetBackup online troubleshooter on the local system
for the message that corresponds to the status code. bperror displays
the message text on one line and an explanation on a second line.
If -r or -recommendation is an option, bperror also queries for the trou-
bleshooting recommendation that corresponds to the status code. bperror
displays the recommendation following the status message, on one or more
lines.
· Error catalog display (for example, bperror -all; bperror -s severity):
bperror queries the NetBackup error catalog on either the local master
server or the master servers in the -M option list. The display consists
of the results returned from querying the error catalog on the master
server(s). The results are limited to catalog entries that satisfy all
the bperror options. For instance, if the bperror command line contains
options for client, start time, and end time, then bperror reports only
the jobs run for that client between the start and end times. For the
display variant that shows individual message entries from the error cat-
alog, the display can appear in long (-L), user (-U), or short (-l) for-
mat. For the display variant that categorizes by status code, the display
can appear in user (-U) format only. The display content for each of
these formats is as follows:
· Error catalog display, individual message entries, long format (for exam-
ple, bperror -media -L). This report produces several lines per log
entry, with the following contents:
Line 1: Date and time
V:NetBackup version
S:Server
C:Client
Line 3: Text (beginning of the log message text, continued on succeeding
lines if necessary)
· Error catalog display, individual message entries, user format (for exam-
ple., bperror -media -U). The user format produces a header line showing
column names, and then one or more lines per log entry, with the follow-
ing contents:
Line 1: Date and time
Server
Client
Text (beginning of the log message text, continued on succeeding lines if
necessary)
· Error catalog display, individual message entries, short format (for
example., bperror -media -l). The short format produces a single line per
log entry, with the following contents:
Line 1: Time (internal system representation)
NetBackup version
Type code (decimal)
Severity code (decimal)
Server
Job ID
Job Group ID
An unused field
Client
Who
Text (the entire log message text, with no truncation of the line length)
· Error catalog display categorized by status code. This display reports
only each unique status code, instead of listing every log entry for that
status code (for example, bperror -backstat -by_statcode -U). This pro-
duces two or more lines per status code, with the following contents:
Line 1: Status code
Text (the beginning of the log message text, continued on succeeding
lines if necessary)
Notice the month/day/year and hours:minutes:seconds requirements for the -d and
-e options. These are for a locale setting of C and can be different for other
locales.
For more information on locale, see the locale(1) man page for your system.
EXAMPLES
Example 1
Here bperror displays the error for a job that failed because the NetBackup
encryption package was not installed. Status code 9 is the NetBackup status code
for this failure. The second run of bperror displays the action recommended for
NetBackup status code 9.
bperror -d 12/23/2003 16:00:00 -e 12/23/2003 17:00:00 -t backstat -U
STATUS CLIENT POLICY SCHED SERVER TIME COMPLETED
9 plim dhcrypt user plim 12/23/2003 16:38:09
(an extension package is needed, but was not installed)
bperror -S 9 -r
an extension package is needed but was not installed
A NetBackup extension product is required in order to perform the
requested operation.
Install the required extension product.
Example 2
Here bperror reports, in User format, the problems that have occurred in the
previous 24 hours.
bperror -U -problems
TIME SERVER CLIENT - TEXT
11/23/2003 16:07:39 raisins - no storage units configured
11/23/2003 16:07:39 raisins - scheduler exiting - failed reading storage
unit database information (217)
11/23/2003 16:17:38 raisins - no storage units configured
11/23/2003 16:17:38 raisins - scheduler exiting - failed reading storage
unit database information (217)
11/23/2003 16:26:17 raisins - WARNING: NetBackup database backup is
code.
The display shows that one or more jobs for each of the clients chive, gava,
plim, and raisins completed successfully (the status code is 0). In addition,
one or more jobs for client nut failed because nut did not allow access by the
master or media server (the status code is 59).
bperror -U -backstat -by_statcode
0 the requested operation was successfully completed
chive gava plim raisins
59 access to the client was not allowed
nut
Example 4
The following example identifies and retrieves the results for a particular user
job. It first lists the log entries with job Ids other than zero. It then runs a
User-format report on the job of interest.
bperror -hoursago 2002 -L | grep 'S:' | egrep 'J\:[1-9]'
12/21/2003 17:24:14 V1 S:plim C:plim J:1 (U:0,0)
12/23/2003 16:31:04 V1 S:plim C:plim J:1 (U:0,0)
12/23/2003 16:31:06 V1 S:plim C:plim J:1 (U:0,0)
12/23/2003 16:38:04 V1 S:plim C:plim J:3 (U:0,0)
12/23/2003 16:38:07 V1 S:plim C:plim J:3 (U:0,0)
12/23/2003 16:38:08 V1 S:plim C:plim J:3 (U:0,0)
12/23/2003 16:38:09 V1 S:plim C:plim J:3 (U:0,0)
01/07/2002 13:12:31 V1 S:plim C:plim J:34 (U:0,0)
01/07/2002 13:12:36 V1 S:plim C:plim J:34 (U:0,0)
01/07/2002 13:12:40 V1 S:plim C:plim J:34 (U:0,0)
01/07/2002 13:12:41 V1 S:plim C:plim J:34 (U:0,0)
bperror -d 1/7/2002 -jobid 34 -U
TIME SERVER CLIENT - TEXT
01/07/2002 13:12:31 plim plim started backup job for client plim, policy jdhcrypt, schedule user on storage unit jdhcrypt
01/07/2002 13:12:36 plim plim begin writing backup id plim_0947272350, copy 1,fragment 1
12/23/2003 16:31:04 plim plim Media Manager terminated during mount of
media id A00000, possible media mount timeout
12/24/2003 04:31:20 plim - media id A00000 removed from Media Manager
database (manual deassign)
Example 6
The following example tallies and reports the total number of bytes backed up in
the past 24 hours.
bperror -all -hoursago 24 | grep "successfully wrote backup id" | awk
'{bytes= bytes + $20} END {print "backed up",bytes," Kbytes of data"}'
backed up 64 Kbytes of data
bperror -all -hoursago 24 | grep "successfully wrote backup id" | grep
fragment | awk '{bytes+=$20} END {printf "backed up fragmented", bytes }'
bperror -all -hoursago 24 | grep "successfully wrote backup id" | grep -v
fragment | awk '{bytes+=$18} END {printf "backed up unfragmented",
bytes}'
Example 7
The following example reports the performance, in Kbytes per second, for each of
today's backups:
bperror -all | grep Kbytes
0912013673 1 4 4 hatt 0 0 0 hatt bptm successfully wrote backup id
hat_0912013584, copy 1, fragment 1, 32256 Kbytes at 891.222 Kbytes/sec
0912014210 1 4 4 hatt 0 0 0 hatt bptm successfully wrote backup id
hat_0912014132, copy 1, fragment 1, 32256 Kbytes at 1576.848 Kbytes/sec
0912016068 1 4 4 hatt 0 0 0 hatt bptm successfully wrote backup id
hat_0912015780, copy 1, fragment 1, 603136 Kbytes at 2645.960 Kbytes/sec
Example 8
Here bperror displays the status message and the recommended action for status
code 0:
bperror -S 0 -r
/usr/openv/netbackup/db/error/log files
/usr/openv/msg/locale/netbackup/TrbMsgs
/usr/openv/msg/C/netbackup/TrbMsgs
/usr/openv/msg/.conf
COPYRIGHT
Copyright (c) 2002-2005 VERITAS Software Corporation. All rights reserved.
18 Feb 2005 bperror(1M)