Neverfail Installation Prerequisites

Follow

Summary

This Knowledgebase article describes the prerequisites for installation of the Neverfail product including both hardware and software.


More Information

Before You Begin

The server to be protected by Neverfail can NOT be 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.

Hardware Requirements

Primary Server

  • Must meet Microsoft's requirements for one of the following installed operating systems:
    • Windows Server 2003 x86 and x64 Standard / Enterprise / R2 with SP1 or SP2
    • Windows Server 2008 x 86 and x64 Standard / Enterprise with SP1 or SP2
    • Windows Server 2008 R2 x64 Standard / Enterprise / Datacenter with SP1
    • Windows Server 2012 x64 Standard/Datacenter
  • 1 GB RAM minimum, 2 GB RAM recommended
  • Minimum available RAM required for Neverfail processes and components (recommended 1GB)
    • Minimum of 256 MB available for Neverfail processes and components on Windows Server 2003
    • Minimum of 512 MB available for Neverfail processes and components on Windows Server 2008/R2
    • Minimum of 512 MB available for Neverfail processes and components on Windows Server 2012
  • 2 GB of available hard disk space
  • Number of NICs:
    • In a Pair configuration: 2 non-teamed NICs required, 3 non-teamed NICs recommended
    • In a Trio configuration: minimum 3 NICs required (one for the Public connection and 2 for the Neverfail Channels)

      Note: Neverfail Heartbeat v6.7 and later supports use of a single NIC for both the Neverfail Channel and Principal (Public) network connection.
  • Multiple hard disk drives are recommended as per application vendors' requirements. Avoid locating OS, database, and log files on the same disks

Secondary Server and Tertiary (if implemented)

  • Must meet Microsoft's requirements for one of the following installed operating systems:
    • Windows Server 2003 x86 and x64 Standard / Enterprise / R2 with SP1 or SP2
    • Windows Server 2008 x 86 and x64 Standard / Enterprise with SP1 or SP2
    • Windows Server 2008 R2 x64 Standard / Enterprise / Datacenter with SP1
    • Windows Server 2012 x64 Standard / Datacenter
  • 1 GB RAM minimum, 2 GB RAM recommended
  • Minimum available RAM required for Neverfail processes and components
    • Minimum of 256 MB available for Neverfail processes and components on Windows Server 2003
    • Minimum of 512 MB available for Neverfail processes and components on Windows Server 2008/R2
    • Minimum of 512 MB available for Neverfail processes and components on Windows Server 2012
  • Total hard disk space should be greater than or equal to the Primary Server
  • Same number of NICs as the Primary Server
  • Hard drive lettering scheme must match the Primary Server (although underlying hardware may be different)

Software Requirements

Note: If installing Neverfail Heartbeat v6.6.0 or later, .Net 4.0 must be installed prior to running Setup of Neverfail Heartbeat.

Primary Server

  • Installed operating system:
    • Windows Server 2003 x86 and x64 Standard / Enterprise / R2 with SP1 or SP2
    • Windows Server 2008 x 86 and x64 Standard / Enterprise with SP1 or SP2
    • Windows Server 2008 R2 x64 Standard / Enterprise / Datacenter with SP1
    • Windows Server 2012 x64 Standard / Datacenter (Neverfail Heartbeat v6.7 and later)
  • Latest Microsoft security updates
  • Installation of Neverfail Heartbeat requires local admin rights
  • When installing into a Windows Server 2008/2012 environment, Neverfail Heartbeat requires that the Windows Server Backup Feature and Command Line Tools are installed. When installing Windows Server Backup Feature, it is also necessary to include Windows PowerShell.

Secondary Server and Tertiary (if implemented)

  • OS version, service pack version and security updates must match the Primary Server
  • OS must be installed to same drive letter and directory as the Primary Server
  • ACPI compliance must match the Primary Server
  • Different machine name from the Primary Server
  • Setup in a workgroup
  • System date/time and time zone consistent with Primary Server
  • Additional applications, including the protected application (such as Exchange or SQL) must NOT be installed on the Secondary Server

Networking Configuration

Primary Server

Public Network connection(s) configured with:

  • Static IP address
  • Correct network mask
  • Correct gateway address
  • Correct DNS server addresses

Channel Network connection(s) configured with:

  • Static IP address (in a different subnet from the Public Network)
  • Correct network mask
  • No gateway IP address
  • No DNS server addresses
  • In a LAN environment, a cross-over cable should be used to connect the channel connection(s) on the Primary Server to the channel connection(s) on the Secondary Server
  • In a WAN environment, persistent static route(s) must be configured to the channel connection(s) on the Secondary Server

Secondary Server and Tertiary (if implemented)

Channel Network connection(s) configured with:

  • Static IP address (in a different subnet from the Public Network)
  • Correct network mask
  • No gateway IP address
  • No DNS server addresses
  • File and Print Sharing enabled
  • In a WAN environment, persistent static route(s) must be configured to the channel connection(s) on the Primary Server. See Knowledgebase Article #466, linked below, for more information.

Login Account Privilege Requirements

Administrator privileges required for login accounts vary according to configuration:

  • For installation and normal system administration, a login account with Local Administrator privilege must be used. This account may also be a Domain Administrator if login with cached credentials is permitted by the security policy.
  • For installation of a Secondary or Tertiary server which is not already a clone of the Primary server, a Local Administrator account is required for installation.
  • For WAN installations, where the public IP addresses differ between servers, the administrator account used must additionally be a member of the DNSadmin group. Domain Administrator accounts have sufficient privilege to meet this requirement.

Service Account Requirements

  • The Neverfail services are required to be run under the Local System account.

Applies To

All Versions


Related Information

Knowledgebase Article #466 How to Create a Static Route for the Neverfail Channel Connection in a WAN Environment

KBID-968

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.