Skip to content

Commit 96c608f

Browse files
committed
Minor edits
1 parent 1ae494e commit 96c608f

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

WindowsServerDocs/failover-clustering/create-storage-spaces-direct-campus-cluster.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -22,18 +22,18 @@ For more information about campus cluster architecture, supported configurations
2222

2323
Before you create a campus cluster, ensure you meet the following requirements:
2424

25-
- **Windows Server 2025** with the 2025-12 Security Update (KB5072033) installed on every node in the failover cluster.
26-
- **Flat S2D storage** - All capacity drives must be flash-based (SSD or NVMe). Don't use HDDs.
27-
- **Exactly two RACK fault domains** - You must define exactly two rack-level fault domains and place the cluster nodes in these two racks.
28-
- **Hardware OEM guidelines** - Follow your hardware OEM's guidelines for the deployment.
29-
- **Cluster quorum resource** - Place the quorum resource (File Share Witness, Disk Witness, Cloud Witness, or USB Witness) in a third room, separate from the data rooms containing the racks.
25+
- Windows Server 2025 with the 2025-12 Security Update (KB5072033) installed on every node in the failover cluster.
26+
- All capacity drives must be flash-based (SSD or NVMe). Don't use HDDs.
27+
- You must define exactly two rack-level fault domains and place the cluster nodes in these two racks.
28+
- Follow your hardware OEM's guidelines for any shared or direct attached storage including driver versions.
29+
- Place the quorum resource (File Share Witness, Disk Witness, Cloud Witness, or USB Witness) in a third location, separate from the campus cluster racks.
3030

3131
For optimal performance and resiliency, use the following configurations:
3232

3333
- Each rack has a separate network path to the cluster quorum resource.
3434
- 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.
3535
- Network latency of 1 ms or less between racks. Use the [PsPing](/sysinternals/downloads/psping) utility to measure network latency.
36-
- RDMA NICs and switches, which can achieve up to 30% CPU savings.
36+
- RDMA NICs and switches, which can achieve CPU savings on your cluster.
3737

3838
## Create the failover cluster
3939

0 commit comments

Comments
 (0)