I have heard it often of TSM administrators wondering why the TSM reclamation process is slow & clumsy process. The good part most of these administrators is that they understand the importance of reclamation & how it help their backup become more efficient & save on tapes, though they still wonder why it takes too longs. I had decided to give my point of view on this.
1- One of the main reasons for the reclamation process to be slow is that you don’t have enough tape drives. If you have only one tape drive into your library then you can have a seriously slow & none efficient reclamation process, as each time you need to reclaim a tape, TSM will have to copy the full tape to the disk, then reclaim the volume on the disk to another tap. So you are basically repeating the reclamation process twice.
2- You have a slower tape drives. Actually the speed of your reclamation is totally dependent on the mechanical speed of your tape drive. To make it clearer imagine a tape with only 7% valid data. When the reclamation process run for this tape, your tape drive will waste most of the time forwarding the tape to the point where is your data is written. The more scattered the data the more forwarding the tape have to do to get to the data. So the slower the drive, the slower it will take to totally forward the full tape looking for your data.
3- Another factor for slow reclamation process, which is specifically for offsite tape. If offsitereclaimlimit=X paramater has not been setup correctly. As the offisite reclamation by default try to reclaim all the tapes which meet your reclamation threshold at the same time. So imagine if you have a 60 tapes which meet your threshold at the same time, it means your reclamation process will take for ever & will never finish unless you have endless drives. To avoid this problem always try to set the parameter offsitereclaimlimit=X, where the best value of X would be the number of drives you have in your tape library. This parameter will limit the amount of offline tapes that TSM will try to reclaim at a certain time.
So where people tend to blame TSM for the slow reclamation process, it seems to be most of the time due to insufficient hardware configuration or TSM misconfiguration instead of the software code it self.
I hope that help some one get the idea of reclamation better, and before complaining about the TSM reclamation process you check your hardware & TSM configuation.
4 Responses to 'Why is TSM reclamation a slow and clumsy process?'
Leave a Reply
Eiad Al-Aqqad, VCDX#89
VMware Canada PSO
- Backup Solutions (3)
- Blades (2)
- IBM Blades (2)
- Data Migration (2)
- EMC (1)
- VPLEX (1)
- How to (1)
- Management Software (5)
- Problem resolutions (0)
- Storage (21)
- Tips & Tricks (7)
- Tivoli (22)
- Tutorials (11)
- VMware (6)
- Iwan: hi… I can not re-install smi-s agent on server windows 2003, I`ve been search the registry but still...
- sindhu: hello sir,i am doing my b.tech 3rd year (e.c.e) i am intrested in doing this tsm course .is this course will...
- CR7: Hi EIAD, I couldnt figure out where to post this doubt of mine, so im just posting it here.Please help out if...
- Errol: I’m using a clean install of windows 7 Ultimate 64 bit with the latest build of Thinapp 5.1.0-2079447....
- arun: Is that tsm is growing and good field
- TSM – IBM Tivoli Storage Manager Guru Blog: Should Virtual Tape Library have a place in your backup strategy?
- Tivoli TSM guide to securing VMware: IBM Tivoli Storage Manager & VMware Consiledated Backup (VCB) I hope these...
- TSM – IBM Tivoli Storage Manager Guru Blog: Microsoft SQL Cluster Data Migration to a new SAN
- TSM – IBM Tivoli Storage Manager Guru Blog: Migrating Exchange 2007/2003 Cluster to a new SAN
- IBM Tivoli Storage Manager Guru Blog: TSM
- Should Virtual Tape Library have a place in your backup strategy?
- Symantec Backup Exec StarWind Virtual Tape Library Integration
- Comparing Online Backup Services
- Veeam & PHD Virtual comparison
- IBM Tivoli Storage Manager support for VADP
- StarWind is Named a Finalist in The Storage Awards 2012
- PHD Virtual Monitor Review
- vSphere manual Disaster Recovery failback when using VMware SRM
- Migrating Exchange 2007/2003 Cluster to a new SAN
- Microsoft SQL Cluster Data Migration to a new SAN