6.5.1

Table Of Contents
5 Power o the VM.
6 Detach the RDM disks.
Detaching the RDM disks is not a permanent deletion. Do not select Delete from disk and do not delete
the vmdk les.
7 Clone the VM and select the Customize the operating system option, so that the clone has a unique
identity.
Create a unique identity through either the default sysrep le or the custom sysrep le.
8 Aach the shared RDMs to both VMs and power them on.
9 Change the host name and IP address on the rst VM (VM1).
Note the original IP address and host name that were used at the time of the installation of
vCenter Server on VM1. This information is used to assign a cluster role IP.
10 Install failover clustering on both nodes.
11 To create an MSCS cluster on VM1, include both nodes in the cluster. Also select the validation option
for the new cluster.
12 To start conguring roles, select Generic Service and click Next.
13 Select VMware Service Lifecycle Manager from the listed services and click Next.
14 Enter the host name and IP used for the VM1. Then assign the RDM to the role.
15 In the Replicate Registry Seings wizard, add the registry key
SYSTEM\CurrentControlSet\Services\VMwareDirectoryService and click Next.
16 Using Add Resource, add the VMware AFD and VMware vCenter Conguration services to the role.
17 Stop and restart the role.
You have created an MSCS cluster that can support vCenter Server availability.
What to do next
After you have created the MSCS cluster, verify that failover is occurring by powering o the VM hosting
vCenter Server (VM1).In a few minutes, verify that the services are running on the other VM (VM2).
vSphere Availability
82 VMware, Inc.