November 13, 2013 at 4:52 pm
We failed over the services to the passive node. In this process quorum has not moved to the passive node although all the resources moved to the other node. Does it will have any affect or is it expected ? Can we move the quorum resource to other node?
November 14, 2013 at 2:41 am
The clustergroup doesn't failover automatically along with the application groups.
You can safely move this group on to the active cluster. Im not aware of any impact if you don't. Its just a preference.
November 14, 2013 at 8:33 am
MysteryJimbo (11/14/2013)
The clustergroup doesn't failover automatically along with the application groups.You can safely move this group on to the active cluster. Im not aware of any impact if you don't. Its just a preference.
Thanks Jimbo. But how to move the quorum to the active node. I don't get any option when I right click on the quorum drive for move resource to another node. We are planning to patch the passive node in couple of days. I got the option simulate failure of this resource. This is what we need to do ?
If we restart the node automatically does it move to the active node ? Please advise.
November 14, 2013 at 9:04 am
I tried it on a test server using the command prompt command. I can move the cluster group but i still see the quorum drive on the passive node only. It's not moving to the active node.
November 14, 2013 at 9:14 am
Restarting the passive node would do it, but that's overkill.
I use powershell when moving the cluster groups around.
Get-ClusterGroup
Get-ClusterGroup | Move-ClusterGroup
November 14, 2013 at 9:24 am
muthyala_51 (11/14/2013)
I tried it on a test server using the command prompt command. I can move the cluster group but i still see the quorum drive on the passive node only. It's not moving to the active node.
From a command prompt run the follwoing and note the results for the QUORUM group
cluster group
Use the following to move the group
cluster group QUORUM /moveto:newnode
Once done, run this again and check
cluster group
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 14, 2013 at 10:53 am
Perry,
I try to do it but it failed throwing the following error--
System error 5013 has occurred (0x00001395).
The cluster group could not be found.
I can see the cluster group status from the command cluster group. It's on node1 and online.
November 14, 2013 at 10:59 am
Can you post the output please
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 14, 2013 at 11:01 am
actually i found an article .......
Actually you don't need to. This layer of clustering has been abstracted from the administrator as it used to cause confusion for some administrators in Windows Server 2003 server clusters. Now this is managed entirely by the cluster service. If you shut down the node that contains the quorum disk (if you're using that mode), it will automatically be moved to another node.It's not something you need to deal with any more.
November 15, 2013 at 1:54 am
You should still be able to move it using the commands above, works just fine for me
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 19, 2013 at 11:18 pm
Here is the exact command line to move the Disk Witness in Quorum.
Literally just copy and paste this without changing a word.
Open Command Prompt as Administrator.
cluster group "Cluster Group" /move
Just did it in production with no issue.
Good Luck
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply