Leave No VM Behind

A complete VMware migration moves every workload, including the clustered SQL Server instances that nobody wants to touch. Most VMware exits start with the easy virtual machines. File servers, web tiers and test systems move quickly. Then the project stalls on two problems: the cutover window for large, busy VMs and the Windows workloads that depend on Microsoft Failover Clustering. The organization ends up running two hypervisors and paying VMware to protect a handful of servers. VergeOS 26.2 solves both problems, so IT can finish a complete VMware migration.

The last workloads in a VMware estate are the ones the business depends on most. They run the ERP database, the order system and the applications with uptime commitments written into contracts. Two issues hold them back. Large VMs with high change rates need a cutover window that application owners refuse to approve. Windows workloads protected by Microsoft Failover Clustering need a shared disk with SCSI-3 Persistent Reservations, a requirement that has historically pushed customers toward a dedicated storage array.

When those requirements go unmet, IT keeps a small VMware cluster running next to the new platform. That choice means two management interfaces, two support contracts and a VMware renewal sized around the servers that matter to the business. Many teams renew VMware for just one year to buy time, and the renewal repeats every year the hard workloads stay put. The exit stays incomplete, and the savings that justified it shrink.

The VergeOS VMware migration service has used changed block tracking for years. First, it copies the full VM with the source still running. Then it sends only the blocks that changed since the last pass. At cutover, the source VM powers off, the last changed blocks transfer, and the VM boots on VergeOS. Version 26.2 adds asynchronous I/O to its network block device (NBD) transfers, so both the initial full copy and the final transfer move faster. In VergeIO lab testing against VergeOS 26.1.8, transfers ran 2.2 times faster, cutting transfer time by about 55 percent.

A cutover that fits inside a standard maintenance window gets approved. One that stretches past it gets deferred, and deferred workloads are how VMware exits stall.

SQL Server Failover Cluster Instances and clustered file servers rely on a shared disk that every cluster node can reach. Microsoft Failover Clustering also uses SCSI-3 Persistent Reservations to control which node owns that disk at any moment. VergeOS 26.2 delivers both inside VergeFS, the storage layer built into VergeOS. VergeFS aggregates the drives inside each server into a single high-performance pool, so the cluster gets its shared disk from the same servers that run it.

Clustered SQL Server now moves with the rest of the estate. For the workloads that kept VMware in the data center, a complete VMware migration is finally on the table.

VergeOS virtual data centers (VDCs) give these workloads a home of their own. A VDC encapsulates virtual machines, virtual networks, storage and policies into a single object that IT manages as a unit. The clustered database, its application servers and the network that connects them all live inside one VDC.

IT snapshots, clones and replicates the entire VDC as one object. For example, cloning a production VDC creates a copy of the application environment, network configuration included, for testing patches, upgrades or a new SQL Server version without touching production. The clone keeps its internal addressing inside its own isolated network, so nobody re-addresses servers for a test lab. For disaster recovery, IT replicates the VDC to a second VergeOS site and brings up the whole application environment there with its networking intact.

Each VDC runs in its own network space, separate from other VDCs and from the host environment. Ransomware that compromises a workstation or a general-purpose server elsewhere reaches the VDC holding the clustered database only through the paths IT explicitly allows. That boundary limits lateral movement, the technique attackers use to spread from an initial foothold to the systems that hold the most valuable data. Frequent VergeOS snapshots of the VDC also give IT a clean, complete point to recover from.