# Choose node recovery or cluster-configuration recovery deliberately

> When does a Storage Spaces Direct recovery require restoring cluster configuration authoritatively?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:13:41+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: 2 minutes

## What you need to know

When does a Storage Spaces Direct recovery require restoring cluster configuration authoritatively?

## Potentially affected

Administrators planning backup-based recovery of S2D cluster nodes and configuration.

## DSE recommendation

Have the cluster and workload owners document what must be recovered and which current state must be preserved.

## Article

## Source facts

Microsoft distinguishes nonauthoritative restoration of a cluster node from authoritative restoration of the cluster configuration. A nonauthoritative restore is described for recovering a node when the current cluster information remains good. An authoritative restore returns cluster configuration to an earlier state and is reserved for cases where that configuration itself was lost. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/Storage-Spaces-Direct-Disaster-Recovery).

## Applicability

Determine whether the failure concerns one node, application data, or the shared cluster configuration. Identify a suitable backup and compare its scope and time with the incident. Do not choose an authoritative operation simply because a node is unavailable.

## DSE recommendation

Have the cluster and workload owners document what must be recovered and which current state must be preserved. Name the restore point and explain why its configuration is appropriate. Use a representative recovery exercise to distinguish node repair from restoring a deleted or lost cluster resource definition. Keep the selected recovery type and its approval visible in the runbook.

## Verification

After the approved exercise, verify node membership, resource definitions, workload ownership, and the application’s expected behavior. Compare restored configuration with the chosen backup and with any legitimate changes made afterward. Record which state was intentionally returned to an earlier point. Resolve unexplained configuration loss before treating the recovery as complete.

## Official references

[Microsoft Learn: Disaster Recovery Scenarios for Storage Spaces Direct in Windows Server](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/Storage-Spaces-Direct-Disaster-Recovery). Source reviewed September 8, 2026.

## Primary reference

- Name: Disaster Recovery Scenarios for Storage Spaces Direct in Windows Server
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/Storage-Spaces-Direct-Disaster-Recovery
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Choose node recovery or cluster-configuration recovery deliberately,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/
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.