Separate a cluster set’s management plane from its member workloads

Source facts

A cluster set combines multiple failover clusters into a larger fabric while preserving an individual cluster as the software fault boundary. Its management cluster hosts the available management plane and namespace-referral Scale-Out File Server, separate from member clusters running VM workloads. Member servers in the set must use the same operating-system version; Microsoft does not support live migration across differing operating systems in this configuration. Microsoft documentation.

Applicability

Inventory the proposed member clusters, management cluster, operating-system releases, workloads, and storage paths. Review the source prerequisites before interpreting cluster-set scale as permission to mix incompatible members.

DSE recommendation

Document the management functions and the workloads separately, with an owner and failure response for each. Have the platform team review the member boundaries and the proposed migration paths. Keep the management-cluster dependency explicit in the design and maintenance plan.

Verification

Test representative management operations and an approved VM movement within the proposed set. Examine the expected behavior during a controlled member-cluster interruption. Record which functions remain available and any unresolved dependency, then compare those results with the documented fault-boundary design.

Official references

Microsoft Learn: Deploy a cluster set for Windows Server Failover Clusters. Source reviewed September 8, 2026.