My Google-fu is failing me. We're standing up a brand-new TSM 7 environment to replace our TSM 6 setup. I'm wondering if there are huge disadvantages to using a directory container pool to store the backups, or if there is a major reason why these should continue to be disk-based. This pool is only for the TDP backups.

Hi,

I have used container pool for some time now, With no issues. So far I have only seen advantages. But it is important to monitor disk usage and Growth.

Rgd.

Espen

If you pay /TB you would save some money... for cont stg pool it recommended to you second TSM server where to replicate/protect client data, for cont stg pools there is no copy storage pool, so no off-site tapes storage ....

Cahvdar Cholev

IBM Certified Advanced Deployment Professional - IBM Service Management Tivoli Storage Management V5
IBM Certified Deployment Professional - Tivoli Storage Manager V7.x/6.x
IBM Certified Deployment Professional - Tivoli Monitoring V6.x
IBM Certified Administrator - Tivoli Monitoring V6.x
IBM Certified Deployment Professional - Tivoli Identity Manager V5.1
IBM Certified Deployment Professional - Tivoli Storage Manager Fastback V6.1.1

Thanks for the replies! This location would not need off-site replication/backup of any kind, as it isn't production data. I've decided to go ahead and leave it as a container pool to help save on costs.

I believe that from Version 7.1.7 it is possible to create a 'container copy Storage pool' on tape Device. But I have not tried this yet.

Rgd.

Espen

We have a number of TDP, oracle, informix, sql, domino, db2 hitting TSM 7.1.7 container pools.  Our pools are configured for dedupe and compression.

The only thing that has been mentioned by our DBAs is that backup performance is slower with the inline dedupe and compression.

Restores don't appear to be affected.  This all is OK given the storage savings on the TSM side.