Failing over CMS
Running Exchange 2007 SP2 on Windows 2008 Server SP2, SCC Active/Passive nodes (nodea.domain.com and nodeb.domain.com, cms cms.domain.com).
Currently, cms.domain.com is on nodea.domain.com. I want to fail this over to nodeb.domain.com so I can replace a part on nodea.domain.com
I was thinking:
1. Use Exchange Management Console (Clustered Mailbox Properties) to move CMS from nodea to nodeb just before maintenance time.
Problem is - this will leave the Quorum owner nodea.domain.com.
Will this cause an issue? Is it ok for the quorom to move to nodeb when I shut down nodea? How else can I move it? If I go to Failover Cluster Management > Services and Applications, then there is only one application listed there, the CMS. I can't see
how I can move the Quorum without rebooting the server itself.
February 28th, 2011 2:17pm
Move the quorum prior to shutting down node 1.
You can achieve this using the cluster.exe cmdline tool.
Michael
Free Windows Admin Tool Kit Click here and download it now
February 28th, 2011 2:53pm
Hi
You can use
Cluster.com group "Cluster group" /move:PassiveNodeName
http://myitforum.com/cs2/blogs/yli628/archive/2008/05/11/use-move-clusteredmailboxserver-cmdlet-to-transfer-cms-to-a-passive-cluster-node.aspxJonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog:
http://www.testlabs.se/blog | Follow me on twitter:
jonand82
March 1st, 2011 4:14am
Is there any way to actually see the Cluster Group in the Failover Management Console? All I can see is the Exchange virtual server resources?
Free Windows Admin Tool Kit Click here and download it now
March 8th, 2011 5:36am