Neverfail IT Continuity Engine v7.1 - Release Notes



This Knowledgebase article provides information about this specific release of Neverfail IT Continuity Engine v7.1


IT Continuity Engine v7.1 is the latest addition to the Neverfail family of continuous availability technologies that has been optimized for use in VMware virtualized environments. It provides product capabilities and benefits similar to Neverfail Heartbeat, but with a highly simplified and automated deployment process. IT Continuity Engine's deep integration with VMware vSphere provides complementary add-on HA/DR value in addition to the native VMware BCDR oriented solutions such as HA, SRM, and so on.

What’s New

Engine 7.1 builds on the core features and benefits of Engine 7.0 by adding the following:

  •  Tertiary Support
    • Create new trio (tertiary) deployments via an easy to use wizard
    • Transition an existing pair (HA/DR) to a trio (tertiary) deployment
  • Streamlined Deployment Options
    • The ability to customize IP configurations on each node during each deployment by allowing you to select which IP will be your public and which interface you want to use for the Neverfail Channel
    • Support for multiple NICs. Use a single or dual NIC configuration while using the Engine deployment wizard.
  • Redesigned Network Management
    • A complete redesign of packet filtering to leverage Windows Filtering Platform thus restricting network access on passive nodes without the need for hardware specific network interface device drivers.
  • Redesigned User Interface (Web Services)
    • Engine Management Service now has its own web portal service which enables management and deployment without the need for VMWare specific plug-ins.
  • Licensing Enhancements
    • Offline key application process. This now allows for pre-authorized license keys to be deployed quickly and easily for systems that are not connected to the internet.
  • Citrix Xen to VMWare as a Deployment Option 

Additional Detailed Information

Supporting Documentation

  • Neverfail IT Continuity Engine v7.1 Quick Start Guide
  • Neverfail IT Continuity Engine v7.1 Installation Guide
  • Neverfail IT Continuity Engine v7.1 Administrator’s Guide

Supported Deployment Infrastructure

  • Server roles/applications for which protection will be installed automatically are:
    • SQL Server 2008 R2 SP2, SQL Server 2012 SP1, SQL Server 2014
    • Exchange 2010 SP3, Exchange 2013 up to and including SP1, plus
      • ForeFront for Exchange
      • Symantec Mail Security
    • SharePoint 2007 SP2, SharePoint 2010, SharePoint 2013 up to and including SP1
    • File Server
    • Internet Information Server
    • vCenter Server 5.1 Update 2, vCenter Server 5.1 Update 3, vCenter Server 5.5 Update 1a, vCenter Server 5.5 Update 2
    • VMware View Composer 5.3
  • Additional supported plug-ins
    • Neverfail for Business Application


  • For information about pre-requisites for deploying Neverfail IT Continuity Engine v7.1, refer to either of the following:
    • Neverfail IT Continuity Engine v7.1 Installation Guide
    • Knowledgebase article #2800 – Neverfail IT Continuity Engine Installation Pre-requisites

Fixed Issues 

  • Tasks and events may be delayed before displaying in the Engine Management Service. (Ref-14897)
  • If the Secondary server virtual machine is deleted, the Neverfail Engine Management Service may continue to display the Secondary server as present and connected until the channel disconnect timeout completes. (Ref-14855)
  • When starting the Secondary virtual machine the first time after deployment, a Windows Unexpected Shutdown dialog is displayed as a result of hot-cloning (Ref-14659). 
  • When installing on Windows Server 2012, as a result of deployment, Windows Activation may not be retained. (Ref-14556)
  • The system tray icon will appear when the user logs on to the target server after installing Neverfail Engine. (Ref-14660)
  • If a NIC properties dialog is open on the target server when attempting to install Neverfail Engine, the installation will fail
  • When deploying Neverfail Engine, all NICs should be configured to Connect at power on and Connected prior to deployment of the Secondary server (Ref-16805)
  • Logging: Engine NFLog contains multiple informational-level entries like INFO351641[Commands](com.neverfail.amfx.AMFramework) - Licenses> Name=FileServer, value={featureIDs = [I@313e6479partnerIDs = [I@77365d30productIDs = [I@12203775} […] (Ref-17515).
  • When configuring the VmAdapter, configuring the Resource Pool text field with the keyword root prevents the migration from completing (Ref-15386)

Known Issues

Install/Uninstall/Upgrade of Neverfail IT Continuity Engine Management Server

  • After deploying the Engine, the navigation through Status/Events/Tasks/Rules/Settings is blocked.
    Workaround: Refresh the page and login again (EN-965).
  • When upgrading Neverfail IT Continuity Engine with the Neverfail System Tray tool running, the About information may not be updated.
    Workaround: Restart the Neverfail System Tray tool (EN-867).
  • The Engine Management Service User Interface fails to display a correct status when it is closed and reopened during an upgrade process (EN-1083). 
  • On uninstallation of Neverfail IT Continuity Engine Management Service, you may receive a popup about another process holding a lock on a log-file.
    Workaround: Start Task Manager and terminate any instances of nfremoteexec.exe (Ref-15310)
  • After uninstalling Neverfail Engine, when reinstalling, the status of the operation may briefly display inaccurately. (Ref-16640)
  • Converting a physical server to a virtual machine using VMware vCenter Converter fails with the error message: 'NBD_ERR_NETWORK_CONNECT' (error code:2338).
    Workaround: See Knowledgebase article #2889.
  • Importing a virtual machine using VMware vCenter Converter fails with the error message: Crypto Exception: error:02001005 when importing a virtual machine.
    Workaround: See Knowledgebase article #2888.


  • Logging out of the Neverfail Engine Management Service User Interface with a server pair selected in the Protected Servers pane and logging back in may result in the server cluster's information failing to display.
    Workaround: Refresh the Neverfail Management Engine User Interface page (F5) and re-login (EN-1018).
  • The Plan Execution pane steps displayed may not correspond to the server cluster selected in the Protected Servers pane except when an update arrives (EN-905).
  • When a trio is installed and the Secondary server becomes dead or deleted, you reinstall the entire trio (EN-508).
  • Synchronization status between servers in a trio is relative, for example, "A" is in-sync with "C" if "A" is in-sync with "B" and "B" is in-sync with "C" (EN-1037).
  • When extending a pair to a trio, the status message displayed during tertiary deployment may not be accurate (EN-1094).  
  • If a protected server is removed and re-added via Discover Protected Servers in the Neverfail Engine Management Service, old tasks may display in the tasks pane for the newly added protected server (Ref-15470)
  • Multiple concurrent tasks of the same type may not be shown correctly in the Neverfail Engine Management Service (Ref-16522)
  • When attempting to collect logs via the Neverfail SCOPE Configuration Tool, the dialog prompting you to put Neverfail into the Maintenance Mode is hidden behind the Neverfail SCOPE Configuration Tool dialog and prevents you from collecting the logs (Ref-14294).
    Workaround: Either maximize the dialog icon from the Windows Toolbar or use Alt+Tab to bring the dialog forward so that a response can be given to the prompt.

Install/Uninstall Information

Installation instructions are found in the following document(s)

  • Neverfail IT Continuity Engine v7.1 Installation Guide
    Important: If there is an existing installation of Neverfail Heartbeat Management for vCenter (also known as "Virtual Availability Director (VAD)/SRMXtender"), you MUST uninstall it before attempting to install Neverfail IT Continuity Engine. (Ref-15099)
  • Neverfail IT Continuity Engine v7.1 Quick Start Guide 

Uninstalling Neverfail Engine Management Server

  1. On the server running Engine Management Service, stop the Engine Management Service.
  2. From the Control Panel, uninstall Neverfail Engine Management Service.
    Note: If you receive a popup warning about another process accessing a log, start Task Manager and terminate any instances of nfremoteexec.exe 

Related Information



0 out of 0 found this helpful



Please sign in to leave a comment.