Comments on: Microsoft Cluster Server anomaly http://technology.amis.nl/2006/07/05/microsoft-cluster-server-anomaly/?utm_source=rss&utm_medium=rss&utm_campaign=microsoft-cluster-server-anomaly Fri, 12 Apr 2013 10:04:09 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Jacco Landlust http://technology.amis.nl/2006/07/05/microsoft-cluster-server-anomaly/#comment-3552 Jacco Landlust Sun, 09 Jul 2006 14:42:17 +0000 http://technology.amis.nl/blog/?p=1271#comment-3552 For me this is expected behaviour. The first node of the cluster is started and checks if he can manage the assigned quorum disk. In fact it can, since no other node contacted the quorum disk. So there you have cluster number 1. The second node tries to do the exact same thing, but instead of contacting the same quorum disk, it contacts a new quorum disk. So the second node also “thinks” that the other node is down and start running a cluster.

In the disk manager you could (and should) have checked if the disks were mapped to the same lun. Seems that clustering on Windows is made a bit too easy ;)

]]> By: Marco Gralike http://technology.amis.nl/2006/07/05/microsoft-cluster-server-anomaly/#comment-3551 Marco Gralike Wed, 05 Jul 2006 11:52:24 +0000 http://technology.amis.nl/blog/?p=1271#comment-3551 Great post ;-)

]]>