VMware vCenter Server Heartbeat 6.4 | Build 6643
Last Document Update: 16 FEBRUARY 2013
Check frequently for additions and updates to these release notes.
This release of VMware vCenter Server Heartbeat provides protection for the following products:
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 5.0
These release notes include the following topics:
- What's New
- Learning about vCenter Server Heartbeat
- Prior Releases of vCenter Server Heartbeat
- Before You Begin
- Known Issues
- Resolved Issues
The following information provides highlights of some of the enhancements available in this release of vCenter Server Heartbeat 6.4
Note: The features available depend on the version of vCenter Server installed.
- Administer VMware vCenter Server Heartbeat via vSphere Client — You can now install a vSphere Client Plug-in to administer VMware vCenter Server Heartbeat directly from the vSphere Client Heartbeat tab.
- Enhanced Passive server Management Capabilities for all Deployments — This option is used for all installs so the passive server can always be managed and monitored remotely, this includes receiving file level anti virus updates. This option is also supported when SQL Server is local to vCenter Server.
- Support for vCenter Server 5.0 — This release of VMware vCenter Server Heartbeat now provides support for vCenter Server 5.0
- Support for Microsoft Windows Data Center Edition — This release of VMware vCenter Server Heartbeat provides support of the Data Center Edition of supported versions of Microsoft Windows Server.
- Support for Microsoft SQL Server 2008 R2 SP1 — This release of VMware vCenter Server Heartbeat provides support for Microsoft SQL Server 2008 R2 SP1.
- Unattended Installation — You can now perform an unattended installation of vCenter Server Heartbeat using a script.
- Multi-Identity in a WAN — Support for Multi-Identity configurations in a WAN environment.
- Deployment Options — All deployment options (Virtual to Virtual, Physical to Virtual, and Physical to Physical) are supported in this release.
Note: The term vSphere Client is applicable to both vSphere Client and VI Client except where VI Client is specifically stated.
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:
- Click Video Download and save the .zip file to a folder on your computer.
- Extract the files into a directory on your system and navigate to the vCSHB_QuickStart_VideoInstall subdirectory.
- Double-click the vCSHB_QuickStart_VideoInstall.html file to start the video.
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
- vCenter Server Heartbeat 5.5
- vCenter Server Heartbeat 5.5 Update 1
- vCenter Server Heartbeat 5.5 Update 2
- vCenter Server Heartbeat 6.3
- vCenter Server Heartbeat 6.3 Update 1
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.
The vCenter Server Heartbeat Installation 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/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
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
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 Installation Guide (PDF)
- vCenter Server Heartbeat Administrator Guide (PDF)
Read the vCenter Server Heartbeat Installation Guide 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:
- SQL Server 2005 SP1 and later
- SQL Server 2008 including SP1 and later
- SQL Server 2008 R2 SP1
This release of vCenter Server Heartbeat 6.4 supports upgrades from previously supported versions. The vCenter Server Heartbeat 6.4 Installer prompts you to perform an upgrade only when a previously supported version of vCenter Server Heartbeat is found. See the vCenter Server Heartbeat Installation Guide for installation requirements and VMware Knowledge Base article 1014435 (vCSHB-Ref-1815) for the upgrade procedures. 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: After upgrading from a previous version with identical nodes to vCenter Server Heartbeat 6.4 you must migrate to non-identical nodes configuration. To migrate from identical nodes to non-identical nodes, refer to VMware Knowledge Base article 2002112 (vCSHB-Ref-2137) - Migrating vCenter Server Heartbeat 6.3 Update 1 and later from identical nodes to non-identical nodes or VMware Knowledge Base article 2002117 (vCSHB-REF-2209) - Migrating vCenter Server Heartbeat 6.3 Update 1 and later from identical nodes to non-identical (Updates MS DNS) nodes as appropriate.
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.
This section contains known issues for this release in the following subject areas:
- vCenter Server Heartbeat Setup
- vCenter Server Heartbeat Administration
- vCenter Server Heartbeat Plug-Ins
Setup — Configuring Management IP addresses with the same prefix as the Public (Principal) IP address may result in an error during switchover/failover
If a management IP addresses is configured with the same prefix as the Public (Principal) IP address, an error may result during switchover/failover.
Workaround: Configure Management IP addresses to use a different prefix than the Public (Principal) IP address. See VMware Knowledge Base article 2004926 (vCSHB-Ref-2297) for more information.
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 — 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.
Setup — vCenter Server Heartbeat Client Tools Only installation requirements for Windows XP
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
If you intend to install vCenter Server Heartbeat using a local Administrator account rather than a Domain Administrator account, please see VMware Knowledge Base article 1022867 (vCSHB-Ref-1916).
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.
Physical to Physical Install — 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.
Physical to Physical Install— During installation, the backup fails
with the error no drives included in the backup if command-line tools are
During installation, when the backup is taken, it fails with the error 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.
Physical to Physical Install— 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.
DNS tasks must be removed after upgrading from vCenter Server Heartbeat 6.3 Update 1
After performing an upgrade from vCenter Server Heartbeat 6.3 Update 1 you must remove DNS tasks via vCenter Server Heartbeat Console. See VMware Knowledge Base article 1014435 (vCSHB-Ref-1815) for the procedure to remove the DNS tasks.
vCenter Server Heartbeat tab fails to register during an upgrade
During upgrade, the vCenter Server Heartbeat Plug-in for vSphere Client fails to register.
Workaround: Register the plug-in manually providing the vCenter Server username and password following the post-upgrade steps in VMware Knowledge Base article 1014435 (vCSHB-Ref-1815).
After a switch/failover the Update Manager Client Plug-in requires the vSphere Client to be restarted
After a switchover or failover, the Update Manager client connection is lost if the timeout exceeds 15-20 seconds.
Workaround: Restart the vSphere Update Manager Client Plug-in once the Update Manager service has started.
After a failover or switchover the vSphere Converter Plug-in may report Unable to connect to vCenter Converter Server
After a switchover or failover, the vSphere Converter Plug-in fails to connect to vCenter Converter Server.
Workaround: Restart the vSphere Client.
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.
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 vci-integrity.xml file with the correct IP address or Fully Qualified Domain Name (FQDN).
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.
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.
DB Files Allocated Space check fails because of a missing
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.
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
ESX hosts version 3.5 managed by a vCenter Server 4.0 or 4.1 may fail to successfully reconnect following a failover or switchover.
Workaround: Re-register the ESX 3.5 hosts against the vCenter 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.
Unable to synchronize after a switchover
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. This can occur when the install path to the license server component is installed below that of vCenter Server.
Workaround: Close vSphere Client when performing a switchover using vCenter Server Heartbeat Console.
DNS update fails with exit code 104 at switchover
During a switchover, the DNS update task is run but finishes with exit code 104 although the switchover completes successfully.
Error #2032 displayed when using the Heartbeat Plug-in for vSphere Client for the first time
When selecting the Heartbeat tab of the vSphere Client for the first time results in the error #2032: Stream Error. URL: <url to textLayout %version% .swz>.
Workaround: Connect to the internet prior to selecting the Heartbeat tab of the vSphere Client for the first time. Subsequent use of the Heartbeat tab will not produce the error.
Heartbeat tab in vSphere Client may fail to display properly after a switchover
The Heartbeat tab in vSphere Client may fail to display properly after performing a Make Active operation.
Workaround: Restart the vSphere Client.
VMware vCenter Server Heartbeat Log Collector fails to collect logs from the remote server
When attempting to collect vCenter Server Heartbeat logs, the log collector fails to collect the logs from the remote server.
Workaround: Collect the logs from each server separately. See VMware Knowledge Base article 2004377 (vCSHB-Ref-2296) for more information on how to collect the logs separately.
Clicking Make Active in the Heartbeat tab of the vSphere Client results in a Security Certificate being presented for acceptance
When attempting to perform a Make Active operation via the Heartbeat tab in the vSphere Client, a Security Certificate is presented 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.
State of vSphere 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.
Installing vSphere Client Plug-in results in an error
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.
This release includes fixes in the following subject areas:
- vCenter Server Heartbeat Setup
- vCenter Server Heartbeat Administration
- vCenter Server Heartbeat Plug-Ins
- vCenter Server Heartbeat Rules
- vCenter Server Heartbeat Uninstall/Modify
- Setup — During pre-install checks on Windows Server 2008, a Windows pop-up may appear stating Server is busy: The action cannot be completed because the other program is busy.
- Setup — vCenter Server Heartbeat installation stops when an Oracle service is detected.
- Install Clone — Installing vCenter Server Heartbeat in a Physical to Virtual environment using the install clone technique with differing disk subsystems may cause the Operating System to fail.
- Setup — User Access Control (UAC) must be disabled during installation.
- UAC on Windows Vista blocks the user from adding server pairs.
- The Message Incompatible product: unable to connect to server when vCenter Server Heartbeat is shutting down.
- Uninstalling the 5.5.3086 Service Pack removes the R2\logs folder.
- The Server Configuration wizard reports License Key valid when it has in fact expired 60 days after the installation date.
- After a reboot of the active server, .Net components registering in WMI may cause a delay in the startup of vCenter Server.
- VCWanUtility may cause the CPU to spike to 50%-100% when executing vCenter health checks.
- After installing vCenter Server Heartbeat Client Tools and attempting to start the vCenter Server Heartbeat Console, if the SSL certificate is refused, vCenter Server Heartbeat Console may not start but leaves the nfgui.exe process running.
- The System Tray application may fail after restarting the server when running Windows 2003 SP2 x64.
- Configuring a plug-in user that has spaces in its name requires double quotes to work.
- Setup copies the vCenter Server, SQL Server and System Plug-ins to a location accessible from vCenter Server Heartbeat Console for use during the upgrade procedures.
- If one vCenter Server instance is not accessible, the Tomcat rule fails with the error Object reference not set to an instance of an object.
- Some vCenter Server Heartbeat server performance counters are missing when installed on Windows 2008 servers.