Below is the error I recieve in the DPM 2010 Monitoring Alert. I am using Exhange 2010 v 14.01.0289.001 on a Windows 2008 R2 SP1 Enterprise server. DPM 2010 on a Windows Server Enterprise SP2.
I have been getting these erros enough that my transaction log files have taken up all of my hard drive space on the log file drive. So I decided to remove the database from the current protect group and start over.
I created a new protection group and added the 1 mail database, ended up say it was 186GB and 485GB was allocated.
Exchange 2010 is not being backed up by anything else. Circular loggin is not enabled. There is only 1 copy of the database for backup. I have ran the consitancy check with syncronization and still get the replica is inconsistant error. I have also tried to create a recovery point with a full backup and I get an error that tells me: "Cannot perform creation of a recovery point on a replica which is inconsistent. (ID: 31209) Run syncronization with consistency check for this replica and then retry this operation."
This is a vicious circle - there is no solution that I see!! I need some ideas to get successful backups so the transaction logs are removed and email can still be received!
Thanks!
DPM Error:
Affected area: SG1-Def
Occurred since: 8/26/2011 4:13:16 PM
Description: The replica of Exchange Mailbox Database SG1-Default on CHIPMBX01 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)
DPM has detected a discontinuity in the log chain for Exchange Mailbox Database SG1-Def on CHPMBX01 since the last synchronization. (ID 30216 Details: Unspecified error (0x80004005))
More information
Recommended action:
1. Consult the administrator of the Exchange server to rectify the problem. Please ensure that Exchange circular logging is turned off. Synchronization jobs may continue to fail until this issue is resolved.
2. Last backup might have failed after log truncation.
In the Protection task area, click 'Create recovery point' and select 'Full backup' option.
3. If the protected datasource is an Exchange 2010 database, make sure that multiple copies of the database are not protected for FULL backup. DPM supports protecting only one copy of the database using FULL backup and the other copies have to be protected
using COPY backup.
Synchronize with consistency check.
Run a synchronization job with consistency check...
Resolution: To dismiss the alert, click below
Inactivate alert