Study guide

6.4 vSAN Space Efficiency & Capacity Accounting

VMware vSphere Foundation 9.0 Administrator VCP-VVF, 2V0-16.25

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Preparation Strategy

1.1 Exam Format, Passing Standard & Blueprint Structure 1.2 Preparation Strategy & Hands-On Lab Setup

2 Chapter 2: Virtualization & ESXi Host Fundamentals

2.1 Hypervisor Architecture & ESXi Operating Model 2.2 ESXi Deployment, DCUI & Initial Host Configuration 2.3 Workload Consolidation & Private Cloud Economics

3 Chapter 3: vCenter Server & Cluster Management

3.1 vCenter Server Appliance (VCSA) Architecture & Deployment 3.2 vSphere High Availability (HA) & Admission Control 3.3 Distributed Resource Scheduler (DRS) & EVC Configuration

4 Chapter 4: Virtual Machine Operations & Resource Management

4.1 Virtual Machine Provisioning, Templates & Content Libraries 4.2 Resource Allocation: Shares, Reservations & Limits 4.3 vMotion, Storage vMotion & Snapshot Management 4.4 Content Libraries, Publication & Template Versions

5 Chapter 5: vSphere Storage Architecture & Traditional Datastores

5.1 Block Storage Architecture, Fibre Channel & VMFS Datastores 5.2 NFS Datastores, Software iSCSI & Multipathing (NMP) 5.3 Storage Policy-Based Management (SPBM) Framework

6 Chapter 6: VMware vSAN Architecture & Storage Policies

6.1 vSAN Core Architecture: OSA vs Express Storage Architecture (ESA) 6.2 Deploying & Configuring a vSAN Cluster 6.3 vSAN Storage Policies, Resilience (FTT) & Fault Domains 6.4 vSAN Space Efficiency & Capacity Accounting

7 Chapter 7: vSphere Networking & Traffic Management

7.1 Standard Switches (vSS) vs Distributed Switches (vDS) 7.2 Port Groups, VMkernel Adapters & Traffic Isolation 7.3 NIC Teaming, Load Balancing, VLANs & NIOC

8 Chapter 8: VVF Deployment & Supervisor Configuration

8.1 VMware vSphere Foundation 9.0 Stack & Deployment Prerequisites 8.2 End-to-End VVF Deployment Workflow 8.3 Enabling & Configuring the vSphere Supervisor

9 Chapter 9: Identity, Licensing & Security Management

9.1 vCenter Single Sign-On (SSO), Identity Federation & RBAC 9.2 VVF 9.0 Core-Based Licensing & License Management 9.3 VMware Certificate Authority (VMCA) & TLS Configuration 9.4 Workload & Infrastructure Encryption

10 Chapter 10: Lifecycle Management with vLCM

10.1 vSphere Lifecycle Manager (vLCM) Image Architecture 10.2 Base Images, Vendor Add-ons & Hardware Support Managers (HSM) 10.3 Host Compliance Checks, Staging & Cluster Remediation

11 Chapter 11: VCF Operations: Performance, Capacity & Alerts

11.1 VCF Operations Architecture, Node Types & Adapters 11.2 Dashboards, Custom Views, Metrics & Reports 11.3 Capacity Planning, Rightsizing & Alert Policies

12 Chapter 12: VCF Operations for Logs & Compliance

12.1 VCF Operations for Logs Architecture & Ingestion 12.2 Interactive Log Analytics, Query Syntax & Dashboards 12.3 Security Hardening Compliance & Storage/App Monitoring

13 Chapter 13: Workload Consumption & Automation

13.1 vSphere VM Service: Classes, Images & Declarative Deployment 13.2 VMware Kubernetes Service & Workload Clusters 13.3 VCF Operations Orchestrator Workflows & Automation 13.4 Supervisor Services & vSphere Pods

14 Chapter 14: Operations Evidence, Policies & Financial Reporting

14.1 Metrics, Properties & Logs 14.2 Custom Views & Scheduled Reports 14.3 Effective Policies, Groups & Overrides 14.4 Cost Drivers, Pricing & Showback

15 Chapter 15: Log Integrations & Shared Operational Views

15.1 VVF Integrations & Log Events in Operations 15.2 Logs Dashboards, Queries & Sharing

16 Chapter 16: Guest Services & Application Monitoring

16.1 Configure Service Discovery 16.2 Application & Guest Monitoring

6.4 vSAN Space Efficiency & Capacity Accounting

Key Takeaways Explain This Topic AI

Thin allocation, parity, compression, deduplication and reclamation are different mechanisms.

OSA disk-group deduplication differs from ESA 9.0 global deduplication; availability and feature compatibility must be checked.

600 GiB at a simplified 3+1 multiplier requires 800 GiB before other overhead.

Efficiency savings do not eliminate operational/rebuild reserves or independent failure-domain requirements.

Last updated: October 2026

Separate the Capacity Mechanisms

The storage blueprint asks why vSAN space efficiency matters. Thin provisioning , erasure coding , compression , deduplication and space reclamation save capacity through different mechanisms. They do not substitute for fault tolerance, backups or operational headroom. A system can show excellent compression while lacking enough free independent capacity to repair a failed host.

Thin provisioning allocates storage as data is written rather than reserving the full logical disk immediately. Erasure coding stores data and parity instead of full mirrored copies. Compression represents suitable content in fewer bytes; deduplication avoids storing identical blocks repeatedly. Reclamation releases storage that no longer needs to hold live data, subject to the relevant filesystem, snapshot and storage layers.

Mechanism What reduces consumption Common misunderstanding

Thin allocation Unwritten logical capacity need not be physically allocated Logical provisioned size is not current consumption

Erasure coding Parity overhead is lower than extra full copies for applicable policies A smaller capacity multiplier is not more failure tolerance by itself

Compression Compressible blocks occupy fewer bytes Precompressed or encrypted data may save little

Deduplication Identical blocks share storage representation Savings depend on actual duplicate content and supported scope

Reclamation Unneeded allocated blocks can be released Guest deletion does not always release every underlying layer immediately

OSA and ESA Have Different Designs

All-flash OSA can use deduplication/compression with a disk-group deduplication scope. It also has supported compression-only options in applicable releases; do not claim deduplication and compression must always be enabled together. Enabling or changing a cluster-level efficiency service can involve data movement and operational prerequisites. Plan the change rather than assuming it is just a policy label.

ESA compresses data high in the I/O path, before network transmission, and supports policy-specific controls. ESA 9.0 also introduces global deduplication , so the older statement that ESA eliminates deduplication entirely is incorrect. Its deduplication scope spans the cluster and its processing occurs after data has been persisted, using the supported background design.

Availability is a separate issue from architectural existence. The 9.0 global-deduplication introduction explains the design; the 9.0 FAQ describes limited availability. Verify the exact product release, access, entitlement, encryption compatibility and supported configuration before selecting it. Do not promise that every VVF installation can turn it on immediately.

Work a Capacity Example Correctly

Assume a logical payload of 600 GiB . In a simplified calculation ignoring compression, metadata, snapshots and reservations, two-way RAID-1 mirroring requires 1,200 GiB . A 3+1 erasure-coded layout needs 600 × 4/3 = 800 GiB . A 4+2 layout needs 600 × 6/4 = 900 GiB , providing the corresponding dual-parity protection.

These are planning multipliers, not exact datastore measurements. Add metadata, object-management overhead, reservations, snapshot history, transient policy-conversion space and rebuild headroom. Do not apply a compression ratio twice or mix a raw-to-logical ratio with a logical-to-raw multiplier. Also keep decimal GB/TB separate from binary GiB/TiB.

For ESA 9.0 adaptive RAID-5, a three-to-five-host cluster selects 2+1 and a cluster with six or more hosts selects 4+1. The selected layout's host-count rule differs from simply counting five fragments. Use the architecture-specific behavior rather than importing OSA's 3+1 rule or a later release's Auto-RAID behavior.

Observe Before Promising Savings

Choose representative data, not an empty VM or a duplicated test image alone. Observe logical use, physical use, savings, policy and available reserve over a realistic period. Database encryption, compressed media and repeated operating-system images produce different efficiency results. Background deduplication can also make immediate post-write consumption differ from later steady-state consumption.

A storage-policy change can temporarily need old and new layouts to coexist. Ensure that the cluster has enough compatible hosts/fault domains and free capacity before applying it to many objects. Watch resynchronization and policy compliance afterward. A successful policy edit does not establish that every object's physical conversion has finished.

Administrative Scenario

A capacity report shows strong data reduction but a planned host evacuation fails. Investigate the remaining host count, storage-policy placement, object reservations, operational/rebuild reserves and resync state. Deduplication savings cannot place a second mirror into an unavailable fault domain. Adding nominal free space on the wrong host may also fail to satisfy the placement constraint.

For the exam, explain why a mechanism saves capacity and what it does not prove . The most useful answer connects workload characteristics, supported configuration, resilience and recoverability. A headline reduction ratio alone is insufficient to approve a storage design.

Review Takeaways

Thin allocation, parity, compression, deduplication and reclamation are different mechanisms.

OSA disk-group deduplication differs from ESA 9.0 global deduplication; availability and feature compatibility must be checked.

600 GiB at a simplified 3+1 multiplier requires 800 GiB before other overhead.

Efficiency savings do not eliminate operational/rebuild reserves or independent failure-domain requirements.