Most vSAN explainers were written against the old architecture and never got revised. ESA replaced the storage engine and changed what a write is: acknowledged from a durable log on the default path, with the expensive work (parity, dedup) later, off the guest's clock. One write, end to end, and why the old trade-offs are gone.
I left my cloud platform slowly, one piece at a time. Files went first: a self-hosted Nextcloud on my own cluster, encrypted restic backups to Backblaze B2, and the bots fenced in with their own app passwords and Tailscale ACLs. Email and calendar are later phases, done the same slow way.
Everybody I watch use AI falls into one of two ditches: treat it like an oracle, or write it off after one bad answer. I use it every day, on real work, and I ship the results. This is what I've learned about where it belongs and where it doesn't.
A routine pre-patch health check on my lab's only domain controller turned up something embarrassing: its AD-integrated DNS had never loaded, in the entire life of the domain. The directory itself was healthy by every measure I could test.
VM-level backups for a load-bearing lab: a dedicated backup server locally, restic off-site, restores as the proof.
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.