Multi-Subnet Pool Failover.
Secure your Orion servers and pollers across different subnets to ensure the protection of your data.
Automated failover in under five minutes.
Help ensure monitoring and data collection continuity in under five minutes.
Automatic server failback.
Reduce costs via automatic failback to your preferred server once it’s back online and healthy.
Failover to public cloud and IaaS solutions.
Protect your data by configuring your High Availability so that it performs failover to public cloud and Infrastructure as a Service (IaaS) solutions.
Instant notification and alerting.
Be the first to know when key health thresholds for your monitoring system are crossed.
Customizable failover rules.
Trigger failover based on customizable application, system, process, and service health thresholds.
Provides high availability architecture and helps ensure business continuity.
Real-time monitoring of your Orion implementation saves time by automating failover tasks.
Supported products for HA
| Single subnet |
Multiple subnets |
| Products running on Orion Platform 2016.2 and later |
Products running on Orion Platform 2017.3 and later |
| Enterprise Operations Console 2.0 and later |
Enterprise Operations Console 2.0 and later |
| IP Address Manager 4.3.2 and later |
IP Address Manager 4.5 and later |
| Log Analyzer 1.0 and later |
Log Analyzer 1.0 and later
Some devices do not support sending data to hostnames, which is a requirement for multiple subnets.
|
| NetFlow Traffic Analyzer 4.2.1 and later |
NetFlow Traffic Analyzer 4.2.2 and later |
| Network Configuration Manager 7.5.1 and later |
Network Configuration Manager 7.7 and later |
| Network Performance Monitor 12.0.1 and later |
Network Performance Monitor 12.2 and later |
| Server & Application Monitor 6.3 and later |
Server & Application Monitor 6.4 hotfix 1 and later |
| Server Configuration Monitor 1.0 and later |
Server Configuration Monitor 1.0 and later |
| Storage Resource Monitor 6.3 and later |
Storage Resource Monitor 6.5 and later |
| User Device Tracker 3.2.4 and later |
User Device Tracker 3.2.4 and later when installed on Orion Platform 2017.3 and later |
| Virtualization Manager 8.0 and later |
Virtualization Manager 8.0 and later |
| VoIP & Network Quality Manager 4.2.4 and later |
VoIP & Network Quality Manager 4.2.4 and later when installed on Orion Platform 2017.3 and later |
| Web Performance Monitor 2.2.1 and later |
Web Performance Monitor 2.2.1 and later when installed on Orion Platform 2017.3 and later
WPM Player is not fully supported in a High Availability environment. SolarWinds recommends that you move the WPM Player to a different computer in the environment than the main Orion server.
|
The following products can be integrated with your Orion Platform-based product. The integration module between products is supported under SolarWinds High Availability, but the stand-alone product is not supported.
- Storage Manager 6.2.3
- Virtualization Manager appliance 6.3.2 and later
- Engineers Toolset 11.0.3 and later
- Database Performance Analyzer on Orion 10.2 and later
- Patch Manager 2.1.3 and later
Software and Hardware requirements for HA
SolarWinds strongly recommends that the hardware and software of the standby server matches the primary server. Using matching system specifications and installed software ensures the same performance in the event of a failover.
- SolarWinds does not provide failover support for any database.
- Some SNMP trap, syslog message, and flow data is lost while waiting for the secondary server to become active.
Hardware/
Software |
Requirements for both servers |
| Operating System |
Windows Server 2019
Windows Server 2016
Windows Server 2012 R2
|
| Hardware |
Must meet the minimum hardware requirements for the products you have installed on the primary server or closely match the primary server |
| Software |
Must meet the minimum software requirements for the products you have installed on the primary server or closely match the primary server |
| IP address version |
IPv4 |
| Database connection |
Connection to the SolarWinds Orion database
If protecting an NTA environment, both servers must be able to connect to the separate NTA Flow Storage database.
|
| Other (for virtual hostnames) |
Windows or BIND DNS administrative server credentials
BIND version 9.3 and later or Windows DNS on Windows Server 2008 and later
- You can use other DNS servers using your own scripts.
- The primary and secondary server can be joined to a Windows domain
|