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.
Updated: 4-17-2017 | Migration Guide
This guide details how to migrate from a Failover Engine (FoE) LAN configuration for High Availability environment to SolarWinds High Availability (HA).
Migrating from FoE to SolarWinds HA is an easy process. You simply create and manage an HA pool in the Orion Web Console, using a provided installer to sync the secondary server products and configurations with the primary server. You can migrate to SolarWinds HA using your current server pairs or add new servers for HA pools. When migrating, you may need to upgrade your Orion Platform products.
You may need to upgrade your Orion Platform products to access HA. These instructions include upgrade steps as needed.
SolarWinds HA provides a high availability solution for your Orion server in a LAN environment. For disaster recovery (DR) on a WAN environment, you must continue using FoE.
Yes, you can continue to use FOE and SolarWinds HA in the same Orion Platform environment. SolarWinds HA supports primary and secondary server pools for the Orion server and Additional Polling Servers. For example, you can install FOE to protect your primary/secondary Orion server, and HA to protect your Additional Polling Engines.
You cannot run FOE and SolarWinds HA to protect the same server. Only use FOE or HA to protect one server pair.
SolarWinds HA does not support HA for additional web servers or Enterprise Operations Console (EOC).
Prior to migrating from FoE to SolarWinds HA, you should verify your systems meet the requirements for the new product versions and HA. SolarWinds HA supports High Availability pools with physical to physical (P2P), physical to virtual (P2V), virtual to physical (V2P), and virtual to virtual (V2V) pairs.
To take advantage of SolarWinds HA, you may need to also upgrade your Orion Platform product modules. HA is available in Orion Platform 2016.2 and supported products versions.
This guide includes upgrade instructions, if needed, for your HA migration.
We highly recommend using a new secondary server. If using VM servers, you can delete and create a new VM server for the secondary server. If using physical servers, prepare a new secondary server. Reusing the same FOE secondary server is not recommended. If you use this server, you will need to completely wipe the server and reinstall the OS.
You may need to modify firewall rules to allow traffic from pool members and to the VIP address.
Supported products include:
The following products can be integrated with your Orion Platform-based product. The integration module between products is protected by under SolarWinds High Availability, but the standalone product is not supported.
To migrate to SolarWinds HA, you will uninstall FoE HA from your primary server. You should prepare a new secondary server for HA. SolarWinds HA supports HA servers for your main polling engine and additional polling engines.
Before you begin, you need the following:
As part of your migration to SolarWinds HA, you may need to upgrade your products. If you upgrade, the upgrade order must follow (1) main polling engine, (2) additional polling engines, and finally (3) additional web servers.
These instructions should be followed for all HA environments: physical to physical, virtual to virtual, and other variations.
1. Stop FoE services on the primary and secondary servers
Uninstall FoE from the primary server
Stop the FoE services on the primary and secondary servers.
Uninstall FoE from the primary server.
You can also remove the interfaces for the second network card. SolarWinds HA does not require or use a second network card for communication between the primary and secondary servers.
If you have an FoE pair for your additional polling engines, also uninstall FOE on that primary server.
2. VM: Delete the VM secondary server
Physical: Prepare a new secondary server
The secondary server should be built on the same subnet as the server you want to protect.
If you have a VM for your secondary server, delete the VM. Create a new VM for the secondary server.
If you have a physical for your secondary server, we recommend preparing a new secondary server. If you intend reusing the server, you must uninstall all Orion Platform products including FoE, wipe the computer, reinstall the OS, and reconfigure the hostname and IP address.
|3. If needed: Upgrade Orion Platform product modules|| |
SolarWinds HA is available in Orion Platform 2016.2. If you need to upgrade, complete the upgrades across your environment before creating the HA pool.
|4. Setup the secondary server for HA|| |
|5. Create the High Availability Pool|| |
Your main server or additional polling engine is now highly available and can failover to the standby server.
You do not need to be online. The secondary server only needs access to the primary server in the LAN.
For additional information on requirements and settings, see the HA documentation.