Create New Copy from a Storage Policy with dedup already enabled

Last post 09-21-2020, 3:42 AM by Wwong. 3 replies.
Sort Posts: Previous Next
  • Create New Copy from a Storage Policy with dedup already enabled
    Posted: 09-15-2020, 5:44 PM
    • Egg is not online. Last active: 09-16-2020, 7:26 PM Egg
    • Not Ranked
    • Joined on 02-15-2019
    • Rio de Janeiro, Brazil
    • Newcomer
    • Points 19

    Hi, do we need to enable deduplication when creating a new copy from a storage policy primary copy with deduplication already enabled? If not checked (Enable deduplication) when creating the new copy, will Commvault rehydrate the data? If positive, just to confirm, do we need to create another DDB to dedupe the second copy? 


    Version 11 SP17.46

    Braga, Eduardo
    Backup Administrator
  • Re: Create New Copy from a Storage Policy with dedup already enabled
    Posted: 09-18-2020, 10:36 PM

    You should be able to whatever you want with the new copy.

    So no dedupe - then super straightforward as you won't obviously need a new DDB.

    Yes, your data will be "fat" on this new, non-deduped copy.

    Commvault will rehydrate on a job by job basis until you will end up with a baseline, but it won't be an obvious process. 


  • Re: Create New Copy from a Storage Policy with dedup already enabled
    Posted: 09-18-2020, 11:26 PM

    Please look into using Global deduplication instead of enabling it at the storage policy copy level.

  • Re: Create New Copy from a Storage Policy with dedup already enabled
    Posted: 09-21-2020, 3:42 AM

    Hi Egg 

    Technically if you are using Disk Storage for both Source and Destination (and no Hardware Deduplication) it would be best to use Deduplication on both Source and Destination. 

    The primary purpose of Deduplication/Compression is to minimize your overall capacity consumption at the Storage Layer by using references to associate similar block 

    If you enable the normal Deduplication option - this will create a local Deduplication Engine that is only used for that specific Storage Policy/Copy. As mentioned by Anthony if you use Global Deduplication you can associate multiple Storage Policy/Copy to this single Global Deduplication Policy, providing added space saving. 

    Further to above when you enable Deduplication on Source and Destination, Commvault will then levarage DASH (Deduplication Accelerate Streaming Hash) Copy, which provides added efficiency and security as only unique blocks are transferred across the network (with encryption) and any existing references, Commvault will increment the references in the Deduplication Database (created upon enabling Deduplication on the MediaAgent - preferably on SSD) further minimzing network bandwidth consumption and minimize additional write IOPs when writing to the Disk Library



The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy