Neverfail Continuity Engine 2021 (v9.0) - Release Notes

Neverfail Continuity Engine 2021 (v9.0) - Release Notes

Summary

This knowledge base article provides information about the v9.0 release of Neverfail Continuity Engine and all subsequent updates to this release.

Neverfail Continuity Engine 2021 (v9.0) Update 4

The following information applies to the fourth update of the Neverfail Continuity Engine version 9.0 (Update 4). This information builds upon the release notes for Neverfail Continuity Engine v9.0 Update 3.

What's new

Engine Licensing Server integration enhancements

  1. CE Licensing server: License authorization transformation mechanism
  2. CE Licensing server: License authorization adaptative start date support
  3. CE Management Service: Automated online relicensing for the transformed license authorizations
  4. Updated Neverfail End-User License Agreement

OpenJDK and Apache Tomcat versions

  1. Neverfail Continuity Engine 9.0 is updated to OpenJDK 1.8.0.332. 
  2. Neverfail Continuity Engine 9.0 is updated to Apache Tomcat 9.0.64. Following link lists all security vulnerabilities fixed in released versions of Apache Tomcat.

New or Updated Plugins

  1. Neverfail for Progress MOVEit 2022 Plugins suite: added support for Progress MOVEit 2022.0 suite of products: Automation Server, Transfer Server, Mobile Server, Analytics Agent; Backwards compatible support for MOVEit 2021, MOVEit 2020, MOVEit Central 8.0/8.1 and DMZ 8.1
  2. Neverfail for Neverfail for OpenText CX-E Voice: support for OpenText CX-E Voice (formerly xMedius/AVST CX-E/CallXpress) up to version 22.4.

Changed/Fixed Issues

  1. [EN-5607] - License Validator  simple date format parsing issue for two digits year format (yy/MM/dd)
  2. [EN-5731] - NFClient event logs are not saved in the correct path. They are saved in "C:\R2\" instead.

Neverfail Continuity Engine 2021 (v9.0) Update 3

The following information applies to the third update of the Neverfail Continuity Engine version 9.0 (Update 3). This information builds upon the release notes for Neverfail Continuity Engine v9.0 Update 2.

What's new

Upgraded Apache Log4j 2.17 version

  1. Apache Log4j 2 is an upgrade to Log4j that provides significant improvements and fixes to all known security vulnerabilities present in older Log4j versions.

Engine Licensing Server integration enhancements

  1. "Killswitch" mechanism enabling license authorization termination and license key expiration 
  2. Support for Perpetual Limited 10 years license encoding/decoding
  3. Flexible license authorization patching - enables authorization ownership change (to a different customer)
  4. Automated Licensing optimizations
  5. Updated Neverfail End-User License Agreement

Support for Microsoft Windows Server 2022

  1. Added support for Continuity Engine deployments on Windows Server 2022 Standard / Datacenter.
  2. Validated support for Neverfail System Plug-in, Neverfail for IIS, Neverfail for File Server with Windows Server 2022 features

OpenJDK and Apache Tomcat versions

  1. Neverfail Continuity Engine 9.0 is updated to OpenJDK 1.8.0.322. 
  2. Neverfail Continuity Engine 9.0 is updated to Apache Tomcat 9.0.59. Following link lists all security vulnerabilities fixed in released versions of Apache Tomcat.

New or Updated Plugins

  1. Neverfail for Neverfail for OpenText CX-E Voice: support for OpenText CX-E Voice (formerly xMedius/AVST CX-E/CallXpress) up to version 22.1.

Changed/Fixed Issues

  1. [EN-3380] - [EMS]: Add probe for checking Primary VM MAC address configuration and veto if Manual (to avoid Secondary VM post cloning auto-configuration failure because of identical MAC addresses on Primary and Secondary)
  2. [EN-5253] - [Known limitation]: License keys with expiry date starting from year 2032 are not generated correctly (they appear corrupted when decoding)
  3. [EN-5340] - [EMS websvc]: Automated relicensing task is interrupted prematurely if activation key not found for a server. As a consequence some license expiring Engine servers may not be relicensed (those following after the faulty configured server)
  4. [EN-5621] - [Autorelicensing task]: ApplyLicenseTask steps exceptions interrupt relicense scheduler
  5. [EN-5609] - [LMS]: Notify course(s) registered users about their course completion status
  6. [EN-5599] - [EMS UI]: Server> Server details page load fails with "× TypeError: Cannot read properties of undefined (reading 'failoverTargets')"
  7. [EN-5623] - [EMS UI]: Global search> Pressing enter while in global search makes UI completely white

Neverfail Continuity Engine 2021 (v9.0) Update 2

The following information applies to the second update of the Neverfail Continuity Engine version 9.0 (Update 2). This information builds upon the release notes for Neverfail Continuity Engine v9.0 Update 1.

What's new

Global/centralized mail settings configuration for alerting

  1. Enables the central configuration of mail server settings from Neverfail Continuity Management Service: the globally configured parameters may be pushed to all the Continuity Engine v9.0U2 managed servers.

Automated (re)licensing

  1. The automated (re)licensing mechanism stores the licensing data edited by the end-customer in Continuity Engine Management Service License Server wizard, and uses it during the Continuity Engine license renewal process: license key is automatically regenerated and applied on the managed Continuity Engine server within 10 days before license authorization expiration. 

License expiration alerting

  1. Predefined alert triggers aligned with term license key pre-expiration period.

Centralized service recovery action configuration 

  1. Enables the user to configure globally the service recovery actions for all the protected services.

Engine Licensing Server integration enhancements for Term and Rental subscriptions

  1. Term and rental licensing and renewal service enhancements. Read Continuity Engine Licensing Model for more details.

OpenJDK and Apache Tomcat versions

  1. Neverfail Continuity Engine 9.0 is updated to OpenJDK 1.8.0.302. 
  2. Neverfail Continuity Engine 9.0 is updated to Apache Tomcat 9.0.52. Following link lists all security vulnerabilities fixed in released versions of Apache Tomcat.

New or Updated Plugins

  1. Neverfail for Progress MOVEit 2021 Plugins suite: added support for Progress MOVEit 2021.0 suite of products: Automation Server, Transfer Server, Mobile Server, Analytics Agent; Backwards compatible support for MOVEit 2020, MOVEit Central 8.0/8.1 and DMZ 8.1
  2. Neverfail for Hyper-V: support for Microsoft Hyper-V Server Role installed on standalone (non-clustered) Windows Server 2019/2016 Standard and Datacenter (Desktop Experience)
  3. Neverfail for Neverfail for OpenText CX-E Voice: support for OpenText CX-E Voice (formerly xMedius/AVST CX-E/CallXpress) up to version 21.2
  4. Neverfail for vSphere Integration: added support for VMware vCenter Server 7.0

VMware vCenter Server 7.0 and VMware vCenter Converter 6.2 Support

  1. Neverfail Engine Management Service API support for deployment using the latest versions of VMware vCenter Server 7.0 and VMware vCenter Converter 6.2.
  2. Neverfail for vSphere Integration Plug-in support for interoping with the latest versions of VMware vCenter Server 7.0.

Neverfail Training - updated eLearning Center

Neverfail eLearning Center platform is updated for Continuity Engine v9.0. Following training courses are available:
  1. Neverfail Continuity Engine Certified Administrator 2021
  2. Neverfail Continuity Engine Implementation Engineer 2021
  3. Neverfail Continuity Engine Sales Professional 2021
  4. Neverfail Sales Collateral
  5. Marketing Certification Course
  6. Neverfail Marketing Collateral

Changed/Fixed Issues

  1. [EN-5391] - [Tomcat security] Engine's default Tomcat TLS version should enforce at least TLS 1.2.
  2. [EN-5315] - [Tomcat security]: Apply OWASP recommendation for securing Tomcat.
  3. [EN-5264] - [Websvc/UI]: License keys list fetched incompletely in EMS.
  4. [EN-5260] - [EMS UI]: Enable start/stop actions for applications being in unmanaged/unmonitored state.
  5. [EN-4703] - [Continuity Engine install validation]: Changed validation from Error to Warning for "Failed to determine the number of Free System Page Table Entries…"
  6. [EN-3571] - [Continuity Engine install validation]: Removed probe validation for "Acronis Scheduler2 service is running on target"
  7. [EN-5445] - [EMS UI]: Server> Alerts> Mail settings > Username/Password should be greyed out when using global mail config is enabled
  8. [EN-5431] - [EMS UI]: License server> Count activations> ES and Portuguese caption text doesn't fit
  9. [EN-5395] - [EMS UI]: Server> Alerts > Configure alerts default template is not persisted in edit mode.
  10. [EN-5346] - [EMS UI]: Server> Alerts> Mail Settings> Outgoing mail server validation is too strict.
  11. [EN-5454] - [EMS UI]: Accessing /support/help/ems-user-interface page when localized in zh-CN or zh-HK fails with "Cannot read property '0' of undefined..."

Neverfail Continuity Engine 2021 (v9.0) Update 1

The following information applies to the first update of the Neverfail Continuity Engine version 9.0 (Update 1). This information builds upon the release notes for Neverfail Continuity Engine v9.0.

What's new

Features

  1. [EN-4938] - Dark theme UI for Continuity Engine Management Service
    1. selectable from Light | Dark toggle exposed in the EMS UI's top bar
  2. [EN-5204] - Portuguese - Brazilian localization for Continuity Engine Management Service UI
  3. [EN-3628] - Enable/Disable option for injecting Continuity Engine tasks and events in VMware vSphere Client
    1. configurable via EMS UI's Settings> Configure vCenter Server> I want to view Engine tasks and events in vSphere Client
  4. [EN-5200] - Engine Management Service UI: Start/Stop replication actions offer now options for starting and stopping the protected applications
  5. [EN-3025] - Test Alert Reporting exposed in Continuity Engine Management Service UI
    1. available in EMS UI's Protected server's> Alerts view
  6. [EN-2958] - EMS UI: Add standby server> Allow Engine deployment wizard for DR instance to override DNS Update credentials requirement

Patch Management Solutions / Technologies supported by Neverfail Continuity Engine's Passive Node Management feature

Following Patch Management Solutions / Technologies were validated as supported for interoping with Neverfail Continuity Engine's Passive Node Management feature: 
  1. Ivanti Endpoint Manager
Following document is listing 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 Node Management feature: Patch Management Solutions / Technologies supported by Neverfail Continuity Engine's Passive Node Management feature

Documentation

  • [EN-5205] - Portuguese - Brazilian localization for Continuity Engine Management Service Help

Changed/Fixed Issues

  1. [EN-5144] - EMS UI: Send product feedback fails with internal server error 500
  2. [EN-5201] - EMS UI: Long EMS hostnames and logged-on user names are not displayed user friendly
  3. [EN-5208] - EMS UI: Server name not displayed for Data, Tasks, Rules, Shadows, Alerts, Monitoring
  4. [EN-5237] - EMS UI: Pagination is not refreshed correctly when changing filtering criteria
  5. [EN-5179] - EMS UI: Protected servers list> Type: Double tooltip when hovering over cluster type icon
  6. [EN-4920] - EMS UI: IP-address text box 3-dot-format - add paste from clipboard feature
  7. [EN-5155] - Remove Engine Flash UI
  8. [EN-5249] - EMS UI: Cannot define inclusion filters when no inclusion filter is already defined


Neverfail Continuity Engine 2021 (v9.0)

The following information applies to the v9.0 release of Neverfail Continuity Engine.

What's New

Engine Management Service HTML5 based UI and new user experience

  1. all features from Adobe Flash based UI are now ported and new additional features were added
  2. dashboard, server list with aggregated health status
  3. virtual machine inventory view
  4. simplified server protection (directly from inventory)
  5. unified deployment flow for standby servers:
    1. add a new standby server(s) for HA, DR and Tertiary
    2. reconstruct broken cluster if a standby server(s) is missing or corrupted
    3. reconfigure the cluster configuration from a HA or DR pair to Tertiary including where its hosted
  6. new summary status of protected server including Management Name configuration
  7. visual replication chain representation for the protected server
  8. protected applications configuration feature
  9. new graph representation of protected server data statistics (traffic, queues, WAN compression)
  10. fast-check, orphaned files and control shutdown configuration features
  11. disable all rules feature or sponsor rules within the rules tab
  12. access to how-to video tutorials from EMS UI

Web Services changes

  1. new functionality for enabling new HTML5 UI and new licensing model integration
  2. APIs that capture proprietary and OEM sponsor plugins application information into Engine shared data model to be synchronized with the Engine License Service (ELS)
  3. EMS telemetry feature: fetches managed servers configuration data and sends it daily to ELS

Server Monitoring

This new Server Protection view allows direct monitoring and configuration of key HA/DR settings from the EMS UI: automated failover, data loss avoidance, split brain avoidance, false failover avoidance and active server isolation.

EMS UI Internationalization

The new internationalization framework enables easy localization of EMS UI to a specific language. Neverfail EMS UI and bundled online help are available in the following languages:
  1. English
  2. Chinese Simplified
  3. Chinese Traditional (Hong Kong)
  4. Spanish
  5. Romanian

Engine Licensing Server integration

Neverfail Continuity Engine 2021 integrates directly with a new (SaaS) term and rental licensing service. Read Continuity Engine Licensing Model for more details.

Google Cloud Platform Support

Neverfail Continuity Engine supports deployment on Google Cloud Platform: 
  1. read How to install Neverfail Continuity Engine on Google Cloud Platform for more information on how to perform a GCP-to-GCP installation or on-premises-to-GCP passive node migration.

Microsoft Windows 10 Support

This new feature enables HA/DR for Windows 10 IoT/Enterprise ecosystems. Additional considerations in Additional requirements when installing Neverfail Continuity Engine on Windows 10.

OpenJDK and Apache Tomcat versions

  1. Neverfail Continuity Engine 9.0 is updated to OpenJDK 1.8.0.275. 
  2. Neverfail Continuity Engine 9.0 is updated to Apache Tomcat 7.0.107. Following link lists all security vulnerabilities fixed in released versions of Apache Tomcat.

New Software Licensing Model and Upgrade Notes

New in Continuity Engine 2021 is a new licensing model that transitions Engine from a perpetual model to a (SaaS) term and rental model. A new Engine Licensing Service (ELS) was introduced to enable 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.

New or Updated Plugins

  • Neverfail for Progress MOVEit Plugins suite: support for Progress MOVEit 2020.1 suite of products: Automation Server, Transfer Server, Mobile Server, Analytics Agent; Backwards compatible support for MOVEit Central 8.0/8.1 and DMZ 8.1
  • Neverfail for Oracle Database Plugin: added support for Oracle Database 11g
  • Neverfail for Apache Tomcat Plugin: new plugin adding support for Apache Tomcat 9.x and 8.x servers

Changed Features

  1. License server procedure is changed to integrate with the new term and rental licensing service. 
  2. Existing license keys are removed during the licensing process if a new license key is successfully applied.
  3. Bundled SCOPE Data Collector v5.4.0 has upload, download, upgrade check and support requests features disabled.

VMware vCenter Server 7.0 and VMware vCenter Converter 6.2 Support

  1. Neverfail Engine Management Service API Support for Deployment Using the Latest Versions of VMware vCenter Server 7.0 and VMware vCenter Converter 6.2.
  2. Neverfail for vSphere Integration Plug-in Support for Interoping with the Latest Versions of VMware vCenter Server 7.0 is coming soon.

Backward Compatibility

Neverfail Continuity Engine 2021 (v9.0) Management Service is compatible with older versions of Continuity Engine (i.e. EMS 9.0 manages correctly CE 6.x/7/x/8.x). However, many of the new features are not supported thus cannot be used in this context. For example, here are the new v9.0 features not supported with CE v8.x:
  1. Server Monitoring features. This is new in Engine 9.0 and exposes Failover/ Split-brain avoidance / Isolation / Network Monitoring functionality
  2. Access to unified deployment workflow which includes: Add | Reconstruct | Reconfigure Standby Servers
  3. Access to the new licensing service (ELS), hence to online licensing process

FAQ

  1. 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 2021. However, you will get popup messages asking you to upgrade.
  2. If I upgrade to Continuity Engine 2021, 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.
  3. Can I upgrade using the Upgrade Wizard from 6.7 to Continuity Engine 2021? Yes, the upgrade wizard is still supported. Keep in mind that Continuity Engine 6.7 and 7.0 are currently End-of-Life (EOL). To ensure organization continued support, we would encourage you to upgrade to the latest version.
  4. Will Continuity Engine 8.0 and 8.5 EOL soon? Continuity Engine 8.0 will most likely EOL sometime in 2021 but v8.5 will be support for the foreseeable future.
  5. 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 2021.
  6. Can I stay on Engine 8.5 EMS? Yes, but it will not be supported as of January 1st, 2021 due to Adobe Flash EOL.

Patch Management Solutions / Technologies supported by Neverfail Continuity Engine's Passive Node Management

Following document is listing 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 Node Management feature: Patch Management Solutions / Technologies supported by Neverfail Continuity Engine's Passive Node Management

Installation, Upgrade and Usage Documentation

Restyled and more focused Neverfail Continuity Engine Installation, Usage and Administrators guides.

Supported Deployment Infrastructure

  • Server roles/applications for which protection will be installed automatically are:
    • SQL Server 2008 SP4, SQL Server 2008 R2 up to SP3, SQL Server 2012 up to SP4, SQL Server 2014 up to SP3, SQL Server 2016 SP2, SQL Server 2017, SQL Server 2019
    • 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 2019
    • Internet Information Server including v10 on Windows Server 2019
    • 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.0: Automation, Transfer, Mobile Servers, Analytics Agent
    • MySQL Server 5.x, 8.x
    • MiContact Center Server v9.0, MiContact Center Business 9.3 
    • 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, 2012, 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
  • Additional supported plug-ins
    • Neverfail CE for Business Application

Neverfail Engine Plug-ins

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:

Plugin Installation

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.

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 Neverfail Continuity Engine Cloning and Recloning limitations: disconnected Engine cluster  (EN-3354)
  • Recloning limitations when Neverfail Engine passive nodes when static routes are configured: these are listed in Neverfail Continuity Engine Recloning limitations when static routes are configured  (EN-3355)
  • Neverfail 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).
  • The Neverfail Continuity Engine .msi installer package is sometimes detected as having untrusted publishers (EN-969).
  • The FileServer plug-in bundled with Neverfail 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 8.5 (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
  • [CE9.0 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)
  • [CE9.0 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)
  • [CE9.0 HTML5 UI] Data traffic value in serverlist API is not always accurate. (EN-4859)
  • [CE9.0 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)
  • [CE9.0 HTML5 UI] Startup Engine service may experience delay when unreachable nodes are selected for starting the service on. (EN-4949)
  • [CE9.0 HTML5 UI] EULA accept is required all the time when Engine service is stopped (even if previously accepted). (EN-4958

Fixed Issues

  • [Websvc]: Shadows> Configure shadows POST has no effect when "isEnabled":false. Consequence: you cannot configure shadow location when automatic shadow is disabled. (EN-4832)
  • [Rollback manager]: Invalid path configured by default for shadow location: C:\PROGRAM FILES\NEVERFAIL\\R2\SHADOW\ (EN-4834)
  • [EMS UI]: Internet explorer shows old Client version after upgrade. (EN-3223)
  • [EMS-UI] - Add file filters: autocomplete patterns not working for sub-folders if root folder string contains unicode chars. (EN-3246)
  • Latched Rules should be displayed in the EMS UI with only one "On Failure Action" drop-down field (EN-2023).
  • Downloading the Advanced Client from EMS silently fails in Chrome (EN-1836).
  • Neverfail Continuity Engine does not allow a user to create a VM (Secondary) server when only a Primary and Tertiary server are present (EN-508). 
  • If the targets for network monitoring are not configured, the network status shows -1 missed pings (EN-704).
  • EMS> Uninstall Engine wizard hangs at "Initial checks succeeded. Performing further validation..". Cause: A Subsequent uninstallation attempt is made from EMS after a previous failed uninstallation wasn't acknowledged (by clicking OK...) from the EMS> Status. Workaround: Restart Neverfail Engine Management Web Services on the EMS Server then login again to Engine Management Services console. (EN-3859)

Known Issues

Engine Management Service

  • With SQL Plug-in + 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 Neverfail 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).

Install/Uninstall

Administration

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

Applies To

Neverfail Continuity Engine v9.0


    • 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 ...