A campus cluster is a failover cluster that distributes nodes and data across two physical racks in separate rooms or buildings within the same campus. This topology keeps your workloads available when an entire rack goes offline, such as during a power, network, or cooling outage.
This article shows you how to create a four-node (2+2) Storage Spaces Direct campus cluster on Windows Server 2025 or later, with two nodes in each rack-level fault domain. The cluster uses Storage Spaces Direct for storage and Resilient File System (ReFS) for the file system.
For more information about campus cluster architecture, supported configurations, and how it compares to other topologies, see Failover Clustering topologies.
Prerequisites
- Windows Server 2025 or later with the 2025-12 security update (KB5072033) installed on every server that will be part of the cluster.
- All-flash capacity drives of the same type on every node (SSD or NVMe). Don't use HDDs and don't configure a caching tier.
- An equal number of nodes in each of the two rack-level fault domains. For supported node configurations, see Failover Clustering topologies. This article shows the 2+2 configuration.
- Exactly two rack-level fault domains, with cluster nodes spanning both racks.
- Direct-attached storage that follows your hardware original equipment manufacturer (OEM) guidelines, including driver versions.
- A quorum witness (file share witness, disk witness, cloud witness, or USB witness) in a third physical location, separate from the two campus cluster racks.
For optimal performance and resiliency, use the following configurations:
- A separate network path from each rack to the cluster quorum resource.
- Redundant top-of-rack (TOR) switches, core switches, and dedicated networks for Storage Spaces Direct storage traffic to minimize single points of failure and maximize workload uptime and durability.
- Network latency of 1 ms or less between racks. Use the PsPing utility to measure network latency.
- Remote direct memory access (RDMA) network interface cards (NICs) and switches to achieve up to 30% CPU savings on your cluster.
Create the campus failover cluster
To create a Storage Spaces Direct campus cluster on Windows Server 2025 or later, complete these high-level steps in order:
- Create a failover cluster without storage.
- Define two rack fault domains.
- Enable Storage Spaces Direct.
- Create volumes on the storage pool.
This section covers the first step: creating the failover cluster without storage.
PowerShell
To create the failover cluster, use the New-Cluster cmdlet.
-
Run PowerShell on your computer in an elevated session.
-
Run the following command to create the cluster without storage:
New-Cluster -Name <ClusterName> -Node <Node1,Node2,Node3,Node4> -NoStorageReplace
<ClusterName>with your cluster name and<Node1,Node2,Node3,Node4>with your node names.
Failover Cluster Manager
To create the failover cluster, use Failover Cluster Manager.
-
From the Windows desktop, open the Start menu, and then select the Server Manager tile.
-
On the Tools menu, select Failover Cluster Manager.
-
In the Failover Cluster Manager pane, under Management, select Create Cluster. The Create Cluster Wizard opens.
-
On the Before You Begin page, select Next.
-
On the Select Servers page, in the Enter name box, enter the name of a server to add as a failover cluster node, and then select Add. Repeat this step for each of the four nodes. When you're finished, select Next.
-
On the Validation Warning page, select Yes to run cluster validation, and then select Next. Complete the Validate a Configuration Wizard.
-
On the Access Point for Administering the Cluster page, enter a name for the cluster. If the servers don't use Dynamic Host Configuration Protocol (DHCP), configure one or more static IP addresses for the failover cluster. Select Next.
-
On the Confirmation page, clear the Add all eligible storage to the cluster checkbox because you configure storage later when enabling Storage Spaces Direct. Select Next.
-
On the Summary page, confirm that the wizard created the failover cluster successfully, and then select Finish.
Define rack fault domains for the campus cluster
After you create the campus failover cluster, define two rack fault domains before you enable Storage Spaces Direct. Rack fault domains tell Storage Spaces Direct how to place data copies across the two physical racks so the cluster can tolerate the loss of an entire rack.
Important: Define fault domains before you enable Storage Spaces Direct. After you create the pool and volumes, data doesn't retroactively move in response to changes to the fault domain topology.
PowerShell
Here's how to define fault domains by using PowerShell.
-
Run PowerShell on your computer in an elevated session.
-
Run the following command to define two rack fault domains, with two nodes in each rack:
Set-ClusterFaultDomain -XML @" <Topology> <Site Name="Campus"> <Rack Name="Room1"> <Node Name="Node1"/> <Node Name="Node2"/> </Rack> <Rack Name="Room2"> <Node Name="Node3"/> <Node Name="Node4"/> </Rack> </Site> </Topology> "@Replace the node names with your actual node names, and update the site and rack names as appropriate for your environment.
-
Verify the fault domain configuration by running:
Get-ClusterFaultDomain
For alternative methods to define fault domains, including by using individual PowerShell cmdlets, see Fault domain awareness.
Failover Cluster Manager
Failover Cluster Manager doesn't support configuring rack-level fault domains through the GUI. Use PowerShell to define fault domains.
-
Run PowerShell on your computer in an elevated session.
-
Run the following command to define two rack fault domains, with two nodes in each rack:
Set-ClusterFaultDomain -XML @" <Topology> <Site Name="Campus"> <Rack Name="Room1"> <Node Name="Node1"/> <Node Name="Node2"/> </Rack> <Rack Name="Room2"> <Node Name="Node3"/> <Node Name="Node4"/> </Rack> </Site> </Topology> "@Replace the node names with your actual node names.
-
Verify the fault domain configuration by running:
Get-ClusterFaultDomain
Enable Storage Spaces Direct on the campus cluster
After you define the two rack fault domains, enable Storage Spaces Direct on the campus cluster. When you enable Storage Spaces Direct, it creates the storage pool and configures it for rack-level fault tolerance.
PowerShell
Here's how to enable Storage Spaces Direct by using the Enable-ClusterStorageSpacesDirect cmdlet.
-
Run PowerShell on your computer in an elevated session.
-
Enable Storage Spaces Direct on the cluster:
Enable-ClusterStorageSpacesDirect -
Update the storage pool to use the latest features:
Get-StoragePool S2D* | Update-StoragePool -
Campus clusters need storage pool version 29 or later for rack-level fault domain awareness. Verify the pool version:
(Get-CimInstance -Namespace root/microsoft/windows/storage ` -ClassName MSFT_StoragePool ` -Filter 'IsPrimordial = false').CimInstanceProperties['Version'].Value -
Verify that the storage pool's
FaultDomainAwarenessDefaultproperty has the valueStorageRack. This value confirms that Storage Spaces Direct places data copies across the two rack fault domains:Get-StoragePool -FriendlyName S2D* | Format-List FaultDomainAwarenessDefault
Failover Cluster Manager
Here's how to enable Storage Spaces Direct by using Failover Cluster Manager.
-
In Failover Cluster Manager, expand the cluster name, and then select Storage > Pools.
-
Right-click Pools, and then select Enable Storage Spaces Direct.
-
Complete the wizard to enable Storage Spaces Direct on the cluster.
-
After enabling Storage Spaces Direct, use PowerShell to update the storage pool and verify the configuration:
Get-StoragePool S2D* | Update-StoragePool -
Campus clusters need storage pool version 29 or later for rack-level fault domain awareness. Verify the pool version:
(Get-CimInstance -Namespace root/microsoft/windows/storage ` -ClassName MSFT_StoragePool ` -Filter 'IsPrimordial = false').CimInstanceProperties['Version'].Value -
Verify that the storage pool's
FaultDomainAwarenessDefaultproperty has the valueStorageRack. This value confirms that Storage Spaces Direct places data copies across the two rack fault domains:Get-StoragePool -FriendlyName S2D* | Format-List FaultDomainAwarenessDefault
Create volumes on the campus cluster
Create volumes on the Storage Spaces Direct pool based on your resiliency requirements. For a 2+2 campus cluster (two nodes in each of two racks), use four-copy mirrored volumes. A four-copy volume places one copy of data on each node, so the cluster can survive the loss of an entire rack and one additional node at the same time.
The following table compares the two volume resiliency options for a 2+2 campus cluster:
| Volume type | Storage efficiency | Fault tolerance |
|---|---|---|
| Four-copy mirror | 25% | Survives loss of an entire rack plus one additional node. |
| Two-copy mirror | 50% | Survives loss of one node. Doesn't survive loss of an entire rack. |
For more information about volume resiliency options, see Fault tolerance and storage efficiency.
PowerShell
To create a four-copy mirrored volume by using PowerShell, follow these steps:
-
Run PowerShell on your computer in an elevated session.
-
Run the following command to create a four-copy volume:
New-Volume -FriendlyName "FourCopyVolume" ` -StoragePoolFriendlyName S2D* ` -FileSystem CSVFS_ReFS ` -Size 500GB ` -ResiliencySettingName Mirror ` -PhysicalDiskRedundancy 3 ` -ProvisioningType Fixed ` -NumberOfDataCopies 4 ` -NumberOfColumns 3To create a two-copy volume instead, set
-PhysicalDiskRedundancy 1and remove the-NumberOfDataCopiesand-NumberOfColumnsparameters. To use thin provisioning, change-ProvisioningTypetoThin.
For more information about resiliency types and storage efficiency, see Fault tolerance and storage efficiency.
Failover Cluster Manager
Here's how to create volumes using Failover Cluster Manager. To create four-copy volumes, use PowerShell.
-
In Failover Cluster Manager, expand the cluster name, and then select Storage > Pools.
-
Right-click the S2D storage pool, and then select New Virtual Disk.
-
In the New Virtual Disk Wizard, enter a name for the volume.
-
On the Storage Layout page, select Mirror.
-
On the Resiliency Settings page, select Two-way mirror for a two-copy volume.
-
On the Provisioning Type page, select either Fixed or Thin.
-
Specify the size for the volume and complete the wizard.
-
After you create the virtual disk, right-click it and select New Volume to format it by using ReFS.
Scale the campus cluster by adding nodes
You can grow a campus cluster from 1+1 to 2+2, 3+3, 4+4, or 5+5 by adding one node at a time to a rack and then to the cluster. For each new node, first add it to the rack fault domain by using New-ClusterFaultDomain, and then add it to the cluster by using Add-ClusterNode.
The following example adds Node5 to Room1 and Node6 to Room2:
$nodeName = 'Node5'
$rackFaultDomainName = 'Room1'
New-ClusterFaultDomain -Type Node -Name $nodeName -FaultDomain $rackFaultDomainName
Add-ClusterNode -Name $nodeName
$nodeName = 'Node6'
$rackFaultDomainName = 'Room2'
New-ClusterFaultDomain -Type Node -Name $nodeName -FaultDomain $rackFaultDomainName
Add-ClusterNode -Name $nodeName
Repeat the pattern, alternating racks, until you reach your target configuration. Always keep an equal number of nodes in each rack.
Related content
- Deploy a quorum witness
- Fault domain awareness
- Announcing support for S2D Campus Cluster on Windows Server 2025
Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors (upstream author metadata: robinharwood). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
