{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/",
        "slug": "dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/"
        },
        "title": "Define rack fault domains before enabling campus-cluster storage",
        "summary": "What topology evidence is required before enabling S2D in a campus 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:14:08+00:00",
        "modified_at": "2026-09-08T18:26:32+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 2,
        "word_count": 225,
        "potentially_affected": "Administrators creating the documented Windows Server Storage Spaces Direct campus-cluster topology.",
        "dse_recommendation": "Have facilities and storage owners review a rack map that identifies every node, power source, network dependency, and the separate witness location.",
        "primary_source": {
            "name": "Create a Storage Spaces Direct Campus Cluster",
            "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/create-storage-spaces-direct-campus-cluster",
            "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 describes a campus cluster as nodes and data distributed across two physical racks in separate rooms or buildings on one campus. Its procedure requires defining the two rack fault domains before enabling Storage Spaces Direct. After enablement, the documented verification checks that the storage pool reports StorageRack for FaultDomainAwareness. <a href=\"https://learn.microsoft.com/en-us/windows-server/failover-clustering/create-storage-spaces-direct-campus-cluster\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Check the current prerequisites in full, including the Windows build and update, supported drive configuration, balanced node placement, and witness location. Match the logical rack names to the actual physical layout. Do not adapt the example solely from the total node count.</p>\n<h2>DSE recommendation</h2>\n<p>Have facilities and storage owners review a rack map that identifies every node, power source, network dependency, and the separate witness location. Record the intended rack membership before storage enablement and obtain a second-person check of the mapping. Define an approved rack-loss acceptance exercise with the application owner. Keep the topology record with the cluster configuration rather than in an unrelated floor plan.</p>\n<h2>Verification</h2>\n<p>Verify each node belongs to the intended rack domain and inspect the pool fault-domain-awareness value. Compare the observed placement with the signed-off map. In an approved environment, exercise the chosen rack-failure scenario and validate application behavior and recovery. Resolve incorrect rack membership before treating the cluster as rack-resilient.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/failover-clustering/create-storage-spaces-direct-campus-cluster\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Create a Storage Spaces Direct Campus Cluster</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nMicrosoft describes a campus cluster as nodes and data distributed across two physical racks in separate rooms or buildings on one campus. Its procedure requires defining the two rack fault domains before enabling Storage Spaces Direct. After enablement, the documented verification checks that the storage pool reports StorageRack for FaultDomainAwareness. Microsoft Learn.\nApplicability\nCheck the current prerequisites in full, including the Windows build and update, supported drive configuration, balanced node placement, and witness location. Match the logical rack names to the actual physical layout. Do not adapt the example solely from the total node count.\nDSE recommendation\nHave facilities and storage owners review a rack map that identifies every node, power source, network dependency, and the separate witness location. Record the intended rack membership before storage enablement and obtain a second-person check of the mapping. Define an approved rack-loss acceptance exercise with the application owner. Keep the topology record with the cluster configuration rather than in an unrelated floor plan.\nVerification\nVerify each node belongs to the intended rack domain and inspect the pool fault-domain-awareness value. Compare the observed placement with the signed-off map. In an approved environment, exercise the chosen rack-failure scenario and validate application behavior and recovery. Resolve incorrect rack membership before treating the cluster as rack-resilient.\nOfficial references\nMicrosoft Learn: Create a Storage Spaces Direct Campus Cluster. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nMicrosoft describes a campus cluster as nodes and data distributed across two physical racks in separate rooms or buildings on one campus. Its procedure requires defining the two rack fault domains before enabling Storage Spaces Direct. After enablement, the documented verification checks that the storage pool reports StorageRack for FaultDomainAwareness. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/failover-clustering/create-storage-spaces-direct-campus-cluster).\n\n## Applicability\n\nCheck the current prerequisites in full, including the Windows build and update, supported drive configuration, balanced node placement, and witness location. Match the logical rack names to the actual physical layout. Do not adapt the example solely from the total node count.\n\n## DSE recommendation\n\nHave facilities and storage owners review a rack map that identifies every node, power source, network dependency, and the separate witness location. Record the intended rack membership before storage enablement and obtain a second-person check of the mapping. Define an approved rack-loss acceptance exercise with the application owner. Keep the topology record with the cluster configuration rather than in an unrelated floor plan.\n\n## Verification\n\nVerify each node belongs to the intended rack domain and inspect the pool fault-domain-awareness value. Compare the observed placement with the signed-off map. In an approved environment, exercise the chosen rack-failure scenario and validate application behavior and recovery. Resolve incorrect rack membership before treating the cluster as rack-resilient.\n\n## Official references\n\n[Microsoft Learn: Create a Storage Spaces Direct Campus Cluster](https://learn.microsoft.com/en-us/windows-server/failover-clustering/create-storage-spaces-direct-campus-cluster). 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-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Define rack fault domains before enabling campus-cluster storage",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/",
                "headline": "Define rack fault domains before enabling campus-cluster storage",
                "description": "What topology evidence is required before enabling S2D in a campus cluster?",
                "abstract": "What topology evidence is required before enabling S2D in a campus cluster?",
                "articleBody": "Source facts\nMicrosoft describes a campus cluster as nodes and data distributed across two physical racks in separate rooms or buildings on one campus. Its procedure requires defining the two rack fault domains before enabling Storage Spaces Direct. After enablement, the documented verification checks that the storage pool reports StorageRack for FaultDomainAwareness. Microsoft Learn.\nApplicability\nCheck the current prerequisites in full, including the Windows build and update, supported drive configuration, balanced node placement, and witness location. Match the logical rack names to the actual physical layout. Do not adapt the example solely from the total node count.\nDSE recommendation\nHave facilities and storage owners review a rack map that identifies every node, power source, network dependency, and the separate witness location. Record the intended rack membership before storage enablement and obtain a second-person check of the mapping. Define an approved rack-loss acceptance exercise with the application owner. Keep the topology record with the cluster configuration rather than in an unrelated floor plan.\nVerification\nVerify each node belongs to the intended rack domain and inspect the pool fault-domain-awareness value. Compare the observed placement with the signed-off map. In an approved environment, exercise the chosen rack-failure scenario and validate application behavior and recovery. Resolve incorrect rack membership before treating the cluster as rack-resilient.\nOfficial references\nMicrosoft Learn: Create a Storage Spaces Direct Campus Cluster. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:14:08+00:00",
                "dateModified": "2026-09-08T18:26:32+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/"
                },
                "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-183-define-rack-fault-domains-before-enabling-campus-cluster-storage/#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": "Define rack fault domains before enabling campus-cluster storage"
                },
                "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": "Create a Storage Spaces Direct Campus Cluster",
                    "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/create-storage-spaces-direct-campus-cluster"
                }
            }
        ]
    }
}