Re: reclamation of unavailable primary tapes
Hi Guys, thanks for the reply. OK, I see TSM will handle more tapes than the library can physically digest. I consulted the TSM Admin Guide on this. The tapes in the overflow location will also age, won't they? Now, what are we going to do about space reclamation of the tapes in the overflow location? Will some operator have to stand by just to exchange tapes? On the other hand, this would be a better solution than checking tapes out of a primary storage pool since no backups have to be deleted in order to supply more scratches. Maintaining a copy storage pool on the 3575 should not pose a problem since the customer has another 3575 in a second location. The DLT will be another story because there is no backup changer or drive, so the created copy storage pool volumes will prove to be quite useless in case of a DR situation. I will have to call the customers attention to this. Thanks anyway. Lars On 12.07.2002 02:03:20 "ADSM: Dist Stor Manager" wrote: > For working disaster recovery your customer will need a *compatible* > device to read off-site tapes. In your case if we assume primary tapes are > held only on 3575 and DLT autochanger is used only for off-site: > - primary pool will use 3575. Library might be small but TSM does have > 'MOVE MEDIA' command for that exact purpose. > - copypool tapes will be DLT. Whenever set of tapes is built they are > checked out and sent off-site. Thus no problems with capacity. > - DR site must have DLT drive (not necessarily a library, manual one is > just fine) which should be able to read tapes written by autoloader. If > autoloader is DLT7000 drive might be either DLT7000 or DLT8000 but if the > autoloader is DLT8000 the drive must be the same. If some primary pools > are backed up to a copypool on 3575 then DR site must have 3570! > Doublecheck which is backed up where. > - do not forget to create (and send off-site) DB backups or snapshots > after backup stg finishes. > > Zlatko Krastev > IT Consultant
Re: reclamation of unavailable primary tapes (was: w/o subject)
Lars, I do not know what is the idea behind sending primary tapes off-site (DR ??) but this does not help at all in case tape gets somehow damaged. You will learn it the hard way - when you need to restore from the broken tape. Migration threshold set to anything between 0 and 100% will not force/prevent reclamation. They are just different You already gave the answer: update the volumes to readonly or readwrite, check them in the library and lower reclamation threshold (in any order). BTW: Subjects are very useful to track answers on a mail list with many posts (like this one). Burak, offsite is for copypool volumes only (look at note 3 for UPD VOL). Primary ones have to be unavailable. 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: yes, you may change the accesses to readwrite and then reclaim but you should normally use offsite not unavailable access regards, burak [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09.07.2002 16:23 Please respond to ADSM-L To: [EMAIL PROTECTED] cc: Subject: Hi TSM Guys, I have a customer who moves volumes from a primary storage pool to an offsite location by setting the volumes to "UNAVAILABLE". The storage pool's migration threshold is set to 100% for spacerclamation to be prevented. What do I have to consider if I want to manually start space reclamation on the unavailable volumes? Will it be enough to just check-in the volumes, change their access to ReadWrite, and then start the space reclamation by lowering the reclamation threshhold gradually? Thanx a lot Lars
Re: reclamation of unavailable primary tapes (was: w/o subject)
Hi, First, sorry for sending the message without subject, I guess the human brain is not supposed to to more than one thing at the same time (especially mine ;-) ). I already knew the question of why sending primary tapes offsite will pop up. The only thing that came to my mind was that the library is not big enough to hold copies of all the important storage pools. The customer already uses a DLT-Autochanger as copy destination for some of the primary storage pools. We are currently busy redesigning the implementation. I am sure we will not get the customer convinced to buy a bigger library. So what else could possibly be done to prevent removing tapes from a primary pool? The customer's environment consists of: 1x 3575-L18 with 3x3570 (C-Drives) 1x DLT Autochanger 7 Slots with 70GB per tape Client data is about 800GB I am not expecting a detailed draft but hints are very welcome Thanks Lars On 10.07.2002 03:53:31 "ADSM: Dist Stor Manager" wrote: > Lars, > > I do not know what is the idea behind sending primary tapes off-site (DR > ??) but this does not help at all in case tape gets somehow damaged. You > will learn it the hard way - when you need to restore from the broken > tape. > Migration threshold set to anything between 0 and 100% will not > force/prevent reclamation. They are just different > You already gave the answer: update the volumes to readonly or readwrite, > check them in the library and lower reclamation threshold (in any order). > BTW: Subjects are very useful to track answers on a mail list with many > posts (like this one). > Burak, offsite is for copypool volumes only (look at note 3 for UPD VOL). > Primary ones have to be unavailable. > > 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: > > yes, you may change the accesses to readwrite and then reclaim but you > should > normally use offsite not unavailable access > regards, > burak > > > > > > > [EMAIL PROTECTED] > Sent by: [EMAIL PROTECTED] > > 09.07.2002 16:23 > Please respond to ADSM-L > > To: [EMAIL PROTECTED] > cc: > Subject: > > Hi TSM Guys, > > > I have a customer who moves volumes from a primary storage pool to an > offsite location by setting the volumes to "UNAVAILABLE". The storage > pool's migration threshold is set to 100% for spacerclamation to be > prevented. What do I have to consider if I want to manually start space > reclamation on the unavailable volumes? > Will it be enough to just check-in the volumes, change their access to > ReadWrite, and then start the space reclamation by lowering the > reclamation > threshhold gradually? > > Thanx a lot > > Lars > > > > >
Re: reclamation of unavailable primary tapes (was: w/o subject)
For working disaster recovery your customer will need a *compatible* device to read off-site tapes. In your case if we assume primary tapes are held only on 3575 and DLT autochanger is used only for off-site: - primary pool will use 3575. Library might be small but TSM does have 'MOVE MEDIA' command for that exact purpose. - copypool tapes will be DLT. Whenever set of tapes is built they are checked out and sent off-site. Thus no problems with capacity. - DR site must have DLT drive (not necessarily a library, manual one is just fine) which should be able to read tapes written by autoloader. If autoloader is DLT7000 drive might be either DLT7000 or DLT8000 but if the autoloader is DLT8000 the drive must be the same. If some primary pools are backed up to a copypool on 3575 then DR site must have 3570! Doublecheck which is backed up where. - do not forget to create (and send off-site) DB backups or snapshots after backup stg finishes. 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: reclamation of unavailable primary tapes (was: w/o subject) Hi, First, sorry for sending the message without subject, I guess the human brain is not supposed to to more than one thing at the same time (especially mine ;-) ). I already knew the question of why sending primary tapes offsite will pop up. The only thing that came to my mind was that the library is not big enough to hold copies of all the important storage pools. The customer already uses a DLT-Autochanger as copy destination for some of the primary storage pools. We are currently busy redesigning the implementation. I am sure we will not get the customer convinced to buy a bigger library. So what else could possibly be done to prevent removing tapes from a primary pool? The customer's environment consists of: 1x 3575-L18 with 3x3570 (C-Drives) 1x DLT Autochanger 7 Slots with 70GB per tape Client data is about 800GB I am not expecting a detailed draft but hints are very welcome Thanks Lars On 10.07.2002 03:53:31 "ADSM: Dist Stor Manager" wrote: > Lars, > > I do not know what is the idea behind sending primary tapes off-site (DR > ??) but this does not help at all in case tape gets somehow damaged. You > will learn it the hard way - when you need to restore from the broken > tape. > Migration threshold set to anything between 0 and 100% will not > force/prevent reclamation. They are just different > You already gave the answer: update the volumes to readonly or readwrite, > check them in the library and lower reclamation threshold (in any order). > BTW: Subjects are very useful to track answers on a mail list with many > posts (like this one). > Burak, offsite is for copypool volumes only (look at note 3 for UPD VOL). > Primary ones have to be unavailable. > > 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: > > yes, you may change the accesses to readwrite and then reclaim but you > should > normally use offsite not unavailable access > regards, > burak > > > > > > > [EMAIL PROTECTED] > Sent by: [EMAIL PROTECTED] > > 09.07.2002 16:23 > Please respond to ADSM-L > > To: [EMAIL PROTECTED] > cc: > Subject: > > Hi TSM Guys, > > > I have a customer who moves volumes from a primary storage pool to an > offsite location by setting the volumes to "UNAVAILABLE". The storage > pool's migration threshold is set to 100% for spacerclamation to be > prevented. What do I have to consider if I want to manually start space > reclamation on the unavailable volumes? > Will it be enough to just check-in the volumes, change their access to > ReadWrite, and then start the space reclamation by lowering the > reclamation > threshhold gradually? > > Thanx a lot > > Lars > > > > >
