Skip to main content
commvault.com commvault.com
Solved

Partitioned DDBs Best Practice

  • December 29, 2022
  • 3 replies
  • 719 views
P
Byte
Forum|alt.badge.img+4

Hi Guys,

 

We are using partitioned DDBs running on 2 media agents in the environment on the Azure VMs. 

Our current Deduplication setting on GDSP level is to seal and start a new DDB in case of any DDB corruption instead of Recover Pause and Recover current DDB. Also the option to “Allow jobs to run to this copy while at least 1 partition is online” is not selected. 

 

Just wanted to check what is the best practice for partitioned DDBs as per Commvault.

CS : Azure VM

Primary Library : Azure BLOB

Secondary : Metallic

Best answer by Damian Andre

There isn’t really a best practice here - it’s a trade off. If you seal, you will incur more storage charges and each block will be seen as new. Old blocks won’t age off until every job meets retention. 
 

the alternative is to reconstruct which means backups don’t work until the job is completed, so you may miss a few hours or more of new backups waiting for the reconstruction to complete.

 

personally since cloud costs can be expensive, I’d recommend the reconstruction option and enable garbage collection (may require upgrading the DDB) for optimal performance.

View original
    Did this answer your question?

    3 replies

    O
    Vaulter
    Forum|alt.badge.img+15
    • OrazanVaulter
    • Vaulter
    • 630 replies
    • December 29, 2022

    Good afternoon.  I would say that the setting to seal in case of corruption is best setting as you do not have to worry about reconstructions and DDB verifications which take a lot of time and can increase charges.  As for the option to “Allow jobs to run to this copy while at least 1 partition is online”, that is personal preference.  Not having this selected does not allow you to keep running jobs to the other partition if one goes down.  

    P
    Byte
    Forum|alt.badge.img+4
    • pank1988
    • Author
    • Byte
    • 5 replies
    • December 29, 2022
    Orazan wrote:

    Good afternoon.  I would say that the setting to seal in case of corruption is best setting as you do not have to worry about reconstructions and DDB verifications which take a lot of time and can increase charges.  As for the option to “Allow jobs to run to this copy while at least 1 partition is online”, that is personal preference.  Not having this selected does not allow you to keep running jobs to the other partition if one goes down.  

    Reconstruction and DDB verifications : How it will increase the charges ?
    Also if DDB is sealed a new baseline will be created won’t that increase the cost if it is cloud ? Azure BLOB in our case..

    Damian Andre
    Vaulter
    Forum|alt.badge.img+23
    • Damian AndreVaulter
    • Vaulter
    • 1310 replies
    • Answer
    • December 30, 2022

    There isn’t really a best practice here - it’s a trade off. If you seal, you will incur more storage charges and each block will be seen as new. Old blocks won’t age off until every job meets retention. 
     

    the alternative is to reconstruct which means backups don’t work until the job is completed, so you may miss a few hours or more of new backups waiting for the reconstruction to complete.

     

    personally since cloud costs can be expensive, I’d recommend the reconstruction option and enable garbage collection (may require upgrading the DDB) for optimal performance.

    Onno van den Berg
    Jos Meijer
    O
    3 people like this
    • Onno van den Berg
      Onno van den Berg
    • Jos Meijer
      Jos Meijer
    • O
      Orazan

    Reply


    Most helpful members this week

    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings