I didnt install or configure the cluster but it appears to be setup correctly
per Microsoft standards. Now I'm attempting to test the failover of it
before we add any databases to it.

When I initiate a failure of the SQL Server Service on the active node from
the Cluster Administrator or just stop the service from the Services snap-in,
it doesn't initiate a failover to the 2nd node. Rebooting the server works
to cause the failover, stopping the cluster service works to cause a
failover, but whenever I stop the SQL service it does not. Any ideas on why
this wouldn't cause a failover? Is there something missing in the
configuration?

The first default behavior on a cluster is to restart the service if all the
dependencies are online or can be brought online. I suggest using the
cluster admin tool to move the group. That will test whether the group cna
successfully start on the alternate node.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Rich" <Rich (AT) discussions (DOT) microsoft.com> wrote