# Include resynchronization time in S2D per-server capacity planning

> How should per-server capacity be reviewed before expanding an S2D cluster?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-186-include-resynchronization-time-in-s2d-per-server-capacity-planning/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:14:05+00:00
- Modified: 2026-09-08T18:26:32+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

How should per-server capacity be reviewed before expanding an S2D cluster?

## Potentially affected

Administrators planning drive capacity for Azure Local or Windows Server storage clusters.

## DSE recommendation

Prepare a per-node capacity inventory and a separate pool total.

## Article

## Source facts

Microsoft recommends limiting the total storage capacity on an individual server to about 400 terabytes. The source connects greater capacity per server with longer data-resynchronization time after an outage or reboot. It lists a four-petabyte maximum storage-pool size, with a one-petabyte limit for Windows Server 2016. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/choose-drives).

## Applicability

Identify the server version and distinguish capacity on one server from capacity across the whole pool. Review the current platform limits before applying the numbers. Ask the workload owner what recovery and maintenance duration is acceptable for the proposed expansion.

## DSE recommendation

Prepare a per-node capacity inventory and a separate pool total. Pair the expansion request with an observed or tested resynchronization-time estimate appropriate to the actual hardware and workload. Have the storage owner explain how the larger node affects the maintenance plan. Avoid presenting a supported maximum as the preferred design target without considering operational recovery.

## Verification

Measure a representative approved node-return and resynchronization exercise before accepting the expanded design. Record data volume, workload, hardware, elapsed time, and health at completion. Compare the result with the maintenance and recovery expectations. Retain the measured conditions so future capacity additions trigger another review rather than inheriting an unrelated timing assumption.

## Official references

[Microsoft Learn: Choose drives for Azure Local and Windows Server clusters](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/choose-drives). Source reviewed September 8, 2026.

## Primary reference

- Name: Choose drives for Azure Local and Windows Server clusters
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/choose-drives
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Include resynchronization time in S2D per-server capacity planning,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-186-include-resynchronization-time-in-s2d-per-server-capacity-planning/
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.