Protection of Exchange 2012 SP1 DAG with DPM 2012R2 not working - Replica is Inconsistent

Question

We are struggling to get DPM 2012 R2 to protect our Exchange 2013 SP1 DAG, and receiving the error "Replica is inconsistent". I have copied the current versions of eseutil.exe and ese.dll to the DPM servers, and the DPM agent is the latest version
on the Exchange boxes.
The sanitised error is:
Affected area: Database123
Occurred since: 10/11/2014 11:39:02
Description: The replica of Exchange Mailbox Database Mailbox Database123 on <servername> 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.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
 Data consistency verification check failed for LOGS of Exchange Mailbox Database Mailbox Database123 on <servername>. (ID 30146 Details: The extended attributes are inconsistent (0xFF))
 More information
Recommended action: Either the database files are corrupt or the proper versions of the Eseutil.exe and Ese.dll files are missing.
If you have recently upgraded your Exchange server, copy them from that server to the DPM server.Contact your Exchange server administrator, and then verify the issue. You can recover the last known good backup to address the corrupted state.
 Synchronize with consistency check.
 Run a synchronization job with consistency check...
Resolution: To dismiss the alert, click below
 Inactivate
Running a synchronization job with consistency check does not work and we end up back to the same error. Circular logging is not enabled.
We are starting an upgrade of Exchange 2007 to 2013 and the DAG has little in it yet, and the Exchange 2007 environment is being backed up by a different product that we are moving away from.
Any suggestions welcome
Mark

Answer 1

Hi,
Has any testing been done with the
option to run Eseutil on the backup not enabled via the DPM GUI when creating protection, and identifying if DPM reports the same error?
Also
with Eseutil enabled I recommend reviewing the below links which, may assist with the issue being faced. The first link aligns with the error reported (ID
30146). The second outlines high level overview for protecting Exchange 2013.
https://social.technet.microsoft.com/Forums/en-us/home?forum=dpmexchbackup&announcementId=0d4fcbc7-199c-4f7a-813a-862437c0aa4e
http://technet.microsoft.com/en-us/library/dn751026.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community
members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."