Restart Passive Member of Exchange 2007 CCR Cluster

While restarting the passive node in our CCR cluster all our terminal server users lost connection to Exchange.  It appears that all the storage groups went offline even though the active member ofthe cluster remained up.  

Here was my procedure:

Passive Node:
1) Paused the node in Failover cluster management
2) Suspended replication between the 2 members of the clusters for all the storage groups
3) Test to make sure mail was still working - OK
4) Restart the passive node

Did I do something wrong or is there some sort of problem in my environment.  To my knowledge this should work.

Thanks
K00lguyAsked:
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.

lciprianionutCommented:
I did all this in the past for Ex2007 when it was MS patching time every month without any problems. Steps was like:
1) Patch passive node, reboot
2) move DB + cluster resources to passive node
3) Patch old active one, reboot
4) Move DB back to original active
In my environment at that time I had Exchange, BES, SQL, Enterprise Vault and all this needed to be coordinated in the right order for everything to be OK.
0
Jamie McKillopIT ManagerCommented:
Hello,

Your problem is that you used Failover Cluster Management. Never use Failover Cluster Management with an Exchange cluster. You should always use the Exchange tools to manage the cluster.

In EMC, expand Server Configuration / Mailbox. Right-click your server and select "Properties". Click the "Clustered Mailbox Server" tab. This will show which server is the "Active" server. You can restart your passive server without taking any prerequisite action. If you want to make the other node active, right-click the server and select "Manage Cluster Mailbox Server" then follow the wizard.

The issue is that the Failover Cluster Management tool is not Exchange aware. If you use the Exchange tools, it will ensure that your cluster is managed properly and it will not allow or at least warn you when you attempt to perform an action that will cause the cluster to become unstable or unusable.

JJ
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 ProfessionalCommented:
JJ, does this means that we need to issue Suspend Replication command as well before failing it over ?

if CCR is robust or smart enough then why do we need to use the Move Storage Group cmd to do the failover gracefully ?
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Jamie McKillopIT ManagerCommented:
You cannot suspend the storage group copy before failing over. That will result in the nodes not being in sync. The nodes need to be in sync for a lossless failover.

When you use the Move Storage Group command, it performs checks to ensure the storage group is healthy on both nodes and in a state that would allow failover. If you just reboot the active node, those checks are not performed, which could result in the databases not mounting on the other node.

-JJ
0
Senior IT System EngineerIT ProfessionalCommented:
Thanks JJ.

So even after the failover from the exchange management console, do I need to suspend the replication ?
0
Jamie McKillopIT ManagerCommented:
No, you do not need to suspend the replication.

-JJ
0
Senior IT System EngineerIT ProfessionalCommented:
Ok so when do we need to suspend the replication ? Any scenario to use that command ?
0
Jamie McKillopIT ManagerCommented:
There may be many scenarios when you would need to suspend replication. One I can think of off the top of my head is if you need to reseed a database.

-JJ
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
Outlook

From novice to tech pro — start learning today.