Academy/VCF 9.0 Support (2V0-15.25)/Storage Core Concepts — vSAN for VCF
This lab targets VCF 9.0

Storage Core Concepts — vSAN for VCF

VCF 9.0Beginnersupportadmin⏱ 60 min

VCFFTS9 course content — VCF 9.0 focused

Objectives

  • List principal and supplemental storage options for VCF
  • Compare vSAN OSA (disk groups, cache+capacity) vs ESA (single pool, all-NVMe)
  • Explain vSAN data services including dedup, compression, encryption, erasure coding
  • Describe SPBM and FTT requirements (3 hosts for FTT≤1, 5 hosts for FTT=2)
  • Explain stretched vSAN cluster architecture and requirements (<5ms RTT, 10Gbps)

Prerequisites

Active Holodeck VCF 9.0 lab or access to VCF documentation

Required skills:

  • Basic VMware terminology

Tasks

Task 1 VCF Storage Options & vSAN Architecture

vSAN architecture understanding is critical for VCF — every VCF domain uses vSAN by default. The transition from OSA (Original Storage Architecture) to ESA (Express Storage Architecture) in VCF 9.0 is a key exam and design topic.

Master storage options in VCF and deep-dive into vSAN OSA vs ESA

Step 1
VCF Storage Options

Principal storage (chosen at domain/cluster creation and not changeable afterwards; VCF 9.0 Table 23): vSAN ESA, vSAN OSA (plus the vSAN storage-cluster and single-rack compute models for non-default clusters), VMFS on Fibre Channel, NFS v3. Supplemental storage (added later): VMFS on FC, NFS v3 and v4.1, iSCSI, NVMe/TCP, NVMe/FC, NVMe/RDMA. vSphere Virtual Volumes (vVols) is deprecated in VCF 9.0 and absent from Table 23, but the host-commissioning and workload-domain workflows still offer it as principal storage (vVols on FC, iSCSI or NFS); do not choose it for new designs. vSAN is preferred — fully integrated into VCF stack, no NFS share/permission config needed, VMs provisioned via built-in storage policies. NFS must be accessible from VCF network with read/write permissions. VMFS on FC: LUN must be pre-accessible and datastore pre-created.

Step 2
vSAN OSA vs ESA

OSA (Original Storage Architecture): two-tiered disk groups (cache tier + capacity tier), SSDs/NVMe for cache, SSDs/NVMe/magnetic for capacity. ESA (Express Storage Architecture): single storage pool, all-NVMe only, 4x better storage efficiency for compressible workloads, native zero-cost snapshots/clones without performance degradation. ESA designed for modern NVMe hardware evolution. ESA minimum host memory: 128 GB (significantly higher than OSA). The 'up to 4x storage efficiency' claim from VMware marketing refers to combined benefits of compression, deduplication, and single-tier architecture — actual efficiency varies by workload I/O pattern.

[HOLODECK NOTE] Holodeck simulates vSAN with virtual disks on the physical host's datastore. Neither OSA disk groups nor ESA NVMe pools use real physical disks — all I/O goes through the nested virtualization layer. vSAN performance metrics (IOPS, latency) in Holodeck are not representative of production. ESA's all-NVMe requirement is satisfied by virtual NVMe controllers in nested ESXi. Deduplication/compression ratios may differ from real workloads.

Step 3
vSAN Data Services & File Services

vSAN data services: deduplication and compression, encryption (at-rest + in-flight), RAID 5/6 erasure coding, high-performance snapshots (ESA). vSAN File Services: NFS/SMB file shares served directly from vSAN cluster. File Service resource requirements: ESX host minimum requirements must be met. Fault domains provide rack-level fault tolerance.

Validation Gate

Check: Calculate usable capacity for: 8 hosts × 6 NVMe × 3.84TB, RAID-1, including slack and metadata overhead

Expected: Raw: 184.32TB → RAID-1 (/2): 92.16TB → Reserved Capacity (Operations Reserve + Host Rebuild Reserve; for 8 hosts the host-rebuild share is about one host, ~12.5 %, plus the operations reserve — take the exact figures from the vSAN Sizer): roughly 75-78TB → metadata (~2 %): ~74TB usable

Common Errors

Confusing vSAN OSA and ESA architectures
Fix: OSA: two-tier (cache + capacity disks, separate disk groups). ESA: single-tier (all NVMe, no disk groups, no cache tier). VCF 9.0 defaults to ESA. OSA is legacy but still supported for upgrades. Key difference: ESA processes I/O in a single data path — lower latency, simpler management.
Not accounting for vSAN slack space in capacity planning
Fix: Current vSAN manages spare capacity as Reserved Capacity: an Operations Reserve plus a Host Rebuild Reserve, off by default, enabled per cluster and scaling with host count (host rebuild reserve about 25 % at 4 hosts, ~8 % at 12). VCF design recommendation VCF-VSAN-RCMD-CFG-003 is to enable it instead of a generic 25-30 % 'slack'. Always include the reserves in capacity waterfalls, sized for the actual host count.
Applying RAID-5/6 erasure coding without understanding minimum host requirements
Fix: RAID-5 on vSAN OSA needs 4 hosts (3+1, 1.33×); on vSAN ESA — the VCF 9.0 default this lab assumes — RAID-5 adapts to cluster size: 2+1 (1.5×) on 3-5 hosts and 4+1 (1.25×) on 6 or more (VCF 9.0.1 docs p.1709). RAID-6 (4+2, 1.5×) needs 6 hosts on either architecture. Attempting to apply these policies on undersized clusters causes object creation failures.

Task 2 Storage Policy Based Management & Stretched Clusters

Storage policies drive vSAN behavior — understanding FTT, stripe width, and encryption at the policy level is essential for matching storage characteristics to workload requirements.

Understand SPBM and stretched vSAN cluster architecture

Step 1
Storage Policy Based Management (SPBM)

VM storage policies define performance, availability, and compliance requirements. Key capabilities: FTT (Failures to Tolerate — determines data copies), stripe width, force provisioning. Policies applied per-VM or per-VMDK. Policy compliance monitoring ensures VMs meet their storage SLA. FTT=0 or 1 requires minimum 3 hosts; FTT=2 requires minimum 5 hosts.

Step 2
Stretched vSAN Clusters

Architecture: two active availability zones + one witness site. Each AZ = own fault domain. Requirements: VCF 9.0 subscription (vSAN capacity is included with the VCF core subscription; license keys are no longer used), ≥10 Gbps bandwidth and <5 ms RTT between the two data sites, and a third witness site reachable at 2 Mbps per 1,000 vSAN components with <200 ms RTT (<100 ms at 11-15 hosts per site). Witness host/appliance requirements: network connectivity to both AZs, sufficient resources. Provides resilience across geographic locations for DR.

[HOLODECK NOTE] Stretched vSAN clusters require <5 ms RTT and 10 Gbps between the data sites; the witness link is low-bandwidth (2 Mbps per 1,000 components, <200 ms RTT). Holodeck runs on a single physical host — you cannot meaningfully simulate cross-site latency, witness placement, or site failure scenarios. Stretched cluster configuration can be studied architecturally but not tested for real fault-domain behavior in Holodeck.

Step 3
Supplemental Storage Options

Beyond vSAN as principal storage, VCF supports supplemental storage: NFS v3 and v4.1 (network-attached, must be accessible from the VCF network with read/write permissions), VMFS on Fibre Channel (LUN pre-provisioned and visible to the ESX hosts, datastore pre-created), iSCSI, and NVMe over Fabrics (NVMe/TCP, NVMe/FC, NVMe/RDMA). vVols is deprecated in VCF 9.0 and should not be recommended for new designs. Supplemental storage can be added after workload domain creation — e.g., vSAN principal + NFS ISO store, or NFS principal + FC supplemental for specific workloads. For exam objective 5.7: understand troubleshooting iSCSI (network path, initiator config, CHAP auth), NFS (export permissions, firewall rules, DNS resolution), and FC (zoning, LUN masking, path failover via PSA/NMP).

Validation Gate

Check: Explain the capacity multiplier for: FTT=1 RAID-1, FTT=1 RAID-5, FTT=2 RAID-1, FTT=2 RAID-6

Expected: FTT=1 RAID-1: 2×; FTT=1 RAID-5: OSA 1.33× (3+1), ESA 1.5× (2+1, under 6 hosts) or 1.25× (4+1, 6+ hosts); FTT=2 RAID-1: 3×; FTT=2 RAID-6: 1.5×

Common Errors

Setting FTT=2 without understanding the 3× capacity cost of RAID-1
Fix: FTT=1 (RAID-1) uses 2× raw capacity. FTT=2 (RAID-1) uses 3× raw capacity — three copies of every object. FTT=2 with RAID-6 (erasure coding, 4+2) uses 1.5× — more efficient but requires 6+ hosts (RAID-5 tolerates only one failure). Always calculate the capacity impact before choosing FTT level.
Enabling both vSAN encryption and VM encryption (double encryption)
Fix: vSAN data-at-rest encryption (cluster level) + VM encryption (per-VM) results in double encryption — no additional security benefit, approximately 8-10% cumulative CPU overhead. Choose one layer: vSAN encryption for broad coverage, VM encryption only for VMs requiring per-VM key management.

Design Reflection (VCDX)

vSAN capacity waterfall calculations are one of the most frequently asked VCDX questions. Be prepared to walk through raw → RAID → slack → usable on a whiteboard. Panelists also test whether you understand when to use RAID-1 vs RAID-5/6 for different workload tiers.

Requirements

  • Understand vSAN ESA vs OSA architectures
  • Calculate capacity waterfall from raw to usable
  • Apply appropriate RAID policies per workload tier

Constraints

  • RAID-5: OSA 3+1 needs 4 hosts (1.33×); ESA uses 2+1 on 3-5 hosts (1.5×) and 4+1 on 6+ hosts (1.25×). RAID-6 (4+2) needs 6 hosts (1.5×)
  • vSAN Reserved Capacity (Operations Reserve + Host Rebuild Reserve) must be sized; it scales with host count (≈25 % at 4 hosts, ≈8 % at 12) and can be enabled or disabled
  • ESA requires all-NVMe — no HDD or SAS support

Assumptions

  • All drives are same capacity within a cluster (homogeneous)
  • Network bandwidth sufficient for rebuild operations (25GbE recommended)

Risks

  • Capacity exhaustion during rebuild if slack space is consumed
  • Double encryption overhead degrading performance without security benefit

⚠ Known Pitfalls

Forgetting vSAN Reserved Capacity — every capacity calculation must include the Operations Reserve and the Host Rebuild Reserve for the actual host count (not a flat 25 %).
Assuming vSAN OSA knowledge transfers directly to ESA — the single-tier architecture, I/O path, and management model are fundamentally different.

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.