What I have done in the past is to use a weekly schedule with a set backup
window, and a calendar based backup with the same window.  The weekly gets
an exclude date for the window when you want the monthly to run, and a
calendar backup is set to run on those days.  So you get 3 weeklies and a
monthly. 

I wrote a script that uses the command line to set the exclude and include
dates.  You could also use a "first Saturday" type schedule for the monthly,
and set the excludes on the weeklies around that.

Inline copies would work as well, but I wouldn't go that route for resource
reasons if I could avoid it.

Mark

P.S.: do you really have 70 policies and 7 *master* servers?  This sounds
like a lot of unneccessary licensing revenue to Veritas. Why do you need 7
master servers?

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.