We have two mail servers (Exchange 2007, SP0, Windows 2008, patch level unknown) - mail01 and mail02 which are running high availabilty CCR (Cluster Continous Replication). mail01 is the "backup" at this point with mail02 running the full production copy. When mail02 fails over to mail01, the cluster goes down.
We try to reseed the cluster using the "Suspend-StorageGroupCopy" but this always times out no matter how high the timeout value. (Here is an example of the error we receive, this is not from the production machine, but the errors match what we are getting):
C:\>Suspend-StorageGroupCopy -Identity "MBSRVCLUSTER\First Storage Group"
Are you sure you want to perform this action?
Suspending Storage Group Copy "First Storage Group".
Yes Yes to All No [L] No to All Suspend [?] Help
(default is "Y"):y
WARNING: The Microsoft Exchange Replication Service has not responded to the
suspend request in 5 seconds. The service may not be running. Press CTRL-C to
stop waiting for the service to respond, or alternatively, wait another 5
seconds before the operation times out.
Suspend-StorageGroupCopy : The Microsoft Exchange Replication Service has not r
esponded to the suspend request in 10 seconds. The ExecutionTimeout period has
elapsed. Operation exited without receiving a confirmation from the Microsoft E
xchange Replication Service. The service may not be running. Get-StorageGroupCo
pyStatus cmdlet will show updated status when the service completes the suspend
request. Resume-StorageGroupCopy will clear the request.
At line:1 char:25
+ Suspend-StorageGroupCopy <<<< -Identity "MBSRVCLUSTER\First Storage Group"
When we run "Get-storagegroupcopystatus" we always get " Initializing". Here is a copy from the production mail01 Exchange Command Shell: (also attached as an image)
Name SummaryCopySt CopyQueueLeng ReplayQueueL LastInspecte
atus th ength dLogTime
---- ------------- ------------- ------------ ------------
Customer Contact Initializing 0 0
Information Systems Initializing 0 0
Executive Initializing 0 0
Human Resources Initializing 0 0
Public Folders Initializing 0 0
We are then unable to "reseed" mail01 to allow CCR to continue to run. When mail02 goes down the cluster fails. When checking mail01 log files, they do not match mail02 and are not synced.
Any ideas how to get this cluster up and running again?