In the DPM Administrator Console, a critical alert may be listed as in the following example:
Occurred since: 1/07/2008 4:13:00 PM
Description: The replica of Volume C:\ on servername.domainname.com is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent (ID 3106)
If you run a consistency check, the protection status will be listed as OK until the next synchronization job runs, then the protection status will change to Replica is inconsistent. Installing this hotfix may address the issue.
Recommended action: Synchronize with consistency check.
Run a synchronization job with consistency check…
Resolution: To dismiss the alert, click below
Incoming search terms:
- – dpm system state replica is inconsistent  – Windows Server 2003 replica  – system state replica is inconsistent  – DPM Replica inconsistent  – replica is inconsistent dpm 2010  – dpm 2010 replica is inconsistent  – dpm 2016 error 207 0x8004230C  – dpm 2007 id 207 0x8007000e