1. 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.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    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.

One Container Stgpool or Two???

Discussion in 'TSM Server' started by booman55, Jul 21, 2017.

  1. booman55

    booman55 ADSM.ORG Senior Member

    Joined:
    Feb 21, 2007
    Messages:
    207
    Likes Received:
    5
    Customer wants to put 500 Windows client’s backup data on Container storage pool. The nodes are split 250 Prod & 250 Dev and they only need to DR via replication the Prod data.

    Do I create one container storage pool or two containers? If I create one it will copy all extents via Protect Storage pool and node replication would send meta data for Prod nodes. Is that a waste of space on DR side to send the data for Dev nodes?? DR Target site has less disk space available than Source site.

    Would creating two container storage pools be less efficient use of disk storage??
     
  2.  
  3. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,486
    Likes Received:
    348
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    One storage pool is recommended because it's easier to manager and there is higher dedup ratio.

    My customers that have two pools normally have one dedup and one traditional. They use the traditional pool for backups that don't dedup well, like data that is encrypted prior to the backup, like certain DB backups. And everything else to a single container pool.
     
  4. booman55

    booman55 ADSM.ORG Senior Member

    Joined:
    Feb 21, 2007
    Messages:
    207
    Likes Received:
    5
    Thanks for the response. I've been doing the single pool for quite a while for those same reasons. The situation with this customer is 50% of the data on the source does not need to be DR protected and they are buying storage to reflect that. For some raw numbers, if they have 1 PB of primary storage 500 TB is prod and 500 TB is dev. Theoretically, you would need approx 100 to 150 TB of container storage pool space. If they're only going to protect 500 TB offsite then they only need 50-75 TB at DR site.

    So the question would be splitting in two pools would that make my source side storage swell to 150 - 200 TB?? And would that overall make any additional storage on DR side not worth it??

    I'm leaning toward just a single pool to provide the benefits of repairing storage pool in event of an issue, but wanted to hear some other ideas.
     
  5. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,486
    Likes Received:
    348
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    If you are going to protect all the data, may as well replicate too. Replicate only sends metadata since the protect already sent all the data.

    They may have a case where using 2 pools would have benefits. But even if they don't need the data for DR, are they ok with losing some of the data in the pool should there be a problem with the storage?
     

Share This Page