Automated Split-Brain Avoidance Configuration Improvements

1. Split-Brain Avoidance auto-configuration task will execute only if automated failover is enabled.
2. Continuity Engine 12 monitors the management identity configuration and will automatically configure a set of ping routes which will be used to avoid potential split-brain situations when failover is initiated as a consequence of channel loss. The automatic configuration of split-brain avoidance requires a minimum of one management IP address defined on each Primary and Secondary nodes.  Split-brain avoidance works by pinging from the passive server to the active server across the client network. If the active server responds, the passive does not failover, even if the channel connection is lost. Ping routing configuration means defining ping routes between Primary and Secondary instances using existing/defined management IP addresses.
   
3. This feature is enabled by the updated version of Neverfail System Plug-in bundled with Continuity Engine 12.

SMBv1 Detection

More Secure

Core Security Enhancements

• Various security and code quality improvements to some of the core components. 

• Encryption updated to latest strongest standard commercially available today.

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.

  • Continuity Engine 12 is updated to Azul Zulu 8.74.0.17 (JDK version 8u392-b08). 

  • Neverfail Continuity Engine 11 is updated to Apache Tomcat 9.0.82. Following link lists all security vulnerabilities fixed in released versions of Apache Tomcat.

Continuity Engine CLI Installer

Better User Experience

UI Fixes

1. [EN-6202]: Unsetting ISC ping routes via SBA leaves null value in properties which is seen as a leftover in UI
2. [EN-6163]: Autofill option for user/password in Password Manager
3. [EN-6134]: Protect server> Validating install > Wrong Acknowledge logic when multiple Warnings
4. [EN-6127]: Auto recloning> Ready to complete> Empty host. Wasn't changed to get target host from compute resource name
5. [EN-6013]: Protected Server> Monitoring> Application configuration> Reset rule trigger count after: Value is being automatically reset/refreshed with the one already configured
6. [EN-5967]: Some plugin rules have optional parameters which are considered mandatory in UI modal automatically reset/refreshed with the one already configured

Access to Continuity Engine Utils-Addon Repository

Bundled Plugins Visibility

• The set all of the bundled plugins which offer out-of-the-box automated protection for client applications (specific versions) is linked directly from Engine Management Service UI support section
  

Google Cloud Platform Support Enhancements - Solution Pack for streamlining hybrid deployments

• 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
  

New Supported Versions

New or Updated Plugins

• Neverfail System Plug-in (new version): Split-brain avoidance autoconfiguration improvements. SMBv1 detection. And more.

• Neverfail for Mitel MiContact Center Business (new version): support for MiContact Center Business R10/SIP; Elasticsearch rule fix.

• Neverfail for Progress MOVEit 2023 Plug-ins Suite (new version): support for MOVEit 2023.0

• Neverfail for Neverfail for OpenText CX-E Voice Plugin Version 201.23.4 (new version): support for CX-E Voice version 23.4

• Neverfail for Clever Devices CleverCAD (new): protection for Clever Devices CleverCAD v9.9 and v10.15
  

• Neverfail for Mitel MiContact Center Enterprise (new): protection for Mitel MiContact Center Enterprise 9.6

VMware vCenter Server and VMware vCenter Converter Support

Licensing Updates 

1. Improved in Continuity Engine v12, 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. Continuity Engine 12 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

Neverfail Continuity Engine 12 Management Service is compatible with older versions of Continuity Engine (i.e. EMS 12.0 manages correctly CE 9.x/10.x/11.x). 

1. If I upgrade to Continuity Engine 12, 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 12? 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, 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 v12. And evenly important, your systems will be more exposed to cyberattacks. For example:
   


1. CEv9.0
   
1. misses all the security fixes between OpenJDK 8u332-b09 (April 2022) and 8u382-b05 (July 2023)
2. misses all the security fixes between Tomcat 9.0.64 (May 2022) and 9.0.78 (July 2023)