1. Please help support our sponsors by considering their products and services.
    Our sponsors enable us to maintain high-speed Internet connection and fast webservers.
    They support this free information and knowledge exchange forum service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions

Directory-Container pools and migration

Discussion in 'TSM Server' started by rowl, Dec 28, 2016.

  1. rowl

    rowl ADSM.ORG Senior Member

    May 18, 2006
    Likes Received:
    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.

  3. marclant

    marclant ADSM.ORG Moderator

    Jun 16, 2006
    Likes Received:
    Accelerated Value Specialist for Spectrum Protect
    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).
  4. Nicke

    Nicke ADSM.ORG Member

    Mar 17, 2005
    Likes Received:
    Storage consultant
    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-'


Share This Page