Hi Tim,

We had the exact same problem
we have 3 weekly backups and 1 monthly backup and so on and so on.
I can't make a calendar based schedules since there are months that have
5 weeks in them...

so I've made a scripts that makes the changes for me!
I can change any policy on any day to any retention level by running the
script with parameters I set in advance.
It's cyclic and the retention is set by the backup we had last week,
that means - we keep the generation of last weekend's backup
if it was weekly 1 it sets the next week backup to be weekly 2,
weekly 3 sets the next week backup to monthly #
monthly 12 will set the retention to yearly backup (yearly is always
monthly 13 since there are 52 weeks) and so on....
besides the first time you set the data of your site you will only need
to update new schedules you need to change...

the script is in ksh, and I don't know if that is good for you... 
would you like me to send it to you?

Michal


-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Tim Berger
Sent: Tuesday, February 15, 2005 3:40 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Month End and Weekly Backup

Please clarify "getting old".  What you're doing sounds like the most
efficient way of getting the task accomplished (if it were automated).
 It would also minimize the chance of more than one level 0 happening
within the approximate monthly time frame.

If your weekly backups are done the "netbackup way" (eg. every 7 days
on any day) it's a very resilient way of getting regular backups done,
but that makes it harder to have another calendar based monthly
schedule that doesn't take place immediately after the weekly.

For example, host "foo" gets backed up on Jan 31st on the weekly
schedule, then the monthly schedule with a window from Feb 1st to the
7th says, it's time for a level 0. Somewhat of a waste, don't you
think?

I'm thinking a scriptable solution of adjusting the retention periods
would minimize potential scheduling complications.  But maybe there's
another reason why you've rulled that out. Can anyone think of a
reason why this might be *bad*?

On Thu, 10 Feb 2005 13:57:17 -0500, Zermeno, Brandon (Contractor)
<BZERMENO AT intersil DOT com> wrote:
>  
>  
> 
> What is the "best practice" on handling the Month end backups and the
weekly
> backups? What I mean is, I have Full Weekly's that are retained for 3
> months, but I also have to squeeze in the Month Ends that are retained
for 1
> year. How are you dealing with this? I have about 70 policies with 7
master
> servers. We have a ton of apps that all require different settings. I
have
> just been going in and modifying the retention period of the weekly's
to 1
> year but this is getting old. I am thinking of doing inline copies to
a
> different pool. Any ideas. 


-- 
-Tim
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



---------------------------------------------------------------------------------------------------------------
This e-mail message may contain confidential, commercial and privileged 
information or data that constitute proprietary information of Cellcom Israel 
Ltd. Any review or distribution by others is strictly prohibited. If you are 
not the intended recipient you are hereby notified that any use of this 
information or data by any other person is absolutely prohibited. If you are 
not the intended recipient, please delete all copies.

Thank You.
http://www.cellcom.co.il