DDB physical pruning is increasing costs at AWS S3 Glacier library

Last post 05-29-2020, 5:40 AM by karthik. 1 replies.
Sort Posts: Previous Next
  • DDB physical pruning is increasing costs at AWS S3 Glacier library
    Posted: 05-28-2020, 10:48 AM


    I have an issue related to AWS and its S3 Glacier library. DDB pruning is making a big amount of requests every day to this library. Due to the data is not accessible, the DDB pruning process has no sense. Furthermore, that amount of requests to a Glacier library are increasing the monthly cost. To stop it, I decided to unckeck "physical pruning" at the Global Deduplication Policy. I would like that to occurs every 3 months. Does anybody know how to do it?

    Thanks in advanced!

  • Re: DDB physical pruning is increasing costs at AWS S3 Glacier library
    Posted: 05-29-2020, 5:40 AM

    Please refer this planning document section for Glacier / Archive Cloud storage.  peridcially  Seal the DDB and disable Micro pruning .  




    Deduplication Support



    Ensure that the following options are configured on these storage classes:

    • For deduplicated data, make sure to seal the DDB every 6 months, to make sure that the data is periodically pruned. This can be done by setting the value of Create new DDB every [] days option to 180 in the Storage Policy Copy Properties dialog box.

      In addition, as a DDB reconstruction will require all the data to be recalled, it will be very expensive. Hence, choose the Seal and Start new DDB automatically on detection of inconsistency option.

    • Micro-pruning is not supported. Hence, ensure that micro-pruning is disabled. For more information on disabling micro-pruning, see Configuring Micro Pruning.
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