This Knowledgebase article provides a best practice to upgrading vCenter Server when vCenter Server Heartbeat is installed.
Use the following procedure to upgrade vCenter Server when vCenter Server Heartbeat 6.5.x or later is installed.
Upgrading the Primary node
If the Secondary node is active, use vCenter Server Heartbeat Console on the Primary node to perform a manual failover to make the Primary node active. If the Primary node is currently active, go to Step 2.
Shutdown the Secondary node and delete the Secondary virtual machine.
Rename the Primary node from the Management Name to the Public Service Name and reboot when asked.\
Shutdown vCenter Server Heartbeat leaving protected applications running.
Using the Service Control Manager, configure VMware vCenter Server Heartbeat service Startup Type to Manual.
Upgrade all the protected applications installed on the server to include: Single Sign On, Inventory Service, Web Client, vCenter and the vCenter Support Tools. In the event that errors are encountered during the upgrade process, research the cause of the error. If the issue can be resolved then it is safe to proceed with the upgrade procedure.
Start vCenter Server Heartbeat and run a protected service discovery.
Clone the server (do not start the newly cloned node yet).
Using the Service Control Manager, configure VMware vCenter Server Heartbeat service Startup Type to Automatic.
Rename the server back to the Primary nodes previous Management Name, reboot when asked.
Upgrading the Secondary node
- Ensure the NICs of the cloned node are not connected.
- Start the newly cloned node.
- Reconfigure the NICs with the correct IP addresses corresponding to the Secondary node.
- Launch the vCenter Server Heartbeat Configure Server wizard and select the Machine tab. Change the physical server identity to Secondary.
- Select the Public tab, configure the correct IP addresses and click Finish.
- Change the server name to the Secondary node’s previous Management name and add it to a Workgroup. Reboot when asked.
- After the server reboots, connect the NICs.
- Using the Service Control Manager, configure VMware vCenter Server Heartbeat service Startup Type to Automatic.
- Join the server to the domain. Reboot when asked.
After the servers connect and synchronize, uninstall and re-install the vCenter plug-in.
- Using the vCenter Server Heartbeat Console, verify that all status icons on the Server: Summary page are green, indicating that the Start process has completed and all protected services are started.
- Navigate to the Applications: Plug-ins page, select the VirtualCenterNFPlugin and click Uninstall.
- After the plug-in has been removed from the plug-ins list, click Install.
- Navigate to the location of the vCenter Server plug-in (the default location is C:\Program Files\VMware\VMware vCenter Server Heartbeat\R2\plugins\VMwareVirtualCenter\18.104.22.16806) and select the VirtualCenterNFPlugin.dll file.
- After the plug-in has been added, select it, click Edit, then enter the credentials used to connect to vCenter Server.
vCenter Server Heartbeat 6.5.x and later