Home > Blogs > VMware vSphere Blog


Upgrading vCenter when using vCenter Heartbeat, Part 1

A common question that comes up when a new vCenter Server version is released is “How do I upgrade if I’m using vCenter HeartBeat?”.

The first thing we need to check is whether the version of vCenter HeartBeat we’re running is compatible with the version of vCenter we want to upgrade to. You can check this by visiting the VMware Product Interoperability Matrixes.

VCHBComp

You can see from the screenshot above that only version 6.6 is compatible with both vCenter Server 5.1 and 5.5. So our first step is getting vCenter HeartBeat upgraded to 6.6. Page 51 of the Install and Upgrade guide lists the following step by step instructions:

  • Download the new version of vCenter Server Heartbeat WinZip Self-Extracting file to a desired location on both the Primary and Secondary nodes.
  • On the Primary/active node, right-click on the System Tray icon and select to Shutdown vCenter Server Heartbeat opting to leaving protected applications running.
  • Navigate to Start > Administrative Tools > Services and set the VMware vCenter Server Heartbeat service to Manual.
  • On the Secondary/passive node, navigate to Start > Administrative Tools > Services and set the VMware vCenter Server Heartbeat service to Manual.
  • On the Secondary/passive node, right-click on the System Tray icon and select to Shutdown vCenter Server Heartbeat.
  • On the Secondary/passive node, disconnect the network cable from the Public NIC.
  • On the Primary/active node, double-click the WinZip Self-Extracting file. The Setup Introduction page is displayed. Click OK.
    The WinZip Self-Extractor page is displayed.
  • Click Setup to open the VMware vCenter Server Heartbeat Setup window.
  • Select the option to Install Update when the Setup Type page is displayed.
  • Follow the on-screen instructions to install the ServicePack.nfs script. Click Add and use the default path to the Service Pack. When prompted, reboot the node.
    Note During the Service Pack installation, the new vCenter Server Heartbeat plug-ins are copied to <Heartbeat install dir>\R2\<version> plug-ins\<plug-in name>
  • On the Secondary/passive node, double-click the WinZip Self-Extracting file. The Setup Introduction page is displayed. Click OK.
    The WinZip Self-Extractor page is displayed.
  • Click Setup to open the VMware vCenter Server Heartbeat Setup window.
  • Select the option to Install Update when the Setup Type page is displayed.
  • Follow the on-screen instructions to install the ServicePack.nfs script. Click Add and use the default path to the Service Pack. When prompted, reboot the node.
    Note During the Service Pack installation, the new vCenter Server Heartbeat plug-ins are copied to <Heartbeat install dir>\R2\<version> plug-ins\<plug-in name>
  • On both the Primary/active node and the Secondary/passive node, check the configuration of the NICs and make corrections if necessary (the packet filter should be selected on Public NICs and cleared on channel NICs).
  • On the Primary/active node, right-click on the System Tray icon and select to Start VMware vCenter Server Heartbeat.
  • Navigate to Start > Administrative Tools > Services and set the VMware vCenter Server Heartbeat service to Automatic.
  • On Secondary/passive node, right-click on the System Tray icon and select to Start VMware vCenter Server Heartbeat and then reconnect the network cable to the Public NIC.
  • On the Secondary/passive node, navigate to Start > Administrative Tools > Services and set the VMware vCenter Server Heartbeat service to Automatic

Note During the upgrade vCenter will experience downtime so plan accordingly.

In my next post we’ll go through upgrading vCenter and all related components to 5.5.

 

This entry was posted in Uptime, vCenter Server, vSphere and tagged , , on by .
Mike Brown

About Mike Brown

Mike Brown is a senior technical marketing manager in the Cloud Infrastructure Technical Marketing group. Mike has worked in the IT industry for more than 17 years. His focus is on reference architectures for VMware vCloud Suite and the software-defined data center (SDDC) as well as VMware vCenter Server, vCenter Single Sign-On, VMware vSphere Web Client, and resource management technologies such as vSphere Distributed Resource Scheduler, VMware vSphere Network I/O Control, VMware vSphere Storage DRS, and VMware vSphere Storage I/O Control. Mike has multiple industry certifications, including VMware Certified Design Expert (VCDX). Follow Mike on Twitter @vMikeBrown.

6 thoughts on “Upgrading vCenter when using vCenter Heartbeat, Part 1

  1. Frank

    Hi,
    thanks. I am waiting for your next post. I am reading in the release notes that it is curently not supported to do an upgrade. Just a fresh install.
    Thanks for updating.
    Frank

    Reply
    1. Mike BrownMike Brown Post author

      Hi Frank,

      Yes at the time of writing the documentation there was no way to upgrade to 5.5 with all components on a single server protected by HeartBeat, that has been addressed now in KB 2059820.

      Mike

      Reply
  2. Pingback: Upgrading vCenter when using vCenter Heartbeat, Part 2 | VMware vSphere Blog - VMware Blogs

  3. Edward Morrison

    I’m not sure if I’m reading the document “vcenter-server-heartbeat-66-installation-upgrade-windows-2008-2012-virtual-guide.pdf” section “Upgrading vCenter Server 5.0 or 5.1 to vCenter Server 5.5 when SQL Database is Remote and vCenter Server Heartbeat is Installed” correctly, can you please confirm?

    The procedure starts with upgrading the secondary node web client server (step 5, p 53). When we get to the primary node, it does not list this as the first step in the upgrade of the primary, it lists it as an optional step at the end. Is this correct? If you don’t upgrade on the primary and then restart vCHB at the end of the upgrade with primary as active, doesn’t that essentially downgrade the secondary node web client?

    Reply
    1. Mike BrownMike Brown Post author

      Hi Edward,

      Yes, you will need to install/upgrade the same components on the primary as you do on the secondary.

      Mike

      Reply
  4. Pingback: VMware vSphere Blog: Upgrading vCenter when using vCenter Heartbeat, Part 2 | System Knowledge Base

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>