SQL Cluster Failover on vmware

Hi All

We are trying to setup HA in our database server, in our vSphere 5.1 VM environment.

I tried using MSCS Cluster failover 2008 with Shared SAN disk.
Both nodes are VMs and the shared disks were using vmware RDM and SCSI bus Sharing.

It works find except we lose vmware HA on the 2 nodes.
We cant vmotion /storage vmotion on active VM with SCSI bus sharing.

Is there anyway we can do this failover clustering and still be able VM vmotion / storage vmotion?
Or perhaps there is a way or 3rd Party Software that we can use that would enable MSCS like failover Clustering, combined with "database mirroring"?

If we do "database mirroring" we lose the automatic cluster fail over we get when we use MSCS.

Any input to this would be much appreciated.

Thanks
BCSITSAsked:
Who is Participating?
 
Eugene ZConnect With a Mentor Commented:
there are some limitations:
for ESX 4 p.12-13http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_mscs.pdf

for ESX 5 p.9  http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-mscs-guide.pdf
vSphere MSCS Setup Limitations
Before you set up MSCS, review the list of functions that are not supported for this release, and requirements
and recommendations that apply to your configuration.
The following environments and functions are not supported for MSCS setups with this release of vSphere:
n Clustering on iSCSI, FCoE, and NFS disks.
n Mixed environments, such as configurations where one cluster node is running a different version of
ESXi than another cluster node.
n Use of MSCS in conjunction with vSphere Fault Tolerance (FT).
n Migration with vSphere vMotion® of clustered virtual machines.
n N-Port ID Virtualization (NPIV)
n With native multipathing (NMP), clustering is not supported when the path policy is set to round robin.
Third-party multipathing plug-ins might support round robin or other load balancing behavior with
Microsoft clusters. Support of third-party multipathing plug-ins is provided by the plug-in vendor.
n ESXi hosts that use memory overcommitment are not suitable for deploying MSCS virtual machines.
Memory overcommitment can cause virtual machines to stall for short durations. This can be significantly
disruptive as the MSCS clustering mechanism is time-sensitive and timing delays can cause the virtual
machines to behave incorrectly.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
You only use SCSI Bus Sharing if you are building a Cluster in a Box, if you have shared storage, why are you not using all your LUNs on the SAN?

Setup for Failover Clustering and Microsoft Cluster Service - ESXi 5.0/vCenter Server 5.0

Creating a Cluster in Windows Server 2008

http://blogs.msdn.com/b/clustering/archive/2008/01/18/7151154.aspx

Installing a SQL Server 2008 R2 Failover Cluster

http://msdn.microsoft.com/en-us/library/ms179410.aspx

Getting Started with SQL Server 2008 R2 Failover Clustering

http://msdn.microsoft.com/en-us/library/ms189134.aspx

Installing SQL Server 2008 on a Windows Server 2008 Cluster Part 1

http://www.mssqltips.com/tip.asp?tip=1687

SQL Server 2008 Failover Cluster Document from Microsoft

http://tinyurl.com/SQL2K8Cluster
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.