VMware

VMware vCenter Server Heartbeat 5.5 Update 2 Release Notes

VMware vCenter Server Heartbeat 5.5 Update 2 | 19 NOVEMBER 2009 | Build 3117
Last Document Update: 14 DECEMBER 2011
Check frequently for additions and updates to these release notes.

This release of VMware vCenter Server Heartbeat provides protection for the following products:

vCenter Server 2.5
vCenter Server 2.5 Update 1
vCenter Server 2.5 Update 2
vCenter Server 2.5 Update 3
vCenter Server 2.5 Update 4
vCenter Server 2.5 Update 5
vCenter Server 2.5 Update 6
vCenter Server 4.0
vCenter Server 4.0 Update 1
vCenter Server 4.0 Update 2

These release notes include the following topics:

What's New

The following information provides highlights of some of the enhancements available in this release of vCenter Server Heartbeat 5.5 Update 2.
Note: The features available depend on the version of vCenter Server installed.

Features

  • Support for Windows Server 2008 SP1 and SP2 (x86/x64) — VMware vCenter Server Heartbeat now supports running on Windows Server 2008 SP1 and SP2 (including x86 and x64 versions) operating systems.
  • Support for Windows Server 2003 Enterprise SP2 (x64) — VMware vCenter Server Heartbeat now supports running on the Windows Server 2003 Enterprise SP2 (x64) operating system.
  • Protection of VMware vCenter Management Web Services — This release of VMware vCenter Server Heartbeat adds the vCenter Management Web Server to its list of protected vCenter Server components.
  • Introduction of the WinZip Self-Extracting executable file for Setup — Installation and setup of VMware vCenter Server Heartbeat is initiated through the use of a WinZip Self-Extracting executable file.
  • 60-day evaluation mode — This release of VMware vCenter Server Heartbeat provides a built-in 60-day evaluation mode that is triggered from the date of installation. Either prior to or upon expiration of the 60-day evaluation period, administrators will need to provide a valid license key to continue to leverage VMware vCenter Server Heartbeat functionality.
  • Note: The term vSphere Client is applicable to both vSphere Client and VI Client except where VI Client is specifically stated.

Top of Page

Learning about vCenter Server Heartbeat

VMware provides you with manuals that show you how to work with vCenter Server Heartbeat. Additionally, you can view a video that introduces you to the product and demonstrates a sample installation. To download and play the video:

  1. Click Video Download and save the .zip file to a folder on your computer.
  2. Extract the files into a directory on your system and navigate to the vCSHB_QuickStart_VideoInstall subdirectory.
  3. Double-click the vCSHB_QuickStart_VideoInstall.html file to start the video.

Top of Page

Prior Releases of vCenter Server Heartbeat

Features and known issues from prior releases of vCenter Server Heartbeat are described in the release notes for each release. To view release notes for a prior release of vCenter Server Heartbeat, click the appropriate link:

vCenter Server Heartbeat releases

Top of Page

Before You Begin

Before installing this release, review the vCenter Server Heartbeat Quick Start Guide for important information about environmental requirements and the selection of options during the installation process.

vCenter Server Heartbeat and vCenter Server Compatibility

The vCenter Server Heartbeat Reference Guide provides details on the compatibility of current and previous versions of vCenter Server.

This release of vCenter Server Heartbeat operates on the following platforms:

  • Windows Server 2003 x86 Standard SP2.
  • Windows Server 2003 x86 Enterprise SP1 and SP2.
  • Windows Server 2003 Standard x64 SP2.
  • Windows Server 2003 Enterprise x64 SP2.
  • Windows Server 2008 x86 SP1 and SP2.
  • Windows Server 2008 x64 SP1 and SP2.

This release of vCenter Server Heartbeat supports the following versions of SQL Server

  • SQL Server 2005 SP1-SP3
  • SQL Server 2008

This release of vCenter Server Heartbeat only supports vCenter Converter Enterprise. This version of vCenter Server Heartbeat does not support vCenter Converter 3.0.3 (Starter edition) or vCenter Converter Standalone 4.0.

Installation Notes for This Release

See the vCenter Server Heartbeat Guides before installing this software. You must verify that your server environment meets the minimum requirements for the network option (LAN or WAN) selected. These guides also address minimum hardware/software requirements and scaling recommendations associated with this release. To view a guide, click one of the following links:

  • vCenter Server Heartbeat Quick Start Guide (PDF)
  • vCenter Server Heartbeat Reference Guide (PDF)

Read the vCenter Server Heartbeat Reference Guide for step-by-step guidance on installing and configuring vCenter Server Heartbeat.

Upgrading to vCenter Server Heartbeat 5.5 Update 2

This release of vCenter Server Heartbeat 5.5 Update 2 supports upgrades only from previously supported versions. The vCenter Server Heartbeat 5.5 Update 2 Installer prompts you to perform an upgrade only when a previously supported version of vCenter Server Heartbeat is found. See the Reference Guide for installation requirements and VMware Knowledge Base article 1014435 (vCSHB-Ref-1815) for the upgrade procedures.

Note: If upgrading from an Evaluation Version of vCenter Server Heartbeat to a Production Version, refer to VMware Knowledge Base article 1010792 (vCSHB-Ref-1767) for the upgrade procedure.

Upgrading vCenter Server 2.5 and its updates to vCenter Server 4.0 when protected by vCenter Server Heartbeat.

This release of vCenter Server Heartbeat supports upgrading to the latest version of vCenter Server. Perform the Upgrade to vCenter Server Heartbeat 5.5 Update 2 before upgrading vCenter Server. See VMware Knowledge Base article 1010479 (vCSHB-Ref-1764) if protecting vCenter Server only or VMware Knowledge Base article 1010483 (vCSHB-Ref-1765) if protecting vCenter Server with a local SQL database for instructions on how to upgrade vCenter Server 2.5 and its updates to a later version.

Top of Page

Known Issues

This section contains known issues for this release in the following subject areas:

vCenter Server Heartbeat Setup

  • Setup - The recommended minimum display resolution for Setup and vCenter Server Heartbeat Console is 1024 X 768
    Prior to starting Setup or launching the vCenter Server Heartbeat Console, set the display to a minimum of 1024 X 768.
  • vCenter Server Heartbeat does not support the ` (grave accent) character
    vCenter Server Heartbeat does not support usernames and passwords that use the ` (grave accent) character. Change the vCenter Server password before configuring vCenter Server Heartbeat rules.
  • Install Clone — Prior to starting Setup on the Secondary server, the WebClient service must be set to Manual or Automatic
    If VMware License Server is installed, before starting vCenter Server Heartbeat Setup you must set the WebClient service to Manual or Automatic. Failing to do so will result in an error preventing Setup from progressing.
  • Install Clone — During installation, the backup fails with the error "no drives included in the backup" if command-line tools are missing
    During installation, when the backup is taken, it fails with the error "No drives included in the backup" unless both the Windows Backup Features and Command-line Tools are installed.
    Workaround: Install both the Windows Backup Features and Command-line Tools and then attempt the backup again.
  • Install Clone — During installation on Windows Server 2008 SP2, the restore process may fail with the error "System writer is not found in the backup"
    During installation, when the restore process runs, it may fail with the error "System writer is not found in the backup". This is caused by a problem with permissions on the %windir%\winsxs\filemaps folder contents.
    Workaround: See Microsoft Knowledge Base article http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/b5236028-4bfe-400c-90e2-b6d40b08e776 to reset the permissions.
  • Install Clone — Installing vCenter Server Heartbeat in a P2V using the install clone technique with differing disk subsystems may cause the Operating System to fail.
    During installation, with the Primary and Secondary servers having different disk subsystems, the operating system may fail when the restore process runs. This is caused when the restore process overwrites the registry settings for the disk subsystem type on the Secondary server with the values of the Primary server.
    Workaround: Prior to performing the restore process, see VMware Knowledge Base article 1014436 (vCSHB-Ref-1819) to prevent this issue.
  • Upgrade of vCenter Server 2-5 to 4.0 — After switchover, managed ESX hosts enter a 'Not responding' state on vCenter Server 4.0 upgraded from vCenter Server 2.5 when vCenter Server Heartbeat is installed
    During the upgrade procedure from vCenter Server 2.5 and its updates to vCenter Server 4.0, the vSphere Client Managed IP Address field was not cleared.
    Workaround: Launch the vSphere Client and navigate to Administration > vCenter Server Settings > Runtime settings and clear the vCenter Server Managed IP field in the Managed IP Address pane and click OK. See VMware Knowledge Base article 1010483 (vCSHB-Ref-1765).

vCenter Server Heartbeat Administration

  • Manually checking the value of a rule using the Application > Rules tab of vCenter Server Heartbeat Console does not provide immediate feedback
    Manually selecting a rule and clicking on the Check Now button fails to update the value in a timely manner.
  • After a switchover, vCenter Service status displays an Alert with a red status
    After a switchover, vCenter Service reports red for com.vmware.vcIntegrity and displays the alert message "Health data retrieved is invalid".
    Workaround: Manually update the <vpxdlocation></vpxdlocation> field of the vci-integrity.xml file with the correct Public IP address, the Fully Qualified Domain Name (FQDN) must be used when deployed in a WAN.
  • When attempting to upgrade the vCenter and SQL Plug-ins, the plug-ins are not accessible
    When attempting to upgrade the vCenter and SQL Plug-ins, the user cannot access the updated plug-ins because they are contained in the WinZip Self-Extracting executable file.
    Workaround: Use WinZip to access the plug-in files within the WinZip Self-Extracting executable file.
  • The server monitoring task will continue to run after a protected service is edited
    After editing the parameters of a protected service, the server monitoring task will continue to run to ensure the service configuration is updated.
  • License key reported as expired when it is valid
    vCenter Server Heartbeat reports "License expired" and the Configure Server wizard reports "License Key valid" when current date is exactly 60 days later than installation date.
  • Client Tools — Cannot add Server Pairs on Windows Vista
    After installing the Client Tools on Windows Vista and adding a new server pair, the new server pair is not saved and the following error message is displayed: "Failed to save server configuration".
    Workaround: Before installing the Client Tools, disable UAC. After installing the Client Tools, UAC can be re-enabled.
  • The Look and Feel of some elements in the Data > File Synch and Verify panel do not get updated
    The Look and Feel of some elements in the vCenter Server Heartbeat Console require restarting the Heartbeat Console to update changes made to the Look and Feel.
    Workaround: Close the vCenter Server Heartbeat Console and restart it to update changes made to the Look and Feel of the Heartbeat Console.
  • Heartbeat Server performance monitors missing when vCenter Server Heartbeat is installed on Windows Server 2008
    When vCenter Server Heartbeat is installed on Windows Server 2008, the Heartbeat Server performance monitor is not displayed when using perfmon or perfmon /wmi.
  • When deployed in a WAN configuration, after a switchover or failover, the Update Manager Server starts with a wrong IP address
    This issue appears in WAN deployments, when the network identification of VMware Update Manager Server is configured using the vCenter Server Heartbeat Primary server's Principal (Public) IP address, rather than Fully Qualified Domain Name (FQDN). After a switchover or failover, the Principal (Public) IP address is changed to the Secondary server's while Update Manager Server remains configured with the Primary server's Principal (Public) IP address.
    Workaround: Change the network address and then re-register Update Manager Server according to VMware Knowledge Base article 1013222.
  • DB Files Allocated Space check fails because of a missing performance object
    The VMware SQL Server Plug-in cannot evaluate performance counters on 32-bit versions of SQL Server installed on 64-bit Windows Operating Systems.
    Workaround: To prevent alerts from being raised, disable the relevant performance counter.

vCenter Server Heartbeat Plug-ins

  • State of VI Client plug-in not replicated from active server to passive server
    The enabled / disabled state of plug-ins in the vSphere Client are not replicated from the active server to the passive server.
  • Incorrect network configuration might cause vSphere Client Plug-in installation errors
    Installing vCenter Plug-ins through the vSphere Client requires the vSphere Client to connect and download the plug-ins through the Principal (Public) IP address. The Principal (Public) network adapter must be first in the bind order. If vSphere Client is configured with any other IP address, then the installation will fail.

vCenter Server Heartbeat Uninstall/Modify

  • Uninstalling a vCenter Server Heartbeat Service Pack on a Client Tools installation deletes the <install_path>\R2\Logs folder
    During the uninstall process, vCenter Server Heartbeat Client Tools will delete the <install_path>\R2\Logs folder resulting in the deletion of the nfclientlog.txt file.
    Workaround: Manually create the <install_path>\R2\Logs folder and the nfclientlog.txt file.

Top of Page

Resolved Issues

This release includes fixes in the following subject areas:

vCenter Server Heartbeat Networking

  • Managed ESX host not responding
    A Managed ESX host enters a Not Responding state after a switchover when the vpxd.cfg file is configured with a management IP address.

vCenter Server Heartbeat Setup

  • vCenter Server Heartbeat Setup fails when run from a mapped drive
    Running vCenter Server Heartbeat Setup.exe remotely from a mapped network drive causes Setup to terminate.
    Workaround: Download the distribution .zip file to a physical drive on the server, extract the contents to a local folder, and run Setup.exe from the folder.
  • Setup fails to properly extract files if WinRAR is used to extract the kit
    Extraction utilities that do not extract empty folders will cause Setup to fail.
    Workaround: Use WinZip, Windows Explorer, or utilities that can be configured to extract empty folders when extracting the kit files.
  • vCenter Update Manager and vCenter Converter must be configured with the server's Fully Qualified Domain Name (FQDN) before installing vCenter Server Heartbeat
    Prior to installing vCenter Server Heartbeat, verify that vCenter Update Manager and vCenter Converter are configured using Fully Qualified Domain Names rather than IP addresses.
  • An incorrect icon is displayed in Add/Remove Programs on the Secondary server
    The Secondary server's Add/Remove Programs displays a default Java icon for vCenter Server Heartbeat.
  • Client Tools — Upgrade Cannot upgrade from vCenter Server Heartbeat 5.5 to vCenter Server Heartbeat 5.5 Update 2
    When attempting to upgrade the Client Tools for vCenter Server Heartbeat 5.5 to vCenter Server Heartbeat 5.5 Update 2, an error is logged and the installation cannot continue.

vCenter Server Heartbeat Administration

  • vSphere Client must not be left running on the passive server during a switchover operation
    Leaving the vSphere Client running during a switchover operation will cause vCenter Server Heartbeat to go into a Sweep Synchronize state and initiate a Full System Check.
  • After changing the look and feel of the vCenter Server Heartbeat Console, some settings are not retained.
    After configuring the look and feel preferences, some subordinate dialogs do not display with the new look and feel.

vCenter Server Heartbeat Plug-ins

  • A user's Custom Performance Charts are not replicated by vCenter Server Heartbeat
    Custom Performance Chart settings are not replicated from the active server to the passive server. Workaround: Create an Inclusion File Filter for:
    C:\Documents and Settings\<username>\Application Data\VMware\**.

vCenter Server Heartbeat Tasks

  • Protected Service Discovery
    Under normal operating conditions, vCenter Server Heartbeat runs the Protected Service Discovery task at the interval configured in the vCenter Server Heartbeat Console. When vCenter Server is run in the evaluation mode, vCenter Server Heartbeat will detect this condition through the plug-in Rules and display the Application Health status as Degraded. When the Application Health status is Degraded, Protected Service Discovery tasks will not run.
    Workaround: To allow the Protected Service Discovery task to run while running vCenter Server is in the evaluation mode, disable the Check vCenter License rule through the vCenter Server Heartbeat Console. Refer to VMware Knowledge Base article 1010463 (vCSHB-Ref-1754) for procedures to disable the vCenter License Check rule using the vCenter Server Heartbeat Console.

vCenter Server Heartbeat Rules

  • DB Files Allocated Space check cannot analyze the SQLEXP_VIM instance
    The VMware SQL Server Plug-in may fail to read performance counter information for the instance on the Secondary server after switchover. VMware SQL Server Plug-in counters are not available on the Secondary server when passive because the SQL Server services are stopped. .NET may cache this information and when the rule runs on the Secondary server when active, it provides this cached information on the availability of the counters instead of looking for the counters.

vCenter Server Heartbeat File Filters

  • vCenter Server Heartbeat fails to create a file filter for SQL Server Reporting services when SQL Server 2005 SP3 is installed
    During the installation of vCenter Server Heartbeat a file filter is not created for SQL Server 2005 SP3 Reporting services.
    Workaround: Manually configure an Inclusion File Filter for SQL Server 2005 SP3 Reporting services located at:
    <install_directory>\MSSQL.3\REPORTING SERVICES\REPORT*\*.CONFIG

Top of Page