Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Orion Platform > Orion Documentation > Orion Platform Administrator Guide > High Availability > Set up an HA pool

Set up an HA pool

Table of contents
No headers
Created by Magdalena.Markova, last modified by Magdalena.Markova on Dec 08, 2016

Views: 107 Votes: 0 Revisions: 5

Updated: 12-1-2016

An HA pool is a group of two servers that have access to the same network and database resources. The pool includes one main server or additional polling engine and one secondary server or polling engine. Each server is called a pool member and can take over all responsibilities of the other server.

When a pool member is sending and receiving data, it is the active member. When a pool member is waiting to take over, it is the standby member.

Because of the web-based License Manager, the main Orion server must stay up. If the main server is down for more than 14 days, your licenses may be invalidated. The main Orion server does not require Internet access.

Before you begin, you need the following:

  • A VIP address
  • The secondary HA server
  • An available HA pool license
  1. In the Orion Web Console, click Settings > All Settings > High Availability Deployment Summary.
  2. Click Setup High Availability pool next to your standby server. If a HA pool license is not available, you are prompted to activate an HA pool license.
  3. Enter the pool name and the virtual IP (VIP) address.

    The VIP must be unassigned and on the same subnet as the primary and secondary servers.

  4. Click Create Pool to complete the pool setup.

Your main server or additional polling engine is now highly available and can failover to the standby server. A failover audit event is logged when you create the pool.

When the pool is created, the High Availability Deployment Summary displays the active and standby servers grouped under the pool name. Failover events will be logged and you can receive email notifications.

You may need to refresh the page to see the correct pool and server status.

SolarWinds recommends that you perform a manual failover after you create your pool and observe the data collected to ensure that all network and device changes are correct.

Last modified
02:18, 8 Dec 2016