Steve, I don't see how this will save tapes, in fact it should use more tapes if you could get it to work.
It sounds like your management wants two offsite copies, is that the case? Belt and braces so they are not relying on a single copy in the case of a disaster? Do they understand that TSM retention periods have nothing to do with how long the tape is offsite? In a normal TSM operation, because of the incremental nature of backups you already use far fewer tapes than you would with the equivalent GFS rotation. Of course this can be defeated if you are doing a lot of full database backups or lots of weekly archives because of obsolete policies that demand a "weekly full", but if that is the way that things are, you can do nothing on the TSM side to reduce the offsite requirement. If two offsite copies are required, then you need two *full* offsite copies. Nothing else will do (although you needn't send off the second copy every day). Periodic export node or generate backupset can be used if you want a snapshot of a subset of nodes, but this is unwieldy and impractical for all data. I don't know how iron mountain operates but, reading between the lines, it sounds like they offer a simple time-based rotation scheme, or that your organization has signed up for such a service. Such schemes don't fit well with the TSM paradigm. However, TSM can be forced to fit. There was a discussion by Paul Seay a couple of years ago where he described his method of dealing with this :- if there is a monthly rotation, then after 25 days offsite, a delete volume or move data is run on the offsite tape and thus its contents are recreated at the next backup stg. Check the archives. Some combination of this rotation scheme, changed offsite return cycles and multiple copypools should be able to satisfy your management's requirements. Regards Steve Harris TSM Admin Queensland Health, Brisbane Australia >>> [EMAIL PROTECTED] 06/01/2005 23:08:51 >>> In order to save tapes. Managements would like to make 2 copies of files to go offsite to iron mountain. One copy would be sent off daily and we would like It to be returned in 14 days with a retention of 14 days. The other copy will be sent off weekly and have a retention of 1 year. The only thing I can think of So far is when a daily offsite tape is returned from iron mountain, I could do a discard data to free up that tape, but I would like a better way. steve -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steve Harris Sent: Wednesday, January 05, 2005 5:36 PM To: ADSM-L@vm.marist.edu Subject: Re: Creating a copy storage pool with a different retention time Why do you want to do this? We may be able to come up with a different way to satisfy your requirement. Steve >>> [EMAIL PROTECTED] 05/01/2005 2:16:05 >>> Currently I have my policy set to retain file backups for 1 year. First I do my backups to my disk storage pools, I then have 2 copy pools, I copy the data to a non-collocated copy pool I send off site for 1 year, and then make a second copy which I keep onsite as a spare copy of my onsite-pool that gets migrated from the disk pool. What I would like to do is create another copy storage pool with a different retention, just 14 days. How would I do this, or the better question is is possible to do?? ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at postmaster at dor.state.ma.us. ********************************************************************** *********************************************************************************** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone or by return email. You should also delete this email and destroy any hard copies produced. *********************************************************************************** *********************************************************************************** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone or by return email. You should also delete this email and destroy any hard copies produced. ***********************************************************************************
