Scribd
Upload
181 views3 pages

Neverfail Installation Prerequisites

This document outlines the hardware, software, and networking prerequisites for installing the Neverfail failover solution. The primary server must meet Windows Server 2003 or 2008 requirements and have a minimum of 1GB RAM and 2 NICs. The secondary and tertiary servers must match the primary server configuration. Networking on all servers must be configured with static IPs, no gateway, and file sharing enabled on secondary servers. Administrator privileges are required for installation and administration.

Uploaded by

xaviersavioit
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
181 views3 pages

Neverfail Installation Prerequisites

This document outlines the hardware, software, and networking prerequisites for installing the Neverfail failover solution. The primary server must meet Windows Server 2003 or 2008 requirements and have a minimum of 1GB RAM and 2 NICs. The secondary and tertiary servers must match the primary server configuration. Networking on all servers must be configured with static IPs, no gateway, and file sharing enabled on secondary servers. Administrator privileges are required for installation and administration.

Uploaded by

xaviersavioit
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Neverfail Installation Prerequisites

NOTE: - 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.

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

 1 GB RAM minimum, 2 GB RAM recommended

 256 MB of available RAM minimum

 2 GB of available hard disk space

 Number of NICs:

o 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 Never fail
Channels)

 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

 1 GB RAM minimum, 2 GB RAM recommended

 256 MB of available RAM minimum

 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

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

 Latest Microsoft security updates

 Installation of Never fail Heartbeat requires local admin rights

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

 The same Windows IIS components must be installed as the Primary Server. Once installed, set each of these
component services to have the same startup type as the Primary Server (automatic, manual or disabled)

 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

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.

You might also like