Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

If I'm migrating from Windows 2016 to Windows 2022

Hello!

I've got both a Windows 2016 and a Windows 2022 VM server up with the applicable (IPAM, NPM and SAM Solarwinds installs) on the new Windows 2022 server, we use at our company.

Am going to try using the High Availability Deploy method and failover procedure to migrate Solarwinds from the Windows 2016 to the new Windows 2022 server.

I've got a ticket in for this as I'd like to have a Solarwinds expert on the call as I do this but thought I'd also post some questions here so THWACK Points could be issued

Questions:

1. Does the secondary (Windows 2022 server) need to have the configuration wizard completed first and does this include creating a new SQL Server Database structure for it? which will be eventually not used? (As I understand using the HA Deploy tool after failing over to the secondary it will\should be using the existing SQL Server database the Windows 2016 server is connecting to.)

2. Does the new Windows Server 2022 version (being newer) matter? Windows 2016 version of Solarwinds hasn't been updated lately and am wondering if this might need to be done first.

I'm new to THWACK and am not a SCP so please be patient.

Thanks-

Find more posts tagged with

Accepted answers

All comments

shuth

The SolarWinds versions need to be the same for HA to work.

For your questions:

It will use the current SQL server and database. If you chose the HA option it would have pulled those details automatically.
Windows version should not matter but the SolarWinds versions need to match.

Looks like you are trying to do this: https://documentation.solarwinds.com/en/success_center/orionplatform/content/migrate_orion_server_zero_downtime.htm

I would completely uninstall SolarWinds from the new Windows 2022 server as you have probably installed the main software instead of setting the system up as a standby server. Then follow the instructions above.

The general steps to set up a new HA server/pool is as follows:

Run the same installer from your main server on the new server (to ensure same version)
1. Choose the option for scalability and select the High Availability for Main Server option
2. It will ask for the details of your main server (hostname/IP and an admin username/password)
The system will install the SolarWinds software in a standby mode. It will run the Configuration Wizard and register itself in your SolarWinds instance. It will use the same SQL server and database details that your main server is currently using (the details will be pulled from the main server and the Config Wizard should have the details automatically).
Once completed, you can go into the High Availability settings (My Deployment) and set up the HA pool.

Depending on how old your current SolarWinds is (on the Windows 2016 server), you may want to look at upgrading that first.

Alternatively you can go with the migration option.
https://documentation.solarwinds.com/en/success_center/orionplatform/content/migrate_solarwinds_to_a_new_server_with_a_new_ip_and_hostname.htm

rbmowbray

Thanks for this info. Yes. I started down the road of a new ip migration and installed the Solarwinds. I'll be uninstalling it at going with the zero down time HA instead. This explains why when I exported the install (HA Deploy) the software said a new version exist as it saw the new install on the newer server.