Setup for Failover Clustering and Microsoft Cluster Service Update 1 VMware vSphere 6.5 VMware ESXi 6.5 vCenter Server 6.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
Setup for Failover Clustering and Microsoft Cluster Service You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2006–2017 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc.
Contents About Setup for Failover Clustering and Microsoft Cluster Service 5 1 Getting Started with MSCS 7 Clustering Configuration Overview 7 Hardware and Software Requirements for Clustering 10 Supported Shared Storage Configurations 11 PSP_RR Support for MSCS 11 iSCSI Support for MSCS 11 FCoE Support for MSCS 12 vMotion support for MSCS 12 vSphere MSCS Setup Limitations 13 MSCS and Booting from a SAN 13 Setting up Clustered Continuous Replication or Database Availability Groups with Exchange Setting
Setup for Failover Clustering and Microsoft Cluster Service 6 vSphere MSCS Setup Checklist 35 Index 4 39 VMware, Inc.
About Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service describes the types of clusters you can implement using virtual machines with Microsoft Cluster Service for Windows Server 2003 and Failover Clustering for Windows Server 2008, Windows Server 2012 and above releases. You get step-by-step instructions for each type of cluster and a checklist of clustering requirements and recommendations.
Setup for Failover Clustering and Microsoft Cluster Service 6 VMware, Inc.
Getting Started with MSCS ® 1 ® VMware vSphere supports clustering using MSCS across virtual machines. Clustering virtual machines can reduce the hardware costs of traditional high-availability clusters. Note vSphere High Availability (vSphere HA) supports a clustering solution in conjunction with vCenter Server clusters. vSphere Availability describes vSphere HA functionality.
Setup for Failover Clustering and Microsoft Cluster Service Clustering MSCS Virtual Machines on a Single Host A cluster of MSCS virtual machines on a single host (also known as a cluster in a box) consists of clustered virtual machines on the same ESXi host. The virtual machines are connected to the same storage, either local or remote. This configuration protects against failures at the operating system and application level, but it does not protect against hardware failures.
Chapter 1 Getting Started with MSCS Figure 1‑2. Virtual Machines Clustered Across Hosts private network virtual machine Node1 cluster software virtual machine Node2 cluster software public network physical machine physical machine storage (SAN) Note Windows Server 2008 SP2 and above systems support up to five nodes (virtual machines). Windows Server 2003 SP1 and SP2 systems support two nodes (virtual machines). For supported guest operating systems see Table 6-2.
Setup for Failover Clustering and Microsoft Cluster Service The following figure shows a standby host using three virtual machines on a single physical machine. Each virtual machine is running clustering software. Figure 1‑4.
Chapter 1 Getting Started with MSCS Supported Shared Storage Configurations Different MSCS cluster setups support different types of shared storage configurations. Some setups support more than one type. Select the recommended type of shared storage for best results. Table 1‑2.
Setup for Failover Clustering and Microsoft Cluster Service n Mixed mode of iSCSI config is supported. For example, Node A on ESXi with iSCSI software initiator and Node B on ESXi with Qlogic, Emulex or Broadcom hardware adapter. n Mixed mode configurations of ESXi 6.0 with previous ESXi releases are not supported. n Rolling upgrades of cluster Hosts from previous versions of ESXi to ESXi 6.0 builds are not supported. FCoE Support for MSCS ESXi 6.
Chapter 1 Getting Started with MSCS Failover cluster nodes use the network to send heartbeat packets to other nodes of the cluster. If a node does not receive a response from another node for a specified period of time, the cluster removes the node from cluster membership. By default, a guest cluster node is considered down if it does not respond within 5 seconds. Other nodes that are members of the cluster will take over any clustered roles that were running on the removed node.
Setup for Failover Clustering and Microsoft Cluster Service 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.
Cluster Virtual Machines on One Physical Host 2 You can create an MSCS cluster with up to five nodes on a single ESXi host. Note Windows Server 2008 SP2 and above systems support up to five nodes (virtual machines). For supported guest operating systems see Table 6-2. Windows Server 2003 SP1 and SP2 systems support two nodes. A cluster of virtual machines on one physical machine requires a host with one physical network adapter for the VMkernel.
Setup for Failover Clustering and Microsoft Cluster Service 4 Page Action Compatibility The host or cluster suports more than one VMware virtual machine version. Select a compatibility for the virtual machine. Guest operating system Select the guest operating system that you intend to install. Customize hardware Select virtual hardware, advanced virtual machine options, and SDRS rules. Ready to Complete Review your selections. Click Finish to complete creating the virtual machine.
Chapter 2 Cluster Virtual Machines on One Physical Host 4 5 6 Proceed through the deployment wizard to deploy the virtual machine. Page Action Name and folder Enter a name (for example, Node2) and select a location. Compute resource Select the host or cluster where you will run the virtual machine. Disk Format Select Same format as source. Datastore Select a datastore as the location for the virtual machine configuration file and the .vmdk file.
Setup for Failover Clustering and Microsoft Cluster Service Add Hard Disks to Additional Nodes for Clusters on One Physical Host To allow shared access to clustered services and data, point the quorum disk of the second node to the same location as the first node’s quorum disk. Point shared storage disks to the same location as the first node’s shared storage disks.
Cluster Virtual Machines Across Physical Hosts 3 You can create a MSCS cluster that consists of two or more virtual machines on two ESXi or more hosts. A cluster across physical hosts requires specific hardware and software. n ESXi hosts that have the following: n Two physical network adapters dedicated to the MSCS cluster and to the public and private networks. n One physical network adapter dedicated to the VMkernel. n Supported shared storage configuration.
Setup for Failover Clustering and Microsoft Cluster Service 3 4 Proceed through the wizard to create the virtual machine. Page Action Creation type Select Create a new virtual machine. Name and folder Enter a name and select a location. Compute resource Select a cluster, host, vApp or resource pool to run this virtual machine. Storage Select a datastore as the location for the virtual machine configuration file and the virtual machine disk (.vmdk) file.
Chapter 3 Cluster Virtual Machines Across Physical Hosts Page Action Storage Select a datastore as the location for the virtual machine configuration file and the .vmdk file. Ready to Complete Click Finish to create the virtual machine template. 3 Right-click the virtual machine template and select Deploy VM from this Template. 4 Proceed through the deployment wizard to deploy the virtual machine. 5 6 Page Action Name and folder Enter a name (for example, Node2) and select a location.
Setup for Failover Clustering and Microsoft Cluster Service 7 Click OK to complete creating the disk. The wizard creates a new hard disk. 8 In the New Virtual Machine - Edit Settings dialog box, expand SCSI controller and select the Change Type drop-down menu. 9 Select the appropriate type of controller, depending on your operating system.
Chapter 3 Cluster Virtual Machines Across Physical Hosts 7 In the New Virtual Machine - Edit Settings dialog box, expand SCSI controller and select the Change Type drop-down menu. 8 Select the appropriate type of controller, depending on your operating system. Operating System Type of Controller Windows Server 2003 SP1 and SP2 LSI Logic Parallel Windows Server 2008 SP2 and above LSI Logic SAS For supported guest operating systems see Table 6-2. 9 Click OK.
Setup for Failover Clustering and Microsoft Cluster Service 24 VMware, Inc.
Cluster Physical and Virtual Machines 4 You can create an MSCS cluster in which each physical machine has a corresponding virtual machine. This type of configuration is known as a standby host cluster. A standby host cluster has specific hardware and software requirements. Use ESXi hosts that have the following: Two physical network adapters dedicated to the MSCS cluster and to the public and private n networks. n n One physical network adapter dedicated to the VMkernel.
Setup for Failover Clustering and Microsoft Cluster Service Procedure u Set up the physical machine using the settings listed in the table. Component Requirement Windows Cluster Administrator application Advanced minimum configuration if Windows 2003 is used. Network adapters At least two. Storage Access to the same storage on a SAN as the ESXi host on which the corresponding virtual machine will run. Operating system Installed on each physical machine.
Chapter 4 Cluster Physical and Virtual Machines 7 In the New Virtual Machine - Edit Settings dialog box, expand Network adapter. Select the adapter type and network label. n If you selected a private network for the first network adapter, you must select a public network for this network adapter. n If you selected a public network for the first network adapter, you must select a private network adapter. 8 Click Finish to complete creating the device.
Setup for Failover Clustering and Microsoft Cluster Service In complex storage solutions, such as an FC switched fabric, a storage unit might have a different identity (target ID or raw disk ID) on each computer in the cluster. Although this is a valid storage configuration, it causes a problem when you add a node to the cluster. The following procedure allows you to avoid target identity problems when using clustering with Windows 2003.
Use MSCS in an vSphere HA and vSphere DRS Environment 5 When you use MSCS in a vSphere High Availability (vSphere HA) or vSphere Distributed Resource Scheduler (DRS) environment, you must configure your hosts and virtual machines to use certain settings. All hosts that run MSCS virtual machines must be managed by a vCenter Server system. vSphere includes vMotion support for MSCS cluster virtual machines.
Setup for Failover Clustering and Microsoft Cluster Service Create VM-VM Affinity Rules for MSCS Virtual Machines For MSCS virtual machines in a cluster, you must create VM-VM affinity or anti-affinity rules. VM-VM affinity rules specify which virtual machines should be kept together on the same host (for example, a cluster of MSCS virtual machines on one physical host).
Chapter 5 Use MSCS in an vSphere HA and vSphere DRS Environment 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.
Setup for Failover Clustering and Microsoft Cluster Service Create a Virtual Machine DRS Group (MSCS) Before you can create a VM-Host affinity rule, you must create the host DRS group and the virtual machine DRS group that the rule applies to. For both, a cluster of virtual machines on one physical host(CIB) and a cluster of virtual machines across physical hosts(CAB), create one virtual machine DRS group that contains all MSCS virtual machines.
Chapter 5 Use MSCS in an vSphere HA and vSphere DRS Environment Set up VM-Host Affinity Rules for DRS Groups (MSCS) Create VM-Host affinity rules to specify whether the members of a selected virtual machine DRS group can run on the members of a specific host DRS group. Prerequisites Create virtual machine DRS groups that contain one or more MSCS virtual machines as described in “Create a Virtual Machine DRS Group (MSCS),” on page 32.
Setup for Failover Clustering and Microsoft Cluster Service 34 VMware, Inc.
6 vSphere MSCS Setup Checklist When you set up MSCS on ESXi, see the checklists to configure your environment according to the requirements. You can also use the checklists to verify that your setup meets the requirements if you need technical support. Requirements for Clustered Disks Each type of clustered disk has its own requirements, depending on whether it is in a single-host cluster or multihost cluster. Table 6‑1.
Setup for Failover Clustering and Microsoft Cluster Service Other Requirements and Recommendations The following table lists the components in your environment that have requirements for options or settings. 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.
Chapter 6 vSphere MSCS Setup Checklist Table 6‑3. Information Required by Technical Support File or Information Description or Location vm-support tarball Contains the vmkernel log, virtual machine configuration files and logs, and so on. Application and system event logs of all virtual machines with the problem Cluster log of all virtual machines with the problem %ClusterLog%, which is usually set to %SystemRoot %\cluster\cluster.log. Disk I/O timeout HKEY_LOCAL_MACHINE\System\CurrentControlSet\Ser
Setup for Failover Clustering and Microsoft Cluster Service 38 VMware, Inc.
Index A affinity rules DRS groups and MSCS 33 enforcing and MSCS 30 MSCS 30, 31 AlwaysOn 14 anti-affinity rules, MSCS 30 automation level, MSCS 31 Fibre Channel (FC) SAN 17 Fibre Channel (FC) SAN and MSCS 19 format disks 15 disks MSCS 19 eagerzeroedthick 15, 19 H boot from SAN, MSCS 13 hardware requirements, MSCS 10 high availability and MSCS, See vSphere HA hosts, standby 25 C I B cluster across boxes, MSCS 8, 30 cluster in a box, MSCS 15, 30 clustering MSCS physical hosts and virtual machines 9 M
Setup for Failover Clustering and Microsoft Cluster Service iSCSI 13 LSI Logic Parallel 10 LSI Logic SAS 10 Microsoft Exchange and Database Availability Groups 14 Microsoft Exchange and CCR, See Clustered Continuous Replication (CCR) multipathing 13 multiple host clustering 8 N-Port ID Virtualization (NPIV) 13 native multipathing (NMP) 13 NFS 13 non-pass-through RDM 11 NTP server 10 pass-through RDM 11 physical compatibility mode 11 requirements 10 SAN 8, 14 shared storage configurations 11 single host clu
