{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/",
        "slug": "dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/"
        },
        "title": "Expand guest-cluster S2D storage without resizing its existing disks",
        "summary": "How should capacity be added to a Storage Spaces Direct guest cluster?",
        "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:49+00:00",
        "modified_at": "2026-09-08T18:29:33+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 2,
        "word_count": 228,
        "potentially_affected": "Administrators running Storage Spaces Direct inside a VM guest cluster.",
        "dse_recommendation": "Prepare a disk inventory for every guest node with identifiers, capacity, and presentation settings.",
        "primary_source": {
            "name": "Using Storage Spaces Direct in a virtual machine",
            "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-in-vm",
            "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>Microsoft documents Storage Spaces Direct guest clusters as shared virtual storage built across multiple VMs. The exposed virtual disks must keep their existing size and characteristics. Its capacity-expansion procedure adds more virtual disks to each VM and then to the pool, recommending disks with the same size and characteristics as the existing ones. <a href=\"https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-in-vm\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Confirm the guest-cluster platform, underlying VM placement, and current virtual-disk layout. Review the guest-cluster requirements for the actual hypervisor before making a storage change. Keep a host-level disk expansion and a guest-cluster pool expansion as separate operations.</p>\n<h2>DSE recommendation</h2>\n<p>Prepare a disk inventory for every guest node with identifiers, capacity, and presentation settings. Have the storage owner review the additional-disk plan against that inventory. Record the expected new pool capacity and the assignment of every added disk before execution. Preserve a recoverable configuration record and schedule the change with the application owner rather than resizing an existing disk as an informal shortcut.</p>\n<h2>Verification</h2>\n<p>After the approved addition, inspect the disks presented to each guest and compare their characteristics with the plan. Confirm pool membership, health, and the expected capacity increase. Exercise a representative application transaction and record any asymmetric node configuration. Resolve missing or unexpected disks before creating or extending workloads on the new space.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-in-vm\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Using Storage Spaces Direct in a virtual machine</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nMicrosoft documents Storage Spaces Direct guest clusters as shared virtual storage built across multiple VMs. The exposed virtual disks must keep their existing size and characteristics. Its capacity-expansion procedure adds more virtual disks to each VM and then to the pool, recommending disks with the same size and characteristics as the existing ones. Microsoft Learn.\nApplicability\nConfirm the guest-cluster platform, underlying VM placement, and current virtual-disk layout. Review the guest-cluster requirements for the actual hypervisor before making a storage change. Keep a host-level disk expansion and a guest-cluster pool expansion as separate operations.\nDSE recommendation\nPrepare a disk inventory for every guest node with identifiers, capacity, and presentation settings. Have the storage owner review the additional-disk plan against that inventory. Record the expected new pool capacity and the assignment of every added disk before execution. Preserve a recoverable configuration record and schedule the change with the application owner rather than resizing an existing disk as an informal shortcut.\nVerification\nAfter the approved addition, inspect the disks presented to each guest and compare their characteristics with the plan. Confirm pool membership, health, and the expected capacity increase. Exercise a representative application transaction and record any asymmetric node configuration. Resolve missing or unexpected disks before creating or extending workloads on the new space.\nOfficial references\nMicrosoft Learn: Using Storage Spaces Direct in a virtual machine. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nMicrosoft documents Storage Spaces Direct guest clusters as shared virtual storage built across multiple VMs. The exposed virtual disks must keep their existing size and characteristics. Its capacity-expansion procedure adds more virtual disks to each VM and then to the pool, recommending disks with the same size and characteristics as the existing ones. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-in-vm).\n\n## Applicability\n\nConfirm the guest-cluster platform, underlying VM placement, and current virtual-disk layout. Review the guest-cluster requirements for the actual hypervisor before making a storage change. Keep a host-level disk expansion and a guest-cluster pool expansion as separate operations.\n\n## DSE recommendation\n\nPrepare a disk inventory for every guest node with identifiers, capacity, and presentation settings. Have the storage owner review the additional-disk plan against that inventory. Record the expected new pool capacity and the assignment of every added disk before execution. Preserve a recoverable configuration record and schedule the change with the application owner rather than resizing an existing disk as an informal shortcut.\n\n## Verification\n\nAfter the approved addition, inspect the disks presented to each guest and compare their characteristics with the plan. Confirm pool membership, health, and the expected capacity increase. Exercise a representative application transaction and record any asymmetric node configuration. Resolve missing or unexpected disks before creating or extending workloads on the new space.\n\n## Official references\n\n[Microsoft Learn: Using Storage Spaces Direct in a virtual machine](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-in-vm). 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-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Expand guest-cluster S2D storage without resizing its existing disks",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/",
                "headline": "Expand guest-cluster S2D storage without resizing its existing disks",
                "description": "How should capacity be added to a Storage Spaces Direct guest cluster?",
                "abstract": "How should capacity be added to a Storage Spaces Direct guest cluster?",
                "articleBody": "Source facts\nMicrosoft documents Storage Spaces Direct guest clusters as shared virtual storage built across multiple VMs. The exposed virtual disks must keep their existing size and characteristics. Its capacity-expansion procedure adds more virtual disks to each VM and then to the pool, recommending disks with the same size and characteristics as the existing ones. Microsoft Learn.\nApplicability\nConfirm the guest-cluster platform, underlying VM placement, and current virtual-disk layout. Review the guest-cluster requirements for the actual hypervisor before making a storage change. Keep a host-level disk expansion and a guest-cluster pool expansion as separate operations.\nDSE recommendation\nPrepare a disk inventory for every guest node with identifiers, capacity, and presentation settings. Have the storage owner review the additional-disk plan against that inventory. Record the expected new pool capacity and the assignment of every added disk before execution. Preserve a recoverable configuration record and schedule the change with the application owner rather than resizing an existing disk as an informal shortcut.\nVerification\nAfter the approved addition, inspect the disks presented to each guest and compare their characteristics with the plan. Confirm pool membership, health, and the expected capacity increase. Exercise a representative application transaction and record any asymmetric node configuration. Resolve missing or unexpected disks before creating or extending workloads on the new space.\nOfficial references\nMicrosoft Learn: Using Storage Spaces Direct in a virtual machine. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:13:49+00:00",
                "dateModified": "2026-09-08T18:29:33+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/"
                },
                "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-202-expand-guest-cluster-s2d-storage-without-resizing-its-existing-disks/#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": "Expand guest-cluster S2D storage without resizing its existing disks"
                },
                "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": 228,
                "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": "Using Storage Spaces Direct in a virtual machine",
                    "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-in-vm"
                }
            }
        ]
    }
}