Neverfail Continuity Engine Environmental Overview

Neverfail Continuity Engine Environmental Overview

Summary

This Knowledgebase article describes the environment into which Neverfail Continuity Engine can be successfully installed.  

More Information

Neverfail Continuity Engine is a versatile solution that provides multiple configurations to suit user requirements. It can be deployed in a LAN for high availability and/or across a WAN to provide disaster recovery.

During the installation process, Engine Management Service performs a variety of checks to ensure the server meets the minimum requirements for a successful installation. A critical stop or warning message appears if the server fails a check. You must resolve critical stops before you can proceed with setup. Prior to installing Neverfail Continuity Engine, select the deployment options you intend to use. The installation process will prompt you to select options throughout the procedure to create the configuration you want.

Environmental Prerequisites
 
Neverfail Continuity Engine supports the following environments listed below.
  • Supported Environments
    • Neverfail Continuity Engine is supported on the following versions of Windows Server all flavors included: Standard, Datacenter, Enterprise.
      • Windows Server 2008 R2
      • Windows Server 2012 
      • Windows Server 2012 R2
      • Windows Server 2016 
      • Windows Server 2019 
  • Unsupported Environments
    • Neverfail Continuity Engine is not supported across the following:
      •  A server where Engine Management Service is already running
      • On a server deployed as a Domain Controller (DC)
      • On a server deployed as a Global Catalog
      • On a server deployed as a DNS (Domain Name System) Server
      • On an IA-64 Itanium Platform
  • Minimal VMware Permissions Requirements:
Procedure
To integrate the Neverfail Engine Management Server (EMS) which is the centralized web console with VMware vCenter please follow the steps below:
  1. Using the VMware vSphere Client, log into vCenter Server as an Administrator.
  2. Navigate to Home > Roles.
  3. Select the Read-only role.
  4. Right-click the role and click Clone.
  5. Rename the new role. For example, Neverfail Continuity Engine.
  6. Right-click the newly cloned role and select Edit Role.
  7. Add the following privileges:
    Note: The below listed permissions are the minimal required permissions to perform an installation.
    • Datastore > Allocate Space
    • Datastore > Browse Datastore
    • Extension
    • Global > Log Event
    • Network > Assign Network
    • Resource > Assign Virtual Machine to Resource Pool
    • Resource > Migrate powered off virtual machine
    • Resource > Migrate powered on virtual machine
    • Tasks
    • Virtual Machine > Change Configuration
    • Virtual Machine > Interaction > Configure CD Media
    • Virtual Machine > Interaction > Connect Devices
    • Virtual Machine > Interaction > Power On
    • Virtual Machine > Interaction > Power Off
    • Virtual Machine > Interaction > Reset
    • Virtual Machine > Edit Inventory
    • Virtual Machine > Provisioning
    • Virtual Machine > Snapshot Management
  8. Map the vCenter Server user account configured in Engine Management Service (EMS) to the newly created Neverfail Continuity Engine role, at the vCenter Server level.
    1. Select the top level for vCenter Server, then click the Permissions tab.
    2. Right-click and select Add Permission.
    3. Add the vCenter Server EMS user (if not already present) and assign the newly created Neverfail Continuity Engine role.
      Note: You may need to bind the role at the host level (in Hosts and Cluster View) as well as the Datastore permissions tab level (in Datastores & Datastore Clusters).
Applies To
 
Neverfail Continuity Engine v8.x, 9.x
 
Related Information
 
None
 
KBID-2974 

    • Related Articles

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

    • Continuity Engine Troubleshooting - Channel Drops

      This article discusses unexpected channel drops. Under normal operations, Neverfail Continuity Engine maintains continuous communications between servers using the Neverfail Channel. When communications between servers fail, the condition is referred ...

    • Reference: Continuity Engine Product Architecture

      Summary This Quick Reference provides an overview of the key concepts and components of Neverfail Continuity Engine product architecture: More Information Key Concepts and Components Component / Concept Description Active-Passive Server Pair ...

    • Accessing the Continuity Engine Servers

      This article introduces the Neverfail Continuity Engine Management IP addressing. It allows you to manage your Neverfail Continuity Engine servers even when they are in a passive role.  Continuity Engine employs 2 or 3 servers working together. One ...

    • Continuity Engine Troubleshooting - Synchronization Failures

      Neverfail Continuity Engine provides protection to your applications by replicating data to a passive server. Continuity Engine attempts to synchronize protected data on all servers and continually replicates changes to that data. This article ...