Skip to main content
Question

Commvault DR Restore to New host

  • July 13, 2026
  • 2 replies
  • 31 views

Forum|alt.badge.img+1

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

  1. Configure a Primary Deduplicated Disk Library.
  2. Configure an Auxiliary Copy (Copy-2) to a remote deduplicated Disk Library.
  3. Run backups successfully.
  4. Run Auxiliary Copy successfully.
  5. Create a CommServe Disaster Recovery Backup.
  6. Simulate a complete disaster:
    • Original CommServe is lost.
    • Original MediaAgent is lost.
    • Original DDB files are completely lost.
  7. The remote Copy-2 Disk Library (Chunk Store) remains intact.
  8. Install Commvault 11.40.51 on a new Windows server.
  9. Restore the CommServe using the DR Backup.
  10. 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

2 replies

Forum|alt.badge.img+2

Just to clarify, in this scenario, I'm not sure if you also lost the primary library data.
If this is true, you should ensure that the DDB backup is in the same library that holds the pointers,

Lib1<-backup DDB lib1

Lib2<-backup DDB Lib2.

This way, you'll always be able to restore a "live" library. You can also copy DDB backups between libraries. I recommend not deduplicating these jobs.

There are many ways to approach the problem; this seems to be one that fits your situation.


Lukas3D
Explorer
Forum|alt.badge.img+13
  • Explorer
  • July 13, 2026

In the past I went into DDB reconstruction problems, just because path didn’t exists at the host (just root folder like D:\DDBs\DDB1), once directory was created reconstruction was started.