# Map cluster fault domains to the actual rack and site layout

> Which physical relationships should be represented in a cluster fault-domain hierarchy?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:10+00:00
- Modified: 2026-09-08T18:20:21+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

Which physical relationships should be represented in a cluster fault-domain hierarchy?

## 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.

## Article

## Source facts

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](https://learn.microsoft.com/en-us/windows-server/failover-clustering/fault-domains).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

[Microsoft Learn: Fault domain awareness](https://learn.microsoft.com/en-us/windows-server/failover-clustering/fault-domains). Source reviewed September 8, 2026.

## Primary reference

- Name: Fault domain awareness
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/failover-clustering/fault-domains
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Map cluster fault domains to the actual rack and site layout,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-061-map-cluster-fault-domains-to-the-actual-rack-and-site-layout/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.