# Revisit mirror policy when a Storage Spaces Direct cluster grows

> What resiliency decision becomes available when a two-node Storage Spaces Direct cluster gains a server?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:13+00:00
- Modified: 2026-09-08T18:20:21+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

What resiliency decision becomes available when a two-node Storage Spaces Direct cluster gains a server?

## Potentially affected

Use this review when an existing Storage Spaces Direct cluster expands from two servers.

## DSE recommendation

Have the storage owner review the new resiliency choice alongside capacity and recovery requirements.

## Article

## Source facts

Adding a server expands storage capacity and can also add compute resources in a hyperconverged deployment. Microsoft describes two-way mirroring for two-server clusters and the availability of three-way mirroring when a third server is added. The mirror resiliency setting can be changed so newly created mirrored volumes default to three-way mirroring. An existing two-way mirror cannot become a three-way mirror through an in-place upgrade; Microsoft instead describes copying data to a new volume. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/add-nodes).

## Applicability

Use this review when an existing Storage Spaces Direct cluster expands from two servers. Identify the existing volume layouts and the intended policy for new volumes. Distinguish adding hardware from deciding how subsequent storage will use it.

## DSE recommendation

Have the storage owner review the new resiliency choice alongside capacity and recovery requirements. Record which volumes are existing and which will be created after expansion. Approve any default-setting change explicitly and document its effect on future provisioning. Plan any existing-data migration separately, including new-volume capacity and verification before authorizing removal of an old volume.

## Verification

Inspect cluster membership and health after the approved addition. Create a controlled test volume through the intended provisioning workflow and inspect its actual resiliency. Compare the result with the new-volume policy and capacity plan. Retain existing-volume observations separately so an unchanged layout is not mistaken for a failed default-setting change.

## Official references

[Microsoft Learn: Adding servers or drives to Storage Spaces Direct](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/add-nodes). Source reviewed September 8, 2026.

## Primary reference

- Name: Adding servers or drives to Storage Spaces Direct
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/add-nodes
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Revisit mirror policy when a Storage Spaces Direct cluster grows,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.