{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/", "slug": "dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately", "url": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/" }, "title": "Choose node recovery or cluster-configuration recovery deliberately", "summary": "When does a Storage Spaces Direct recovery require restoring cluster configuration authoritatively?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:13:41+00:00", "modified_at": "2026-09-08T18:29:33+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 225, "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.", "primary_source": { "name": "Disaster Recovery Scenarios for Storage Spaces Direct in Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/Storage-Spaces-Direct-Disaster-Recovery", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Disaster Recovery Scenarios for Storage Spaces Direct in Windows Server. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft 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.\nApplicability\nDetermine 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.\nDSE recommendation\nHave 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.\nVerification\nAfter 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.\nOfficial references\nMicrosoft Learn: Disaster Recovery Scenarios for Storage Spaces Direct in Windows Server. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft 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).\n\n## Applicability\n\nDetermine 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.\n\n## DSE recommendation\n\nHave 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.\n\n## Verification\n\nAfter 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.\n\n## Official references\n\n[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." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/", "url": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose node recovery or cluster-configuration recovery deliberately", "item": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/", "url": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/", "headline": "Choose node recovery or cluster-configuration recovery deliberately", "description": "When does a Storage Spaces Direct recovery require restoring cluster configuration authoritatively?", "abstract": "When does a Storage Spaces Direct recovery require restoring cluster configuration authoritatively?", "articleBody": "Source facts\nMicrosoft 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.\nApplicability\nDetermine 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.\nDSE recommendation\nHave 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.\nVerification\nAfter 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.\nOfficial references\nMicrosoft Learn: Disaster Recovery Scenarios for Storage Spaces Direct in Windows Server. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:13:41+00:00", "dateModified": "2026-09-08T18:29:33+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-210-choose-node-recovery-or-cluster-configuration-recovery-deliberately/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Choose node recovery or cluster-configuration recovery deliberately" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 225, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Disaster Recovery Scenarios for Storage Spaces Direct in Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/Storage-Spaces-Direct-Disaster-Recovery" } } ] } }