Installation guide

•
Plugs-ins on pre-cloned servers must be located with the same path as on
the primary server for a successful installation. For example, if the path on
the primary server is C:\temp\<pluginname.dll>, then the path to the
plug-in on the pre-cloned server(s) also must be
C:\temp\<pluginname.dll>.
•
All applications intended to receive SolarWinds Failover Engine protection
must be installed and configured on the primary server prior to installing
SolarWinds Failover Engine
•
The primary and secondary servers must be set to identical System Date,
Time, and Time Zone. Once configured, do not change the Time Zone
•
If installing on Windows Server 2003, verify that the Principal (Public)
network adapter is listed as the first network adapter in the Network
Connections Bind Order on each server. (Network Connections >
Advanced > Advanced Settings)
Server Architecture Options
SolarWinds Failover Engine supports Virtual to Virtual, Physical to Virtual, and
Physical to Physical architectures. The selected server architecture determines
the hardware requirements and impacts the technique used to clone the primary
server.
Virtual to Virtual (V2V)
In a V2V architecture, SolarWinds Failover Engine allows cloning of the primary
server prior to the installation of SolarWinds Failover Engine using VMware
Converter, VMware vCenter Cloning Utility, and other 3rd party utilities. Benefits
to this architecture include reduced hardware cost, shorter installation time,
and use of the Pre-Clone technique for installation. The secondaryvirtual
machine must meet the following minimum requirements:
•
The configuration of secondary virtual machine must match the primary
virtual machine:
◦
Similar CPU, including resource management settings
◦
Similar memory configuration, including resource management settings.
•
Appropriate resource pool priorities
•
Each virtual machine in a V2V configuration must be on a separate host
to guard against failure at the host level
•
Each virtual NIC must use a separate virtual switch (network)
Physical to Virtual (P2V)
P2V architecture is used when the environment requires a mix of physical and
virtual machines, such as when SolarWinds Failover Engine is installed on a
physical server in an environment with limited available hardware. This
architecture is appropriate if you must avoid adding additional physical servers
Implementation - 13
SolarWinds Failover Engine - Installation Guide