6.7
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
- How Fault Tolerance Works
- Fault Tolerance Use Cases
- Fault Tolerance Requirements, Limits, and Licensing
- Fault Tolerance Interoperability
- Preparing Your Cluster and Hosts for Fault Tolerance
- Using Fault Tolerance
- Best Practices for Fault Tolerance
- Legacy Fault Tolerance
- Troubleshooting Fault Tolerant Virtual Machines
- Hardware Virtualization Not Enabled
- Compatible Hosts Not Available for Secondary VM
- Secondary VM on Overcommitted Host Degrades Performance of Primary VM
- Increased Network Latency Observed in FT Virtual Machines
- Some Hosts Are Overloaded with FT Virtual Machines
- Losing Access to FT Metadata Datastore
- Turning On vSphere FT for Powered-On VM Fails
- FT Virtual Machines not Placed or Evacuated by vSphere DRS
- Fault Tolerant Virtual Machine Failovers
- 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
Upgrade vCenter Server in an MSCS Environment
If you are running vCenter Server 6.0, you must upgrade to vCenter Server 6.5 to set up an MSCS high
availability environment.
vCenter Server 6.0.x has 18 services, assuming that the PSC server is running on a different host.
vCenter Server 6.5 has 3 services and the names have changed. An MSCS cluster configuration created
to set up high availability for vCenter Server 6.0 becomes invalid after an upgrade to vCenter Server 6.5.
The process for vCenter Server high availability in an MSCS environment is as follows.
1 Remove the MSCS configuration for vCenter Server.
2 Upgrade the vCenter Server from version 6.0 to version 6.5.
3 Configure 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 finished and running vCenter Server 6.5.
n
Collect the inventory database backup.
Note When you reconfigure an MSCS cluster for CISWIN VC 6.5, before you remove the cluster
configuration, make sure that all VC services have "cluster disk on which VC is installed" and "cluster role
IP (VC virtual IP)" as dependencies for the VMware vCenter Configuration Service.
Procedure
1 Power off 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 finishes, open the Service Management view and verify that the new services are
installed and running.
vSphere Availability
VMware, Inc. 96