There is no real way for you to have separate fulls kept for different retentions without using multiple nodes.
What it sounds like you want kept over 1 year is 12 Monthly Full backup 26 Most current Sun Full Backups 4 Most current Wed Full Backups Not sure what you want for retention of Inc. The issue is that you can only have 1 mgmtclass for each TYPE of backup. What you could do is the following DBCOPY kept for 1 year (monthly) FULL kept for 26 weeks INC kept for 2 - 4 weeks or whatever you needed. However, I suspect this would give you 22 extra fulls that you do not appear to want to keep, and would require performing a separate backup for the Monthly. (I would do it on the first x day of the month where you run an incr and then run it after the incr. You could setup a separate node for the Sunday backups, but there would be no association between the sunday backup and all the incrs. i.e. if you lost your machine on a tuesday, you would have to go back to the previous Wednesdays full and all incr since then. I hope that is clear.... On Mon, 18 Oct 2004 12:14:46 -0400, David Soucy wrote: >Hi all. Hope you are well. > > > >I was wondering if anyone could suggest a way to backup 3 exchange >servers by doing 5 incs and 2 fulls per week but only keep 4 fulls for 6 >months and 1 full per month for backups >6 months old up to 1 year? > > > >I'll map it out > > > >Weekly schedule = Sunday FULL Keep 4 >versions for 6 months (one per week). After 6 months keep 1 version for >1 year > >Monday INC > > Tuesday INC > > Wednesday FULL >Keep for 30 days. > > Thursday INC > > Friday INC > > Saturday INC > > > >I'm keeping all versions just to be safe right now but it's getting to >be a lot of data! Any suggestions are *greatly* appreciated!! > > > >-dave soucy Ian Hobbs [EMAIL PROTECTED] ======================================================= "Never argue with an idiot. They drag you down to their level then beat you with experience." -Dilbert