vSAN ESA Global Dedup: One Store for the Whole Cluster

vSAN ESA in 9.1 makes the cluster-wide dedup toggle generally available. Turning it on creates one dedup store for the whole cluster: a real backend object with its own UUID, holding two kinds of objects. Chunk objects are the deduplicated data, and hash objects are the fingerprint index.

Global dedup runs on single-site ESA clusters (3 to 64 HCI hosts, or vSAN storage clusters). It isn't supported on stretched or two-node clusters.

The command line is where you'll find the store's UUID. The Virtual Objects UI doesn't show it, which is a documented 9.1 Known Issue, so the checks are CLI:

esxcli vsan dedup dedupstore get
esxcli vsan dedup dedupstore distribution get -c
esxcli vsan dedup dedupstore distribution get -x

The first command shows the store: whether the service is enabled and paused (turning dedup off pauses the service; data already deduplicated stays deduplicated), the store UUID, and the counts of chunk and hash objects. The distribution commands show how those objects spread across hosts.

The reading that proves the model is the shared UUID. On my cluster the day I enabled it, Oct 22, the store held 32 chunk objects and 32 hash objects. The distribution rows showed 10 chunk and 10 hash on the first host, 11 and 11 on each of the other two, and every single row carried the same store UUID. If you see a different store UUID on one host, that is the anomaly. If you see the same one everywhere, the cluster agrees about its store.

Empty output is also a reading. On a cluster with the feature off, both the store command and the distribution command answer with a single line: "Global dedup is not enabled on current host." That is the off state, not an error or a failed command.

The resync commands are where I learned the most, because the numbers looked broken until I understood what they were saying:

esxcli vsan dedup dedupstore resync list
esxcli vsan dedup dedupstore resync summary get

I captured these during a reconfiguration where the cluster was resyncing more than 200 GB of VM objects. The dedup summary showed 64 total dedup objects, zero resyncing, zero bytes left to sync, and the resync list returned no output at all. My first instinct was that something was wrong with the dedup store. It was not. The dedup store's objects report resync through their own commands, and that reconfiguration didn't touch them.

When dedup looks wrong, check the store object itself: its UUID, whether it is enabled and unpaused, its distribution across hosts, and its resync state. Check whether the cluster agrees on one store before you chase host-level theories.

This write-up covers the object model and the readings. I enabled global dedup in the lab to learn how the store behaves; capacity numbers will come when there's something worth measuring.

Sources

Updated Nov 17, 2026: narrowed the resync description to what the readings show, and edited the prose for clarity.


Daniel Barnes

Technical Support Engineer, VMware Cloud Foundation Division at Broadcom. Customer-facing work on VMware vSAN, ESXi, and VMware Cloud Foundation: storage, HCI, and virtualization troubleshooting. Views are my own and not necessarily those of Broadcom. I use AI tools for drafting and editing; the technical claims are mine, checked against public documentation and my own lab.

Started in 2018.

Homelab is a 3-host vSAN ESA cluster on ESXi 9.1 running self-hosted services (Nextcloud, Pi-hole DNS). That's where the write-ups come from.