There's probably an easier way, with a utility that automates what I'm
about to tell you, but...
/usr/openv/netbackup/logs/bptm
view log.mmddyy
You'll see the events, eg.
00:33:27 [10243] <2> bptm: INITIATING: -w -c someclient bla bla bla
<snip>
<snip>
00:36:36 [10243] <2> bptm: EXITING with status 0 <----------
10243 is the job id., now you'll have an idea when things started and
ended.
Hope this helps you.
On Mon, 19 Mar 2001 AhrensJ AT psi DOT ca wrote:
> This weekend, I had a very large number of clients fail with status 196
> (Closing window) I know what this means (the job was in the queue but not
> running yet when the backup window closed) but my questino is, how can I
> figure out why? Volume of data did not grow enough to make a 196 on so many
> clients feasable in only one week. Other options are slow network (unlikely
> at this point) or clients that were feeding data to the servers at a very
> slow rate, so chewed up all the time. My question is, how is an easy way to
> determine which clients started when, and the length of the backup for each
> client (with amount of data backed up in the time) .. I could do it manually
> with the activity monitor, but I have ~100 clients to go through for this
> check.
>
> Jason
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
--
Lou A. Costabile 416-215-2800
Bell Nexxia
--
|