# Wait for storage resynchronization before the next cluster interruption

> Which storage observations should gate the next S2D maintenance action?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-216-wait-for-storage-resynchronization-before-the-next-cluster-interruption/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:13:35+00:00
- Modified: 2026-09-08T18:29:33+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

Which storage observations should gate the next S2D maintenance action?

## Potentially affected

Administrators returning Storage Spaces Direct nodes to service during maintenance.

## DSE recommendation

Add an explicit storage-resync gate to the maintenance runbook between one node returning and another being interrupted.

## Article

## Source facts

Microsoft explains that drives on an unavailable node miss updates until that node returns. The storage-resync health fault was introduced in Windows Server 2019. With that fault, Windows Admin Center shows a yellow resyncing state between down and up. Get-StorageJob provides underlying long-running storage-job information. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/understand-storage-resync).

## Applicability

Identify the node that returned and the storage workloads affected by its absence. Review the server-version-specific monitoring guidance before relying on a dashboard color. Keep host availability, storage resynchronization, and application readiness as separate observations.

## DSE recommendation

Add an explicit storage-resync gate to the maintenance runbook between one node returning and another being interrupted. Assign a storage owner to decide which health and job observations satisfy the gate. Preserve the original failure or maintenance timeline and record any additional fault. Avoid scheduling the next interruption merely because management access to the first node has returned.

## Verification

Inspect the applicable health faults and storage jobs throughout the recovery interval. Confirm the expected resync completion and workload health before releasing the next maintenance step. Record any persistent or failed job and escalate rather than overriding the gate. Retain the timeline so later reviews can distinguish normal resync duration from a stalled operation.

## Official references

[Microsoft Learn: Understand and monitor storage resync](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/understand-storage-resync). Source reviewed September 8, 2026.

## Primary reference

- Name: Understand and monitor storage resync
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/understand-storage-resync
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Wait for storage resynchronization before the next cluster interruption,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-216-wait-for-storage-resynchronization-before-the-next-cluster-interruption/
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.