Background: I have an orion 2020.2.6 installation with NPM/SAM/and NCM with HA. Both HA servers are on 2012 Win OS and I want to move to 2 new servers on 2019 Win OS with new hostnames and IP's (on same subnet as old servers). I see this documentation on migrating an Orion server to a new server via using a temp HA pool: Migrate the SolarWinds Platform server with minimal downtime
Also: The Orion VIP address MUST be identical in the new HA environment as the old one, as many devices are sending in SNMP and syslogs only via that IP, and firewalls are allowing only that IP for communication, etc. I'm aware of the "HA servers must have IP addresses "above" the VIP address in the subnet so all polling traffic goes out of the VIP address, and we are using this "feature" (a Windows NIC thing, documented somewhere) and our new servers will have IP's that are "above" the VIP address.
So, it appears to migrate using the docs linked above, one would need to:
- Turn off HA in current environment.
- Break HA pool/configs (remove secondary server/HA completely).
- Now i have a "standalone" Orion system, which is the original "primary" in the HA pair... and the docs above seem to be working with a standalone server. Ffollow the docs (basically: make new HA pool with "secondary" server using a new server, fail over to it and shut down old 2012 primary server. break HA and delete HA pool. Now I have a "primary" non HA server on the new server (which will become the new primary in the new HA pair) but the server I am running on is/was the "secondary" server.... not the primary. Question 1: I assume? that breaking and deleting the HA pool, while running on the secondary "new" server will convert it to teh "new" primary/standalone server?
- Recreate the HA pool using a "new" secondary server, and the same VIP as the original HA.
Question 2: Has anyone had issues with this type of migration (moving an HA setup via this procedure to a new HA setup on new servers with new hostnames and IP's)? I believe I have read in the forums (years ago) that doing this might cause issues in the DB that need to be cleaned up (like there are old DB records remembering your old primary/secondary, and it causes issues. maybe something to do with the "primary" having issues and failovers?).
Also: This documentation from 2019 ( (+) Deployment sequence for Solarwinds Orion platform in HA with SQL server also in HA with Always On Availability Group. - Forum - Network Performance Monitor (NPM) - THWACK) doesn't do the HA migration listed above, nor mentions using HA as a migration mechanism so I feel using HA as a migration for an existing HA pool has caveats or isn't recommended maybe?. This migration doc is a LOT more involved (and 4 years old) than using HA so if the HA mechanism "works great now" then I'd rather do that.
