Study guide

3.5 vSAN Resilience & Data Availability: FTT, Fault Domains, and Stretched Clusters

VMware Certified Professional - VMware Cloud Foundation Administrator VCP-VCF 2V0-17.25

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Private Cloud Vision & Architecture

1.1 Private Cloud Principles & The Modern Cloud Operating Model 1.2 VMware Cloud Foundation Architecture & Full-Stack Value Proposition 1.3 Private Cloud Use Cases, Service Models & Workload Strategy

2 Chapter 2: VMware Compute Fundamentals

2.1 ESXi Host & vCenter Architecture and Deployment 2.2 vSphere Cluster Design, High Availability (HA), and DRS 2.3 Virtual Machine Deployment, Advanced Hardware, & Management 2.4 Managing Virtual Machines Through vCenter: Day-2 Operations

3 Chapter 3: VMware Storage Fundamentals

3.1 vSphere Core Storage Architecture: VMFS, NFS, & vVols 3.2 vSAN Architecture: Express Storage Architecture (ESA) vs. Original Storage Architecture (OSA) 3.3 vSAN Cluster Deployment, Storage Pools, & Disk Configurations 3.4 Storage Policy-Based Management (SPBM), Fault Tolerance, & Space Efficiency 3.5 vSAN Resilience & Data Availability: FTT, Fault Domains, and Stretched Clusters 3.6 vSAN Space Efficiency: Compression, Deduplication, TRIM/UNMAP & Reclamation

4 Chapter 4: VMware Network Fundamentals

4.1 VCF Network Architecture & NSX Core Components 4.2 NSX Virtual Network Fabrics, Transport Nodes, & Geneve Overlays 4.3 Edge Clusters, Tier-0/Tier-1 Gateway Routing, & Uplink Connectivity 4.4 NSX Distributed Firewall (DFW) & Distributed Network Services 4.5 VCF 9.0 Virtual Private Clouds (VPCs) & Transit Gateway Connectivity

5 Chapter 5: VCF Deploy and Configure

5.1 VCF Deployment Models: Standard vs. Consolidated & Prerequisites 5.2 VCF Installer Bring-Up & Management Domain Deployment 5.3 VI Workload Domain Deployment, Commissioning Hosts, & Storage Attachment 5.4 vSphere Supervisor Configuration & vSphere Kubernetes Service (VKS) Integration 5.5 VCF Deployment Components & Additional Required Infrastructure 5.6 Deploying & Configuring the VCF Network Gateway 5.7 VCF Networking Deployment: NSX Instances, Transport Fabric & Edge Clusters 5.8 Workload Domain Storage: Principal vs. Supplemental Storage

6 Chapter 6: VCF Manage & Lifecycle Operations

6.1 VCF Fleet Management & Existing vCenter Import Workflows 6.2 Identity Federation, VCF Identity Broker, & RBAC 6.3 Certificate & Password Lifecycle Management in VCF Operations 6.4 Lifecycle Management (LCM), Upgrade Bundles, & Drift Remediation 6.5 License Management in VMware Cloud Foundation

7 Chapter 7: VCF Operations: Architecture, Metrics & Health Diagnostics

7.1 VCF Operations Architecture, Cluster Nodes, & Deployment Options 7.2 Metrics, Properties, Symptom Definitions, & Alerting Mechanics 7.3 Health Diagnostics, Troubleshooting Workflows, & Operational Policies

8 Chapter 8: VCF Operations: Monitoring, Logs & Compliance

8.1 Dashboards, Views, & Management Reporting in VCF Operations 8.2 Storage, Network, and Workload Application Monitoring 8.3 Log Analytics & Troubleshooting with VCF Operations for Logs 8.4 Security Compliance Benchmarks, Hardening, & Configuration Drift 8.5 VCF Operations for Networks: Flow Analytics, Path Troubleshooting & Micro-Segmentation Planning

9 Chapter 9: VCF Consume & Automate: Architecture, Tenancy & Networking

9.1 VCF Automation Architecture, Services, & Automation Use Cases 9.2 Regions, Cloud Zones, Projects, & Multi-Org Tenancy 9.3 Provider Networking, Org Networks, & Content Library Integration

10 Chapter 10: VCF Consume & Automate: Templates, Extensibility & Governance

10.1 Cloud Templates (Blueprints), Schema, & Infrastructure as Code 10.2 Extensibility: Action-Based Extensibility (ABX) & Orchestrator Workflows 10.3 Governance Policies: Approvals, Leases, Resource Quotas, & Day-2 Actions 10.4 Supervisor-Based Services, vSphere Kubernetes Service (VKS), & Modern App Consumption

3.5 vSAN Resilience & Data Availability: FTT, Fault Domains, and Stretched Clusters

Key Takeaways Explain This Topic AI

Failures to Tolerate (FTT) is a storage policy attribute; RAID-1 mirroring for FTT=n requires 2n+1 fault domains, so FTT=1 needs three and FTT=2 needs five.

vSAN OSA erasure coding uses a fixed 3+1 RAID-5 requiring four hosts and a 4+2 RAID-6 requiring six; vSAN ESA uses adaptive RAID-5, choosing 2+1 on clusters of up to five hosts and 4+1 on six or more.

A fault domain groups hosts that share a failure boundary such as a rack, so vSAN places replicas across domains rather than across hosts that could fail together.

A stretched cluster spans two data sites plus a witness host that stores only witness components and casts the tie-breaking vote; the witness holds no VM data.

vSAN distinguishes ABSENT components, which trigger rebuild only after the 60-minute repair delay, from DEGRADED components, which begin rebuilding immediately because the failure is known to be permanent.

Last updated: September 2026

3.5 vSAN Resilience & Data Availability: FTT, Fault Domains, and Stretched Clusters

Exam Focus: The blueprint calls out "identify the options for Resilience and Data Availability in VMware vSAN" as a discrete objective. Scenario items typically supply a host count and a required protection level and ask which placement scheme is possible — so the host-count arithmetic matters as much as the concepts.

Failures to Tolerate (FTT) and Placement Schemes

Failures to Tolerate (FTT) is an attribute of a vSAN storage policy , not a cluster-wide switch. It states how many concurrent failures of a host or fault domain an object must survive. Because it lives in policy, two VMs on the same cluster can carry different protection levels.

vSAN implements FTT through one of two placement families:

RAID-1 Mirroring

Full copies of each object are written to separate fault domains, with witness components breaking ties. Mirroring costs the most capacity and delivers the lowest write amplification.

  • Protection Data copies Minimum fault domains Capacity overhead
  • FTT=1 (RAID-1) 2 3 2.0×
  • FTT=2 (RAID-1) 3 5 3.0×
  • FTT=3 (RAID-1) 4 7 4.0×

The rule generalises to 2n+1 fault domains for FTT=n . The extra domain exists to host witness components so a surviving partition can establish a quorum of more than 50 percent of votes.

RAID-5 and RAID-6 Erasure Coding

Erasure coding stores data plus parity fragments instead of whole copies, trading write amplification for a large capacity saving. The scheme differs between the two vSAN architectures, and this is a frequent exam discriminator.

  • Architecture Scheme Fragments Minimum hosts Capacity overhead
  • OSA RAID-5 (FTT=1) Fixed 3+1 3 data + 1 parity 4 1.33×
  • OSA RAID-6 (FTT=2) Fixed 4+2 4 data + 2 parity 6 1.5×
  • ESA RAID-5 (FTT=1) Adaptive 2+1 2 data + 1 parity 3 1.5×
  • ESA RAID-5 (FTT=1) Adaptive 4+1 4 data + 1 parity 6 1.25×
  • ESA RAID-6 (FTT=2) Fixed 4+2 4 data + 2 parity 6 1.5×

Adaptive RAID-5 is an ESA capability: on clusters of up to five hosts vSAN uses the 2+1 layout, and on six hosts or more it uses the more efficient 4+1 layout. Note the boundary carefully — 4+1 requires six fault domains, not five, because each of the five fragments needs its own domain plus room to rebuild.

Important

Why ESA changes the erasure-coding calculus. In OSA, RAID-5 and RAID-6 carried a real write penalty, so mirroring was the default for performance-sensitive workloads. ESA's log-structured design writes and acknowledges at the performance leg before computing parity, which allows erasure coding at mirror-like performance. In ESA the space-efficient scheme is therefore the sensible default rather than a compromise.

Fault Domains: Failure Boundaries, Not Hosts

By default vSAN treats every host as its own fault domain. That is correct only if hosts fail independently. When twelve hosts occupy three racks, a single rack power loss takes out four hosts at once — and unconfigured vSAN may have placed both mirror copies inside that rack.

Configuring fault domains groups hosts by shared failure boundary (rack, chassis, or power feed). vSAN then places replicas and parity fragments across domains , so a whole-rack outage costs at most one component per object.

The host-count arithmetic changes accordingly: FTT=1 with RAID-1 needs three fault domains , which with rack-level grouping means three racks rather than three hosts.

Stretched Clusters and the Witness

A stretched cluster extends a single vSAN cluster across two geographically separated data sites to survive the loss of an entire site. It has three participants:

Preferred site and secondary site , each holding a complete copy of protected data.

A witness host at a third location, which stores only witness components — metadata, never VM data . Its role is to cast the deciding vote so that when the inter-site link fails, exactly one site retains quorum and the other stops serving I/O. This prevents split-brain.

Protection in a stretched cluster is expressed on two axes:

Site disaster tolerance governs cross-site mirroring.

Failures to tolerate governs protection within each site, so a site can survive a local host failure without falling back to the remote copy.

A related topology, the two-node cluster , applies the same witness concept to a pair of hosts at a remote or edge location.

Component States and Repair Behaviour

When vSAN loses access to a component it classifies the failure, and the classification determines how fast it reacts.

State Meaning vSAN response

ABSENT Component unreachable, but the failure may be transient — a rebooting host, a pulled network cable, maintenance mode Waits out the repair delay (default 60 minutes) before rebuilding, avoiding a costly resync for a host that is coming back

DEGRADED Component is on hardware that has failed permanently — a dead device reporting errors Begins rebuilding immediately , because waiting cannot help

Tip

The maintenance-mode connection. The 60-minute repair delay is precisely why patching a host does not trigger a fleet-wide resync storm. It is also why Ensure accessibility is the usual maintenance-mode choice: it evacuates just enough data to keep objects available rather than fully evacuating, which would be a Full data migration .

Exam Watch: Key Scenarios and Candidate Traps

Warning

Count fault domains, not hosts. A six-host cluster that has been carved into three rack-level fault domains cannot satisfy RAID-6, which needs six domains. The host count looks sufficient; the domain count is not.

Important

The witness never holds data. If an answer option claims the witness host stores a third copy of virtual machine data, it is wrong. The witness stores witness components only.

Loading diagram... vSAN Protection Schemes, Fault Domains, and Component Repair Logic