Editorial pass and technical check

robinharwood · robinharwood · commit dfa7bea538a2 · 2026-05-29T17:35:00.000+01:00
diff --git a/WindowsServerDocs/failover-clustering/create-storage-spaces-direct-campus-cluster.md b/WindowsServerDocs/failover-clustering/create-storage-spaces-direct-campus-cluster.md
@@ -1,49 +1,53 @@
 ---
-title: Create a Storage Spaces Direct Campus Cluster on Windows Server
-description: Discover step-by-step instructions to deploy a Storage Spaces Direct campus cluster for high availability and fault tolerance on Windows Server 2025.
+title: Create a Storage Spaces Direct Campus Cluster
+description: Learn how to deploy a Storage Spaces Direct campus cluster for high availability and fault tolerance on Windows Server 2025 or later.
 #customer intent: As an IT administrator, I want to create a Storage Spaces Direct campus cluster so that I can ensure rack-level resiliency for my workloads across two physical locations.
 author: robinharwood
 ms.author: roharwoo
 ms.reviewer: robhind
 ms.date: 01/20/2026
 ms.topic: how-to
+ai-usage: ai-assisted
 ---
 
 # Create a Storage Spaces Direct campus cluster
 
-Learn how to create a Storage Spaces Direct campus cluster on Windows Server 2025 and later. A campus cluster distributes data across two physical racks in separate rooms or buildings within the same campus, providing rack-level resiliency for your workloads.
+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, for example because of a power, network, or cooling outage.
 
-In this article, you'll create a four node campus cluster with two nodes in each rack-level fault domain. The cluster will use Storage Spaces Direct (S2D) for storage and ReFS for the file system. Adapt the instructions as needed for your specific requirements and deployment.
+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.
 
-Campus clusters are different from stretch clusters. Campus clusters use LAN connectivity within the same location with S2D replication, while stretch clusters span geographically distant sites connected by WAN and use Storage Replica for replication.
-
-For more information about the campus cluster architecture, supported configurations, and how it compares to other topologies, see [Failover Clustering topologies](topologies.md).
+For more information about campus cluster architecture, supported configurations, and how it compares to other topologies, see [Failover Clustering topologies](topologies.md).
 
 ## Prerequisites
 
-Before you create a campus cluster, ensure you meet the following requirements:
-
-- Windows Server 2025 with the 2025-12 Security Update (KB5072033) installed on every node in the failover cluster.
-- All capacity drives must be the same type. Flash-based (SSD or NVMe) drives are recommended for optimal performance.
-- A minimum of four nodes, with at least two nodes in each rack-level fault domain.
-- You must define exactly two rack-level fault domains and place the cluster nodes in these two racks.
-- Follow your hardware OEM's guidelines for any shared or direct attached storage including driver versions.
-- Place the quorum resource (File Share Witness, Disk Witness, Cloud Witness, or USB Witness) in a third location, separate from the campus cluster racks.
+- Windows Server 2025 or later with the 2025-12 security update ([KB5072033](https://support.microsoft.com/help/5072033)) installed on every node in the failover 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](topologies.md). This article shows the 2+2 configuration.
+- Exactly two rack-level fault domains, with cluster nodes spanning both racks.
+- Shared or 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:
 
-- Each rack has a separate network path to the cluster quorum resource.
-- Use redundant top-of-rack (TOR) switches, core switches, and dedicated networks for S2D storage traffic to minimize single points of failure and maximize workload uptime and durability.
+- 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](/sysinternals/downloads/psping) utility to measure network latency.
-- RDMA NICs and switches, which can achieve CPU savings on your cluster.
+- 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, complete these high-level steps in order:
 
-## Create the failover cluster
+1. Create a failover cluster without storage.
+1. Define two rack fault domains.
+1. Enable Storage Spaces Direct.
+1. Create volumes on the storage pool.
 
-To create a campus cluster, first create a failover cluster without storage, then define fault domains before enabling Storage Spaces Direct.
+This section covers the first step: creating the failover cluster without storage.
 
 #### [PowerShell](#tab/powershell)
 
-Here's how to create the failover cluster using the [New-Cluster](/powershell/module/failoverclusters/new-cluster) cmdlet.
+Here's how to create the failover cluster by using the [New-Cluster](/powershell/module/failoverclusters/new-cluster) cmdlet.
 
 1. Run PowerShell on your computer in an elevated session.
 
@@ -57,7 +61,7 @@ Here's how to create the failover cluster using the [New-Cluster](/powershell/mo
 
 #### [Failover Cluster Manager](#tab/fcm)
 
-Here's how to create the failover cluster using Failover Cluster Manager.
+Here's how to create the failover cluster by using Failover Cluster Manager.
 
 1. From the Windows desktop, open the **Start** menu, and then select the **Server Manager** tile.
 
@@ -71,24 +75,24 @@ Here's how to create the failover cluster using Failover Cluster Manager.
 
 1. On the **Validation Warning** page, select **Yes** to run cluster validation, and then select **Next**. Complete the Validate a Configuration Wizard.
 
-1. On the **Access Point for Administering the Cluster** page, enter a name for the cluster. If the servers don't use DHCP, configure one or more static IP addresses for the failover cluster. Select **Next**.
+1. 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**.
 
 1. 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**.
 
 1. On the **Summary** page, confirm that the failover cluster was created successfully, and then select **Finish**.
 
 ---
 
-## Define fault domains
+## Define rack fault domains for the campus cluster
 
-After you create the cluster, define fault domains before you enable Storage Spaces Direct.
+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]
-> You must define fault domains before enabling Storage Spaces Direct. Once you create the pool and volumes, data doesn't retroactively move in response to changes to the fault domain topology.
+> 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](#tab/powershell)
 
-Here's how to define fault domains using PowerShell.
+Here's how to define fault domains by using PowerShell.
 
 1. Run PowerShell on your computer in an elevated session.
 
@@ -119,7 +123,7 @@ Here's how to define fault domains using PowerShell.
    Get-ClusterFaultDomain
    ```
 
-For alternative methods to define fault domains, including using individual PowerShell cmdlets, see [Fault domain awareness](fault-domains.md).
+For alternative methods to define fault domains, including by using individual PowerShell cmdlets, see [Fault domain awareness](fault-domains.md).
 
 #### [Failover Cluster Manager](#tab/fcm)
 
@@ -156,13 +160,13 @@ Failover Cluster Manager doesn't support configuring rack-level fault domains th
 
 ---
 
-## Enable Storage Spaces Direct
+## Enable Storage Spaces Direct on the campus cluster
 
-After defining fault domains, enable Storage Spaces Direct on the cluster.
+After you define the two rack fault domains, enable Storage Spaces Direct on the campus cluster. Enabling Storage Spaces Direct creates the storage pool and configures it for rack-level fault tolerance.
 
 #### [PowerShell](#tab/powershell)
 
-Here's how to enable Storage Spaces Direct using the [Enable-ClusterStorageSpacesDirect](/powershell/module/failoverclusters/enable-clusterstoragespacesdirect) cmdlet.
+Here's how to enable Storage Spaces Direct by using the [Enable-ClusterStorageSpacesDirect](/powershell/module/failoverclusters/enable-clusterstoragespacesdirect) cmdlet.
 
 1. Run PowerShell on your computer in an elevated session.
 
@@ -178,55 +182,68 @@ Here's how to enable Storage Spaces Direct using the [Enable-ClusterStorageSpace
    Get-StoragePool S2D* | Update-StoragePool
    ```
 
-1. Verify that the storage pool version is 29 or later:
+1. Verify that the storage pool version is 29 or later. A campus cluster requires storage pool version 29 for rack-level fault domain awareness:
 
    ```powershell
-   (Get-CimInstance -Namespace root/microsoft/windows/storage -ClassName MSFT_StoragePool -Filter 'IsPrimordial = false').CimInstanceProperties['Version'].Value
+   (Get-CimInstance -Namespace root/microsoft/windows/storage `
+       -ClassName MSFT_StoragePool `
+       -Filter 'IsPrimordial = false').CimInstanceProperties['Version'].Value
    ```
 
-1. Verify that the storage pool's `FaultDomainAwareness` property is set to `StorageRack`:
+1. Verify that the storage pool's `FaultDomainAwareness` property has the value `StorageRack`. This value confirms that Storage Spaces Direct places data copies across the two rack fault domains:
 
    ```powershell
-   Get-StoragePool -FriendlyName S2D* | Format-List FaultDomainAwarenessDefault
+   Get-StoragePool -FriendlyName S2D* | Format-List FaultDomainAwareness
    ```
 
 #### [Failover Cluster Manager](#tab/fcm)
 
-Here's how to enable Storage Spaces Direct using Failover Cluster Manager.
+Here's how to enable Storage Spaces Direct by using Failover Cluster Manager.
 
 1. In **Failover Cluster Manager**, expand the cluster name, and then select **Storage** > **Pools**.
 
-1. Right-click **Pools**, and then select **Enable Storage Spaces Direct**. Follow the wizard to complete the operation.
+1. Right-click **Pools**, and then select **Enable Storage Spaces Direct**.
+
+1. Complete the wizard to enable Storage Spaces Direct on the cluster.
 
 1. After enabling Storage Spaces Direct, use PowerShell to update the storage pool and verify the configuration:
 
    ```powershell
    Get-StoragePool S2D* | Update-StoragePool
    ```
 
-1. Verify that the storage pool version is 29 or later:
+1. Verify that the storage pool version is 29 or later. A campus cluster requires storage pool version 29 for rack-level fault domain awareness:
 
    ```powershell
-   (Get-CimInstance -Namespace root/microsoft/windows/storage -ClassName MSFT_StoragePool -Filter 'IsPrimordial = false').CimInstanceProperties['Version'].Value
+   (Get-CimInstance -Namespace root/microsoft/windows/storage `
+       -ClassName MSFT_StoragePool `
+       -Filter 'IsPrimordial = false').CimInstanceProperties['Version'].Value
    ```
 
-1. Verify that the storage pool's `FaultDomainAwareness` property is set to `StorageRack`:
+1. Verify that the storage pool's `FaultDomainAwareness` property has the value `StorageRack`. This value confirms that Storage Spaces Direct places data copies across the two rack fault domains:
 
    ```powershell
-   Get-StoragePool -FriendlyName S2D* | Format-List FaultDomainAwarenessDefault
+   Get-StoragePool -FriendlyName S2D* | Format-List FaultDomainAwareness
    ```
 
 ---
 
-## Create volumes
+## 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:
 
-Create volumes on the storage pool based on your resiliency requirements. For a 2+2 campus cluster, use four-copy volumes as they provide the best balance between cost, performance, and resiliency. A four-copy volume places a copy of data on each node, so the cluster can survive losing an entire rack and a node at the same time.
+| 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. |
 
-A four-copy volume provides 25% storage capacity, while a two-copy volume provides 50% capacity with less resiliency. For more information about volume resiliency options, see [Fault tolerance and storage efficiency](../storage/storage-spaces/fault-tolerance.md).
+For more information about volume resiliency options, see [Fault tolerance and storage efficiency](../storage/storage-spaces/fault-tolerance.md).
 
 #### [PowerShell](#tab/powershell)
 
-Here's how to create a four-copy mirrored volume using PowerShell.
+Here's how to create a four-copy mirrored volume by using PowerShell.
 
 1. Run PowerShell on your computer in an elevated session.
 
@@ -254,7 +271,7 @@ Here's how to create volumes using Failover Cluster Manager. To create four-copy
 
 1. In **Failover Cluster Manager**, expand the cluster name, and then select **Storage** > **Pools**.
 
-1. Select the **S2D** storage pool, and then right-click and select **New Virtual Disk**.
+1. Right-click the **S2D** storage pool, and then select **New Virtual Disk**.
 
 1. In the New Virtual Disk Wizard, enter a name for the volume.
 
@@ -266,7 +283,7 @@ Here's how to create volumes using Failover Cluster Manager. To create four-copy
 
 1. Specify the size for the volume and complete the wizard.
 
-1. After creating the virtual disk, right-click it and select **New Volume** to format it by using ReFS.
+1. After you create the virtual disk, right-click it and select **New Volume** to format it by using ReFS.
 
 ---
 
diff --git a/WindowsServerDocs/failover-clustering/toc.yml b/WindowsServerDocs/failover-clustering/toc.yml
@@ -8,8 +8,6 @@
   items:
   - name: Create a failover cluster
     href: create-failover-cluster.md
-  - name: Create a Storage Spaces Direct campus cluster
-    href: create-storage-spaces-direct-campus-cluster.md
   - name: Deploy a two-node file server
     href: deploy-two-node-clustered-file-server.md
   - name: Recover a failover cluster without quorum
@@ -42,6 +40,8 @@
       href: cluster-aware-updating-options.md
 - name: How-tos
   items:
+  - name: Create a Storage Spaces Direct campus cluster
+    href: create-storage-spaces-direct-campus-cluster.md
   - name: Cluster-domain migration
     href: cluster-domain-migration.md
   - name: Troubleshooting using Windows Error Reporting
