Installation guide

Important: For dependent services, failure actions must match the failure
actions for any protected service on which those services depend, in both
type and order. For example:
•
Service X is automatically protected by SolarWinds Failover Engine
•
Service Y is automatically protected by SolarWinds Failover Engine and
has a dependency on service X
•
The system administrator sets custom recovery actions for service X
as follows:
First Failure = Recover Service
Second Failure = Application Restart
Third Failure = Switchover
In this situation, the system administrator should also set the service
recovery actions for service Y to:
First Failure = Recover Service
Second Failure = Application Restart
Third Failure = Switchover
Note that if service X fails, the dependent service Y must also fail. If the
service recovery actions for service Y are different to those for service
X, they may take precedence, for example service X requires a
switchover but the failure of service Y has already triggered a service
restart action.
This advice applies only to services which are automatically protected by
SolarWinds Failover Engine and dependent upon one another. These
dependencies may be examined via the Windows Service Control Manager,
under Properties > Dependencies.
For services which are shown in the Protected services depend on: pane
of the SolarWinds Failover Manager Applications: Services page, this advice
is not applicable, because:
•
These services do not depend on protected services; rather, protected
services are dependent upon them; and
•
These services are not directly managed by SolarWinds Failover Engine
and therefore have no configurable recovery actions.
Note: If an application with the failure option set to Application Restart fails,
only the services that have failed are restarted. Dependent services do not
stop and restart as a result of the failure.
30 - Command Line Installation
Installation Guide - SolarWinds Failover Engine