In this failover clustering demo, a two-node Windows cluster runs SQL Server and a clustered file server on VergeOS 26.2 shared disks, with no external SAN.
Mission-critical Windows workloads in VergeOS 26.2 · Narrated demo, 3:16
Why the Shared Disk Kept VMware in Place
Microsoft Failover Clustering needs a shared disk that every node in the cluster can reach. On VMware, that shared disk usually sits on a dedicated storage array, so the array, its refresh cycle and its support contract stay in place for one cluster. VMware stays with it, along with the renewal.
VergeOS 26.2 creates the shared disk inside VergeFS. Mark a virtual disk as shared, attach it to each node in the guest cluster, and SCSI-3 Persistent Reservations decide which node owns it, so failover works the way Windows expects. SQL Server failover instances, clustered file servers and Cluster Shared Volumes run on the same storage as every other VM.
These are guest clusters. The cluster software inside the guests coordinates writes, as it does on any platform. The demo cuts power to the active node and times how long SQL Server and the file share take to come back on the surviving node.
What to Watch in the Failover Clustering Demo
- Two-node Windows failover cluster. SQL Server and a clustered file server on VergeFS shared disks, with no external SAN.
- Power cut to the active node. SQL Server is back on the surviving node in 31.4 seconds; the file share in 25.3 seconds.
- Node returns. The failed node powers back on and rejoins the cluster.
See the full story. This demo is part of the VergeOS 26.2 presentation: Complete the VMware Exit with VergeOS 26.2.
Every VergeOS 26.2 asset is in one place at verge.io/vergeos26. To plan your own move, request a VergeOS demo or schedule a technical whiteboard session.
