vSAN Capacity ConsoleESA 8.0 U1 · sizing, what-if & HPE bill of materials
Design passes
Inputs
Hardware you already have
Set the host count, devices per host and device capacity in the cluster section below. The console works forwards from that hardware and tells you what fits.
Derived from your hardware
—
Capacity target
Derived workload
—
Virtual machine profile
Shape of a typical VM
Cluster and hardware
In OSA each disk group needs one cache device that contributes no capacity. The "NVMe per host" field is ignored in OSA mode — groups × capacity devices applies instead.
Topology and resilience
Storage policy (SPBM)
Reserves and assumptions
Datastore capacity
Usable capacity from hardware alone
Capacity ladder
From the requirement to the purchase order, one multiplier at a time
Object layout across hosts
data fragment
parity fragment
performance leg (RAID-1 durable log)
cache device (no capacity)
host outside the stripe
Compute
What-if
Effect of one change against the current design
Change
Raw
Usable for VMs
Δ capacity
Utilization
Δ vs today
Note
Design validation
Against the ReadyNode profile, vSAN limits and design guidance
Recommended HPE ReadyNode
Certified for vSAN ESA
Bill of materials — per host
Line
Description
Qty
HPE product no.
Source
HPE NVMe catalogue for vSAN ESA
Certified device families and verified product numbers
Certification audit
What is verified, what you must confirm before you order
Excluded — do not order with NVMe
Tri-mode controllers are unsupported by vSAN when attached to NVMe
vSAN ESA vs vSAN OSA
Live comparison for your design
Customer letter
Regenerates from the live design
Assumptions first, numbers second, the way a solution architect would send it.
Accuracy notes: The structure of the performance leg and of system overhead is well defined, but no single sizing figure is published for either, so those two sliders are planning assumptions rather than quoted constants. Operations reserve is calculated dynamically by vSAN; the slider is a conservative approximation. Compression defaults to 1.0:1 on purpose, because savings should not be banked before deployment. Product numbers marked confirm were not individually verified and must be picked in the Designer Tool. Every bill of materials must be validated in the Broadcom Compatibility Guide before ordering.