Leaving VMware means leaving vSAN, which makes every VMware exit a storage decision. vSAN customers who stay are steered toward vSAN ESA, which runs only on certified NVMe flash at a time when NVMe drive prices have tripled, rules out the SAS and SATA drives already in their servers, and needs the full VCF management stack before storage works. The resources below compare that path with VergeOS, which installs on the servers vSAN runs on today, mixes NVMe, SSD and hard drives in one storage pool, and deduplicates inline across every node.
Solution Content
Running vSAN? Your VMware Exit Is a Storage Decision
Most exit plans price a new hypervisor. George Crump and Dave Vincent compare three exit paths for vSAN customers, show how vSAN data moves off VMware on the servers you already own, and close with a live migration demo from Dave’s lab.
Register for the Webinar →VergeIO Blogs
The CPU and Memory Economics of vSAN
Array controllers are servers, vSAN claims CPU and RAM on every host, and NSX adds its own VMs. This post counts the servers a midsize data center actually runs and shows VergeOS handling the same workloads on five, about 20% fewer than the six application servers alone.
Read the Post →Comparing vSAN ESA to VergeFS
A side-by-side look at vSAN ESA and VergeFS across drive support, deduplication, disaster recovery, infrastructure prerequisites and hardware reuse, including the gap between a $10,000 NVMe drive and a $1,200 24 TB hard drive.
Read the Post →Social Media
Count the Servers
Count every server in a midsize three-tier data center and the storage array adds two more. A short look at where vSAN and NSX take CPU and memory from your applications, and what changes when one OS runs compute, storage and networking.
View on LinkedIn →Your Storage Array Is a Server
vSAN takes CPU and RAM from every host, and NSX adds its own VMs. The short version of the server count, and how one infrastructure OS gives that capacity back to your applications.
View on X →Leaving VMware Means Leaving vSAN
A SAN customer points a new hypervisor at the array it already owns. A vSAN customer has no array to point at. The three things a vSAN alternative needs to deliver: reuse of the hosts you own, built-in server-side storage and a backup-style migration.
View on LinkedIn →What to Look for in a vSAN Alternative
The right alternative runs on the hosts you already own, delivers server-side storage that matches vSAN and improves on it, and migrates VMs with a backup-style workflow that keeps production running until cutover.
View on X →Industry Articles
What to Look for in a vSAN Alternative
A vSAN customer has to replace the hypervisor and the storage at the same time. The post covers what the alternative must deliver: reuse of the existing vSAN hardware, server-side storage equal to or better than vSAN, and a migration that keeps production running until cutover.
Read the Post →Can a VSAN Help You Fight Data Center Inflation?
With NVMe flash costing three to four times what it did a year ago, a virtual SAN can lower storage costs, but only if it meets three requirements: it runs without VMware, it supports more than NVMe, and it delivers global inline deduplication.
Read the Post →More to Come
The webinar presentation and on-demand recording will be added here after the November 12 live event, along with additional blogs and campaign assets as they publish.