Neverfail Continuity Engine 19 Release Notes

Neverfail Continuity Engine 19 Release Notes

Summary

The following information applies to the v19 release of Continuity Engine.

Continuity Engine 19.0

This release supersedes Continuity Engine v18.

What's New

Windows Server 2025 Support

  1. Supported deployment of Continuity Engine components: EMS Web Console, Engine, Scope, Cli, Utilities. 
  2. Support for System Plugin, IIS Server Plugin, File Server Plugin with Windows Server 2025 bundled roles and features.
  3. Support for vSphere Integration Plugin operations on WS2025 running inside a VMware VM.

In-Product Notification Enhancements

  1. Improvements to notifications delivery mechanism.
  2. Added silent triggers mechanism used in EMS relicensing task.

Independent Identity Deployment Support

  1. Continuity Engine may be deployed in a Independent Identity  (IID) cluster architecture via CLI Installer.
  2. ProServ driven deployments: additional requirements and post-deployment configuration may be needed, depending on the deployment scenario and protected application.
  3. Plugins will be changed to support IID application deployment (where applicable). In this release, System plugin was added to IID-supporting family. 

EMS UI New Dashboards

  1. New dashboards that offer a synthetic view, consolidating managed Engine server version support and subscription payment status into a single interface.

Alerting based on Managed Server Telemetry

  1. By enabling telemetry, you empower the EMS to deliver better monitoring and alerting for critical events that matter most to your business. This will translate into quicker response times, more accurate alerts, and ultimately, greater peace of mind knowing that your systems are running optimally.
  2. The first chapter in unlocking advanced monitoring and alerting was to enable our new telemetry service v16, which will seamlessly extract relevant information about events happening on the Engine nodes.
  3. v17 adds more to this feature by improving the telemetry data upload-via-EMS feature for a deployment not managed via Engine Management Service. 
  4. v18 enables In-Product Notification feature which may be used for announcing and alerting customers with relevant Engine information.
  5. v19 extends and prepares notification vehicle to be used in relicensing and alerts delivery.

Better User Experience

Application Management - Automating Discovery and Protection via Dedicated Plugins  (on-going)

  1. New plugins will be developed and added to Continuity Engine family, release by release. These plugins will replace the manual implementation of User Defined application protection. 
  2. Application protection made simple. Homogeneous. Reliable.

Configure Server Wizard - Passive patching configuration

  1. Passive patching configuration enables passive node for using DNS port 53 in case this is required. 

Offline Licensing Management via EMS

  1. UX Improvements for hardened environments: managed server will show Product Version on grey background with tooltip message "Cannot validate support". Access to offline licensing is permitted.
  2. Self-service offline licensing based on telemetry data: customers may claim license keys directly from Engine Management Service for deployments which are not managed via EMS.
  3. Install Engine Management Service on any supported Windows machine with access to internet (i.e. Engine Licensing Server) then claim your license keys corresponding to your purchased software subscription from the Support section. Details in Self-Service Offline Licensing: How to Claim a License Key for a Deployment Not Managed via Engine Management Service.

New Version Availability and Download Published via EMS

    Patching Downtime Reduction with Passive Management Name

    1. Continuity Engine's Passive Management Name feature enables the ability of patching of standby passive nodes in centralized update management environment.
    2. Following document lists all the Patch Management or Backup Software Solutions / Technologies proven to work or scheduled in the near future for interoping validation with Continuity Engine's Passive Management Name feature: Patch Management Solutions / Technologies supported by Continuity Engine's Passive Management Name

    Progress MOVEit 2025 Plug-ins Suite

    1. Support for MOVEit Automation Server 2025 (plugin version 201.5.7)
    2. Support for MOVEit Transfer Server 2025 (plugin version 201.5.7)

    File Server Plugin v201.5.9

    1. Support for File Server version bundled with Microsoft Windows Server 2025 Standard / Datacenter.
    2. Protected services management optimization: target states for the protected service Server (lanmanserver)  are changed as follows: Running on the Active Server and Running on the Passive(s) Server(s).
      1. Server service will be restarted only in case of Engine switchover or failover; it won't be restarted anymore in case of FS application stop/start while active server remains the active one.
    3. Dependent services improvement: MsQuic service will me monitored only if found as installed service. This will fix the "Service MSQUIC failed its check" issue cause by Windows OS changes.
    4. More details in File Server Plugin v201.5.9 Release Notes.

    System Plugin v401.0.10

    1. Support for Microsoft Windows Server 2025 Standard / Datacenter
    2. Split-Brain Avoidance (SBA) auto-configuration enhancement: configured Engine Public IP addresses are used as ping targets.
    3. Support for Continuity Engine Independent Identity Configuration
      1. Installation note: IID support must be configured before Engine replication is started between the non-cloned nodes. IID enablement is performed in plugin's configuration section.
    4. More details in System Plugin v401.0.10 Release Notes.

    IIS Plugin v201.5.10

    1. Support for IIS 10.0 bundled with Windows Server 2025.
    2. Retired support for Continuity Engine Independent Identity Configuration.
    3. Read IIS Plugin v201.5.10 Release Notes for more details.

    vSphere Integration Plugin v201.5.4

    1. Support for Windows Server 2025 running inside a VMware VM.
    2. More details in vSphere Integration Plug-in v201.5.4 Release Notes

    Mitel CX Plugin v201.5.7

    1. Mitel CX Plugin provides protection and proactively monitors Mitel CX  environment’s configuration data, services, and application data files.
    2. New: Support for Mitel CX 1.0 for MiVB  / SIP
    3. Backwards compatibility for: MiContact Center Business R10.0/SIP, MiContact Center Business 9.5, MiContact Center Business 9.4, MiContact Center Business 9.3, MiContact Center Server v9.0 (both Main/Enterprise and Remote installation versions)

    Honeywell Pro-Watch Plugin v201.5.1

    1. Honeywell Pro-Watch Plugin provides protection and proactively monitors Honeywell Pro-Watch environment’s configuration data, services, and application data files.
    2. New: Support for Honeywell Pro-Watch 6.5.1 server.

    Clever Devices CleverCAD Plugin v201.5.4

    1. Clever Devices CleverCAD Plugin provides protection and proactively monitors CleverCAD environment’s configuration data, services, and application data files.:
    2. support for CleverCAD 10.19.
    3. support for CleverCAD Rail component: discovery, control, monitoring and failure recovery.

    Access to Continuity Engine Utilities Repo

    1. Access Continuity Engine collection of utility scripts and add-ons designed to extend core features
    2. Collaborate for enhancing and extending Continuity Engine functionality for specific scenarios 
    3. Utilities repo may be accessed directly from EMS UI> Support> Add-ons

    Snapshot Management Improvements

    Ransomware Recovery: With Snapshot Management organizations can take snapshots each 15 minutes and roll back the dataset to before the incident happened thus restoring the protected application server to full operating conditions.
    1. How to Use Continuity Engine For Ransomware Mitigation
    2. How to Setup Snapshot Management for Neverfail Continuity Engine

    CLI Installer and Service Manager Improvements

    1. Upgrade: improvements to preferences preservation mechanism.  
    Engine command-line installer (CLI) may be used for installing, upgrading or uninstalling Continuity Engine on a specific node. 
    It was designed to be used in the scenarios where EMS-driven fully automated install/upgrade cannot be used. Contact Support for guidance.

    Desktop Widget Tool

    1. This standalone tool may be registered to Engine SysTray tool and provides high-level, in-desktop System and Engine status and notifications.
    2. Usage described in Continuity Engine Desktop Widget Tool Guide

    More Secure

    Latest Security Updates and Fixes for OpenJDK and Apache Tomcat

    New Supported Versions

    VMware vCenter Server and VMware vCenter Converter Support

    1. Supported - Engine Management Service API Support for deployment using the latest versions of VMware vCenter Server 7.0 and VMware vCenter Converter 6.2.
    2. Supported - vSphere Integration Plugin Support for interoping with the latest versions of VMware vCenter Server 7.0
    3. Coming Soon - Engine Management Service API Support for deployment using the latest versions of VMware vCenter Server 8.0 and VMware vCenter Converter 6.3.
    4. Coming Soon - vSphere Integration Plugin Support for interoping with the latest versions of VMware vCenter Server 8.0.

    Licensing Updates 

    License Management - Plugin Subscription

    1. Each Engine deployment requires the appropriate Plugins to be installed and corresponding Plugin subscriptions to be purchased.
    2. A separate Plugin subscription is required for each installed and protected application that has its own dedicated Plugin. 

    Licensing Service Access only for Supported Versions

    1. End-User License-Subscription Agrement changes are summarized in the below section extracted from Neverfail End-User Software Subscription License Agreement.
    2. License Key Issuance vs. Software lifecycle: License Key issuance for a new or a renewed Software Subscription is viable only on currently supported versions of the Software..
    3. Engine follows a software subscription term and rental licensing  model. Engine Licensing Service (ELS) enables call-home features that power our software subscription based licensing. The new license service is free but is required for Term and Rental deployments. For more information on how the licensing works and upgrade notes please read Continuity Engine Licensing Model. 

    Backward Compatibility

    Continuity Engine 19 Management Service is compatible with older supported versions of Engine (i.e. EMS 19.0 manages correctly, including licensing services, for all the supported CE versions 15/16/17/18). 

    1. If I upgrade to Continuity Engine 19, will my perpetual license cease? Yes! You are accepting software subscription's  requirements outlined in the new EULA for Term and Rental. Neverfail will generate new software subscriptions expiring the same day as the support was paid through. This means you will need to pay for support to continue software operations yearly or monthly depending on the type of subscription.
    1. Can I upgrade using the Upgrade Wizard from older/unsupported versions to Continuity Engine 19? Yes, the upgrade wizard is still supported. Keep in mind that Continuity Engine versions 6.7, 7.x, 8.x, 9.x, 10, 11, 12, 13 are currently End-of-Life (EOL). To ensure organization continued support and access to licensing services, you must upgrade to the latest Continuity Engine version.

    2. When will Continuity Engine EOL? Check End of Life Policy for Neverfail Continuity Engine

    3. Can I stay on previous versions of Continuity Engine? Yes, however, previous versions will eventually EOL and you will not be able to take full advantage of the new features of Continuity Engine. And evenly important, your systems will be more exposed to cyberattacks. For example:

      1. CEv14.0
        1. misses all the Java OpenJDK security fixes released between April 2024 (8u412-b08)) and July 2025 (8u462-b08).
        2. misses all the Apache Tomcat security fixes released between April 2024 (Tomcat 9.0.89) and August 2025 (9.0.108).

    Supported Deployment Infrastructure

    • Server roles/applications for which protection will be installed automatically via plugins are:
      • SQL Server 2008 SP4*, SQL Server 2008 R2 SP3*, SQL Server 2012 SP4, SQL Server 2014 SP3, SQL Server 2016 SP2, SQL Server 2017, SQL Server 2019, SQL Server 2022
      • Exchange 2010 SP3, Exchange 2013 up CU17, Exchange 2016, Exchange 2019
        • ForeFront for Exchange up v10 SP1
        • Symantec Mail Security up to v7.9
      • SharePoint 2007 SP2, SharePoint 2010 SP2, SharePoint 2013 up to SP1, SharePoint 2016, SharePoint 2019
        • Microsoft Office Online Server 2016
      • File Server including Windows Server 2022
      • Internet Information Server including v10 on Windows Server 2022
      • VMware vCenter Server 6.0 up Update 3c, VMware vCenter Server 6.5 up Update 1d, VMware vCenter Server 6.7
      • vCenter Server 5.1 Update 2, vCenter Server 5.1 Update 3, vCenter Server 5.5 Update 1a, vCenter Server 5.5 Update 2, vCenter Server 5.5 Update 3, vCenter Server 5.5 Update 3a, and vCenter Server 5.5 Update 3b
      • VMware View Composer 5.3, VMware View Composer 6.2.5, VMware View Composer 7.6
      • Progress MOVEit Central 8.0/8.1, MOVEit DMZ 8.1, MOVEit 2017, MOVEit 2018, MOVEit 2019.2, MOVEit 2020.1, MOVEit 2021.1, MOVEit 2022.1, MOVEit 2023.0, MOVEit 2023.1, MOVEit 2024.0, MOVEit 2024.1: Automation, Transfer, Mobile Servers, Analytics Agent
      • MySQL Server 5.x, 8.x
      • Mitel CX 1.0, MiContact Center Server v9.0, MiContact Center Business 9.3, MiContact Center Business 9.4, MiContact Center Business 9.5, MiContact Center Business R10.0/SIP
      • Any of the following SolarWinds Orion Network Management components: SolarWinds NPM v12.0.1, v12.1, SolarWinds APE v12.0.1, v12.1, SolarWinds NCM v7.5.1, v7.6, SolarWinds SAM v6.3.0, v6.4, SolarWinds NTA v4.2.1, v4.2.2
      • Oracle Database 19c, 18c, 12c, 11g
        • Oracle Management Agent v12, v13
      • System Center Operations Manager (SCOM) platforms: 2007*, 2007 R2*, 2012*, 2012 R2*, 2016, 2019 
      • Veeam Backup & Replication 9.5 U3 & U4
      • Atlassian Confluence 6.x versions 
      • Atlassian Jira 7.x versions
      • PostgreSQL 9.3, 9.4, 9.5, 9.6, 10.x versions
      • Apache Tomcat 8.x.x., 9.x.x, 10.x.x. versions
      • OpenText CX-E Voice (formerly xMedius/AVST CX-E/CallXpress) up to version 23.4
      • Clever Devices CleverCAD 9.9, 10.x
      • Automated Logic WebCTRL 8.0
      • Hyper-V Server 2016, 2019, 2022(non-clustered architecture)
      • Mitel BluStar 7.3.0
      • OPSWAT MetaDefender Managed File Transfer v3.6.x, 3.7.x., cloned or non-cloned architecture
      • Honeywell Pro-Watch 6.5.1
    • Additional supported plugins
      • Neverfail CE for Business Application
         *Limited support as per manufacturer (via older Continuity Engine versions) - contact Neverfail Support 

    Continuity Engine Plugins

    Note: Detailed information about each plugin is contained in the plugin's knowledgebase file that is available by clicking on the link.

    Engine plugins provide protection for specific installed application configuration data, services, and application data files.  

    The following plugins are included in this release of Continuity Engine and are installed automatically if the application is present and version supported:

    Plugin Installation

    Initial installations of Continuity Engine Plugins must be performed using the Engine Management Service. Subsequent plugin re-installations and upgrades may be performed using the Applications: Plugins tab of the Advanced Client. However, Neverfail recommends that any subsequent plugin repair installations or upgrades to be performed using Engine Management Service.    

    To manually install a plugin follow the How to install a Continuity Engine Plugin using Advanced Management Client procedure.

    Fixed Issues

    1. [EN-6799]: [AMCx64]: Group/Connection behaves funky: works when defined first. But after restarting AMC group definition is missing and defined connection is misbehaving.
    2. [EN-6816]: [EMS UI]:Logout after timeout expires is not user friendly - it shows a lot of RED toast messages. 
    3. [EN-6828]: [CLI Installer]: Fix version reporting. 
    4. [EN-6848]: [EMS UI]: Replace login suggested "administrator" with something more appropriate indicating a local\domain account.

    Known Limitations

    • Passwords starting and/or ending with space ( ) character(s) are not supported (EN-3935).
    • (Re)cloning limitation: Disconnected Engine cluster after a cloning or recloning action: recloned node is connected to wrong port group. Workaround documented in Continuity Engine Cloning and Recloning limitations: disconnected Engine cluster  (EN-3354)
    • Recloning limitations when Continuity Engine passive nodes when static routes are configured: these are listed in Continuity Engine Recloning limitations when static routes are configured  (EN-3355)
    • Continuity Engine Localization limitations: following localized versions of Windows Server targets/topologies are supported for Engine installation: (EN-3221) 
      • any WS2008R2, WS2012/R2, WS2016 OS domain or workgroup member protected by HA, DR or HA+DR Engine topology having only alphanumeric chars in its hostname and AD domain name
      • any WS2008R2, WS2012/R2, WS2016 OS domain or workgroup member protected by HA or DR-with-same-Public-IP Engine topology having only alphanumeric chars in the AD domain name
    • Engine Management Service will not uninstall a server with an expired license (EN-1315).
    • Affects only vCenter Server 6.x protected by Engine v8.x (or newer) DR deployments with the DR-node configured with different IP address: Managed ESXi hosts appear as disconnected in vCenter Server/vSphere Client after making DR node active. (EN-2042).
    • Continuity Engine .msi installer package is sometimes detected as having untrusted publishers (EN-969).
    • The FileServer plugin bundled with Continuity Engine v8.5 (or newer) properly replicates DFS namespaces. The DFS Management Client does not load the namespaces correctly each time.
    • Affects only MOVEit Central/Automation Server protected by Engine v8.5 (or newer): Local folders specified as source/destination in MOVEit Automation tasks require user-defined filters for protection. (EN-2879)
    • Affects only Engine clusters upgraded from Ipswitch Failover 9.0/9.5 to Engine 8.5 (or newer) (when Create and maintain shadows automatically was not enabled): Progress Failover shadows are still visible as restore points in DRM after upgrading to Engine 8.5 (EN-2863)
    • Affects only upgrades from Ipswitch Failover 9.0/9.5 to Engine 8.5 (or newer): Some Ipswitch Failover 9.0/9.5 log and configuration files are not deleted when upgrading to Engine 8.5 (EN-2820, EN-2861)
    • [Applies to 9.0 (or newer) with Passive Node Management Identity configured] vCenter Inventory passive VMs are not detected as Protected nodes if management name is configured and webservices are stopped on the active. Dashboard's protected servers count in Global Inventory is also impacted. (EN-4647)
      • conditions: Management name configured AND active server webservices stopped
      • result: deployment.location is not available hence the clustername mechanism is used. that makes only the Active server to be reported as protected node (if VM). Passives cannot be determined as vmid is not available
    • [CE HTML5 UI] When extending from pair to trio (add DR to HA pair) Secondary webservices require restart in order to serve (when made active) the updated deployment topology (trio instead of pair). This is known as the webservices are not restarted on S and S is the T's cloning source. (EN-4657)
      • impact: only if S is made active before webservices restart: new HTML UI Datacenter info is not accurate on Tertiary. Possible Protected node count is wrong if management identity is configured on any of the passives.
      • remediation: restart webservices on Secondary/Tertiary
    • [AMFx]: User defined sponsor is not persisted in prefs till Engine service is restarted. Thus webservices don't know about it (till restart is done) (EN-4341)
    • [CE HTML5 UI] Active compression type is shown as 'Standard' when there are no passive instances present in the replication chain. Workaround: This issue is purely cosmetic and it will correct itself once there are passive instances present in the replication chain. (EN-4855)
    • [CE HTML5 UI] Data traffic value in serverlist API is not always accurate. (EN-4859)
    • [CE HTML5 UI] Reconstruct pair: transform from pair HA to pair DR> HA cached configuration must be cleaned up before defining new DR config (EN-4915)
    • [CE HTML5 UI] Startup Engine service may experience delay when unreachable nodes are selected for starting the service on. (EN-4949)
    • [CE HTML5 UI] EULA accept is required all the time when Engine service is stopped (even if previously accepted). (EN-4958)

    Known Issues

    Engine Management Service & Engine

    • With SQL Plugin + SQL 2014 & In-Memory Tables may result in an OFFLINE DB state during "In Recovery" state (EN-329). 
    • Trying to add a 6.7 pair/trio in EMS UI protected servers list fails with an error. 
      Workaround: Restart Engine Web Services on the active server. (EN-1354)
    • Virtual Bytes rule triggered at every check (EN-859).
    • The Engine Management Service MSI repair mode fails to operate properly (EN-1389).
    • If the Engine is running, a new license is added to the list of licenses. If the Engine is stopped, it replaces the list of licenses (EN-902).
    • [WS2022 only]: Sometimes file are not deleted on passive when they're being deleted on active. This may cause orphan files presence on passive nodes. (EN-6346). Workarounds:
      • Run Orphan Files Check on each of the passive nodes
      • Restart replication (stop/start)
      • Restart Engine service

    Install/Uninstall

    Administration

    • LogCollector - The process was terminated due to an unhandled exception (EN-2011).

    Applies To

    Continuity Engine v19


      • Related Articles

      • Neverfail Continuity Engine v10 Release Notes

        Summary The following information applies to the v10 release of Neverfail Continuity Engine. Neverfail Continuity Engine 10.1 This hotfix release supersedes Neverfail Continuity Engine v10.0. Fixes [EN-6024]: [LogCollector] - LogCollector crashes ...

      • Neverfail Continuity Engine v12 Release Notes

        Summary The following information applies to the v12 release of Neverfail Continuity Engine. Neverfail Continuity Engine 12.1 This point release supersedes Neverfail Continuity Engine v12.0. What's New Continuity Engine CLI Installer EMS bundles a ...

      • Neverfail Continuity Engine v11 Release Notes

        Summary The following information applies to the v11 release of Neverfail Continuity Engine. Neverfail Continuity Engine 11 What's New Automated Split-Brain Avoidance Configuration Continuity Engine 11 monitors the management identity configuration ...

      • Neverfail Continuity Engine 13 Release Notes

        Summary The following information applies to the v13 release of Continuity Engine. Continuity Engine 13 This point release supersedes Continuity Engine v12.1. What's New Better User Experience Subscription's Payment Status Exposed in EMS UI Starting ...

      • Neverfail IT Continuity Engine v8.0 - Release Notes

        Summary This Knowledge base article provides information about this specific release of Neverfail IT Continuity Engine v8.0 More Information Supporting Documentation A listing of technical documents supporting this version of Neverfail IT Continuity ...