But this doesn't cover you if you do a "special" backup in addition to the normal incremental. Then you now have 29 versions instead of 28, and there goes your 4-week recoverability. If I have a client that has a point-in-time recoverability requirement, I always set the VEREXIST and VERDELETE to NOLIMIT. That way I don't care how often they backup their data...they're covered.
Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Karel Bos Sent: Wednesday, October 08, 2003 7:08 AM To: [EMAIL PROTECTED] Subject: Re: Point in time restore vs Archiving Hi, Something like: Versions Data 28 Exists Versions Data 28 Deleted Retain Extra 28 Versions Retain Only Version 28 Copy Frequency 1 should work fine. Regard, Karel -----Oorspronkelijk bericht----- Van: Henrik Hansson [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 oktober 2003 13:02 Aan: [EMAIL PROTECTED] Onderwerp: Point in time restore vs Archiving I have a question regarding an issue regarding Archiving. Lets say I have a policy that says that I need to do FULL backups days a week for 4 weeks. Ofcourse I can do archive each day but then I think I don't use the functunallety in TSM. Is there a way of doing incremental backups that covers 4 weeks back in time? I have the following settings in my TSM for a backup group Backup Copy Groups : STANDARD ACTIVE STANDARD STANDARD Policy Domain Name STANDARD Policy Set Name ACTIVE Mgmt Class Name STANDARD Copy Group Name STANDARD Versions Data 5 Exists Versions Data 1 Deleted Retain Extra 30 Versions Retain Only Version 60 Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy Destination BACKUPPOOL Do You think this would meet the 4 weeks restore policy..... Thanx Med Vdnlig Hdlsning/ Best Regards _____________________________ Henrik Hansson