Cluster Sets in Windows Server 2019 – Hyperscale for Hyperconverged !!


Sets is a new feature in Windows Server 2019 that was first introduced at Ignite 2017 Sets is the new cloud scale-out technology that increases node count in a single Software Defined Data Center (SDDC) cloud by orders of magnitude. A Cluster Set is a loosely-coupled federated grouping of multiple Failover Clusters: compute, or hyper-converged.    The Cluster Sets technology enables virtual machine fluidity across member clusters within a cluster set and a unified namespace across the set in support of fluidity.

Cluster Sets gives you the benefit of hyperscale while continuing to maintain great resiliency.  So in more clearer words, you are pseudo clustering clusters together while not putting all your eggs in one basket.  You can now have multiple baskets to maintain greater flexibility without sacrificing resiliency.

While preserving existing Failover Cluster management experiences on member clusters, a Cluster Set instance additionally offers key use cases, such as lifecycle management. The Windows Server Preview Scenario Evaluation Guide for Cluster Sets provides you the necessary background information along with instructions to evaluate cluster sets technology using PowerShell.

Here is a video providing a brief overview of what Cluster Sets is and can do.

The evaluation guide to read more about Cluster Sets along with information on how to set it up is listed on the Microsoft Docs page where this, and numerous other Microsoft products are covered.  The quick link to the Cluster Sets page is .

Finally, there is a GitHub lab scenario where you can set this up on your own and try it out that gives you additional instructions.

We hope that you try it out and provide feedback.  Feedback can be done in two ways:

    1. The Feedback Hub on Windows 10
    2. Email Cluster Sets Feedback .  This alias has been set up to provide feedback only.

John Marlin
Senior Program Manager
High Availability and

Follow me on Twitter @JohnMarlin_MSFT


This article was originally published by Microsoft's Failover Clustering. You can find the original article here.