Data Protection Manager (DPM) will happily fail to backup Exchange if at any point it detects a consistency issue with the log stream. Your choices at this point are basically either dropping the entire protected storage group out of DPM and re-protecting it, or, not having backups. Neither of these are really desirable.
DPM verifies consistency of Exchange backups by running eseutil against the log stream. This is why you have to manually copy eseutil.exe and ese.dll over from an Exchange server after installing DPM. If you use something like Process Explorer, you'll see eseutil.exe as a child process of dpmra.exe when DPM is doing a consistency check.
The good news is that you can tell DPM not to do these consistency checks at least temporarily so you can get into a consistent state and do an Express Full. To do this, right click your Protection Group and select Modify protection group. Click Next until you get to the Specify Exchange protection options section of the wizard. Uncheck the Run Eseutil to check data integrity option:
Resynchronizing should succeed at this point. I wouldn't leave the protection group in this state, but, it's a workaround that does the job.
Comments, Trackbacks, & Pingbacks
#1 re: Working around DPM Consistency Check Failures
Tuesday, February 16 2010 8:48 PM by Prashant#2 re: Working around DPM Consistency Check Failures
Monday, April 05 2010 4:49 PM by Craig ColumbusI'm currently working with RC3 of DPM 2010 and it's still giving major problems with consistency on Exchange 2003. The workaround above sometimes works, sometimes doesn't. Manually running eseutil against the logs shows that all is good, so I'm not sure where the problem is happening. The exposed error messages aren't particularly useful in this case.
This is especially frustrating since SQL and filesystems are working well and staying consistent.
DPM 2010 has new features to handle consistency check problems. See this blog post for details! blogs.technet.com/.../dpm-2010-helpin