Failover Cluster with S2D - VM failing over to Node that is booting up

Ludvig Göransson 6 Reputation points

I have 3 servers running Windows Server 2022 Datacenter edition with a failover cluster and storage spaces direct. When I tested the failover capability, I turned off node-2 that had a VM on it. Node-3 was booting up and Node-1 was operating normally. The VM failed over to Node-3 that was booting which naturally meant that the VM was down until Node-3 had booted up. How could I make it so that the VM fails over to a properly operating node?

Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
975 questions
0 comments No comments
{count} vote

1 answer

Sort by: Most helpful
  1. Limitless Technology 39,506 Reputation points

    Hi LudvigGransson-5193,

    First of all, was the VM that failed over to the booting Node a HA service? ie was it a File Server? When configuring your Cluster, you can set which services should be HA, in which case any VMs performing those roles will failover to the next available Node in the cluster (not one that's booting). Also, do you have a Quorum set up in your cluster? If not, I strongly suggest that you do in order to manage the failover activity in the most efficient way.

    I would suspect that the VM in questions was deemed low priority and therefore waited until the 3rd Node was booted before transferring.

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments