Deduplication database(s) reaching threshold for Pending Logical Pruning

An event message appears when the number of aged job reaches the pruning threshold.

Symptoms

The following event message is displayed in the Event Viewer window, when the number of aged job records is older than seven days and more than the threshold value.

Deduplication database(s) reaching threshold for Pending Logical Pruning [
{StoreName[SIDB_SP01_Primary (Apr 19 2013 12:47AM)] StoragePolicy[SP01] Copy[Primary] Pending Logical Pruning Records[177887]}
{StoreName[SIDB_SP02_Primary (May 18 2013 6:41PM)] StoragePolicy[SP01] Copy[SP01_Primary] Pending Logical Pruning Records[12085]}
]. For more details please refer Deduplication Building Block Guide on Books Online.

The number of aged job records that are pending to be pruned is displayed under Properties section of the Deduplication Database summary. See Monitoring Deduplication Database for more information.

Causes

The threshold value of the deleted number of records is 10,000. If the number of deleted records for a DDB is older than the seven days and more than the threshold value, then an event message with that DDB details is displayed in the Event Viewer. This indicates that the space reclamation of aged data on the disk is falling behind or slow.

This might be because of one of the following reasons:

• This DDB is hosted on a sub-optimal disk/MediaAgent.
• The Mount Path is offline.
• The MediaAgent for the disk with prunable data is offline.

The number of days and records considered for pending deleted records for pruning can be modified in the Data Aging tab of the Media Management Configuration dialog box through the following parameters:

• Days to consider for pending logical pruning for Deduplication pruning threshold event
• Max number of records pending logical pruning for Deduplication pruning threshold event

Resolution

To resolve this issue, perform one of the following tasks:

• Ensure that the DDB is hosted on a server with high-speed processor and effective memory that delivers good deduplication performance.

Depending on your environment, relocate the DDB to a storage that meets the performance requirements associated with Deduplication operations. To ensure optimal performance for deduplication operations, the disk hosting the DDB must satisfy the specifications mentioned in Deduplication Building Block Guide.

• If the mount path is offline, make sure that:
  • The credentials to the mount path are correct.
  • All device controllers for that mount path are accessible.
  • Mount path is not disabled on the Mount Path Properties dialog box.
  • Operating system is able to access the given mount path location.
• If the MediaAgent for the disk with prunable data is offline, then:
  • Verify that the MediaAgent services are up and running.
  • Resolve the Network connectivity issue.