Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Archive > 2017September28 - SRM Deletes > How failovers work

How failovers work

Table of contents
No headers
Created by Nigel, last modified by Gerald.Prado on Sep 28, 2017

Views: 36 Votes: 0 Revisions: 2

After High Availability is enabled and you have set up a pool, each pool monitors itself for failover conditions such as:

  • Inability to connect to the network
  • Stopped SolarWinds services

    Stopped Agent services is not a failover condition.

  • Power loss
  • Network connection loss to the primary server

When a monitored service is down, the Orion server tries to allow the service to recover before failing over to the secondary server. If the same service fails within the default self-recovery period, a failover occurs.

When a failover condition is met and failover occurs in a pool, a failover event is logged and can be viewed in the Event Summary resource or the Events view. An email is also sent to your default recipients.

For example, if the job engine service is down, the High Availability software attempts to restart it. If the job engine fails again within 1 hour, then a failover occurs and the event is logged. If the job engine fails within 61 minutes, a failover does not occur.

 
Last modified

Tags

Classifications

Public