Installing Neverfail Engine Management Service and Continuity Engine Basics
Welcome to the Neverfail Continuity Engine e-learning sessions! This article will introduce you to the process of installing Neverfail Continuity Engine in a production environment. Note the simple straightforward process used to install the product. Following this process will ensure success of your Neverfail Continuity Engine installation. So let's get started!
Learning objectives
At the completion of this session you should be able to recall preinstallation checks before installing Neverfail Continuity Engine software, identify in sequence the steps to install Neverfail Continuity Engine and recall the node deployment process.
Installing Neverfail Continuity Engine
Before beginning your product installation, complete the SCOPE process to ensure the highest likelihood of installation success. You can find out more information about the SCOPE process in the Neverfail Support Knowledge Base. Having used the SCOPE reports, change recommendations to prepare your service for installation. The next step is to install the software. Click each item to find out more.
Basic checks
Obtain your Neverfail Continuity Engine license authorization information from Neverfail. More details about how licensing works are presented in Continuity Engine - Subscription Licensing Model article.
Verify the operability of the protected applications. This ensures that the server you're cloning is indeed operational.
Using the Neverfail Continuity Engine preinstall checklist, verify that all prerequisites have been met.
Download software
To install Neverfail Continuity Engine go to the Neverfail Support and download the Neverfail Continuity Engine software. Always check the Neverfail Support download section for the latest versions before installing Neverfail Continuity Engine. Updates are posted on the download section as soon as they are released.
Install the Neverfail Engine Management Service
Installation of Neverfail Continuity Engine begins with installation of the Engine Management Service (EMS) component. EMS is installed as a separate application on any server running Windows server 2008 R2 64-bit or later, with connectivity to a VMware vCenter Server 5.1 or later, or a desktop edition of Windows operating system 7, 8.x or 10 and is used to prepare and deploy Neverfail Continuity Engine on the primary, secondary and, if installed, tertiary servers. Additionally, the Engine Management Service operates as a central point of control providing a single pane of glass with which to configure and manage your Neverfail Continuity Engine clusters and perform day-to-day operations.
Additionally, the Engine Management Service operates as a central point of control, providing a single pane of glass with which to configure and manage your Neverfail Continuity Engine clusters and perform day-to-day operations.
Deploy the primary server
The process for installing Neverfail Continuity Engine software is relatively simple and straightforward. Using Neverfail Engine Management Service you deploy Neverfail Continuity Engine on to the primary server (Protect Server). EMS probes the server to perform a last minute environmental check and then ejects Neverfail Continuity Engine onto the server. Each Neverfail Continuity Engine cluster requires a distinct license key, which is generated automatically upon request, via the Neverfail Licensing Server. The license key contains information about the primary server and the product features purchased. If your primary server hardware, the main affiliation or licensed modules change, you must generate a new license key for Neverfail Continuity Engine to operate correctly.
Adding secondary and/or tertiary standby servers
The next step is to deploy the secondary server in a pair or tertiary server in a trio. Neverfail Engine Management Service using vCenter Server native cloning technology or a third party manual cloning technique creates a clone of the primary server, which is then deployed as the secondary or tertiary server.
Start Neverfail Engine and synchronize data
With IP address being configured during the installation process, the secondary and/or tertiary server is ready to operate at the completion of the deployment. After the cloning process, the Continuity Engine installation is complete and the product is ready to begin synchronizing your data. If Continuity Engine hasn't been started on the primary server, it should be started now.
Summary
During this session we discussed installing Neverfail Continuity Engine, including these processes.
- Preinstallation checks to include obtaining the licensing information and verifying the operability of the protected application.
- Performing basic checks upon the server
- Downloading the software
- Performing Engine Management Service installation and deployment of the primary server
- The standby server deployment process, including deploying the secondary and, if installed, tertiary server.
- Starting never fail engine and synchronizing data.
This knowledge, combined with knowledge gained from other never fail e-learning sessions will assist you in achieving success with your Neverfail Continuity Engine product.
Note: Detailed installation procedure is documented in Neverfail Continuity Engine 2021 Installation Guide.
Related Articles
Engine Management Service API
Summary This knowledgebase article provides information about Engine Management Service (EMS) API: frequently used API endpoints (applicable to all supported CE versions) procedure for enabling, capturing and viewing Swagger API documentation (valid ...How to enable DEBUG level logging on Neverfail Continuity Engine Management Service
Summary This Knowledgebase article provides information about how to enable DEBUG level logging on Neverfail Continuity Engine Management Service. Procedure To enable DEBUG level logging on Neverfail Continuity Engine Management Service: On the ...How to enable HTTP Strict-Transport-Security (HSTS) in Continuity Engine Management Service
Summary This Knowledgebase article provides information about how to enable HTTP Strict-Transport-Security (HSTS) in Continuity Engine Management Service The HTTP HSTS is a mechanism that allows websites to declare that they can be only accessed via ...Check Continuity Engine Server Status
This article describes how to check server status by reviewing several indicators, including the system tray icon, the Server Details page and Applications page in EMS, and Windows services. Check Server Status Learning objectives At the end of the ...Continuity Engine Product Architecture
Learning objectives At the completion of this session, you should be able to: Identify major components of the Neverfail Continuity Engine product architecture. Describe major component configuration. Identify advantages of the Neverfail Continuity ...