Manually Recovering the Deduplication Database
You can recover an invalid deduplication database (DDB) by manually reconstructing the DDB.
About This Task
A manual recovery process with default settings recovers the DDB from the last DDB backup.
If both the DDB and the DDB backup are also detected as invalid, you can run full reconstruction of the DDB. The full reconstruction process deletes the existing DDB content, reads the entire data on the disk, and recreates a new DDB from the deduplicated data read on the disk. This process can be time-consuming because the full disk needs to be read during the recovery operation.
Before You Begin
Ensure that the DDB that has to be reconstructed is in active state.
- From the CommCell Browser, expand Policies > Storage policies > deduplicated_storage_policy.
- Right-click the appropriate storage policy copy, and click All Tasks > Recover Deduplication Database.
- In the Reconstruct Dedupe Database Options dialog box, specify the reconstruction settings:
- From the Source MediaAgent list, select the MediaAgent that is used to read the data on the disk for signature generation during the DDB reconstruction job.
- If both DDB and the DDB backup are not available or detected as invalid, select the Reconstruct entire DDB without using a previous recovery backup check box to perform full reconstruction of the DDB.
For more information on recovery options, see Reconstruct Dedupe Database Options.
- Click OK.
- When your reconstruction job is complete, you can view the reconstruction job history. For more information, see Viewing the Reconstruction Job History for the Deduplication Database.
- When the manual DDB reconstruction job with Reconstruct entire DDB without using a previous recovery backup option is run, you can view the following phases in the Job Details dialog box and in Job Controller window:
- Restore phase - During this phase cleanup of the current DDB location will take place.
- Add records phase - During this phase the data on the disk library associated with the DDB is read to rebuild the DDB location.
- Prune records phase - During this phase the data in the DDB is cross-verified with the CommServe database.