I have the same reservations expressed by Charles in regard to utilizing
this approach.
If you have 7.3.x or later, you can also use nsradmin in a slightly
different way:
nsradmin –d /nsr/res/jobsd/{general,savejobs,indication}
This works on the server and provides read-only access.
But, one of the lesser known secrets of the NetWorker consultant is you can
kick off save (and with 7.3 it is getting much more useful to do the same
with savegrp) and then you can write your own event driven processes.
I'd stick with the simpler approach of creating custom notifications and
simple scripting where absolutely necessary. If you want to get more
advanced than that you'll need some pretty experienced NetWorker scripters
to help.
Now, if you could just get EMC to kick free an api in some rapid application
development language like, say, python... ;-)
Brian
On Thu, 10 May 2007 15:21:37 -0400, Patterson, Charles P.
<Charles.Patterson AT TUFTS DOT EDU> wrote:
>There is a switch for 'save' which will fail the backup for a particular
>client if an error is encountered.
>
>Here is the section of the man page for save:
>
> -u Stop the save if an error occurs. The save program
> normally treats errors as warnings and continues to
> save the rest of the files in the backup. When this
> option is set, errors will cause save to exit and abort
> the save. This option is not recommended for general
> use, although it can be useful when a group of files
> needs to be backed up as a set.
>
>In the client you could configure the 'Backup Command' to read 'save -n'
>and the client should fail immediately once an error is encountered.
>
>I have to admit I haven't tried this myself. Also it could be
>irritating if the backup is nearly complete for the large saveset you
>have described.
>
>-----Original Message-----
>From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
>Behalf Of Wayne Johnston
>Sent: Wednesday, May 09, 2007 8:04 PM
>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>Subject: Re: [Networker] Immediate Error notification before save set
>finishes
>
>All,
>
>Does anyone have an easy way or know of a product that can immediately
>notify the admin of an error as soon as it happens either via email or
>SNMP. Some save sets can take 12 -13 hours to finish and an error could
>have occurred 1 hour in on one of the first clients. If we can get
>notification then we could still investigate the problem and fix it
>before too much time has past.
>
>Thanks
>
>Wayne Johnston
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and
>type "signoff networker" in the body of the email. Please write to
>networker-request AT listserv.temple DOT edu if you have any problems with this
>list. You can access the archives at
>http://listserv.temple.edu/archives/networker.html or via RSS at
>http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and
>type
"signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>=========================================================================
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
