I had a script that changes the schedule for the client and (since I
know I would forget to change it back) scheduled an "at" job to change
its schedule back to its old one the following morning.

Robert Maiello
Pioneer Data Systems

On Wed, 30 Jun 2004 17:07:21 +0100, Davina Treiber <Treiber AT HOTPOP DOT COM>
wrote:

>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. ;-)
>
>>
>>
>>> Hello,
>>>
>>> I've run into a couple of instances where I need to keep a server from
>>> backing up just for one night, so I remove it from the group it runs in
>>> and then forget and never add it back.  So a couple of weeks/months
>>> later I discover that 'Oh Crap' I don't have that system backed up.  So
>>> I've been considering creating a schedule for each client instead of
>>> standardized schedules like I have now, so that I can just do an
>>> override skip instead of remove them from the group.  My questions are
>>> ... is anyone with a large environment doing this? ...is there a limit
>>> to the number of schedules you can create?  ...is this considered best
>>> practice or a bad practice?
>
>--
>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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=