Well, Marc, if you're stuck between the rock and the political hard place, you could create 2 nodes.
node node_hybrid Create two schedulers. Use two different optfiles with two different inclexcl lists. Or put the nodes in seperate domains so they can use different default mgmtclasses. Make the schedule for node_hybrid run a normal incremental backup on the first of every month. It's copygroup should be something like.... Policy Policy Mgmt Copy Versions Versions Retain Retain Domain Set Name Class Group Data Data Extra Only Name Name Name Exists Deleted Versions Version --------- --------- --------- --------- -------- -------- -------- ------- HYBRID ACTIVE MONTHLY STANDARD 12 12 365 365 You may want to set the frequency to 28, or some such, just in case someone accidentally tries to kick off a mid-month backup under the hybrid node name. This way only new stuff or stuff that gets changed during the last month will get backed up. Granted, that approximately doubles that node's occupancy, and increases backup processing and network utilization and whatnot once a month, but it'll be better than keeping 12 copies of everything and a lot less effort, processing overhead, and database overhead than most archive scenarios. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -----Original Message----- From: Marc Levitan [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 04, 2002 5:51 AM To: [EMAIL PROTECTED] Subject: Monthly Backups, ...again! A question was brought up while discussing retention policies. Currently we have the following retentions: Policy Policy Mgmt Copy Versions Versions Retain Retain Domain Set Name Class Group Data Data Extra Only Name Name Name Exists Deleted Versions Version --------- --------- --------- --------- -------- -------- -------- ------- COLD ACTIVE COLD STANDARD 2 1 5 30 NOVELL ACTIVE DIRMC STANDARD 30 1 120 365 NOVELL ACTIVE STANDARD STANDARD 30 1 120 365 RECON ACTIVE DIRMC STANDARD 36 3 75 385 RECON ACTIVE MC_RECON STANDARD 26 1 60 365 STANDARD ACTIVE DIRMC STANDARD 26 1 60 365 STANDARD ACTIVE STANDARD STANDARD 26 1 60 365 UNIX ACTIVE MC_UNIX STANDARD 30 1 60 30 I believe that this provides for daily backups for over a month. There was a request to have the following: 1) Daily backups for a week. 2) Weekly backups for a month. 3) Monthly backups for a year. I believe we are providing 1 & 2. We are providing daily backups for a month. How can I provide monthly backups for a year? I know that I could take monthly archives, but this would exceed our backup windows and would increase our resources ( db, tapes, etc.) Also, I know we could lengthen our retention policies. Also we could create backup sets. (tons of tapes!) How are other people handling this? Thanks, Marc Levitan Storage Manager PFPC Global Fund Services
