Summary

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

What's New

EMS Alerting based on Managed Server Telemetry

1. The first chapter in unlocking advanced monitoring and alerting is to enable our new telemetry service, which will seamlessly extract relevant information about events happening on the Engine nodes.
   
2. v16 adds more to this feature by unlocking the possibility of uploading-via-EMS the telemetry data  data for a deployment not managed via Engine Management Service. 
3. 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.
   

Better User Experience

EMS API documentation

1. v16 brings end-user enablement for documenting and usage of Engine APIs. 
2. Frequently used APIs as well as the Procedure for enabling, capturing and viewing (Swagger) EMS API documentation are detailed in Engine Management Service API.
   

Systray App Enhancements

Offline Licensing Management via EMS

1. Self-service offline licensing: customers may claim license keys directly from Engine Management Service for deployments which are not managed via EMS.
   
2. 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

1. EMS UI alerts whenever a newer version is generally available, along with download link and release highlights.

Available Plugins Visibility Update

1. Bundled plugins list is linked directly from Engine Management Service UI support section. Engine plugin offers out-of-the-box automated protection for client applications (specific versions). 

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

OPSWAT MetaDefender Managed File Transfer Plugin v201.5.1

1. OPSWAT MetaDefender Managed File Transfer Plugin provides protection and proactively monitors MetaDefender MFT environment’s configuration data, services, and application data files.
2. Support for OPSWAT MetaDefender Managed File Transfer v3.6.x, 3.7.x., cloned or independent-identity architecture.

Clever Devices CleverCAD Plugin v201.5.3

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 v3 

Engine command-line installer was improved in version bundled with CE16:

1. Engine WFP packet filtering preferences are preserved across upgrade.
   
2. Extended Attributes replication preferences are being transformed across upgrade, so that files having this features are replicated and kept syncronized by default.   
   

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.

CLI Service Manager v1 

1. Engine command-lineservice manager for starting/stopping Engine protected services (with or without dependencies).
2. Designed as a standalone helper-tool to be used in case of server maintenance/recovery when user wants to start stop protected services and Engine service is stopped.

More Secure

Read the updated Security Policy Regarding Neverfail Continuity Engine.

OpenJDK and Apache Tomcat version updated to latest

• Continuity Engine's objective is to keep your systems up, running, protected, and safe. Having the latest security updates, fixes and patches for the used open-source software is critical.
  • v16.0 is updated to Azul Zulu 8.82.0.21-CA-win64 (JDK version 8u432-b06). 
  • v16.0 is updated to Apache Tomcat 9.0.97. Following link lists all security vulnerabilities fixed in released versions of Apache Tomcat.
    

HSTS Enablement

• HTTP Strict-Transport-Security (HSTS) is now enabled by default in Continuity Engine Management Service.
  
• Supported older versions of Engine may enable it as described in  How to enable HTTP Strict-Transport-Security (HSTS) in Continuity Engine Management Service

New Supported Versions

New or Updated Plugins

1. Clever Devices CleverCAD Plugin: protection for Clever Devices CleverCAD v9.9 and v10.xx
   
2. OPSWAT MetaDefender Managed File Transfer Plugin: support for MD MFT 3.6.x, 3.7.x. deployed in cloned or independent identity architecture

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 

Software Subscription Cancelation

1. End-User License-Subscription Agrement changes are summarized in the below section extracted from Neverfail End-User Software Subscription License Agreement.
   

Automatic Software Subscription Cancelation. Neverfail reserves the right to automatically cancel any Software Subscription if the Subscriber does not pay for either a monthly or a yearly subscription renewal for it within maximum 6 months past the Software Subscription’s end date. A Canceled Software Subscription is considered end of life, hence will not allow to be reactivated, renewed, or extended. If the subscriber will later want to continue the software usage, a new Software Subscription must be purchased to re-enable the subscriber with the Right of Use for the Licensed Software.

Software Subscription Payment Awareness Improvements

1. Improved in v16.0, the software subscription licensing mechanism is changed to be aware of software subscription's payment status. The changes are summarized in the below section extracted from Neverfail End-User Software Subscription License Agreement.

Term Software Subscription is ready to be consumed immediately upon fulfilment. Depending on the payment status, the right to use may or may not be limited a follows: (a) if the payment is pending when software subscription is being activated (consumed), a limited forty-five (45) days license key counted from the term software subscription start date will be generated; as soon as the payment is confirmed, the full term software subscription period is unlocked; relicensing with a full term license key will be performed automatically for online licensing; (b) if the payment is confirmed when software subscription is being activated (consumed) a full term license key will be generated. Similar payment status usability rules apply also in the case of license term software subscription renewal.

1. v16.0 licensing model is built on top of v9.0 model which transitioned Engine from a perpetual model to a software subscription term and rental model. Engine Licensing Service (ELS) enables call-home features that power our software subscription based licensing. The new cloud 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 16 Management Service is compatible with older versions (i.e. EMS 16.0 manages correctly CE 12/13/14/15). 

1. If I upgrade to Continuity Engine 16, 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 versions to Continuity Engine 16? Yes, the upgrade wizard is still supported. Keep in mind that Continuity Engine versions 6.7, 7.x, 8.x, 9.x, 10, 11 are currently End-of-Life (EOL). To ensure organization continued support, 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 v14. And evenly important, your systems will be more exposed to cyberattacks. For example:
   


1. CEv11.0
   
1. misses all the Java OpenJDK security fixes released between July 2023 (8u382-b05) and October 2024 (8u432-b06).
2. misses all the Apache Tomcat security fixes released between April 2023 (Tomcat 9.0.74) and October 2024 (9.0.97).

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: Automation, Transfer, Mobile Servers, Analytics Agent
    
  • MySQL Server 5.x, 8.x
    
  • 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
    
• Additional supported plugins
  
  • Neverfail CE for Business Application
    

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:

• Exchange Server Plugin (latest version released with v8.5 U6)
  
  • ForeFront (latest version released with v8.5)
    
  • Symantec Mail Security (latest version released with v8.5 U4) 
    
• File Server Plugin (latest version released with v8.5)
  
• IIS Plugin (latest version released with v8.5 U5) 
  
• SharePoint Server Plugin (latest version released with v8.5 U5)
  
  • Office Online Server (latest version released with v8.5 U3) 
    
• SQL Server Plugin (new in v15) 
  
• MySQL Server Plugin (latest version released with v8.5 U6) 
  
• vCenter Server Plugin 
  
• System Plugin  (latest version released with with v12) 
  
• vSphere Plugins Suite - support for vSphere 6.7 and later (latest version released with v8.5 U4)
  
  • VMware vCenter Server 
    
  • VMware Platform Services Controller 
    
  • VMware Authentication Proxy 6.0 
    
  • VMware Update Manager 
    
  • VMware vPostgres 
    
  • VMware Composer 5.x, 6.x and 7.x 
    
• Progress MOVEit Plugins Suite  (latest version released with v12)
  
  • MOVEit Automation Server  
    
  • MOVEit Transfer Server  
    
  • MOVEit Mobile Server 
    
  • MOVEit Analytics Agent 
    
• SolarWinds Orion Network Management Plugin (latest version released with v8.5)
  
• Mitel MiContact Center Business Plugin (latest version released with v13) 
  
• Atlassian Confluence Plugin (latest version released v8.5 with U3) 
  
• Atlassian Jira Plugin (latest version released with v8.5 U3) 
  
• Oracle Database Plugin (latest version released with v9.0) 
  
  • Oracle Management Agent Plugin (latest version released with v8.5 U4) 
    
• PostgreSQL Plugin (new in v8.5 U3) 
  
• Veeam Backup & Replication 9.5 Plugins Suite (latest version released with v8.5 U3)
  
  • Veeam Backup & Replication
    
  • Veeam Backup Enterprise Manager
    
  • Veeam Availability Console
    
  • Veeam Backup Proxy
    
  • Veeam WAN Accelerator
    
  • Veeam Cloud Gateway  
    
• vSphere Integration Plugin (latest version released with v8.5 U4) 
  
• System Center Operations Manager Plugin (latest version released with v8.5 U5)
  
• Apache Tomcat Plugin (new in v15)
  
• OpenText CX-E Voice Plugin (latest version released with v12)
  
• Clever Devices CleverCAD Plugin (new in v16)
• Mitel MiContact Center Enterprise Plugin (latest version released with v13)
  
• Automated Logic WebCTRL Plugin (new in v14)
  
• Hyper-V Plugin (latest version released with v13)
  
• Mitel BluStar Plugin (new in v14)
  
• Schneider Electric Security Expert Plugin (new in v14.1)
  
• OPSWAT MetaDefender Managed File Transfer Plugin (new in v15)

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-6549]: Changes needed in Engine webservices due to Tomcat 9.0 refactoring.

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

• Continuity Engine Secondary server deployment hangs at: Waiting for Secondary VM to complete auto configuration... Workaround: Continuity Engine Secondary server deployment hangs at: Waiting for Secondary VM to complete auto configuration...   (EN-3380)
  
• Engine 8.5 (or newer) re-clone P->V doesn't fully reconfigure networks card on clone target (EN-3352)
  
• DHCP-set gateway and DNS servers present on Secondary-HA post-cloning/configuration (EN-1996).
  
• Continuity Engine fails to uninstall on the Tertiary server (EN-1589).
  

Administration

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

Applies To

Continuity Engine v16