6.7
Table Of Contents
- Setup for Failover Clustering and Microsoft Cluster Service
- Contents
- About Setup for Failover Clustering and Microsoft Cluster Service
- Getting Started with MSCS
- Clustering Configuration Overview
- Hardware and Software Requirements for Clustering
- Supported Shared Storage Configurations
- PSP_RR Support for MSCS
- iSCSI Support for MSCS
- FCoE Support for MSCS
- vMotion support for MSCS
- VVol Support for MSCS
- vSphere MSCS Setup Limitations
- MSCS and Booting from a SAN
- Set up CCR and DAG Groups
- Setting up AlwaysOn Availability Groups with SQL Server 2012
- Cluster Virtual Machines on One Physical Host
- Cluster Virtual Machines Across Physical Hosts
- Create the First Node for MSCS Clusters Across Physical Hosts
- Create Additional Nodes for Clusters Across Physical Hosts
- Add Hard Disks to the First Node for Clusters Across Physical Hosts
- Add Hard Disks to the First Node for Clusters Across Physical Hosts with VVol
- Add Hard Disks to Additional Nodes for Clusters Across Physical Hosts
- Cluster Physical and Virtual Machines
- Use MSCS in an vSphere HA and vSphere DRS Environment
- vSphere MSCS Setup Checklist
Follow these guidelines when you place the boot disk of a virtual machine on a SAN-based VMFS
volume:
n
Consider the best practices for boot-from-SAN that Microsoft publishes in the following knowledge
base article: http://support.microsoft.com/kb/305547/en-us.
n
Use StorPort LSI Logic drivers instead of SCSIport drivers when running Microsoft Cluster Service for
Windows Server 2003 or 2008 guest operating systems.
n
Test clustered configurations in different failover scenarios before you put them into production
environments.
Setting up Clustered Continuous Replication or Database
Availability Groups with Exchange
You can set up Clustered Continuous Replication (CCR) with Exchange 2007 or Database Availability
Groups (DAG) with Exchange 2010 and higher in your vSphere environment. For supported versions of
Exchange, see VMware knowledge base article 1037959.
When working in a vSphere environment:
n
Use virtual machines instead of physical machines as the cluster components.
n
If the boot disks of the CCR or DAG virtual machines are on a SAN, see MSCS and Booting from a
SAN.
For more information, see Microsoft’s documentation for CCR or DAG on the Microsoft Web site.
Setting up AlwaysOn Availability Groups with SQL Server
2012
You can set up AlwaysOn Availability Groups (AAG) with SQL Server 2012 in your vSphere environment.
vSphere 6.0 supports the following deployments of AAG:
n
Using Availability Groups (AG) for high availability and disaster recovery solution (Non-shared disk
configuration).
n
Using Failover Cluster Instance (FCI) for high availability, and Availability Groups (AG) for disaster
recovery solution (Shared Disk Configuration).
When working in a vSphere environment:
n
Use virtual machines instead of physical machines as the cluster components.
n
If the boot disks of the AAG virtual machines are on a SAN, see MSCS and Booting from a SAN.
For more information, see Microsoft's documentation for AAG on the Microsoft Web site.
Setup for Failover Clustering and Microsoft Cluster Service
VMware, Inc. 15