6.5.1
Table Of Contents
- vSphere Availability
- Contents
- About vSphere Availability
- Business Continuity and Minimizing Downtime
- Creating and Using vSphere HA Clusters
- Providing Fault Tolerance for Virtual Machines
- vCenter High Availability
- Plan the vCenter HA Deployment
- Configure the Network
- Configure vCenter HA With the Basic Option
- Configure vCenter HA With the Advanced Option
- Manage the vCenter HA Configuration
- Set Up SNMP Traps
- Set Up Your Environment to Use Custom Certificates
- Manage vCenter HA SSH Keys
- Initiate a vCenter HA Failover
- Edit the vCenter HA Cluster Configuration
- Perform Backup and Restore Operations
- Remove a vCenter HA Configuration
- Reboot All vCenter HA Nodes
- Change the Appliance Environment
- Collecting Support Bundles for a vCenter HA Node
- Troubleshoot Your vCenter HA Environment
- Patching a vCenter High Availability Environment
- Using Microsoft Clustering Service for vCenter Server on Windows High Availability
- Index
The process for vCenter Server high availability in an MSCS environment is as follows.
1 Remove the MSCS conguration for vCenter Server.
2 Upgrade the vCenter Server from version 6.0 to version 6.5.
3 Congure MSCS to make vCenter Server highly available.
Prerequisites
n
Verify that you are not deleting the primary node VM.
n
Verify that the primary node is the current active node.
n
Verify that all the services of vCenter Server 6.0 are running on the primary node.
n
Verify that the Platform Services Controller node upgrade is nished and running vCenter Server 6.5.
n
Collect the inventory database backup.
Procedure
1 Power o the secondary node and wait for all the vCenter Server services to be started on the primary
node.
2 Remove the role name.
3 Destroy the MSCS cluster. Bring the RDM disks online again before changing the startup type.
4 Open the Service Management view and change the startup type for vCenter Server services from
manual to automatic.
5 Before upgrading to vCenter Server 6.5, change the IP and host name to the IP and host name used for
the role.
You must restart the host and ensure that vCenter Server is accessible.
6 Mount the vCenter Server 6.5 ISO and start the installation.
7 After the installation nishes, open the Service Management view and verify that the new services are
installed and running.
8 Set up the MSCS cluster conguration again and set the startup type of all vCenter Server services to
manual.
9 Shut down the primary node and detach the RDM disks, but do not delete them from the datastore.
10 After the reconguration is complete, select VM > Clone > Clone to Template, clone the secondary
node, and change its IP and host name.
11 Keep the secondary node powered o and add both RDM disks to the primary node. Then power on
the primary node and change its IP and host name.
12 Add both RDM disks to the secondary node. Then power on the secondary node.
13 Open Failover Cluster Manager and congure the MSCS cluster.
You must use the cluster role IP and host name.
What to do next
When conguring the MSCS cluster, you must add vCenter Server services such as the VMware AFD service
and the VMware vCenter Conguration service to the role as resources.
vSphere Availability
80 VMware, Inc.