[Veritas-bu] Reporting on jobs that are in process or queued
2003-01-22 18:41:30
This is a multipart message in MIME format.
--=_alternative 00821B9E86256CB6_=
Content-Type: text/plain; charset="us-ascii"
c:\program files\veritas\netbackup\bin\admincmd\bpdbjobs.exe
use the report and grep (either find or findstr on windows if you don't
have grep) for what you want, or it may just be easier to use the -summary
option and look at that.
- Scott
"Glancey, John [NCSUS - NON J&J]" <JGlancey AT cntus.jnj DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
01/22/2003 08:32 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
cc:
Subject: [Veritas-bu] Reporting on jobs that are in process or
queued
I have NetBackup generate a report in the morning of all the jobs that ran
the prior evening (bperror -U -backstat -hoursago 24) and their status and
this is emailed via blat to all of the operators and engineers. However,
we had occasion where a job will hang, etc. and that does not appear on
the report. If no one happens to look at NetBackup during the day and it
is still hung, all of the next nights backups fail.
Does anyone have any good ideas on how to report on jobs that are queued
or running and how long they have been running?
NBU 3.41_2 running on Win2000 Server.
John Glancey
jglancey AT cntus.jnj DOT com
--=_alternative 00821B9E86256CB6_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="Arial">c:\program
files\veritas\netbackup\bin\admincmd\bpdbjobs.exe</font>
<br>
<br><font size=2 face="Arial">use the report and grep (either find or findstr
on windows if you don't have grep) for what you want, or it may just be easier
to use the -summary option and look at that.</font>
<br>
<br>
<br><font size=2 face="Arial">- Scott</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Glancey, John [NCSUS - NON
J&J]" <JGlancey AT cntus.jnj DOT com></b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">01/22/2003 08:32 AM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
veritas-bu AT mailman.eng.auburn DOT edu</font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
[Veritas-bu] Reporting on jobs that are in process or
queued</font></table>
<br>
<br>
<br><font size=2 face="Arial">I have NetBackup generate a report in the morning
of all the jobs that ran the prior evening (bperror -U -backstat -hoursago 24)
and their status and this is emailed via blat to all of the operators and
engineers. However, we had occasion where a job will hang, etc. and that
does not appear on the report. If no one happens to look at NetBackup
during the day and it is still hung, all of the next nights backups fail.</font>
<p><font size=2 face="Arial">Does anyone have any good ideas on how to report
on jobs that are queued or running and how long they have been running?</font>
<p><font size=2 face="Arial">NBU 3.41_2 running on Win2000 Server.</font><font
size=3 face="Times New Roman"> </font>
<p><font size=2 face="Arial">John Glancey</font><font size=3 face="Times New
Roman"> </font><font size=2 face="Arial"><br>
jglancey AT cntus.jnj DOT com</font><font size=3 face="Times New Roman"> </font>
<p>
<p>
--=_alternative 00821B9E86256CB6_=--
|
|
|