Whenever a new DDB is created, a fresh copy of signatures and first occurrence of each subsequent data block is written to storage. However these data blocks may already exist in storage with signature contained in the sealed DDBs residing in the MediaAgent or Data Center. The DDB Priming feature looks for signatures in the previously sealed DDBs and uses them to baseline the new DDB. In source-side deduplication, this saves the need for clients to transfer data blocks that are already available in the storage.
This option is not supported on archive cloud storage.
Two questions here:
- However these data blocks may already exist in storage with signature contained in the sealed DDBs residing in the MediaAgent or Data Center. Data Center? What is a Data Center in CommVault?
- The DDB Priming feature looks for signatures in the previously sealed DDBs and uses them to baseline the new DDB. How the Commvault accomplish it? Does Commvault copy signatures from the sealed DDB to the new DDB? Or does it just query the sealed database at the time of the clients' backup?
