{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/",
        "slug": "dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/"
        },
        "title": "Revisit mirror policy when a Storage Spaces Direct cluster grows",
        "summary": "What resiliency decision becomes available when a two-node Storage Spaces Direct cluster gains a server?",
        "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:16:13+00:00",
        "modified_at": "2026-09-08T18:20:21+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 2,
        "word_count": 238,
        "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.",
        "primary_source": {
            "name": "Adding servers or drives to Storage Spaces Direct",
            "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/add-nodes",
            "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": "<h2>Source facts</h2>\n<p>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. <a href=\"https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/add-nodes\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft documentation</a>.</p>\n<h2>Applicability</h2>\n<p>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.</p>\n<h2>DSE recommendation</h2>\n<p>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.</p>\n<h2>Verification</h2>\n<p>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.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/add-nodes\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Adding servers or drives to Storage Spaces Direct</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nAdding 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.\nApplicability\nUse 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.\nDSE recommendation\nHave 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.\nVerification\nInspect 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.\nOfficial references\nMicrosoft Learn: Adding servers or drives to Storage Spaces Direct. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nAdding 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).\n\n## Applicability\n\nUse 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.\n\n## DSE recommendation\n\nHave 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.\n\n## Verification\n\nInspect 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.\n\n## Official references\n\n[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."
    },
    "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-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Revisit mirror policy when a Storage Spaces Direct cluster grows",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/",
                "headline": "Revisit mirror policy when a Storage Spaces Direct cluster grows",
                "description": "What resiliency decision becomes available when a two-node Storage Spaces Direct cluster gains a server?",
                "abstract": "What resiliency decision becomes available when a two-node Storage Spaces Direct cluster gains a server?",
                "articleBody": "Source facts\nAdding 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.\nApplicability\nUse 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.\nDSE recommendation\nHave 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.\nVerification\nInspect 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.\nOfficial references\nMicrosoft Learn: Adding servers or drives to Storage Spaces Direct. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:16:13+00:00",
                "dateModified": "2026-09-08T18:20:21+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/"
                },
                "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-058-revisit-mirror-policy-when-a-storage-spaces-direct-cluster-grows/#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": "Revisit mirror policy when a Storage Spaces Direct cluster grows"
                },
                "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": 238,
                "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": "Adding servers or drives to Storage Spaces Direct",
                    "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/add-nodes"
                }
            }
        ]
    }
}