6.5.1
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
- 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
- Cluster Physical and Virtual Machines
- Use MSCS in an vSphere HA and vSphere DRS Environment
- vSphere MSCS Setup Checklist
- Index
Set DRS Automation Level for MSCS Virtual Machines
You must set the automation level of all virtual machines in an MSCS cluster to Partially Automated. When
you set the vSphere DRS automation level for the virtual machine to Partially Automated, vCenter Server
will perform initial placement of virtual machines when they are powered on and will provide migration
recommendations for them.
Procedure
1 Browse to the cluster in the vSphere Web Client object navigator.
2 Click .
3 Under Services, select vSphere DRS and click Edit.
4 Expand DRS Automation, under Virtual Machine Automation select the Enable individual virtual
machine automation levels check box and click OK.
5 Under , select VM Overrides and click Add.
6 Click the + buon, select the MSCS virtual machines in the cluster and click OK.
7 Click the Automation level drop-down menu, and select Partially Automated.
8 Click OK.
N VMware recommends partially automated mode for MSCS virtual machines, but there is no
technical restriction which prevents the seing for MSCS virtual machines to be fully automated. If the
fully automated seing is used please tune the migration threshold to suit the workload running on the
MSCS virtual machines.
Using vSphere DRS Groups and VM-Host Affinity Rules with MSCS
Virtual Machines
You can use the vSphere Web Client to set up two types of DRS groups: virtual machine DRS groups, which
contain at least one virtual machine, and host DRS groups, which contain at least one host. A VM-Host rule
establishes an relationship between a virtual machine DRS group and a host DRS group.
You must use VM-Host anity rules because vSphere HA does not obey VM-VM anity rules. This means
that if a host fails, vSphere HA might separate clustered virtual machines that are meant to stay together, or
vSphere HA might put clustered virtual machines that are meant to stay apart on the same host. You can
avoid this problem by seing up DRS groups and using VM-Host anity rules, which are obeyed by
vSphere HA.
For a cluster of virtual machines on one physical host, all MSCS virtual machines must be in the same
virtual machine DRS group, linked to the same host DRS group with the anity rule "Must run on hosts in
group."
For a cluster of virtual machines across physical hosts, all MSCS virtual machines must be in the same
virtual machine DRS group and all hosts must be in the same host DRS group. The virtual machine and host
DRS groups must be linked the anity rule "Must run on hosts in group."
C Limit the number of hosts to two when you dene host DRS group rules for a cluster of virtual
machines on one physical host. (This does not apply to clusters of virtual machines across physical hosts.)
Since vSphere HA does not obey VM-VM anity rules, virtual machines in the conguration could be
spread across hosts during a vSphere HA recovery from host failure if more than two hosts are included in a
host DRS group rule.
Chapter 5 Use MSCS in an vSphere HA and vSphere DRS Environment
VMware, Inc. 31