I believe I am having issues with our cluster but not too sure. Things seem to work at a certain point but fail during a failover. So we have a two node cluster, we will call it MyCluster, with node1 and node2. This cluster is for a Service, and everything seems to work fine until I test failover.
I have an app on my machine, which I connect to the service by using the cluster name "MyCluster", as I always thought you should use the cluster name since you are unaware of the active node. If I restart the active node then my resource drive (E) and the quorum drive (Q) both move over to the passive node making it now the active node.
I can still use the app and connect using the cluster name, but only until node1 comes back online. At that time, the resource drive (E) moves back over to node1, but the quorum drive stays put. Once this happens I can no longer use the cluster name for the application because if I do, it points me to node2 but fails because the resource drive has moved back over to node1.
I have talked to server admin on this issue, and they said according to Microsoft, the quorum drive only moves once the one of the nodes goes completely down, but if comes back up isn't suppose to move back,
I have never setup a cluster before but have worked with them here and there, and was under the impression that all cluster resources should move together. I am misunderstanding something, or is there something not configured properly within the cluster?
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.