Server restart notifications.

[rob@xxxxxxxxx]

Well, that server I had troubles with yesterday?  Last night our backup 
ran an ENDDOMSVR.  After 15 minutes it was still there so it ran a 
DMPSVRSTKS and then an ENDDOMSVR *IMMED.  Of course, whenever you run 
that, you're going to get a server restart notification when you bring the 
server back up.  However the server came back up at 21:14.  Routed me some 
other email based on a agent we run.  I didn't get the server restart 
notification until 7am the next morning.  Aren't server restart 
notifications supposed to be immediate?  And not based on a time or 
duration?
Keeping in mind that I had no problem getting the unrelated agent email 
shortly upon restart (therefore comm, etc was good).
Created date/time on the server restart notification email was 21:15.
Ok, so the receiving server did die for it's nightly backup about 20 
minutes after the sending server was back up.  And stayed down for 2.5 
hours.  But I did get that other email before.

Mail Fault Notification to: 
1 - Systems: Operations
(myCellNumberDeleted)@messaging.sprintpcs.com
CoworkerGal/DEKKO

My cell phone got it about the same time that my email did.
We do have an agent that checks the mail.box for stuck stuff and beats it 
into submission.  The agent starts around 7am.  So that explains why it 
started at 7am.  What isn't explained is why it was stuck in the mail.box 
when it was generated at 21:15 and the unrelated agent email was generated 
at 21:23 and promptly received.

Here's my WAG.  Server restart message gets promptly generated.  Even 
before router, etc are loaded.  Sees that they are not loaded yet and 
stays stuck in the mail.box.

Rob Berendt