Last Updated: September 30, 2016
This release of the SolarWinds Orion Platform features almost instantaneous, automated failover to a secondary server to ensure continuous monitoring when a component failure occurs.
SolarWinds provides high availability under the following failover scenarios:
- Operating system crash
- Power failure
- Network connectivity loss
- SolarWinds application crash
- Hardware failure
- Suspended SolarWinds services
- Database connectivity loss
- Manual failover through the SolarWinds Orion web interface
- Orion SDK support for scripted failover
- User definable failover conditions
The SolarWinds Orion High Availability engine offers the following, key features:
- Rapid failover: Ensures monitoring and data collection continuity.
- Instant notification and alerting: High availability notifications are independent of the SolarWinds alerting service, so you’ll receive alerts even if the SolarWinds Orion server is down.
- Customizable failover rules: Configure alerts to trigger failover based on application, system, process, and service health thresholds.
- Easy installation and configuration: High availability is fully integrated into the SolarWinds Orion platform and is licensed per-pool.
- To deploy HA, set up a secondary server, activate the license, and create a pool. If you evaluate HA, you can create an unlimited number of pools. After 30 days, apply a license key to convert the evaluation to a permanent license.
Supported operating systems and minimum system requirements
High availability supports the following operating systems:
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
There are no HA-specific requirements beyond the requirements of the installed SolarWinds Orion products.
SolarWinds strongly recommends that each member in an HA pool have similar hardware and software configurations.
Minimum supported Orion module versions
High availability ships with all SolarWinds Orion 2016.2 modules including NPM 12.0.1 and SAM 6.3.
Supported high availability configurations
High availability supports the following LAN configurations: physical to physical, physical to virtual, virtual to virtual, and virtual to physical.
The primary and secondary servers must on the same subnet.