Hotfix: “Replica is inconsistent” error with ID 112 (0x8007007B) with DPM 2007 SP1 on a Windows Server 2003 x64
Filed Under (Data Protection Manager) by Just An Admin on 23-01-2009
After applying Data Protection Manager Service Pack 1 on a server running Windows Server 2003 x64, a replica may be listed as inconsistent with error ID 112 (0x8007007B).
In the DPM Administrator Console, a critical alert may be listed as in the following example:
Affected area: C:
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)
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)
Changes for Volume C:\ on servername.domainname.com cannot be applied to \\?\Volume{b071dcc8-8a9e-11dd-901d-806e6f6e6963}\WINDOWS\Debug\UserMode\ChkAcc.bak\. (ID 112 Details: The filename, directory name, or volume label syntax is incorrect (0x8007007B))
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
Inactivate alert
Even at Barca and Bayern, where they have more experience, I always played the games and thought, 鈥榃ow Im lucky.