December 1, 2011 at 10:24 am
Windows Server 2008 R2 (SP1)
SQL Server 2008 (SP2)
Active/Passive cluster
Yesterday we were having errors on Active side of the cluster, but the application and database were performing fine. So we let it go until the evening, then did a controlled hold on the application, then a failover to Node2 of the cluster. This fixed the errors we were having yesterday. We brought everything back online.
After everything was rolling again and everyone had signed off, I noticed that the Quorum Disk was still assigned to Node1 of the cluster. Every other resource is on Node2.
I found the command line method to manually move the Quorum Disk to the other node. There does not appear to be a GUI way to do it. I need to more the Disk Witness in Quorum to the other node because we will be rebooting Node1 a few times. I am sure it will move if I reboot the passive side. Just not sure of the effect on Node2.
I suspect that the Disk Witness in Quorum will just move over to Node2 with no impact on the Active SQL Server processes or the application. But I am not positive. I don't have a QA cluster to test this on.
My question is this: Is there any impact on the active Node while that Quorum Witness Disk is moving from the passive side to the active side? Is this something I can do in the middle of the day? The websites where it showed me the command line did not seem to indicate the effect on the active node.
Thanks,
James
December 1, 2011 at 10:29 am
For the brief moment while transitioning the cluster will not see it (milliseconds maybe). And in case it doesn't move successfully then it could be longer. I would do it after hours as minimal impact as it may be or as quick as it may go. I like to play it safe.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 1, 2011 at 10:56 am
Right after I posted my question, one of our server admins arrived at work (late). He knew the answer. He said it is not an issue. It moves between nodes manually in about 5 seconds.
I found out we do have a VM cluster for QA, so I did some testing on it. It does move seemlessly between nodes without any impact on the SQL Server processes.
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.
December 13, 2011 at 6:32 am
I have seen this behaviour of cluster quorum disk in Windows Server 2008. If you want to do this from GUI, I think (I haven't checked it)simulating quorum disk for failure will move it to active node from passive node.
Anyways, doing it from CMD (which you have done) is the better way.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply