VMware

VMware vCenter Server Heartbeat 6.5 Release Notes

VMware vCenter Server Heartbeat 6.5 | Build 9193

Last Document Update: 05 APRIL 2013

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 4.0 Update 1
vCenter Server 4.0 Update 2
vCenter Server 4.0 Update 3
vCenter Server 4.0 Update 4
vCenter Server 4.1
vCenter Server 4.1 Update 1
vCenter Server 4.1 Update 2
vCenter Server 4.1 Update 3
vCenter Server 5.0
vCenter Server 5.0 Update 1
vCenter Server 5.0 Update 1a
vCenter Server 5.1

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 6.5

Note: The features available depend on the version of vCenter Server installed.

Features

  • Support for vCenter Server 5.1 — This release of VMware vCenter Server Heartbeat now provides support for vCenter Server 5.1
  • Enhanced Setup — This release of VMware vCenter Server Heartbeat provides for more automation during setup resulting in fewer user steps and easier configuration.
  • Administer VMware vCenter Server Heartbeat via vSphere Web Client — You can now install a vSphere Web Client Plug-in to administer VMware vCenter Server Heartbeat directly from the vSphere Web Client Heartbeat tab.
  • Network Isolation — VMware vCenter Server Heartbeat now provides a safeguard to prevent Split-brain in the event of loss of both channel and public visibility of the active server.
  • vCenter Role Based Permissions — The vCenter Server Heartbeat vSphere Web Client supports View Only and Administrator roles.
  • Editing Protected Services — vCenter Server Heartbeat Console now allows you to perform a single operation to configure the actions to take upon failure for all protected services.
  • Support for Microsoft SQL Server 2012 — This release of VMware vCenter Server Heartbeat provides support for Microsoft SQL Server 2012.
  • Support for View Composer — This release of VMware vCenter Server Heartbeat provides support for View Composer 3.0 and 5.2

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

Before You Begin

Before installing this release, review the vCenter Server Heartbeat Installation Guide for your environment 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 Installation Guides provide 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/Enterprise/Data Center including SP1 and later
  • Windows Server 2003 x64 Standard/Enterprise/Data Center SP2 and later
  • Windows Server 2003 R2 x64 Standard/Enterprise/Data Center SP2 and later
  • Windows Server 2008 x86 Standard/Enterprise/Data Center including SP1 and later
  • Windows Server 2008 x64 Standard/Enterprise/Data Center including SP1 and later
  • Windows Server 2008 R2 Standard/Enterprise/Data Center including SP1

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 Installation Guide for your environment 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:

Read vCenter Server Heartbeat Installation Guides for step-by-step guidance on installing and configuring vCenter Server Heartbeat.

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

x86 Platform (32-bit hardware)

  • SQL Server 2012 Standard, Enterprise, and Express Editions on
    • Windows Server 2008 SP2 Standard and Enterprise
  • SQL Server 2008 R2 Standard, Enterprise, and Express Editions on
    • Windows Server 2008 SP2 Standard and Enterprise
    • Windows Server 2003 SP2 Standard and Enterprise
  • SQL Server 2008 Standard, Enterprise and Express Editions up to SP2 on
    • Windows Server 2008 SP2 Standard and Enterprise
    • Windows Server 2003 SP2 Standard and Enterprise
  • SQL Server 2005 up to SP4 Standard, Enterprise, and Express Editions
    • Windows Server 2008 SP2
    • Windows Server 2003 SP2

x64 / 64 Platform (64-bit hardware)

  • SQL Server 2012 Standard, Enterprise, and Express Editions on
    • Windows Server 2008 R2 SP1 Standard and Enterprise
    • Windows Server 2008 SP2 Standard and Enterprise
  • SQL Server 2008 R2 Standard, Enterprise, and Express Editions on
    • Windows Server 2008 R2 Standard and Enterprise
    • Windows Server 2008 SP2 Standard and Enterprise
    • Windows Server 2003 SP2 Standard and Enterprise
  • SQL Server 2008 Standard, Enterprise and Express Editions up to SP2 on
    • Windows Server 2008 R2 Standard and Enterprise\
    • Windows Server 2008 SP2 Standard and Enterprise
    • Windows Server 2003 SP2 Standard and Enterprise
  • SQL Server 2005 up to SP4 Standard, Enterprise, and Express Editions
    • Windows Server 2008 SP2
    • Windows Server 2003 SP2

Upgrading to vCenter Server Heartbeat 6.5

This release of vCenter Server Heartbeat 6.5 supports upgrades from previously supported versions. The vCenter Server Heartbeat 6.5 Installer prompts you to perform an upgrade only when a previously supported version of vCenter Server Heartbeat is found. See the Appendix C of the appropriate vCenter Server Heartbeat Installation Guide for installation requirements. When downgrading to a previous version of vCenter Server Heartbeat, do not use Setup to uninstall plug-ins. For information about performing plug-in installs/uninstalls please refer to VMware knowledge base article 1014435 (vCSHB-Ref-1815).

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.

Known Limitations

This section contains vCenter Server Heartbeat best practices for this release.

  • Setup VMware recommends that User Access Control (UAC) on Windows Server 2008 and Windows Server 2008 R2 be disabled when installing the product on both servers. UAC can be re-enabled once installation of vCenter Server Heartbeat has completed. Attempting to run Setup without disabling UAC will result in permission elevation prompts anytime the server is restarted.
  • Display Resolution Prior to starting Setup or launching the vCenter Server Heartbeat Console, set the display to a recommended minimum of 1024 X 768.
  • Physical to Physical Installation During a Physical to Physical installation on Windows Server 2008 SP2, a problem with Windows native permissions on the %windir%\winsxs\filemaps folder contents may cause the restore process to fail with the error System writer is not found in the backup. For a 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.
  • Setup 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.
  • Switchover/Failover After a switchover or failover, the Update Manager client connection will be lost if the timeout exceeds 15-20 seconds. Restart the vSphere Update Manager Client Plug-in once the Update Manager service has started to resolve the issue.
  • License Server VMware License Server service cannot be added to protected set if any of its dependencies are disabled on the passive server. When running vCenter Server Heartbeat v4.x with License Server installed on Windows 2008, VMware recommends that the Computer Browser service be changed from Disabled to Manual.
  • vSphere Client Plug-in — 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 first in the bind order, the installation will fail.
  • vSphere Web Client — The Heartbeat Plug-in for vSphere Web Client is supported in vSphere Web Client 5.1 and later.

Known Issues

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

vCenter Server Heartbeat Setup

  • Setup — When using the Install Clone technique for a Physical to Virtual architecture, the Secondary server must not have VMware Tools installed during the installation process
    If VMware Tools is installed on the Secondary server when using the Install Clone technique in a Physical to Virtual architecture, the packet filter will fail to install.
    Workaround: Uninstall VMware Tools completely prior to starting the Setup process. Once vCenter Server Heartbeat is installed, reinstall VMware Tool on the Secondary server.
  • Setup — 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.
  • Setup — If 10GB Mellanox network cards are present, TCP Offload Engine (TOE) must be disabled on all network cards before installation
    If 10GB Mellanox network cards are present, TCP Offload Engine (TOE) must be disabled on all network cards before installing vCenter Server Heartbeat. See VMware knowledge base article 1024066 (vCSHB-Ref-1919) for more information about this environment.
  • Setup/Upgrading — During installation, the Primary and Secondary server rename may fail to complete.
    During installation, the server rename of the Primary and Secondary servers may fail to complete because the domain controller for the domain was unable to process the rename request at time of the rename attempt.
    Workaround:The server rename process is the last step of vCenter Server Heartbeat installation. Should the server rename process fail to complete, manually rename the server to complete installation.
  • Upgrading — Upgrading VMware ESXi Dump Collector (Netdump), VMware vSphere Authentication Proxy, and VMware Syslog Collector from version 5.0 to version 5.1 may result in Error 29453 being displayed
    When upgrading VMware ESXi Dump Collector (Netdump), VMware vSphere Authentication Proxy, and VMware Syslog Collector from version 5.0 to version 5.1, with vCenter Server Heartbeat installed, the installer may display the warning: Error 29453 login failed due to bad user name or password.
    Workaround: The warning can be safely ignored. Proceed with the installation.

vCenter Server Heartbeat Administration

  • DB Files Allocated Space check fails because of a missing performance object
    The VMware SQL Server Plug-in does not 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 rule.
  • vCenter Server Heartbeat does not start on Secondary server and displays the following error message: VMware vCenter Server Heartbeat failed to initialize: Failed to set packet filter loadstate
    This error may be accompanied by an IP conflict and can occur after a Physical to Physical Install on Windows 2008 R2 if the packet driver fails to install because of a permissions error during driver installation.
    Workaround: Manually install the packet filter on the Secondary server. See VMware knowledge base article 1009567 (vCSHB-Ref-353) for instructions on how to manually install the packet filter.
  • When using the vCenter Server Heartbeat Plug-in for vSphere Client or vSphere Web Client the first time, the client displays Error #2032
    When selecting the Heartbeat tab of the vSphere Client or the vSphere Web Client for the first time results in the Adobe/Flex error #2032: Stream Error. URL: <url to textLayout %version% .swz> being displayed by vSphere Client or vSphere Web Client.
    Workaround: Connect to the internet prior to selecting the Heartbeat tab of the vSphere Client or vSphere Web Client for the first time. Subsequent use of the Heartbeat tab will not produce the error.
  • Events generated prior to the upgrade will not be readable after upgrade
    Events generated prior to the upgrade to vCenter Server Heartbeat 6.5 will not be readable after upgrade due to changes in the event structure. vCenter Server Heartbeat 6.5 events are now formatted so that they appear as unique Windows events in the Windows Application Event log.
  • During an upgrade, the Alert Configuration settings may be reset to their default values
    During an upgrade, the Alert Configuration settings may be reset to their default values.
    Workaround: If you have customized the Alert Configuration settings, make a note of the settings and reconfigure after the upgrade.
  • Enabling/Disabling the VMware Update Manager vSphere Client plug-in
    When the VMware Update Manager vSphere Client plug-in is enabled or disabled on the active server, the change is not automatically replicated to the passive server. After a subsequent switchover, you must repeat the change on the new active server.
  • Localhost names used prior to the server being renamed during installation appear in the vSphere Web Client Tasks and Events sections
    Localhost names that were assigned to the Primary and Secondary server prior to the renaming of the servers during installation appear in the vSphere Web Client Tasks and Events section.
    Workaround: Remove the old localhost names from the Heartbeat WebServices cache. See knowledge base article 2032853 (vCSHB-Ref-2510).
  • In a WAN environment after a switchover or failover, vCenter Orchestrator Server will fail to connect.
    When deployed in a WAN environment, after a switchover or failover, vCenter Orchestrator Server fails to connect because the Principal (Public) IP address is not updated.
    Workaround: Follow the procedure listed in VMware Knowledge Base article 1010470 (vCSHB-Ref-1762) to correct this issue.

vCenter Server Heartbeat vSphere Client Plug-In

  • After a switchover, vSphere Client or vSphere Web Client may fail to display the Heartbeat tab properly
    The Heartbeat tab in vSphere Client or vSphere Web Client may fail to display properly after performing a Make Active operation.
    Workaround: Refresh the vSphere Web Client browser or if using the vSphere Client, restart the client.
  • Manually restarting the Heartbeat WebServices causes duplicate events in vSphere Web Client
    If the user manually restarts the Heartbeat WebServices service, the service will replay up to a maximum of 300 previous events from the Heartbeat event log.  These events may have been reported previously and if so will be duplicates.
    Workaround: Disregard duplicate events.
  • During a switchover, incorrect Make Active tasks and task status may appear in the task list
    During a switchover, incorrect Make Active tasks and task status may be appear in the task list due to vCenter stopping on the currently active server and starting on the new active to effect the switchover while the task is being updated.
    Workaround: The correct task status is shown in the most recent Make Active task and can be seen on the Heartbeat tab of the vSphere Client, the vSphere Web Client, and the vCenter Server Heartbeat Console.
  • Following a failover or switchover, the vSphere Client fails to reconnect to vCenter Server
    After a switchover or failover, the vSphere Client fails to authenticate as it attempts to reconnect to vCenter Server.
    Workaround: To reconnect vSphere Client to vCenter Server, select the use Windows session credentials checkbox.
  • Clicking Make Active in the Heartbeat tab of the vSphere Client results in the vSphere Client presenting a Security Certificate acceptance
    When attempting to perform a Make Active operation via the Heartbeat tab in the vSphere Client, vSphere Client presents a Security Certificate for acceptance each time the Make Active operation is performed.
    Workaround: Accept the Security Certificate each time it is presented to allow the switchover to proceed.
  • When vCenter Server is configured using custom ports, VMware VirtualCenter Plug-in rules fail
    When vCenter Server is configured to use custom ports, VirtualCenter Plug-in is unable to connect to the remote server causing VirtualCenter Plug-in rules to fail.

Resolved Issues

This release includes fixes in the following subject areas:

vCenter Server Heartbeat Setup

  • Setup — Configuring Management IP addresses with the same prefix as the Public (Principal) IP address may result in an error during switchover/failover
  • Setup Installing vCenter Server Heartbeat Client Tools on Windows XP 32 bit requires SP3 and on Windows XP 64 bit requires SP2.
  • Setup — Installing vCenter Server Heartbeat using the local Administrator account rather than the Domain Administrator account prevents the system tray from starting
  • Physical to Physical Install — During installation, the backup fails with the error no drives included in the backup if command-line tools are missing
  • Upgrading — DNS tasks must be removed after upgrading from vCenter Server Heartbeat 6.3 Update 1
  • Setup — vCenter Server Heartbeat tab fails to register in vSphere Client during an upgrade

vCenter Server Heartbeat Administration

  • After a switchover, vCenter Service status displays an Alert with a red status
  • When deployed in a WAN configuration, after a switchover or failover, the Update Manager Server starts with a wrong IP address
  • vCenter Server Heartbeat plug-ins may fail to update ESX 3.5 hosts when these are managed by vCenter Server 4.0 and 4.1
  • VMware vCenter Server Heartbeat Log Collector fails to collect logs from the remote server
  • With vSphere Client open, performing a switchover using vCenter Server Heartbeat Console can cause a sweep synchronization process resulting in the vCenter Server Heartbeat Console displaying as Out-of-Sync
  • DNS update fails with exit code 104 at switchover although the switchover completes successfully
  • DNSUpdate fails to update DNS servers running on Windows Server 2008
  • Configuring Management IP addresses with the same prefix as the Principal (Public) IP address may result in an error during Switchover/Failover