Quoting Remco Post <[EMAIL PROTECTED]>: > > The problem is that if for example you have 1000 clients scheduled to > > backup during an 8 hour window, it would be nice to know which clients > > have non functioning scheduler daemons at the beginning of the window > > rather than at the end of the window when it would be a lot more difficult > > to meet your SLA's. > > > > Joe Seigh > > > > Of course all client activety is logged in your activety log, one could easily > write a script (unix shell) to find messages stating "Schedule prompter was > not able to contact client" (ANR2716E) in the log every few minutes and send a > warning. Of course there are about 20 of this kind of messages to trigger on...
No, that's good. Probably not perfect as there seem to be limited conditions as to where it applies. I'll have to experiment some more. We will be using Tivoli to handle events from the actlog, but I'll try to see how useful it is for feedback on client schedule activity. Joe Seigh
