So there is no reason to ever set retain only to less then retain extra right?
Gerald Wichmann System Engineer StorageLink 408-844-8893 (v) 408-844-9801 (f) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Bill Mansfield Sent: Tuesday, November 13, 2001 12:43 PM To: [EMAIL PROTECTED] Subject: Re: Data Retention Agreed! Helps to read the question thoroughly. _____________________________ William Mansfield Senior Consultant Solution Technology, Inc David Bronder <david-bronder@ To: [EMAIL PROTECTED] UIOWA.EDU> cc: Sent by: "ADSM: Subject: Re: Re: Data Retention Dist Stor Manager" <[EMAIL PROTECTED] ST.EDU> 11/13/2001 02:18 PM Please respond to David Bronder Based on how the original question was worded, both Mark's and Bill's answers below are incorrect. The last version expires 21 days after it went _inactive_, not after it became the the only version. In the original question, 14 days have passed since the file was deleted (and went inactive), leaving 7 more days before the last version is deleted in TSM (for a total of 21 days). If that isn't how TSM behaves, then the documentation is wrong. =Dave Mark Stapleton wrote: > > On Tue, 13 Nov 2001 10:14:31 -0800, it was written: > >Versions data exists - nolimit > >Versions data deleted - nolimit > >Retain extra versions - 14 > >Retain only versions - 21 > > > >When a version is deleted from the server and after 14 days have passed, > >is the "only" version retained for 7 more days or for 21 more days? > > The retain only version's clock doesn't start running until it does > into effect. Hence, the answer is "21". Bill Mansfield wrote: > > 21 days. According to Table 17 in the admin guide, the RETONLY clock > starts ticking when the file goes inactive, which happens during the first > backup after the file is deleted from server storage. -- Hello World. David Bronder - Systems Admin Segmentation Fault ITS-SPA, Univ. of Iowa Core dumped, disk trashed, quota filled, soda warm. [EMAIL PROTECTED]
