Skip to content

Commit cbf383b

Browse files
committed
Adding scale section to create-storage-spaces-direct-campus-cluster.md
1 parent 5a99361 commit cbf383b

2 files changed

Lines changed: 32 additions & 9 deletions

File tree

WindowsServerDocs/docfx.json

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -216,6 +216,9 @@
216216
"✅&nbsp;<a href=\"https://learn.microsoft.com/windows-server/get-started/windows-server-release-info\" target=\"_blank\">Windows Server 2022</a>",
217217
"✅&nbsp;<a href=\"https://learn.microsoft.com/windows-server/get-started/windows-server-release-info\" target=\"_blank\">Windows Server 2019</a>"
218218
],
219+
"failover-clustering/create-storage-spaces-direct-campus-cluster.md": [
220+
"✅&nbsp;<a href=\"https://learn.microsoft.com/windows-server/get-started/windows-server-release-info\" target=\"_blank\">Windows Server 2025</a>"
221+
],
219222
"get-started/**/*.md": [
220223
"✅&nbsp;<a href=\"https://learn.microsoft.com/windows-server/get-started/windows-server-release-info\" target=\"_blank\">Windows Server 2025</a>",
221224
"✅&nbsp;<a href=\"https://learn.microsoft.com/windows-server/get-started/windows-server-release-info\" target=\"_blank\">Windows Server 2022</a>",

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

Lines changed: 29 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ai-usage: ai-assisted
1212

1313
# Create a Storage Spaces Direct campus cluster
1414

15-
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.
15+
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.
1616

1717
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.
1818

@@ -24,7 +24,7 @@ For more information about campus cluster architecture, supported configurations
2424
- 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.
2525
- 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.
2626
- Exactly two rack-level fault domains, with cluster nodes spanning both racks.
27-
- Shared or direct-attached storage that follows your hardware original equipment manufacturer (OEM) guidelines, including driver versions.
27+
- Direct-attached storage that follows your hardware original equipment manufacturer (OEM) guidelines, including driver versions.
2828
- 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.
2929

3030
For optimal performance and resiliency, use the following configurations:
@@ -36,7 +36,7 @@ For optimal performance and resiliency, use the following configurations:
3636

3737
## Create the campus failover cluster
3838

39-
To create a Storage Spaces Direct campus cluster on Windows Server 2025, complete these high-level steps in order:
39+
To create a Storage Spaces Direct campus cluster on Windows Server 2025 or later, complete these high-level steps in order:
4040

4141
1. Create a failover cluster without storage.
4242
1. Define two rack fault domains.
@@ -47,7 +47,7 @@ This section covers the first step: creating the failover cluster without storag
4747

4848
#### [PowerShell](#tab/powershell)
4949

50-
Here's how to create the failover cluster by using the [New-Cluster](/powershell/module/failoverclusters/new-cluster) cmdlet.
50+
To create the failover cluster, use the [New-Cluster](/powershell/module/failoverclusters/new-cluster) cmdlet.
5151

5252
1. Run PowerShell on your computer in an elevated session.
5353

@@ -61,7 +61,7 @@ Here's how to create the failover cluster by using the [New-Cluster](/powershell
6161

6262
#### [Failover Cluster Manager](#tab/fcm)
6363

64-
Here's how to create the failover cluster by using Failover Cluster Manager.
64+
To create the failover cluster, use Failover Cluster Manager.
6565

6666
1. From the Windows desktop, open the **Start** menu, and then select the **Server Manager** tile.
6767

@@ -71,15 +71,15 @@ Here's how to create the failover cluster by using Failover Cluster Manager.
7171

7272
1. On the **Before You Begin** page, select **Next**.
7373

74-
1. On the **Select Servers** page, in the **Enter name** box, enter the name of a server that you plan 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**.
74+
1. 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**.
7575

7676
1. On the **Validation Warning** page, select **Yes** to run cluster validation, and then select **Next**. Complete the Validate a Configuration Wizard.
7777

7878
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**.
7979

8080
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**.
8181

82-
1. On the **Summary** page, confirm that the failover cluster was created successfully, and then select **Finish**.
82+
1. On the **Summary** page, confirm that the wizard created the failover cluster successfully, and then select **Finish**.
8383

8484
---
8585

@@ -176,7 +176,7 @@ Here's how to enable Storage Spaces Direct by using the [Enable-ClusterStorageSp
176176
Enable-ClusterStorageSpacesDirect
177177
```
178178

179-
1. Update the storage pool to ensure it's using the latest features:
179+
1. Update the storage pool to use the latest features:
180180

181181
```powershell
182182
Get-StoragePool S2D* | Update-StoragePool
@@ -243,7 +243,7 @@ For more information about volume resiliency options, see [Fault tolerance and s
243243

244244
#### [PowerShell](#tab/powershell)
245245

246-
Here's how to create a four-copy mirrored volume by using PowerShell.
246+
To create a four-copy mirrored volume by using PowerShell, follow these steps:
247247

248248
1. Run PowerShell on your computer in an elevated session.
249249

@@ -287,6 +287,26 @@ Here's how to create volumes using Failover Cluster Manager. To create four-copy
287287

288288
---
289289

290+
## Scale the campus cluster by adding nodes
291+
292+
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](/powershell/module/failoverclusters/new-clusterfaultdomain), and then add it to the cluster by using [Add-ClusterNode](/powershell/module/failoverclusters/add-clusternode).
293+
294+
The following example adds `Node5` to `Room1` and `Node6` to `Room2`:
295+
296+
```powershell
297+
$nodeName = 'Node5'
298+
$rackFaultDomainName = 'Room1'
299+
New-ClusterFaultDomain -Type Node -Name $nodeName -FaultDomain $rackFaultDomainName
300+
Add-ClusterNode -Name $nodeName
301+
302+
$nodeName = 'Node6'
303+
$rackFaultDomainName = 'Room2'
304+
New-ClusterFaultDomain -Type Node -Name $nodeName -FaultDomain $rackFaultDomainName
305+
Add-ClusterNode -Name $nodeName
306+
```
307+
308+
Repeat the pattern, alternating racks, until you reach your target configuration. Always keep an equal number of nodes in each rack.
309+
290310
## Related content
291311

292312
- [Deploy a quorum witness](deploy-quorum-witness.md)

0 commit comments

Comments
 (0)