We are migrating DB servers from "real" clusters to VMware. The question is with VMware how do you get similar functionality in VMware? Things like failover etc?
Is vMotion the answer? I wonder what other people do, what is considered best practice?
Hardware Cluster to VMware, is vMotion an alternative for clustering
clusteringvirtualisationvmware
Related Question
- Sql-server – SQL Server 2008 Cluster Across Two VMWARE Hosts
- SQL Server 2012 High Availability on VMware
- SQL Server 2008 R2 – Does VMWare VMotion Affect Performance?
- Sql-server – Migrate from SQL Server 2016 Failover Cluster to Availability Groups
- Sql-server – Methods for right-sizing SQL Server virtualization
- SQL Server – Understanding Standalone vs Failover Instance
Best Answer
vMotion and clustering aren't alternatives for one another. vMotion moves the same "machine" (albeit virtual) from one physical host to another.
This provides some sort of resilience to hardware failure (unless it's the shared SAN bombing out) but you can't fail over to another host if you would like to create a maintenance window with minimal downtime for example. vMotion won't help you if you need to patch the (virtual) servers without downtime.
If you need the clustering for other things than hardware failure resilience I wouldn't rely on the VMware features but I would create 2 VM's on separate physical boxes and create a regular cluster between the 2 VM's.
vMotion adds a few features like being able to move VM's between hosts to redistribute load and hopefully recover from a hardware failure but is not an alternative for clustering. Clustering between 2 VM's is not different from clustering between 2 physical machines.