Neverfail Continuity Engine Server Deployment Architecture Options

Neverfail Continuity Engine Server Deployment Architecture Options

Summary

This Knowledgebase article provides information about the server deployment architecture options and prerequisites for each option. 

More information

The Neverfail Continuity Engine v8.0 selected server architecture affects the requirements for hardware and the technique used to clone the Primary server.

Virtual-to-Virtual (V2V) 

Virtual-to-Virtual is the supported architecture if applications to be protected are already installed on the production (Primary) server running on a virtual machine. Benefits to this architecture include reduced hardware cost, shorter installation time, and use of the VMware Cloning for installation.
 
The Secondary virtual machine will be an exact clone of the Primary server and thus automatically meet the minimum requirements for installation of the Secondary server.
 
Each virtual machine used in the Virtual-to-Virtual pair should be on a separate ESX host to guard against failure at the host level.

Physical-to-Virtual (P2V) 

The Physical-to-Virtual architecture is used when the environment requires a mix of physical and virtual machines. This architecture is appropriate to avoid adding more physical servers or if you plan to migrate to virtual technologies over a period of time.
The Secondary Neverfail Engine virtual machine will be created from the Primary server.
  • The specifications of the Secondary Neverfail Engine virtual machine must match the Primary physical server as follows:
    • Similar CPU
    • Identical Memory
  • The Secondary Neverfail Engine virtual machine must have sufficient priority in resource management settings so that other virtual machines do not impact its performance.

Physical-to-Physical (V2V) 

The Physical-to-Physical architecture is used in environments where both the Primary and Secondary servers are physical servers. Use of Physical-to-Physical limits installation options as it requires using Neverfail Continuity Engine's manual cloning during the installation process. This architecture requires attention to detail when preparing for installation as both hardware and software must meet specific prerequisites.
 
Primary Server
The Primary server must meet the hardware and software requirements as specified in the Pre-Install Requirements.
Secondary Server
The Secondary server operates as a near clone of the Primary server and must meet the following requirements.
  • Hardware
    • Hardware should be equivalent to the Primary server to ensure adequate performance when the server is in the active role:
      • Similar CPU
      • Similar memory
      • Identical number of NICs to the Primary server
      • Drive letters must match the Primary server
      • Available disk space must be greater than or equal to the Primary server
  • Software
    • Software on the Secondary server must meet the following requirements.
      • OS version and Service Pack version must match the Primary server
      • OS must be installed to the same driver letter and directory as on the Primary server
      • Machine name must be different from the Primary server prior to installing Neverfail Continuity Engine
      • Set up in a workgroup prior to installing Neverfail Continuity Engine
      • System date, time, and time zone settings must be consistent with the Primary server

Applies To

Neverfail Continuity Engine v8.x or newer
 
KBID-2975