Neverfail IT Continuity Engine v8.0 Installation Prerequisites

Follow

Summary

This Knowledgebase article describes the prerequisites for installation of the Neverfail IT Continuity Engine product.


More Information

Before You Begin

The server to be protected by Neverfail Engine can NOT be any of the following: a server running Neverfail Engine Management Server, configured as a domain controller, global catalog, DHCP or DNS server. These roles and services must be removed before proceeding with installation.

Neverfail strongly recommends that you perform your product trial within a test lab environment, as we do not provide installation or product support for trial evaluations. Neverfail is not responsible for trial software installed in a production environment.

Supported Environments:

  • Windows Server 2008 R2 Standard/Enterprise/Datacenter up to and including SP1
  • Windows Server 2012 Standard/Datacenter
  • Windows Server 2012 R2 Standard/Datacenter
  • 64bit desktop editions of Windows operating systems 7, 8.x, and 10.

Installation Prerequisites

The following provides a listing of pre-requisites that must be addressed prior to attempting an installation of Neverfail IT Continuity Engine.

  • An accessible version of vCenter Server 5.1 or later running on Windows Server 2008 R2 or later for installation of Engine Management Service. The Engine Management Service is compatible for interoping with vCenter Server versions 5.1 up to U3, 5.5 up to U3, and 6.0 up to U2.

Engine Management Service

Note: Connectivity with VMware vCenter Server is NOT required for deployment of Neverfail IT Continuity Engine but is recommended for fully automated deployments.

  • vCenter Server Administrator level user credentials (equivalent with Administrator@vsphere.local) or a user configured with minimal permissions listed in the previous section. Where possible, we recommend vCenter Server Administrator level user credentials (equivalent with Administrator@vsphere).
  • For P2V installation, VMware Converter 5.5 must be available and configured prior to attempting installation of the Primary server.
  • Engine Management Service (EMS) supports most browsers used to connect to the EMS UI but requires that the latest version of Adobe Flash Player be installed.
  • A local Administrator account (with full admin rights) is required for installation (NOT a domain account nested within groups).
  • Neverfail recommends that User Account Control (UAC) be disabled during installation. If it is not possible to disable UAC for installation, open a command window with elevated permissions and launch the Neverfail-ITCE-n-n-nnnnn-x64.msi file from within the command window.
  • Neverfail Engine requires that Microsoft™ .Net Framework 4.0 or later be installed prior to installation.

Primary Server

  • If the Primary server has a pending reboot, it must be resolved prior to the deployment of Neverfail Engine on to the server.
  • Neverfail recommends that User Account Control (UAC) be disabled during installation. If it is not possible to disable UAC for installation, you must use the built-in local Administrator account during installation. Enter this account information on the Deploy Failover page.
  • A local Administrator account (with full admin rights) is required for installation (NOT a domain account nested within groups).
  • The server to be protected by Neverfail Engine can NOT be any of the following:
    • A server running Engine Management Service
    • A server configured as a Domain Controller, Global Catalog, DHCP, or DNS

Important: These roles and services must be removed before proceeding with installation.

  • The Primary server can be Virtual or Physical with the Secondary and Tertiary server (if deployed) as either Virtual or Physical as well.

Important: When installing in a Virtual-to-Virtual architecture, VMware Tools must be installed and running on the Primary server before starting the Neverfail Engine installation process.

  • Verify that all services to be protected have all three Recovery settings configured to Take no Action.
  • Verify no other critical business applications except those to be protected by Neverfail Engine are installed on the server.
  • Verify that there is a minimum of 2GB of available RAM in addition to any other memory requirements for the Operating System or installed applications. 512MB of RAM must remain available to Neverfail Engine at all times.
  • Verify that a minimum 2GB of free disk space is available on the drive where Neverfail Engine is to be installed.

    Note: Although Neverfail Engine requires only 2GB of available disk space on the drive to receive the Neverfail Engine installation, once installed, the size of each Send and Receive queue is configured by default for 10GB. For Trio configurations the send and receive queues will by default require 20GB per server.You must ensure that sufficient disk space is available to accommodate the send and receive queues or modify the queue size configuration to prevent MaxDiskUsage errors.
  • Obtain and use local administrator rights to perform Neverfail Engine installation.

    Note: Neverfail Engine services are required to be run under the Local System account.
  • Apply the latest Microsoft security updates and set Windows Updates to manual.
  • All applications that will be protected by Neverfail Engine must be installed and configured on the Primary server prior to installing Neverfail Engine.
  • Verify that all services to be protected are running or set to Automatic prior to installation.

    Note: During installation, protected services are set to manual to allow Neverfail Engine to start and stop services depending on the role of the server. The target state of the services is normally running on the active server and stopped on the passive.
  • Register this connection's address in DNS must be disabled on all NICs on the target server.

    Note: If deploying in a DR configuration, replace the existing DNS "A" record for the Public IP address with a static record and configure the TTL to 45 seconds. Otherwise, after installation, re-enable Register this connections's address in DNS.
  • File and Printer Sharing must be enabled and allowed access through all firewalls on the Primary target server prior to deployment.
  • Verify that the Server service is running prior to deployment to the target server.
  • When installing in a P2V or P2P environment, the specifications of the Secondary Neverfail Engine machine must match the Primary physical server as follows:
Secondary Server
  • Similar CPU
  • Identical Memory
  • Sufficient disk space to host VM disks to match the Primary server

    The Secondary Neverfail Engine virtual machine must have sufficient priority in resource management settings so that other virtual machines do not impact its performance.

IP Address requirements:

Public:

  • 1 each Public IP address - Engine Management Service
  • 1 each Public IP address - Primary Server
  • 1 each Public IP address - Secondary Server (only when deployed for DR)

Note: When deployed for HA or as part of a trio, the Primary and Secondary server will share the Public IP address.

  • 1 each Public IP address - Tertiary Server (only when deployed in a trio)

Channel:

  • 1 each Channel IP address - per server when deployed in a pair
  • 2 each Channel IP addresses - per server when deployed in a trio

LAN

When deployed in a LAN environment, Neverfail Engine requires that both servers use the same Public IP address. Each server also requires a unique Neverfail Channel IP address.

Note: After deployment, on the Public NIC, go to the Network Properties for TCP/IP4 and under Advanced Properties, select Register this connection's address in DNS for the Public NIC.

WAN

When deployed in a WAN environment, persistent static routing configured for the channel connection(s) where routing is required.

Note: This requirement can be avoided if the channel IP addresses are in the same subnet as the Public IP address in which case the default gateway can be used for routing.

At least one Domain Controller at the Disaster Recovery (DR) site.

  • If the Primary and DR site uses the same subnet:
    • During installation, follow the steps for a LAN or vLAN on the same subnet.
    • Both the Primary and Secondary servers in the pair use the same Public IP address.
  • If the Primary and DR site use different subnets:
    • During installation, follow the steps for a WAN.
    • The Primary and Secondary servers in the Neverfail Engine pair require a separate Public IP address and an Neverfail Channel IP address.
    • Provide a user account with rights to update DNS using the DNSUpdate.exe utility provided as a component of Neverfail Engine through the Engine Management Service User Interface tasks or Neverfail Engine Manager Applications > Tasks > User Accounts.
    • Neverfail recommends integrating Microsoft DNS into AD so that DNSUpdate.exe can identify all DNS Servers that require updating.
Firewalls

If using Windows Firewall, Engine Management Service can automatically configure the necessary ports for traffic. In the event that other than Windows Firewall is being used, configure the following specific ports to allow traffic to pass through:

  • From VMware vCenter Server -> Engine Management Service
    • TCP 443 / 9727 / 9728 / Ephemeral port range
  • From VMware vCenter Server -> The protected virtual machine
    • TCP 443 / Ephemeral port range
  • From Engine Management Service -> VMware vCenter Server
    • TCP 443 / 9727 / 9728 / Ephemeral port range
  • From Engine Management Service -> The protected virtual machine
    • TCP 7 / 445 / 135-139 / 9727 / 9728 / Ephemeral Port Range
  • From the Protected Virtual Machine -> Engine Management Service
    • TCP 7 / 445 / 135-139 / 9727 / 9728 / Ephemeral Port Range
  • From the Protected Virtual Machine -> VMware vCenter Server
    • TCP 443 / Ephemeral port range
  • From Protected Virtual Machines -> VProtected Virtual Machines in Duo/Trio and back
    • TCP 7 / 52267 / 57348 / Ephemeral port range
  • From Management Workstation -> VProtected Virtual Machines in Duo/Trio and back
    • TCP 52267 / 57348 / Ephemeral port range

For more detailed information, see KB-2907 Firewall Configuration Requirements for Neverfail IT Continuity Engine.

Note: The default dynamic ephemeral port range for Windows 2008 and 2012 is ports 49152 through 65535.


Applies To

Neverfail IT Continuity Engine v8.0


Related Information

Network Ports Required for Neverfail Continuity Engine 8.x

KBID-2915

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.