Questions on Exchange corruption
Posted on 2011-09-10
Environment: Exchange 2007 SP2 on Windows 2008 Server SP2. CCR/SCC clustering in place with SCR.
Example scenario: Due to a driver issue, we recv 10xx alerts on our Exchange servers indicating that there is some corruption within the database. From my understanding, CCR is better in this scenario as the corruption can't be replicated to the passive node due to the Inspector directory. With SCC, on the other hand, there is only one set of data, so my possible options are:
i. Move mailboxes on affected DB to another new DB
ii. Restore from backup
iii. Run ESEUtil /p to hard repair the database (last resort).
I was hoping someone could answer some queries I had on this:
1. Am I correct that most types of data corruption cannot be replicated with CCR/SCR technology. In which case, if the error happened on a CCR cluster, the best option would be to fail over to the passive node.
2. If this happened on an SCC cluster, then the 'move mailbox' idea is the best? However, how can we ensure that we don't carry any corruption across/have any data loss when the mailboxes are moved?
3. If we did decide to use ESEUtil /p, it would be safest to backup the database first. However, I always thought backups would fail if attempting to backup a database that had corruption?
As I mentioned, this is an example scenario.