This Knowledgebase article provides information about Neverfail Heartbeat and Neverfail Replicator V6.0.1.
Technical Documents supporting this version of Neverfail Heartbeat are contained in Knowledgebase article #1776 - 'V6.0[.n] Neverfail Heartbeat and Neverfail Replicator - Technical Documentation'.
These following optional features are enabled by the Neverfail License Key. Please contact your account manager for details.
- Simultaneous support for a High Availability pair and a third Disaster Recovery server known as a Tertiary server.
- WAN Acceleration - Offering significant bandwidth reduction over the Low Bandwidth Module (LBM) improving data transfer to the Disaster Recovery site.
Supported Operating Systems
The following Windows versions are supported for this release:
- Windows Server 2008 SP1/SP2 x86
- Windows Server 2008 SP1/SP2 x64
- Windows Server 2003 SP1/SP2 x86
- Windows Server 2003 SP1/SP2 x64
These versions of Windows may be installed:
Note: Neverfail Heartbeat supports any combination of physical and virtual servers.
- On physical hardware
- In a Virtual Machine running on Microsoft's Hyper-V
- In a Virtual Machine running on VMware's ESX
Please consult the Release Notes for the specific plug-in to see which versions of applications are supported on Windows Server 2008.
- Administrators can now pre-clone the Primary server to rapidly create the Secondary and Tertiary servers during installation.
- Critical checks performed by SCOPE (refer to the Installation Guide).
- Memory requirements - Neverfail Heartbeat will now check for a minimum of 1GB RAM. To ensure memory requirements are satisfied for the Operating System and protected applications at least 2GB is recommended.
- Pre-Clone Installation
Heartbeat System Tray Icon
- The ability to start and stop Heartbeat on all servers (Primary, Secondary, and Tertiary).
Neverfail Heartbeat Management Client
- Displays a Tertiary server topology (if installed).
- The Switch button is replaced by the Make Active button to accommodate 3 servers. Administrators select the server they wish to make active.
- The replication chain is displayed (active > 1st passive > 2nd passive).
- Added ability to specify which Heartbeat servers will shutdown.
- The added ability to configure 'Pings From' and 'Pings To' addresses.
- The added ability to configure 'Ping Interval' and 'Timeout' for LAN and WAN deployments.
- The addition of the WAN Compression screen that includes new settings for statistics for WAN Acceleration.
- Added ability to create snap shot schedules for the Tertiary node.
- System Overview
- Simultaneous support for cached and non-cached writes.
- False failover prevented under low memory conditions.
- Added support for Tertiary DR node.
Heartbeat & Network Checks
- Bound checking to connection and disconnection responses prevents failover when very frequent heartbeat checks have been set.
- Heartbeats are not missed during very large file copies from the passive server.
- Configuration is no longer set in the Configuration wizard; settings are no longer lost after a restart of Heartbeat.
- Added support for Apache Chainsaw format for improved log analysis.
Windows Server 2000 SP4
- No longer a supported operating system.
The following are known issues in Neverfail Heartbeat V6.0.1.
- This version of Neverfail Heartbeat supports in-place upgrades of Neverfail Heartbeat V5.3.4 and V5.5.1 to Neverfail Heartbeat V6.0.1.
- Upgrading to Neverfail Heartbeat V6.0.1 requires that a new license key be generated and added after installation and prior to starting Neverfail Heartbeat.
Prior to installing Neverfail Heartbeat V6.0.1 on a server running SCOPE Data Collector Service V5.0.5 x64 you must manually uninstall SCOPE Data Collector service V5.0.5 x64.
Note: Do not attempt to upgrade to a higher version of SCOPE Data Collector Service or install Neverfail Heartbeat without performing the following procedure.
Workaround: To uninstall SCOPE V5.0.5 x64 perform the following steps:
- From a Windows command prompt type: sc stop scopesvc or navigate to Start > Control Panel > Administrative Tools > Services and stop 'Neverfail SCOPE Data Collector' service.
- Go to http://support.microsoft.com/kb/290301 .
- Download and run Cleanup Utility to remove SCOPE Collector from your system.
Using Regedit, check for the presence of the following registry key and if present, delete it.
- Delete the SCOPE installation directory.
- Workaround: To uninstall SCOPE V5.0.5 x64 perform the following steps:
When Neverfail Heartbeat is installed in a Tertiary configuration and the Neverfail license does not include the Tertiary feature, Neverfail Heartbeat will display an error message stopping Heartbeat. The Configure Server wizard will inappropriately show the license as valid.
- Workaround: Obtain and install a Neverfail license that includes the Tertiary feature.
- When volumes from the Primary and Tertiary servers don't match, a message is not displayed and the installation will be allowed to continue until the backup/restore is started.
- An x64 Client Tools Setup will not be allowed to proceed because the user account is not recognized as an Administrator account.
- Neverfail Heartbeat does not support in place upgrades of the operating system from Windows Server 2003 to Windows Server 2008.
- Neverfail for File Server deployments are not supported on Windows Server 2008.
- Neverfail recommends that the User Access Control (UAC) on Windows 2008 be disabled when installing the product on both servers. UAC can be enabled once the install of Neverfail Heartbeat has been completed.
- When a channel becomes disconnected, the event log entry is not complete.
- The Recovery Point displayed may not be accurate.
- Service monitoring tasks will continue to run when service protection and application monitoring is disabled.
- On a channel disconnect between two servers, the Neverfail Heartbeat Management Client momentarily shows all channels are disconnected.
- Rule Action tasks do not appear in the Task Type drop-down.
- A disconnected passive server will ignore a request to shutdown and add a nullptr to the log.
- The Configure Server wizard shows a license for the Tertiary feature as valid when it does not contain the Tertiary functionality.
Errors are displayed if the System Plug-in is upgraded on the Secondary / passive server using the Neverfail Heartbeat Management Client. Plug-ins should be installed on the Active server.
- Workaround: Stop and restart Neverfail Heartbeat and reinstall the System Plug-in on the Active Server.
When selecting only one license key from a list of license keys in the Configure Server wizard and clicking on the Trash Can icon to delete the single license key, all keys are deleted.
- Workaround: Re-add the required license keys in the Configure Server wizard.
- The server monitoring task will continue to run after a protected service is edited.
- A user defined protected service with a target state of running on both that active and passive server does not stop when the Stop Applications button is clicked.
- When add a new User Account in the Tasks panel of the Neverfail Heartbeat Management Client it may momentarily disappear and reappear.
DNSUpdate doesn't run on the Secondary server after a switchover.
- Workaround: Navigate to Application > Tasks and select the DNSUpdate task. Delete the task and create a new DNSUpdate task using the procedure shown in Knowledgebase article #1425 - How to Configure DNS with Neverfail Heartbeat V5.3.0 and Later in a WAN Environment
- When adding a new User Account in the Tasks panel, the domain is not validated by the Management Client.
- The Max Time Difference dialog is not included in the Neverfail Heartbeat Management Client.
- The Application Status icon will display a "check" after the application is stopped.
If you uninstall a plug-in and then rollback to a snapshot taken when the plug-in was installed, the filters defining the set of data to be protected may refer to the uninstalled plug-in.
- Workaround: Manually remove the filters defining the protected set of data that refer to the uninstalled plug-in on all servers.
An error may appear when attempting to collect logs from the Secondary or Tertiary server.
- Workaround: Manually collect the log files.
- When installing Neverfail Heartbeat from a remote desktop session, the installer (Setup.exe) may run a backup tool during the installation. When the backup process finishes there may be a popup window asking you to check the status of the backup. Occasionally this popup window is hidden by the main installer window. The installation will not proceed because the Next button in the main installer window remains disabled until you have acknowledged the popup by clicking on it.
Installation instructions are found in Neverfail Heartbeat and Neverfail Replicator Installation Guide V6.0-Rev3 .
Neverfail Heartbeat V6.0.1
Instructions for managing the day-to-day operations of Neverfail Heartbeat can be found in the Neverfail Heartbeat and Neverfail Replicator Administrator's Guide V6.0-Rev3