If you had errors in the validation report BEFORE the cluster went down, your configuration is not supported and this is probably the reason for your predicament. If the cluster is still not working, run a full cluster validation an correct any errors.If you have more than two nodes, start enough nodes to establish quorum.Verify that it has a valid connection to the rest of your environment, both networking and storage if applicable.If nothing works, shut down all nodes, then start one node.

If you cannot restart a node, power cycle it. If something works and something does not, restart all nodes one by one.If your cluster has shared storage, call your SAN person and verify that all nodes can access the storage, and that there are no gremlins in the storage and fabric logs.The type of Failover Cluster is somewhat irrelevant for this action plan. I will assume that you have exhausted you normal troubleshooting process to no avail, that your cluster is down and that you do not know why. If your cluster is still down and you are reading this post, you are on the wrong path.īelow you will find a simplified action plan for getting your cluster back online.

In most cases your cluster should self-heal, and all you have to do is figure out what went wrong and what you should do different to prevent it from happening again. Remember that the cluster log is a debug log used for analyzing what went wrong AFTER you get it all working again. Side quest: Basic cluster problem remediation If you are new to Message Analyzer I recommend that you glance at the Microsoft Message Analyzer operating guide while you read this post for additional information. In this post I will show how you can open set of cluster logs from a SQL Server Failover Cluster instance. Microsoft Message Analyzer, the successor to Network Monitor, has the ability to read a lot more than just network captures.

Ms message analyzer