Ruksana, there is no simple answer, it depends. If you make two backups to a primary pool and just send one set of tapes off-site it would expire.If you backup primary pool to copypool it is same. One method to retain "forever" first backup and expire next one (with consequent ones) is to use two node names (with different policies) for same box. The other method is to use archive instead of backup. Thus on 27-th you create archive with RETVer=NOLimit or very long retension and on 29-th you have regular incremental backup with retextra=92.
Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Backup retention period Hi Zaltko, Sorry to bother you again. I understood the concept of VEREXIST AND RETEXTRA. We have done a offlinebackup on 27th may and a online backup on 29th.For me the offline backup is the most imp one if I had to restore. if I do the verexist=unlimit and retextra=92 will the inactive backups ie the offline and the online which I have done ( I have done no backup since thelast offline and online ) will stay there for the period mentioned. is there anyway to let TSM know to hold the offline backup forever till I ask it to delete so ..? I appreciate any help from you. With regards, -----Original Message----- From: Zlatko Krastev [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 28 May 2002 9:48 To: [EMAIL PROTECTED] Subject: Re: Backup retention period Ruksana, the method TSM usilizes is "keep several copies, check to limits, if any limit is reached delete oldest copy" So if you have set 31 versions and perform backups weekly last version would be 31 weeks old. But if you set at the same time versions to stay for 31 days you will have no more than 5 (sixth would be more than 31 days and would be "expired"). Most recent copy ("active" one) would stay forever until you delete the file. At that time next pair of limits (VERDELETED and RETONLY) would take care of the copies. Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Backup retention period Hi Zlatko, Thanks for your quick response. According to my TSM the copygroup setting has nolimit for this management class but the utl file has MAX versions 31. >From what you said ( my understanding is ) below if I don't do the backup of this database it should stay forever as it has nolimit -but if I do perform backup it will stay for next 31 days. Correct me if I'm wrong. The link you sent me was very useful I will start reading it. With regards, Ruksana Siddiqui -----Original Message----- From: Zlatko Krastev [mailto:[EMAIL PROTECTED]] Sent: Monday, May 27, 2002 7:21 PM To: [EMAIL PROTECTED] Subject: Re: Backup retention period The backup would stay there undefinitely if the content does not change. If it changes and a new backup is performed the copy you've just becomes obsolete and according to copygroup settings will expire some day. To ensure it would not be before three months have passed set VEREXIST=NOLimit and RETExtra=92. To become familiar with TSM (which is more evolved than competitive products) I highly recommend you to have a look at nice redbook "Tivoli Storage Management Concepts" - SG24-4877-02 (http://www.redbooks.ibm.com/). This would save you many headaches. Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Backup retention period Hi, I just started working with TSM but can someone tell me how can I find the retention period of the backup I have done. I have done a particular backup and wanted to have it for atleast 3 months - is there anyway I tell TSM to hold it for 3 months or can I actually check how long TSM was configured to hold the data. Any help is highly appreciated. With regards, Ruksana Siddiqui CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify AMCOR immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of AMCOR. CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify AMCOR immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of AMCOR. CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify AMCOR immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of AMCOR.
