We have paging set up for the following status codes:
50, 51, 52, 65, 66, 67, 68, 80, 81, 82, 91, 93, 94, 95, 96, 98, 110,
120, 144, 146, 164, 195, 213, 215, 219
We have e-mail set up for these:
5, 6, 7, 11, 19, 21, 23, 24, 25, 26, 40, 42, 43, 59, 60, 90, 111, 121,
124, 127, 131, 133, 135, 143 , 147 , 154, 160, 165, 167, 168, 169, 174,
175, 176, 189, 190, 191, 201, 202, 203, 204, 205, 206
196 errors are monitored by our LAN center and they will re-start jobs
that go over windows, provided they're application servers and don't
have dependencies on things like Oracle being put into backup mode, etc.
We also monitor ALL netbackup processes on the master servers and all MM
processes on the media servers.
Of course, that last will be changing as soon as I upgrade my real
environments to 6.0.
HTH,
Kate
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Ed Wilts
Sent: Tuesday, November 22, 2005 10:52 AM
To: Bob Stump
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] events sufficient to send a page
On Tue, Nov 22, 2005 at 09:01:13AM -0500, Bob Stump wrote:
> Brainstorm request.
> What events in an Enterprise NetBackup environment would warrant a
> page?
>
> Staus Codes
> 219
> 96
> etc.....
196
Excessive number of 150 events in a short time span. This usually
happens when NetBackup runs low on memory and will flush all of your
jobs. Of course, if the robot is down, you may find that interesting
enough to page on...
--
Ed Wilts, Mounds View, MN, USA
mailto:ewilts AT ewilts DOT org _______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
-----------------------------------------
This e-mail may contain confidential or privileged information. If you
think you have received this e-mail in error, please advise the sender
by
reply e-mail and then delete this e-mail immediately. Thank you.
Aetna
|
