Academy/VCAP Advanced Storage (3V0-23.25)

VCAP Advanced Storage (3V0-23.25)

Advanced storage design and deployment covering vSAN architecture, storage policies, capacity management, encryption, stretched clusters, and HCI integration within VCF environments.

3V0-23.25
VCAP
60
Questions
135m
Duration
300 (scaled score; Broadcom publishes no percentage or ceiling)
Pass Score
33
Objectives

Exam Blueprint Weights

Section titles, groupings and weights below are VCDX Academy study groupings, NOT the official Broadcom blueprint structure. Broadcom publishes no section weights. Always cross-check the official exam guide. Official exam guide ↗
Section 1 — vSAN Architecture
~20%
Section 2 — Storage Policies
~20%
Section 3 — Cluster Operations
~20%
Section 4 — Performance and Capacity
~20%
Section 5 — Troubleshooting
~20%

vSAN iSCSI Target Service and vSAN Transport (RDT vs RDMA)#

vSAN iSCSI TARGET SERVICE

A cluster service (since vSAN 6.5) presenting vSAN-backed LUNs over iSCSI to initiators OUTSIDE the cluster.
SUPPORTED CONSUMERS

├── Remote physical servers and VMs outside the vSAN cluster
├── WSFC (Windows Server Failover Cluster) nodes — vSAN 6.7+
└── Physical Oracle RAC — the docs call it the "preferred method for mapping VMDKs to physical Oracle RAC deployments"

NOT SUPPORTED: other vSphere/ESXi hosts or initiators, third-party hypervisors, RDM migrations, MCS.

MAXIMA: 1024 LUNs per cluster, 128 targets per cluster, 256 LUNs per target, 62 TB per LUN, 64 initiators per LUN. Stretched-cluster support added in 7.0 U1.

ESA in VCF 9.x: supported — the current usage guide is written for VCF 9.1 and its iSCSI LUN policies are managed by Auto-RAID, which is ESA-only.

DESIGN STEER: for VIRTUALIZED WSFC and Oracle RAC, Broadcom recommends native shared VMDKs (SCSI3-PR for WSFC, multiwriter for Oracle RAC) over iSCSI. Reserve the iSCSI Target Service for PHYSICAL clustered hosts and legacy block consumers.

vSAN TRANSPORT — RDT, AND WHERE RDMA FITS

By default vSAN carries I/O as UNICAST TCP over Ethernet, using its purpose-built Reliable Datagram Transport (RDT) protocol on the vSAN-tagged VMkernel port. RDT is lightweight and built to set up and tear down sessions quickly.

RDMA (RoCE v2) is an OPTIONAL alternative introduced in vSAN 7 U2, recommended mainly for ESA. Critical operational property: if any single host loses RDMA, the ENTIRE cluster falls back to TCP.

RDMA constraints: certified NICs only, DCB/PFC-capable switches, 32 hosts maximum, no LACP or IP-hash teaming, and incompatible with 2-node, stretched clusters, datastore sharing and vSAN storage clusters.

COMMON EXAM ERROR: RDT did not replace RDMA. RDT long PREDATES RDMA support in vSAN — RDMA was added later as an accelerator. VCF 9.0 deprecates vSAN over RDMA for vSAN OSA (support will be discontinued in a future VCF release; VCF 9.0.1 docs p.233); RDMA remains available for ESA.

Key Takeaways

  • vSAN iSCSI Target Service serves initiators outside the cluster — physical servers, VMs, WSFC nodes (6.7+) and physical Oracle RAC. NOT other ESXi hosts, third-party hypervisors, RDM migrations or MCS. Supported on ESA in VCF 9.x.
  • For virtualized WSFC/Oracle RAC use native shared VMDKs (SCSI3-PR / multiwriter), not iSCSI — reserve iSCSI for physical clustered hosts.
  • vSAN's default transport is unicast TCP over Ethernet using RDT. RDMA (RoCE v2) is optional, added in vSAN 7 U2; a single host losing RDMA drops the whole cluster back to TCP.
  • Exam trap: RDT did NOT replace RDMA — RDT is long-standing, RDMA came later as an optional accelerator.

vSAN Capacity Reserves and RAID Overhead (verified reference)#

RAID OVERHEAD AND HOST MINIMUMS

├── RAID-1 FTT=1 = 2.0x overhead, 3 hosts minimum
├── RAID-1 FTT=2 = 3.0x, 5 hosts
├── RAID-1 FTT=3 = 4.0x, 7 hosts
├── OSA RAID-5 (3+1) FTT=1 = 1.33x, 4 hosts — OSA only, always 3+1
├── ESA RAID-5 ADAPTIVE FTT=1: 2+1 = 1.5x when the cluster has fewer than 6 hosts (3 host min); 4+1 = 1.25x at 6+ hosts (5 host min). vSAN re-evaluates 24 HOURS after a host-count change
└── RAID-6 (4+2) FTT=2 = 1.5x, 6 hosts minimum (7 recommended) — same in ESA and OSA

VCF 9.1 AUTO-RAID retires the 4+1 scheme: RAID-5 is always 2+1 and used only at 3-5 hosts; RAID-6 4+2 takes over at 6+.

SLACK SPACE IS OBSOLETE TERMINOLOGY

The flat 25-30% "slack space" rule applied only BEFORE vSAN 7 U1. From 7 U1 it is replaced by Reserved Capacity:

├── Operations Reserve (OR): NOT a fixed percentage — varies with capacity-device size/count, disk-group count and dedup/compression. Documented worked examples span 17% / 12% / 10% / 8% / 7% / 6%
└── Host Rebuild Reserve (HRR): approximately 1/N of the cluster — 25% at 4 hosts, ~8% at 12 hosts

Combined OR+HRR under 10% is achievable. EXCEPTIONS: Reserved Capacity cannot be enabled on a stretched or two-node cluster, a cluster with fault domains or nested fault domains, or a cluster with fewer than four hosts (VCF 9.1.x docs, Configure Reserved Capacity for vSAN Cluster, read 1 Oct 2026) — plan the free-capacity headroom manually there (about 25-30 % of free capacity as a working rule). VCF 9.1 keeps both reserves; do not state that they were removed.
Size with the vSAN ReadyNode Sizer, not a flat multiplier. Exam-style arithmetic using a 0.85 or 0.75 factor is a teaching shorthand, not Broadcom guidance.

WITNESS APPLIANCE

Four sizes — Tiny, Medium, Large, Extra Large. ESA DOES NOT SUPPORT THE TINY WITNESS; ESA starts at Medium. ESA and OSA use DIFFERENT witness OVAs with different vCPU/RAM:

  • ESA: XL 8 vCPU/64 GB · L 4/32 · M 4/16 · Tiny not supported
  • OSA: XL 6 vCPU/32 GB · L 2/32 · Normal 2/16 · Tiny 2/8

Capacity tiers: Tiny 750 components / <=10 VMs; Medium 21,833 / 500; Large 45,000 / >500; XL 64,000 / >500.

ESA MEDIA REQUIREMENTS

ESA = EXPRESS Storage Architecture (not "Elastic"). NVMe TLC flash only — at least one NVMe TLC device per storage pool. SAS and SATA devices are NOT supported, nor RAID/tri-mode controllers or HBAs. There is no HDD support of any kind. Minimum 1.6 TB production drives, 4+ devices per host recommended, host RAM >=128 GB. Only OSA (disk groups) can use magnetic media, and only in hybrid mode — which is deprecated as of the vSAN 9.0 announcement.

Key Takeaways

  • ESA RAID-5 is ADAPTIVE: 2+1 (1.5x) below 6 hosts, 4+1 (1.25x) at 6+, re-evaluated 24h after a host-count change. OSA RAID-5 is always 3+1 (1.33x, 4 hosts). RAID-6 4+2 FTT=2 = 1.5x, never 1.33x.
  • 'Slack space' 25-30% is pre-vSAN 7 U1 terminology. It is now Reserved Capacity = Operations Reserve (hardware-dependent, 6-17% in documented examples) + Host Rebuild Reserve (~1/N: 25% at 4 hosts, ~8% at 12). Size with the ReadyNode Sizer.
  • ESA does NOT support the Tiny witness — it starts at Medium — and ESA/OSA use different witness OVAs with different vCPU/RAM.
  • ESA = Express Storage Architecture, NVMe TLC only. No SAS, no SATA, no HDD, no RAID/tri-mode controllers. Only OSA hybrid uses magnetic media, and hybrid OSA is deprecated.

📝 Quiz — VCAP Advanced Storage

0/50 correct

vSAN Architecture

Q1
An ESA all-NVMe cluster must adapt RAID protection dynamically for performance vs. space efficiency. Which statement is correct?
  • ESA uses a log-structured engine with adaptive RAID-5/6 that can shift based on cluster size
  • ESA uses fixed RAID-1 only
  • ESA is identical to OSA internally
  • ESA requires dedicated cache disks
ESA uses a log-structured engine with adaptive RAID-5 erasure coding that adjusts its stripe width based on cluster size — using 2+1 for smaller clusters and 4+1 for 6+ hosts. RAID-5 and RAID-6 remain separate policy choices (not dynamically swapped). ESA is NOT fixed RAID-1 only, does NOT require dedicated cache disks (single-tier NVMe), and is architecturally different from OSA.
Q2
A disk group in OSA consists of:
  • Only SCM for metadata
  • Two witness devices per host
  • Only NVMe capacity drives
  • One cache tier device and up to seven capacity devices
An OSA disk group consists of one cache tier device (SSD/NVMe for read cache + write buffer) and up to seven capacity devices. ESA eliminated this two-tier model. Witness devices are for stretched clusters. SCM is used in ESA for metadata.
Q3
What are objects and components in the vSAN model?
  • Objects are physical disks; components are hosts
  • Objects are logical units like VMDKs; components are replica/witness pieces placed on hosts/disk groups
  • Objects are RAID groups; components are VLANs
  • Objects are clusters; components are vCenters
Objects are logical storage units (VMDKs, VM home namespaces, swap files). Components are the replica/witness/parity pieces of those objects distributed across hosts/disk groups. Objects aren't physical disks, RAID groups, or clusters.
Q4
vSAN Storage Clusters (disaggregated) primarily enable:
  • Removing witness requirement
  • Scaling storage independently from compute
  • Merging vSAN and NFS namespaces
  • Replacing vCenter
vSAN Storage Clusters (disaggregated) scale storage independently from compute by separating storage-only nodes from compute nodes. They don't merge namespaces, replace vCenter, or remove witness requirements.
Q5
In VCF 9.0, the most common principal storage for the management domain's default cluster is:
  • Local VMFS only
  • vSAN (OSA or ESA)
  • Fibre Channel only
  • NFSv3 from an external array
vSAN (ESA or OSA) is the usual principal storage for the management domain. VCF 9.0 also accepts NFSv3 and VMFS on FC as principal storage for the management domain and workload domains; NFSv4.1 is supplemental only (VCF 9.0.1 docs p.1086). Local VMFS is not a principal storage option.

Storage Policies

Cluster Operations

Performance and Capacity

Troubleshooting

🃏 Flashcards — VCAP Advanced Storage

53 cards
Card 1 of 53
vSAN Object
The logical storage unit in vSAN (a VMDK, namespace, or swap) composed of multiple components distributed across hosts by policy. Objects are opaque to the guest but visible in vSAN management. They are the atomic unit of placement and repair.
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.