In Scenario 2, failure is caused by Node 1 being down or offline but not irretrievably broken. This could be caused by an operating system failure or a hardware failure.
To recover from a failover cluster failure
-
After Node 1 fails, the SQL Server failover cluster fails over to Node 2.
-
Resolve the problem with Node 1.
-
Ensure that the Microsoft Cluster Service (MSCS) cluster is working and all nodes are online.
-
Attempt to fail over SQL Server to the recovered node. If this succeeds, no further action is required, with the exception of normal testing. If SQL Server fails to come online on the recovered node, see >How to: View and Read SQL Server Setup Log Files.
Concepts
Failover Cluster Troubleshooting
How to: View and Read SQL Server Setup Log Files
Other Resources
How to: Rebuild the Master Database for SQL Server 2005
How to: Rebuild the Registry for SQL Server 2005
Help and Information
Getting SQL Server 2008 Assistance