Exchange 2007 Cluster - Outage Causing "Split Brain" - Lost Emails

We have a two node Exchange cluster (CCR) that experienced a non controlled outage on one of the nodes today (outage at 1pm). We have 5 Information Stores, and four of them came up on the Passive node with no problem. The fifth looked at first like it worked but then we realized that it was missing emails from the last week.

We then realized that on the Node B (Originally passive, now active) it showed that Information Store as "Initalizing" and the Information Store Logs had not been replicated for over a week from Node A.

We tried to dismount (and suspend replication) the broken Information Store and transfer back to Node A (used the -IgnoreDismount switch) and it worked but we then had all emails prior to the outage but none between 1pm and 5pm when we took down the server again for maintenance. We then realized that the log files were re-creating on Node A and were conflicting with the log files on Node B. At this point I think we have a "Split Brain" convergence of the Information Stores. We have a backup and snapshot of both Node A and Node B .edb and log files before we started to troubleshoot this problem so we could roll back.


Are there any options? Is the best option to get Node A working up to 1pm, re-seed Node B, then use the backup of Node B .edb and log files into a DR environment and then just export the changes since 1 pm in mail to a PST (and give to the users)? Are there better options? Could we use the Exchange Recovery Group?
rsp_itAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rsp_itAuthor Commented:
We don't think an eseutil /r will work on Node A since the log file file names are the same as Node B. It feels like a split brain and our only option is to choose one of the versions of the DB and then go from there trying to recover as much data as we can between 1pm and 5pm.
0
rsp_itAuthor Commented:
We ended up resolving this ourselves by moving back to Node A, losing information between 1pm and 5pm. Then we used Recovery Storage Groups with Node B's database version and the "merge" functionality to get the old emails between 1pm and 5pm back.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.