1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link 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 message will disappear after you have made at least 12 posts. Thank you for your cooperation.

how to move away from deduplication in the long run

Discussion in 'TSM Server' started by oskie, May 5, 2011.

  1. oskie

    oskie New Member

    Joined:
    Jul 14, 2008
    Messages:
    62
    Likes Received:
    2
    Occupation:
    System Technician
    We decided to no longer use deduplication because of the little gain and many issues (TSM bugs) it introduced. What is the best way to get rid of potentially deduplicated data in the long run? Should I just set dedup=no on the storage pool and disable the backup stgpool job, or should I create a new storage pool? I guess the benefit of a new storage pool would be that you'd know when there is 0 deduplicated data (and 0 bitfile issues...).

    Has anyone else stepped away from dedup?

    Regards,

    Oskar Liljeblad (oskar@osk.mine.nu)
     
  2.  
  3. chad_small

    chad_small Moderator

    Joined:
    Dec 17, 2002
    Messages:
    2,205
    Likes Received:
    44
    Occupation:
    AIX/SAN/TSM
    Location:
    Gilbert, AZ
    Which dedupe solution were you using? IBM's or EMC's?
     
  4. oskie

    oskie New Member

    Joined:
    Jul 14, 2008
    Messages:
    62
    Likes Received:
    2
    Occupation:
    System Technician
    TSM's solution
     
  5. yuki

    yuki New Member

    Joined:
    Jun 30, 2004
    Messages:
    79
    Likes Received:
    3
    Location:
    Finland
    Hi,

    Couple of ways... Just update stgpool with DEDUPLICATE=NO, but with that all deduplicated data will remain in stgpool.
    Deduplicated files will be discarded during time, reclamation and so on. New backups will not be deduped.

    Other way is to migrate data to another storage pool (no deduplication), for example add next stgpool and update deduplicated stgpool migration tresholds to 0.
    When migrated, all deduplicated data will be reconstucted. Deduplication is only allowed in file- device class and that's why you can't have deduped tapes :)

    If you like to use same stgpool for backups and not to update copygroups, start with DEDUPLICATION=OFF
     
  6. smetter

    smetter New Member

    Joined:
    Dec 22, 2009
    Messages:
    33
    Likes Received:
    0
    I'm curious,

    What kind of problems exactly did you run into using TSM6 deduplication?
     
  7. dlemieux33

    dlemieux33 New Member

    Joined:
    Jun 16, 2006
    Messages:
    12
    Likes Received:
    0
    Occupation:
    TSM ADMIN/General Storage
    Location:
    Maine
    We're running tests now with TSM dedupe and have seen some savings, so plan to deploy to the QA and production environment where were have TB's of fileserver data.

    I'm curious about the kind of data you were deduping, why did you decide to "De-Dedupe"? Performance or lack of savings?
     

Share This Page