I've been wondering about the best way to do that as well.
Depending on your configuration, the backup server will retry
a client x number of times then give up, but as you said you
wouldn't really know that until the savegrp is finished.
I think the best way to know as it happens would be to write
a perl script that tails the nsr.log file and alerts on certain
types of failures:
tail -f /nsr/logs/daemon.001 | perl -lane 'if (/Failed/) { \
system qq/echo $_ | mail -s "NSR Client Failure" user-pager\@domain.com/ }'
you get the idea.
--joey
On Fri, Aug 15, 2003 at 12:01:55AM +0200, John Hope-Bailie wrote:
> Good-day all,
>
> We have a requirement in which rapid response is required to failed client
> backups.
>
> The current approach using email/pager notifications linked to savegroup
> completion events is not working well enough.
>
> There are hundreds of clients in about 10 groups, so the groups often run
> for 12 hours (or more).
>
> The savegroup notification is only issued when the savegroup finally ends.
>
> If a client fails early on, this would typically only be reported say 10
> hours later.
>
> This is too late to investigate and fix the client problem during the backup
> window.
>
> We have been advised to try the "owner notification" feature which is
> configurable per client.
>
> Functionally, this is better, but I seem to recall that this too, is only
> issued when the entire savegroup completes.
>
>
> Question
>
> Has anyone been faced with this requirement to take immediate corrective
> action to failed client backups during the backup window ?
>
> If so, how did you arrange per/client failure notifications in real time ?
>
> I suppose it might be possible to hook into the save processes on the
> client itself and work from there ?
>
> Has anyone tried anything like this ?
>
>
> regards,
>
> John Hope-Bailie
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
