Failover Clustering - Cluster Sets

Lanky Doodle 226 Reputation points
2021-02-10T16:10:15.217+00:00

Hi,

I was just wondering about Cluster Sets. Does this overcome the requirement of having the CPUs aligned to not have to use processor compatibility for failover VMs between nodes; a lot of what I read about Cluster Sets is the ability to use hardware diversity.

Also, can you can the individual clusters be different sizes, in terms of nodes?

Thanks

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,538 questions
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.
969 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Mico Mi 1,921 Reputation points
    2021-02-11T05:51:29.19+00:00

    Hi,
    Please check the following docs:
    Processor Compatibility Mode in Hyper-V

    If you plan to move virtual machines, without rebooting them, between virtualization hosts that may use different generations of processors, you should enable processor compatibility mode. For example, you would enable processor compatibility mode to ensure that you can live migrate your virtual machines between cluster nodes that use different processor feature sets. You could also use processor compatibility mode to save a virtual machine and restore it on a host computer that has a different processor feature set than the source host.

    Performance Impact of Hyper-V CPU Compatibility Mode

    Planning Failover Cluster Node Sizing

    So let’s say you have 1,000 VMs… if you have a single 32-node cluster, and the entire cluster goes down, that means all 1,000 VMs go down. Where if you had them broken into two 16-node clusters, then only 500 VMs (half) go down. Defining fault domains can protect you from cluster class failures.
    The larger the cluster, the more nodes Dynamic Optimization has to work with and the better balancing it can achieve. So while creating multiple smaller clusters may divide up multiple fault domains, creating too small of clusters can increase the management and keep them from being utilized optimally. Defining a larger cluster creates finer granularity to spread and move across.

    Thanks for your time!
    Best Regards,
    Mico Mi

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.