The best thing what you can do is to check the clients before backup runs. It
is not possible to get notified during savegroup running. What i have done is i
check the clients with 'nsradmin -s clientname -v1 -p 390113' and if i get
answer from them, then the possibility to backup this clients is very high :)
and needs no notification. But if the client didn't answer then i have to
notify the responsible person to check this client.
It is not the best way but the willing to do something for our customer !!!
Yeah !
Cheers ramazan
-----Original Message-----
From: Eidler, Dean [mailto:dean.eidler AT AGRESEARCH.CO DOT NZ]
Sent: Friday, August 15, 2003 1:22 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Immediate reporting of client-level backup failures
You are correct that owner notification is only done when the savegroup
completes. There is a problem with this also. If a group is aborted the owner
notifications don't get sent either.
We have a RFE in with Legato so that aborted groups stil run onwer
notifications.
Dean
-----Original Message-----
From: John Hope-Bailie [mailto:johnhb AT SOURCECONSULTING.CO DOT ZA]
Sent: Friday, 15 August 2003 10:02 a.m.
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Immediate reporting of client-level backup failures
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
=======================================================================
Attention: The information contained in this message and/or attachments from
AgResearch Limited is intended only for the persons or entities to which it is
addressed and may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon, this information by persons or entities other than the intended
recipients is prohibited by AgResearch Limited. If you have received this
message in error, please notify the sender immediately.
=======================================================================
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
