Environment
- Commvault Version: 11.40.51
- Windows Server
- CommServe and MediaAgent installed on the same server
- Primary Storage: Disk Library (Deduplication Enabled)
- Secondary Copy (Copy-2): Remote Disk Library (Deduplication Enabled)
- Copy-2 uses its own Global Deduplication Policy
Disaster Recovery Test Scenario
- Configure a Primary Deduplicated Disk Library.
- Configure an Auxiliary Copy (Copy-2) to a remote deduplicated Disk Library.
- Run backups successfully.
- Run Auxiliary Copy successfully.
- Create a CommServe Disaster Recovery Backup.
- Simulate a complete disaster:
- Original CommServe is lost.
- Original MediaAgent is lost.
- Original DDB files are completely lost.
- The remote Copy-2 Disk Library (Chunk Store) remains intact.
- Install Commvault 11.40.51 on a new Windows server.
- Restore the CommServe using the DR Backup.
- Reconnect the existing remote Disk Library.
Current Status
After DR recovery:
- CommServe recovery completed successfully.
- Storage Policies were restored.
- Disk Library was restored and is Online.
- Mount Path is Online.
- Deduplication Engine objects were restored.
- The Chunk Store still exists on the remote storage.
- The original DDB files do not exist
Problem
When I run Recover Deduplication Database, I receive the following message:
"No Deduplication Backup exists. Skipping reconstruction."
The reconstruction process never starts.
- Is there any additional step required after CommServe DR recovery (for example, media catalog synchronization, library recovery, or another operation) before DDB Reconstruction can begin?
- Is a DDB Backup mandatory for this disaster recovery scenario, or should Full Reconstruction from the Chunk Store work without a DDB Backup?
Any clarification would be greatly appreciated.
Thank you


