The following information applies to the v10 release of Neverfail Continuity Engine.
Continuity Engine installation and upgrade wizards will check starting v10 if SMBv1 is present on the target server and will veto deployment: if SMBv1 is found present, installation and upgrade of CEv10 won't be permitted due to security and interoping considerations.
For more information, please read The risks of using the deprecated SMBv1 feature on a Windows Server. Potential collisions with Continuity Engine functionality.
Procedure described in: Disabling SMB v2/v3 on a server protected by Neverfail Continuity Engine
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.
Engine Management Service Inventory view aligned with VMware vSphere Web Client hierarchy.
VMware Clusters and Resource Pools can now be selected and configured as compute resource targets when deploying Continuity Engine solution (Protect | Add Standby | Reconstruct | Reclone).
Streamlines on-premises (VMware vCenter Server) to Google Cloud deployment process (prepare, migrate and configure DR standby node)
Solution pack with documentation available here: Neverfail Continuity Engine Add-on for Hybrid Deployment to Google Cloud Platform
Neverfail Continuity Engine's Passive Management Name feature enables the ability of patching of standby passive nodes in centralized update management environment.
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 Neverfail Continuity Engine's Passive Management Name feature: Patch Management Solutions / Technologies supported by Neverfail Continuity Engine's Passive Management Name
Added support for Continuity Engine deployments on Windows Server 2022 Standard / Datacenter.
This new feature enables HA/DR for Windows 11 IoT/Enterprise ecosystems. Additional considerations in Additional requirements when installing Neverfail Continuity Engine on Windows 10 or Windows 11.
Neverfail System Plug-in: added a generic rule for checking a website / URL availability
Neverfail for Progress MOVEit: support for Progress MOVEit 2022.1 suite of products: Automation Server, Transfer Server
Neverfail for Mitel MiContact Center Business: added support for MiContact Center Business 9.5
Neverfail for Neverfail for OpenText CX-E Voice: added support for CX-E Voice version 23.2
Continuity Engine 10 licensing model is built on top of v9.0 model which transitioned Engine from a perpetual model to a (SaaS) term and rental model. Engine Licensing Service (ELS) enables call-home features that power our SaaS 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 and updated Neverfail End-User License Subscription Agreement (valid for Continuity Engine 10 and later).
The Engine Management Service provides the mechanism to securely communicate with the ELS via SSL and transfer hardware signatures to the ELS to generate licenses. Then the EMS delivers a node locked key to the EMS and it automatically assigns that license to the protected application server. Then daily it sends Neverfail telemetry information describing the current state of the license.
ELS has a fully automated process for regenerating license keys if a customer decides to continue to renew its SaaS license yearly.
Continuity Engine 10 doesn’t support anymore the legacy business model with perpetual limited licenses introduced by v9.0. The only supported model is subscription (term) based licenses. Check the new Neverfail End-User License Subscription Agreement.
Neverfail Continuity Engine 10 Management Service is compatible with older versions of Continuity Engine (i.e. EMS 10.0 manages correctly CE 6.x/7.x/8.x/9.x). However, many of the new features are not supported thus cannot be used in this context. For example, here are the new v10.0 features not supported with CE v8.x:
Server Monitoring features. This is new in Engine 9.0 and exposes Failover/ Split-brain avoidance / Isolation / Network Monitoring functionality
Access to unified deployment workflow which includes: Add | Reconstruct | Reconfigure Standby Servers
Access to the new licensing service (ELS), hence to online licensing process
Will the HTML5 UI work with my Engine 8.0/8.5 deployments for I don’t have to use FLASH? Yes, but some features as mentioned above will be disabled as they are exclusive to Continuity Engine 9.0 and later. However, you will get popup messages asking you to upgrade. However, Continuity Engine 8.x is already end of life, since January 31, 2023. For more information regarding Continuity Engine v8.x EOL Policy, please read Notice of End of Support Life for Neverfail Continuity 8.1, 8.2 and 8.5.
If I upgrade to Continuity Engine 10, will my perpetual license cease? Yes! You are accepting SaaS license. requirements outlined in the new EULA for Term and Rental. Neverfail will generate new license authorizations for your current deployment. This means you will need to pay for support to continue software operations yearly or monthly depending on the type of license. Please read carefully the Continuity Engine Licensing Model article.
Can I upgrade using the Upgrade Wizard from 6.7 to Continuity Engine 10? Yes, the upgrade wizard is still supported. Keep in mind that Continuity Engine 6.7, 7.x and 8.x are currently End-of-Life (EOL). To ensure organization continued support, we would encourage you to upgrade to the latest version.
Will Continuity Engine 9.0 EOL soon? Continuity Engine 9.0 will be EoL 30th of April, 2024. For more information regarding Continuity Engine v9.0 EOL Policy, please read Notice of End of Support Life for Neverfail Continuity 9.0.
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 v10. And evenly important, your systems will be more exposed to cyberattacks. Just as a brief "illustration" for older version cybersecurity risks compared to CEv10:
Note: Detailed information about each plug-in is contained in the plug-in's knowledgebase file that is available by clicking on the link.
Neverfail plug-ins provide protection for specific installed application configuration data, services, and application data files.
The following plug-ins are included in this release of Neverfail Continuity Engine and are installed automatically if the application is present:
Initial installations of Neverfail Continuity Engine Plug-ins must be performed using the Engine Management Service. Subsequent plug-in re-installations and upgrades may be performed using the Applications: Plug-ins tab of the Neverfail Advanced Client. However, Neverfail recommends that any subsequent plug-in repair installations or upgrades to be performed using Engine Management Service.
To manually install a Neverfail Continuity Engine Plugin follow the How to install a Neverfail Continuity Engine Plugin using Advanced Management Client procedure.
MailHost can be now set from
Neverfail Continuity Engine v10.0