Skip to main content
Solved

DDB with secondary copy

  • 13 August 2021
  • 5 replies
  • 287 views

Hi Commvault Team

 

how DDB works with the secondary copy (New Copy) to another disk library?
 

assuming that we have two sites, each one has its own MA, DDB, Disk pool. 

and DASH copy is enabled.
​​​​​​

@Nedal1993 , the DDB for the Dash copies works the same as the source DDB.  It checks each hash signature and if it is new, we store the block and write a new Primary record.  If it is already there, we just add another reference to the Primary record.

Is there something specific you want to know?

thanks, it's clear

 

Glad to help!

So would it be better to add a “ Backup Location” from the primary library correct? As apposed to adding another “Disk Storage” pointing to the off-site storage. ( With that it asks for where to put the ddb)

So would it be better to add a “ Backup Location” from the primary library correct? As apposed to adding another “Disk Storage” pointing to the off-site storage. ( With that it asks for where to put the ddb)


I’m not sure I understand your question, but to clarify you want secondary copies to be completely independent from the primary copy.  The whole point for additional copies is for them to be accessible if there’s any problem accessing the primary copy.  So you want those additional copies to be on new storage, DDB, etc.

Thanks,
Scott
 

Reply


Terms & ConditionsCookie settings