> Date:    Wed, 30 Jun 2004 17:07:21 +0100
> From:    Davina Treiber <Treiber AT HOTPOP DOT COM>
> Subject: Re: one schedule per client entry
>
> Roberta Butcher wrote:
> > For this purpose, I created a schedule called "Incr Daily". This
> > schedule does an incremental daily. When I want to force a skip on a
> > client, I do an override skip for that day in that schedule, then put
> > that schedule in the client definition. This way, if I forget to put
> > the client back in its regular schedule, at least it will be doing
> > incrementals ...
>
> That looks like a good compromise. If need be you could have a couple of
> these schedules for ad hoc requirements. You could also have a daily
> script to check for any clients with this schedule and alert you by
> email or similar. Probably easier to detect than a client that may not
> be in the correct group.
>
> I'd say the original suggestion is a bit unwieldy. Not exactly bad
> practice, but not the best. ;-)

Maybe I'm misunderstanding the problem, and making it too simple, but
when I want to have a client skip its nightly backup for just a night
or two, I just kill the Networker processes on the client.  The backup
fails, and I get notified about it via the standard notification
mechanism.  It will continue to fail (and notify me) until I restart
the Networker client software or the machine is rebooted.

Like I said, maybe I'm not getting it, but that seems like a simple
solution to me...

Sean Ross
Corvallis, Oregon, USA
rosss AT ace.orst DOT edu

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=