Of course, if you just want a point-in-time snapshot of the current data while continuing to use existing management classes for all data going forward, why not kick off a backupset, eject the tape when complete, and send it off to the vault with a copy of the BA client and the OS you're using. Now you have a standalone restore tape and everything else you'll need. Ten years from now, all you'll need to do is get a stand alone "legacy" tape drive, a machine that you can connect the tape drive to, the BA client, the OS, and the backupset tape. JM2C worth. Mahesh
>>> "Hart, Charles A" <[EMAIL PROTECTED]> 4/29/2008 10:43 >>> Thanks for input, we've done the same thing for the Exchange Environment, but I was under the impressions that once data is Archived using the TSM ba client archive function that you could not extend the retention on exiting archives... Example Client A Archives data to a 2yr Mgmtclass (Archive CopyGroup) then for the process below (New Domain with BU/Archive Copygroups set to 10years the archives that were processed with a 2year archive copygroup would still drop of in 2 years not the new 10year copygroup setting in the new domain structure. Thanks Charles Hart -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dwight Cook Sent: Tuesday, April 29, 2008 6:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Retain All Existing TSM Backup / Archive Data for 10Yrs If you only have to keep what is there for 10 years and can allow normal processing of new data going forward... set up a new domain with grace periods to fit your needs... for 10 years 3,666 days will work, my example here is where I had to keep everything for an umlimited period of time. (put in a base backup and archive mgmt that will fit your needs, again, here my example was unlimited) Move whatever nodes need the extended retention over into this domain and rename them something like <existing_name>_10YR Then register the existing name back into their initial domain. This will basically freeze all of the existing data tsm: XXXXXXXX>q domain unlimited f=d Policy Domain Name: UNLIMITED Activated Policy Set: STANDARD Activation Date/Time: 12/15/2006 13:59:50 Days Since Activation: 501 Activated Default Mgmt Class: UNLIMITED Number of Registered Nodes: 3 Description: Backup Retention (Grace Period): 9,999 Archive Retention (Grace Period): 30,000 Last Update by (administrator): XXXXX Last Update Date/Time: 12/15/2006 13:59:50 Managing profile: Changes Pending: No Active Data Pool List: tsm: XXXXXXXX>q copy unlimited active t=a Policy Policy Mgmt Copy Retain Domain Set Name Class Group Version Name Name Name --------- --------- --------- --------- -------- UNLIMITED ACTIVE UNLIMITED STANDARD No Limit tsm: XXXXXXXX>q copy unlimited active t=b Policy Policy Mgmt Copy Versions Versions Retain Retain Domain Set Name Class Group Data Data Extra Only Name Name Name Exists Deleted Versions Version --------- --------- --------- --------- -------- -------- -------- ------- UNLIMITED ACTIVE UNLIMITED STANDARD No Limit No Limit No Limit No Lim- it tsm: XXXXXXXX> Dwight E. Cook Systems Management Integration Professional, Advanced Integrated Storage Management TSM Administration (405) 253-4397 Ok, we have a requirements to retain all Backup / Archive data that exists in our TSM environment today for 10 years. There's a few "ugly" options, but would it be possible to do the following? Export node from Existing TSM servers to New TSM Server with Archive And Backup Copy Groups set to 10 years retention. I know that just increasing the Archive Copy group on the existing TSM Server's Archives to 10YR will not re-bind those Archive objects, but what if you export a node to a new TSM server with Longer retention Archive Copy Groups will the Archives bind to the new Archive Copy groups on the new TSM server? (I'm hoping so) Appreciate the input! This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
