I am not sure shrinking the amount of disk space used by the DB will be worth the time. TSM will use the pages in the DB, even if they are not at the end. You will still have to add new disks at the same point in the future.
Andy Huebner -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Ochs, Duane Sent: Wednesday, July 01, 2009 2:31 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] DB size and expiration Good Day all, About a month ago, I was prepping to split a TSM DB because it was growing out of control after the addition of a number of remote imaging sites. After much review I was able to find failures in the expiration process. I tracked it down to a single client and after a call to IBM it was recommended to run a cleanup exptable. Needless to say it was running a very long time. After completion, the next expiration also ran for a very long time deleting hundreds of millions of objects. This should have translated to about 1/3 the database size being freed up. The problem is that I'm seeing max reduction at 4gb. The stats I'm seeing indicated 74 million usable pages and 52 million used. Other than a unloaddb and loaddb. Is there any other way to reclaim this DB space ? Thanks, Duane This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
