Thwack peer review for HA for our primary polling engine.

bourlis

Hey fellow THWACK brothers & sisters.  I've got a quick question/peer review thing for you all.  I have 3 separate that on the surface would cause a service outage but I'm thinking I can potentially navigate around if I implement HA on our primary polling engine.  The 3 separate issues are:

1. Upgrade our SolarWinds primary server from Windows 2016 to Windows 2025.
2. Change the server name to follow our current naming standard.
3. Migrate the server from vSphere to Nutanix VM environment.    

In of themselves would require a minor interruptions of service, however I believe I might be able to navigate the interruption of service if I go down the road of HA.  I just need to have someone let me now if my idea is sound or not.  My plan is:

1. Stand up 2 new Windows 2025 servers in our new Nutanix VM environment using our new naming standard.
2. Create a multi-subnet HA pair with our legacy primary polling engine and the 2 new servers.
3. After a week of burn in time remove the legacy primary polling engine from the multi-subnet HA configuration.
4. Lastly, after another week decommission the legacy server.

If my understanding is correct, this would meet my 3 separate tasks and with no interruption of service.  Please let me know if I'm missing something or if you have any sage advice on my plans.

thank you!

Bourlis

Lofstrand

Should work. Have a look at this page also: (+) How to Migrate Orion to a New Server With Zero Downtime - Product Blog - Resources - THWACK

Also, make sure firewalls etc supports your new addresses. If you use NTA or LA, make sure your devices send their data to the new HA hostname