We have several 2 node Microsoft 2008 Server Failover Clusters. Mostly SQL and File Servers. Currently we have Node and Disk Majority setup as the quorum model. On occasssion when nodes are patched and restarted - specifically noticed when both nodes have to be shutdown, the cluster won't start when only 1 node is brought back online. Initially thought these rare occassions were when one node owned the quorum drive and the other node owned the application/service. Then when both nodes are off one is powered up and of course the cluster won't start until I bring up the other node or forcequorum. My questions are as follows: (all based on the above 2 node cluster with node and disk majority quorum model)
1. If node 1 is powered off, ALL resources/applicatons and quorum drive if owned by node 1 moves to node2 as long as the node is functioning properly CORRECT?
2. Assuming everything moved to node2 and node 1 is powered off. If node 2 then is powered off - it has nothing to failover to so I assume that node 2 has the last known good cluster configuration and will RETAIN ownership of the applications/resources/quorum disk.
3. Both nodes are powered off and assuming node 2 still is defined as owning the applications/resources. If I power up node 1 in this condition - will this fail to form the cluster because the quorum drive and apps are still on node 2? Is this the rare condition that I mention above.
4. In our lab, I've done every possible combination of tests of powering down, stopping cluster service, keeping both off, turning both on at the same time... you name it. I can't get it to NOT START UP NORMALLY.
Anyone enlighten me on the specific condition that is causing my cluster to not start?