Jason,

Couple of ways to find the information you're looking for.

/usr/openv/netbackup/bin/admincmd/bperror -U -media -client [clientname] -d
[yy/mm/dd hh:mm:ss] 

-d flag is start time of backup, you can also use -hoursago [# of hours].
Using the -media flag should show all media related errors on the client for
the specified time period.  You can also further narrow search by using
-jobid flag, specifying the jobid as represented in the job monitor.

If the -media flag does not give you the information you're looking for, use
-all instead.  This will provide details on all processes on the specified
client for the specified time period.

As to why you're not seeing the status 84's in the job monitor, could be a
couple of reasons for this.  One is that NetBackup will "hide" errors if the
backup is automatically relaunched on failure.  Only the exit status for the
last attempt will show in the job monitor.  You can see other attempts by
selecting the job in the activity monitor, then choosing "monitor" from the
actions menu.  Also, use the bperror command with -backstat flag instead of
-media or -all to see each failure.

You'll also want to check your /usr/openv/netbackup/db/jobs/job.conf file.
Settings here will determine how long you keep information on all backups in
the activity monitor.  Once a failure has disappeared from the activity
monitor, there is no way that I am aware of to gather information about it,
other than by sifting through the logs.  Page 349 of the UNIX
Administrator's Guide has more information.

Hope this helps.

Ken Zufall
Technical Analyst
Phone: 216.471.3613
Pager: 440.303.1656
Fax: 216.491.4051

"It's not the most intellectual job, but I do have to know all the letters."
Vanna White



                -----Original Message-----
                From:   Jason Ahrens [mailto:ahrensj AT psi DOT ca]
                Sent:   Tuesday, March 06, 2001 10:50 AM
                To:     veritas-bu AT eng.auburn DOT edu
                Subject:        [Veritas-bu] Determining bad tape

                Hello

                Over the weekend, I had a number of jobs 'fail' with status
84 "Media write
                error". I beleive this indicates a bad tape. The jukebox we
use is huge,
                containing hundreds of tapes. I cannot find any jobs in the
activity monitor
                that failed with status 84, so I cannot find out there which
tape was
                mounted to determine which was the 'bad' one. The syslog
files confirm that
                the tape was bad, showing numerous SCSI write errors.

                How can I find out which tape is bad? Media and MAster
servers are both
                Solaris 2.6.

                Thanks

                Jason

                _______________________________________________
                Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
                http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu