{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/", "slug": "dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout", "url": "https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/" }, "title": "Map cluster fault domains to the actual rack and site layout", "summary": "Which physical relationships should be represented in a cluster fault-domain hierarchy?", "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:10+00:00", "modified_at": "2026-09-08T18:20:21+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 205, "potentially_affected": "Use this review when documenting a cluster's physical placement.", "dse_recommendation": "Have the facilities and server owners reconcile the logical hierarchy with the equipment inventory.", "primary_source": { "name": "Fault domain awareness", "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/fault-domains", "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 defines a fault domain as hardware sharing a single failure point; tolerance at a level requires multiple domains at that level. The documented hierarchy includes site, rack, chassis, and node. Nodes are discovered automatically, while additional levels are optional. Storage Spaces uses fault-domain information to place redundant copies on separate failure domains. Microsoft documentation.

\n

Applicability

\n

Use this review when documenting a cluster’s physical placement. Identify real racks, chassis, sites, and shared dependencies. Include only hierarchy levels that describe the deployment rather than inventing unused physical distinctions.

\n

DSE recommendation

\n

Have the facilities and server owners reconcile the logical hierarchy with the equipment inventory. Record each node’s actual placement and the failure event each level represents. Review recent equipment moves for stale mappings. Keep data-copy placement objectives separate from quorum-witness placement, and obtain storage-owner review before changing the configured hierarchy.

\n

Verification

\n

Compare the reported fault-domain hierarchy with a checked physical inventory. Inspect the selected storage configuration through the supported management tools and record the relevant placement evidence. Exercise only the approved failure scenario and retain the observed workload result. Update both the map and its ownership record after accepted hardware moves or site changes.

\n

Official references

\n

Microsoft Learn: Fault domain awareness. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft defines a fault domain as hardware sharing a single failure point; tolerance at a level requires multiple domains at that level. The documented hierarchy includes site, rack, chassis, and node. Nodes are discovered automatically, while additional levels are optional. Storage Spaces uses fault-domain information to place redundant copies on separate failure domains. Microsoft documentation.\nApplicability\nUse this review when documenting a cluster’s physical placement. Identify real racks, chassis, sites, and shared dependencies. Include only hierarchy levels that describe the deployment rather than inventing unused physical distinctions.\nDSE recommendation\nHave the facilities and server owners reconcile the logical hierarchy with the equipment inventory. Record each node’s actual placement and the failure event each level represents. Review recent equipment moves for stale mappings. Keep data-copy placement objectives separate from quorum-witness placement, and obtain storage-owner review before changing the configured hierarchy.\nVerification\nCompare the reported fault-domain hierarchy with a checked physical inventory. Inspect the selected storage configuration through the supported management tools and record the relevant placement evidence. Exercise only the approved failure scenario and retain the observed workload result. Update both the map and its ownership record after accepted hardware moves or site changes.\nOfficial references\nMicrosoft Learn: Fault domain awareness. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft defines a fault domain as hardware sharing a single failure point; tolerance at a level requires multiple domains at that level. The documented hierarchy includes site, rack, chassis, and node. Nodes are discovered automatically, while additional levels are optional. Storage Spaces uses fault-domain information to place redundant copies on separate failure domains. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/failover-clustering/fault-domains).\n\n## Applicability\n\nUse this review when documenting a cluster’s physical placement. Identify real racks, chassis, sites, and shared dependencies. Include only hierarchy levels that describe the deployment rather than inventing unused physical distinctions.\n\n## DSE recommendation\n\nHave the facilities and server owners reconcile the logical hierarchy with the equipment inventory. Record each node’s actual placement and the failure event each level represents. Review recent equipment moves for stale mappings. Keep data-copy placement objectives separate from quorum-witness placement, and obtain storage-owner review before changing the configured hierarchy.\n\n## Verification\n\nCompare the reported fault-domain hierarchy with a checked physical inventory. Inspect the selected storage configuration through the supported management tools and record the relevant placement evidence. Exercise only the approved failure scenario and retain the observed workload result. Update both the map and its ownership record after accepted hardware moves or site changes.\n\n## Official references\n\n[Microsoft Learn: Fault domain awareness](https://learn.microsoft.com/en-us/windows-server/failover-clustering/fault-domains). 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-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/", "url": "https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Map cluster fault domains to the actual rack and site layout", "item": "https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/", "url": "https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/", "headline": "Map cluster fault domains to the actual rack and site layout", "description": "Which physical relationships should be represented in a cluster fault-domain hierarchy?", "abstract": "Which physical relationships should be represented in a cluster fault-domain hierarchy?", "articleBody": "Source facts\nMicrosoft defines a fault domain as hardware sharing a single failure point; tolerance at a level requires multiple domains at that level. The documented hierarchy includes site, rack, chassis, and node. Nodes are discovered automatically, while additional levels are optional. Storage Spaces uses fault-domain information to place redundant copies on separate failure domains. Microsoft documentation.\nApplicability\nUse this review when documenting a cluster’s physical placement. Identify real racks, chassis, sites, and shared dependencies. Include only hierarchy levels that describe the deployment rather than inventing unused physical distinctions.\nDSE recommendation\nHave the facilities and server owners reconcile the logical hierarchy with the equipment inventory. Record each node’s actual placement and the failure event each level represents. Review recent equipment moves for stale mappings. Keep data-copy placement objectives separate from quorum-witness placement, and obtain storage-owner review before changing the configured hierarchy.\nVerification\nCompare the reported fault-domain hierarchy with a checked physical inventory. Inspect the selected storage configuration through the supported management tools and record the relevant placement evidence. Exercise only the approved failure scenario and retain the observed workload result. Update both the map and its ownership record after accepted hardware moves or site changes.\nOfficial references\nMicrosoft Learn: Fault domain awareness. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:10+00:00", "dateModified": "2026-09-08T18:20:21+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/" }, "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-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/#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": "Map cluster fault domains to the actual rack and site layout" }, "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": 205, "timeRequired": "PT1M", "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": "Fault domain awareness", "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/fault-domains" } } ] } }