wyclef1
asked on
Exchange corruption and Exchange 2007
Hi
We are running Exchange 2007 SP2 - a mixture of CCR and SCC clusters. All clusters have an SCR target in another data center.
We've had Exchange database corruption problems before on our CCR clusters, and generally we fail them over to the passive CCR node. We then reseed the offending DB on the old active. Is this the right way to do things? From what I understand, CCR replication will not replicate corruption.
However ,how about if we have DB corruption errors on the SCC clusters? Since there is only one set of data, failing over wouldn't help would it?
And how does SCR fit into all this?
We are running Exchange 2007 SP2 - a mixture of CCR and SCC clusters. All clusters have an SCR target in another data center.
We've had Exchange database corruption problems before on our CCR clusters, and generally we fail them over to the passive CCR node. We then reseed the offending DB on the old active. Is this the right way to do things? From what I understand, CCR replication will not replicate corruption.
However ,how about if we have DB corruption errors on the SCC clusters? Since there is only one set of data, failing over wouldn't help would it?
And how does SCR fit into all this?
ASKER
Hello endital1097
Thanks for the reply, so if we had the database corruption issues on CCR, you're saying that failing over to the passive CCR node wouldn't really help as the corruption could follow? I thought the point of the Inspector Directory was to prevent corruption replicating to the passive node?
Thanks for the reply, so if we had the database corruption issues on CCR, you're saying that failing over to the passive CCR node wouldn't really help as the corruption could follow? I thought the point of the Inspector Directory was to prevent corruption replicating to the passive node?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
CCR replicates logs from one node to the other and replays the transactions, so it is possible that corruption could follow
SCR allows you to configure a replay lag time which would give you an opportunity to stop log replay before the corruption occurs (still difficult to catch but possible)