Total failure of the Active Production node on Exchange Server 2007 CCR

Hi,

What should I do when the Active Production site of Exchange CCR mailbox node is lost or corrupted entirely ?

My understanding is that the passive node can only receive update or replication from the active node and cannot be forced to replicate to the active node.

can anyone please explain to me ?
LVL 9
Senior IT System EngineerIT ProfessionalAsked:
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.

Adam FarageSr. Enterprise ArchitectCommented:
Did this happen in your production lab, or are you just asking? It is painful in Exchange 2007 to recover, but here goes nothing..

Part one - Evicting the active node

Before you evict the node, you should force the CMS to the passive node. This allows mail to continue to flow as you rebuild this mess. You can do this using the following command..

Move-ClusteredMailboxServer -Identity:CMSName -MoveComment:"Evicting Node Failure" -TargetMachine:PassiveMachineFQDN

Open in new window


Once this is done (might fail because the Active node is not online) then you can evict the old node:

Server 2008 Command

Cluster <ClusterName> node <FailedNode> /evict 

Open in new window


If this fails, you will have to force eviction

Cluster <ClusterName> node <FailedNode> /force

Open in new window


Server 2003 Steps

http://technet.microsoft.com/en-us/library/cc784955(v=ws.10).aspx


Afterwards you should reset the following:

1) Delete all DNS entries for the evicted node
2) Delete all AD entries for the evicted node

After this is done, rebuild the machine with the same FQDN, IP and OS / Patch level as the previous one / same patch level and OS as the active node in the current cluster. Make sure to add this machine to the domain.

Part two - rebuilding your Clustered Mailbox Server

Once you have the new server online, you will need to install the passive mailbox role onto it. You can do this by following these steps here: http://technet.microsoft.com/en-us/library/bb123674(v=exchg.80).aspx

Once this is done, you will need to run the following command *after* stopping cluster services.

Setup.com /recoverCMS /CMSName:ClusterName /CMSIPAddress:IPofCluster

Open in new window


Once this is done, you may need to bring the system attendant service online and reseed the cluster.

More information about the command above
http://technet.microsoft.com/en-us/library/bb124095.aspx

It has been a while since I have done this, so if you run into a snag let us know.
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
Senior IT System EngineerIT ProfessionalAuthor Commented:
This is happening on the test lab, not a production environment, so I wonder whatis the best suggested way to recover from the DR situation with 15 Storage Groups in total of 2.6TB for the 2x mailbox server role spanned across two different AD site in single domain.
0
Adam FarageSr. Enterprise ArchitectCommented:
The method I provided above is the way it *should* be done.
0
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.