Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Storage Resource Monitor (SRM) > SRM 6.4 Administrator Guide > High Availability in SRM > How failovers work

How failovers work

Table of contents
No headers
Created by Nigel, last modified by Nigel on Mar 14, 2017

Views: 11 Votes: 0 Revisions: 1

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
08:56, 14 Mar 2017

Tags

Classifications

Public