• 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.

Directory-Container pools and migration


ADSM.ORG Senior Member
I am reading through the Spectrum Protect 8.1 documentation and see that Directory-Container pools have Migration listed as a function that can't be used. I had hoped we could set up our storage pools in such a way that we could migrate dusty old data off to an object store setting up a migration delay of 365 days or something along those lines.

Anyone hear if this may change down the road? If not, any suggestions on how to do an age based data migration? Looks like move nodedata or move data don't have date options unless that has been added in a release newer than 7.1.1.

Given the potential savings from dedup and compression I am not sold on this being worth doing. Just something to check into.



ADSM.ORG Moderator
There's no way to migrate data out of a container pool. It's also highly possible that old data have duplicate chunks with newer versions, so you'd actually consume more space by moving data out (if possible).


I'm currently working with a TSM (Spectrum Protect) v 8.1.0 installation that the customer wanted to use only one directory / container stgpool per "front-end" TSM instance.

It works to move TSM node data into a container pool (setup without compression but working inline dedup) by using "node replication" from TSM servers that use 7.1.6 and 7.1.7.

The two front-end TSM servers replicate it's container stgpool to a dedicated back-end replication "target" server via cmd: "protect stgpool <stgpool>".

As I read in an IBM web site before 8.1.0 was released there would might be a "move nodedata" function to and/or from a Container pool but I haven't had time to test it yet.

Also you can convert a FileDev pool to a container pool directly (background process) via dsmadmc (earlier it was via the O.C) > convert stgpool:

CONvert STGpool--source_stgpool--target_stgpool-------------->



'-MAXPRocess--=----number---' '-DUration--=--minutes-'


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: 8 21.6%
  • Keep using TSM for Spectrum Protect.

    Votes: 19 51.4%
  • Let's be formal and just say Spectrum Protect

    Votes: 6 16.2%
  • Other (please comement)

    Votes: 4 10.8%

Forum statistics

Latest member