cartergspot
asked on
Replica is inconsistent on Windows Storage Server Protection group for Exchange 2007 mailstores
We have recently installed A Dell Powervault running Windows Storage Server 2003 R2 x64. On it, we are using Data Protection Manager 2007. We have created protection groups for our 3 servers. They are all working fine, with one exception: On our Exchange 2007 server (running Windows 2003 R2 x64 Standard), the stores will not back up, because every time create the protection group for them, when it begins creating the replica, it says "data is inconsistent" and won't progress. If you try to manually launch a consistency check at this point, it does the same thing. This happens on both the first and second storage group (all the groups we have). The error in event viewer states the following:
The replica of First Storage Group on mailserv1.xxxxx.xxx is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3163)
DPM has detected a discontinuity in the log chain for First Storage Group on mailserv1.xxxxx.xxx since the last synchronization. (ID: 30216)
(I have removed our domain name for security reasons).
I have tried the following (before doing all of these, I deleted, did the item, then recreated the protection group):
1) Ran a full NTBackup to properly truncate and otherwise handle the log files on the exchange server.
2) Trying both the 32 bit and 64 bit versions of eseutil.exe and ese.dll
3) Unchecking the "use eseutil to verify database integrity" option when creating the protection group
It was suggested I remove, reboot, and repush the agent onto the exchange server, but I can't imagine why this would work, considering the other three items (two drives and a the system state) on the exchange server all seem to be functioning fine. It's specifically the exchange stores.
Another thing to note is that when doing the consistency check, DPM 2007 labels the stores "replica is inconsistent" fairly quickly.
Any ideas?
The replica of First Storage Group on mailserv1.xxxxx.xxx is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3163)
DPM has detected a discontinuity in the log chain for First Storage Group on mailserv1.xxxxx.xxx since the last synchronization. (ID: 30216)
(I have removed our domain name for security reasons).
I have tried the following (before doing all of these, I deleted, did the item, then recreated the protection group):
1) Ran a full NTBackup to properly truncate and otherwise handle the log files on the exchange server.
2) Trying both the 32 bit and 64 bit versions of eseutil.exe and ese.dll
3) Unchecking the "use eseutil to verify database integrity" option when creating the protection group
It was suggested I remove, reboot, and repush the agent onto the exchange server, but I can't imagine why this would work, considering the other three items (two drives and a the system state) on the exchange server all seem to be functioning fine. It's specifically the exchange stores.
Another thing to note is that when doing the consistency check, DPM 2007 labels the stores "replica is inconsistent" fairly quickly.
Any ideas?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
I'm having this same issue, my replica volume is as follows- 30.33 GB allocated, 16.36 GB used, Recovery point volume allocated- 31.13 GB, 1.91 GB used
I found that with my 2007 cluster that the databases needed to be reseeded once on the fail over box. I was able to back it up using NTBACKUP but for some reason the DPM saw it as inconsistent.
Is circular logging turned on? It needs to be off. Express full backup will truncate logs, which is frequently why it is on.
http://technet.microsoft.c
For error:
30216 - DPM has detected a discontinuity in the log chain for <data source type> <data source name> on <server name> since the last synchronization.
Actions:
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.
http://technet.microsoft.c
For error:
30216 - DPM has detected a discontinuity in the log chain for <data source type> <data source name> on <server name> since the last synchronization.
Actions:
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.
I am having the same problem, and also have circular logging off, did a full backup with ntbackup to ensure proper truncation, etc. In my case with non-clustered Exchange 2003. The store appears to backup correctly, but the replica becomes inconsistent as soon as DPM starts the log replication.
I am coming to the conculsion that DPM is not really ready for production use. Good concept though.
I am coming to the conculsion that DPM is not really ready for production use. Good concept though.
hey everyone,
why don't you try to change the location for backing up system state to another location, for exmple D: PARTITION, from the Datasourcefolder, found in the path:
Microsoft Data Protection Manager\DPM\Datasources\PS
why don't you try to change the location for backing up system state to another location, for exmple D: PARTITION, from the Datasourcefolder, found in the path:
Microsoft Data Protection Manager\DPM\Datasources\PS
As of right now I only have one storage group successfully being backed up by the DPM on that server. I have run the ESEUTIL on the groups but none of them had any errors. I have done everything that you have done also except for removing the agent from the servers and reinstalling it. But I agree with you that it is unlikely that would yield any positive results seeing how one of my storage groups is still being protected.
The only thing I can think to do next is add a new volume, delete the storage group, and then re-create it on the new volume. Like I said this work for about a month. Not really sure what the issue could be at the point.