Keith, You can just use "checkout libvolume library_name volume_name remove=bulk checklabel=no" and insert your library_name and volume_name as appropriate. Then you want to "update volume volume_name access=unavail" so TSM won't try to access them. TSM will not loose track of the data on a tape just because it is checked out of the library. It will still be in a storage pool, and TSM still knows everything on it. If you have any separate storage pools for archive data, you could check out those first, because you are probably less likely to need them. Also, you can query the tapes and see which ones have not been written to in a long time as good candidates to check out. You can issue "select volume_name,status,pct_utilized,last_write_date from volumes order by last_write_date" to get a list of tape candidates. Ideally you want to check out tapes with a status of Full, and a high pct_utilized, because they won't come up for reclamation for awhile.
I hope you can get an additional frame soon, because TSM is much easier to manage if you have enough room in the library. Best Regards, John D. Schneider The Computer Coaching Community, LLC Office: (314) 635-5424 / Toll Free: (866) 796-9226 Cell: (314) 750-8721 -------- Original Message -------- Subject: [ADSM-L] rotating private tapes into/out of 3584 manually From: Keith Arbogast <warbo...@indiana.edu> Date: Tue, October 19, 2010 11:18 am To: ADSM-L@VM.MARIST.EDU We are running TSM 5.5.4.3 on RHEL 5.5. Our tape library is a 3584 with ALMS and twelve 3592-E05 drives. Expiration and reclamation are not producing enough scratch tapes to stay ahead of their usage, so our scratch tape supply is dwindling (#18). More tapes are on the way, but only 15 empty slots remain in the 3584. Another frame for the 3584 is being negotiated, but Rome was not built in a day, administratively speaking. Given the current pace of expiration and reclamation, we could hit 0 scratch tapes. If that happens, I am thinking our only recourse will be to eject Private tapes and load new tapes manually until new capacity is in place. How is that done, properly? Is it like ejecting tapes for offsite vaulting? I don't have experience checking-out or checking-in Private volumes, so I am concerned that no data be lost due to incorrect parameters on checkouts and checkins. Is running dsmadmc in mountmode going to be the best way to do this? Or, console mode? With many thanks and best wishes, Keith