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
Other Requirements and Recommendations
The following table lists the components in your environment that have requirements for options or seings.
Table 6‑2. Other Clustering Requirements and Recommendations
Component Requirement
Disk If you place the boot disk on a virtual disk, select Thick Provision during disk provisioning.
The only disks that you should not create with the Thick Provision option are RDM les (both
physical and virtual compatibility mode).
Windows Use:
n
Windows Server 2003 SP1 (32 bit/64 bit)
n
Windows Server 2003 SP2 (32 bit/64 bit)
n
Windows Server 2003 R2 (32 bit/64 bit)
n
Windows Server 2003 R2 SP1 (32 bit/64 bit)
n
Windows Server 2003 R2 SP2 (32 bit/64 bit)
n
Windows Server 2008 SP1 (32 bit/64 bit)
n
Windows Server 2008 SP2 (32 bit/64 bit)
n
Windows Server 2008 R2 (64 bit)
n
Windows Server 2008 R2 SP1 (32 bit/64 bit)
n
Windows Server 2012
n
Windows Server 2012 R2
For Windows Server 2003 SP1 and SP2, use only two cluster nodes.
For Windows Server 2008 SP2 and above, you can use up to ve cluster nodes.
Disk I/O timeout is 60 seconds or more
(HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk\TimeOutValue).
N If you recreate the cluster, this value might be reset to its default, so you must change it
again.
The cluster service must restart automatically on failure (rst, second, and subsequent times).
ESXi conguration Do not overcommit memory. Set the Memory Reservation (minimum memory) option to the same
as the amount of memory assigned to the virtual machine.
If you must overcommit memory, the swap le must be local, not on the SAN.
ESXi 5.0 uses a dierent technique to determine if Raw Device Mapped (RDM) LUNs are used for
MSCS cluster devices, by introducing a conguration ag to mark each device as "perennially
reserved" that is participating in an MSCS cluster. For ESXi hosts hosting passive MSCS nodes with
RDM LUNs, use the esxcli command to mark the device as perennially reserved:
esxcli storage core device setconfig -d <naa.id> --perennially-reserved=true. See
KB 1016106 for more information.
Multipathing Contact your multipathing software vendor for information and support of non-VMware
multipathing software in vSphere.
Required Information for Technical Support
The following table lists the les and seings to collect if you require technical support. Technical support
uses these les and seings to analyze clustering issues.
N Verify that your setup complies with the checklists in Table 6-1 and Table 6-2 before you contact
technical support.
Setup for Failover Clustering and Microsoft Cluster Service
36 VMware, Inc.