I try to avoid removing a client because of what might happen. You may want
to have a special schedule that you can assign to a client. This special
schedule would be pretty much the same as your other schedules, but you
would be able to modify it to skip one night and only affect that client. If
you forget to change it back, you would still get the regular backups in the
special schedule. Problem is if you forget to change the schedule back and
skip another day in the future for another, you will skip that backup also.
When I make changes like this, I send myself a reminder in addition to
others.
James Rohrich
UOP LLC
25 E. Algonquin Rd.
Des Plaines, Illinois 60016
Tel: (847) 391-3958
james.rohrich AT uop DOT com
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On
Behalf Of Davina Treiber
Sent: Wednesday, June 30, 2004 11:07 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] 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. ;-)
>
>
>> 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
