• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Unusual TSM server database size growth


I have a customer who has been using TSM for quite many years, around 2-3 months ago they have it upgraded to 8.1 version for the sake of IBM support.

Because of no additional resources they used their old server for the purpose, which has additional RAM to meet the minimum requirements. After these months of running we found the TSM server database growth seems to be unusual, when they are using the old version (6.2) the database size is just roughly over 20GB, but after 2-3 months of running, now their TSM server database is over 40GB. which seems unusual. Since they are also running TSM database backups to local disk, there were a few occassions when the disk becomes full and caused TSM service to stop.

We placed an IBM support call on this but there is no update as of today after a week, so I just come here and see if there could be any advice on this... TSM should be able to housekeep by default? Any reason why the database is growing like this? Any suggestions to shrink the database or at least make it not growing again? (I compared to 1 week ago that was around 40GB but it is now almost 42GB)

Please advise, thanks...


ADSM.ORG Senior Member
Still using legacy file pools or have you switched over to container pools?
Going from memory here but legacy file pools with dedup was about 600 bytes per chunk plus another 200 bytes for each copy storage pool that data was sent to.
If you are using container pools the size has gone up to 1000 bytes and I want to say another 1000 bytes for each copy. I could be mistaken.

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.4%
  • Keep using TSM for Spectrum Protect.

    Votes: 60 61.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.2%
  • Other (please comement)

    Votes: 8 8.2%

Forum statistics

Latest member