This alert is generated in Data Protection Manager (DPM) when the replica of the data source is inconsistent with the data source on the protected computer.

All protection activities for the data source will fail until the replica is made consistent with the data source by performing synchronization with a consistency check. Although the replica is marked inconsistent, older recovery points are still recoverable. Validate and fix the replica inconsistency as soon as possible.


Review the alert details in Data Protection Manager (DPM) Administrator Console, and take the appropriate action.

Possible causes for the alert include the following:

  • A replica creation job did not complete successfully—for example, a connection failed or the job was canceled.

  • There were issues with the change journal that marked the replica as inconsistent.

  • There were volume filter bitmap errors.

  • DPM determined that the protected computer shut down unexpectedly.

  • The replica was valid, but the administrator opted to run a consistency check; therefore, DPM marked the replica as inconsistent.

For SQL Server and Exchange Server:

Possible causes for the alert include the following:

  • DPM ran out of bitmap space on the protected server.

  • Possible owner nodes have been added for a protected cluster resource.

  • The propagation of DPM configuration information (such as volume filter information) about clustered resources failed to detect all possible owner nodes.

For Exchange Server only:

Possible causes for the alert include the following:

  • The Eseutil.exe utility check failed on a replica.

  • The path of the database or log files changed.

  • DPM detected a new Exchange Server database on the application server. The replica is marked as inconsistent, and the synchronization fails.

  • DPM detected an unplanned cluster failover.

For Windows SharePoint Services:

Possible causes for the alert include all of the SQL Server causes, as well as the following:

  • A component has been added to the protected farm.

For Virtual Server:

  • A new disk was added to a virtual machine.

  • Paths to any virtual hard drives changed.


The error conditions and recommended actions associated with each “Replica inconsistent” alert are provided in the alert details.

Follow the recommended action in the alert, and retry the job.

  • To remove the inconsistencies with the data source, a consistency check must be performed on the specified replica.

  • If a daily consistency check is scheduled for the protection group, DPM will automatically perform the consistency check at the next scheduled time. For information about scheduling a daily consistency check, see How to Modify Protection Options.

    If the consistency check fails, the database on the protected computer is corrupt and needs to be manually corrected. Otherwise, you need to manually perform a consistency check on the replica. For more information, see How to Synchronize a Replica.

  • For Exchange Server, if Eseutil.exe is not installed on your DPM server, copy the Eseutil files from the computer running Exchange Server in the folder <drive letter>:\Program files\Microsoft Data Protection Manager\DPM\bin. For more information about Eseutil files, see How to run Eseutil on a computer without Exchange Server (

    Do not copy the Eseutil.exe 64-bit version onto a 32-bit DPM server.
    If Eseutil.exe is installed on your DPM server, ensure that the version on the DPM server is the version of Eseutil.exe that is running on your protected computers running Exchange Server.

Resolved when: DPM verifies the replica. When the verification task starts, this alert changes to the “Verification in progress” alert.

See Also