As the subject says, I've built a fresh install w2k8r2 and sql2k8r2 failover cluster.
Sql works fine on the primary node, but when I test a failover it breaks.
Specifically, if I were to stop the node1 cluster service (causing the cluster to switch to node2), windows changes the cluster DNS appropriatly and moves the shared storage just fine, but sql server doesn't failover. Server Name, Disk Drives and Other
Resources all go offline.
I've verified that the advanced policies of the server name, IP, cluster drives all have both nodes checked as possible owners
However, Other resources only lists node1 as a possible owner and there appears to be no way to add node2. Under the Other resources, SQL Server and SQL Server Agent are listed.
I'm sorta stumped, I've been combing the forums and have found similar issues, but nothing seems to explain why the two resources won't failover.
View Complete Post