Hide this message
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.
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:
The VIP must be unassigned and on the same subnet as the primary and secondary servers.
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.