Hello All,
Is clustering in a box (CIB) possible and supported on vsan?
Thanks in advance.
For SQL Server the best thing you can do is to use AlwaysOn Availability Groups. This config requires Windows Cluster but does not require shared storage. See:
Let's assume you have 3 physical hypervisor hosts. So make:
HostA: Primary SQL Server VM
HostB: Secondary SQL Server VM
HostC: Windows VM with SMB3 share to handle MSFT cluster witness
Simple
Good luck!
Anton
--
I want to find out what my possibilities are for Microsoft SQL Server 2012.
I know I have VMWare HA, but MS clustering gives some advantages regarding maintenance, and is also useful in case of OS error (BSOD).
I am also looking at the "Always On", but that is an SQL Server Enterprise Edition feature, and it has to be supported by the applications as well.
Officially (from VMware) vSAN is not supported on MSCS. However, as per my understanding, it may work for CIB. You can give a try in test environment.
Message was edited by: Vikas
Directly - no. But you may run "proxy" VM feeding some shared storage to MSCS. What exactly do you want to cluster?
--
Is clustering in a box (CIB) possible and supported on vsan?
I want to find out what my possibilities are for Microsoft SQL Server 2012.
I know I have VMWare HA, but MS clustering gives some advantages regarding maintenance, and is also useful in case of OS error (BSOD).
I am also looking at the "Always On", but that is an SQL Server Enterprise Edition feature, and it has to be supported by the applications as well.
For SQL Server the best thing you can do is to use AlwaysOn Availability Groups. This config requires Windows Cluster but does not require shared storage. See:
Let's assume you have 3 physical hypervisor hosts. So make:
HostA: Primary SQL Server VM
HostB: Secondary SQL Server VM
HostC: Windows VM with SMB3 share to handle MSFT cluster witness
Simple
Good luck!
Anton
--
I want to find out what my possibilities are for Microsoft SQL Server 2012.
I know I have VMWare HA, but MS clustering gives some advantages regarding maintenance, and is also useful in case of OS error (BSOD).
I am also looking at the "Always On", but that is an SQL Server Enterprise Edition feature, and it has to be supported by the applications as well.