DDB Reconstruction Job is not initiating

Article ID: DD0016 The DDB reconstruction job does not initiate and when manual reconstruction job is performed an error message is displayed.

Symptom

The deduplication database (DDB) reconstruction job does not initiate and when manual reconstruction job is performed the following error message is displayed in the Job Details:

Some deduplication partitions of this Storage Policy Copy are skipped due to reconstruction threshold. Skipping reconstruction. Please check event viewer for details.

The following message is displayed in the Event Viewer:

Reconstruction of a deduplication partition on MediaAgent [ ] at path [ ] of Storage Policy [ ] Copy [ ] has been skipped due to exceeding threshold of [5] reconstructions with [24]hrs. Please start full reconstruction of this partition from GUI.

Cause

For a specific deduplicated storage policy when more than 5 failed reconstruction jobs have occurred in less than 24 hours, future reconstruction jobs will not be initiated.

Note that during this process, the timing of the first failed reconstruction job is considered. For example: If the first reconstruction job failed at 10:00 AM on 15th, only 5 failed reconstruction job are allowed untill 10:00 AM of 16th. If the number of failed reconstruction jobs during that time period exceeds more than 5, then a new reconstruction job can be performed only after 10:00 AM of 17th.

Resolution

We recommend that you perform a full reconstruction of the DDB using Reconstruct entire DDB without using a previous recovery backup option during manual recovery of the DDB or contact your software provider.

See Manually Recovering the Deduplication Database for instructions.