Help and opinions on OS upgrade for Solarwinds Orion platform

I am looking for feedback on which route I should take with our Windows 2016 upgrade. We are currently on 2012 R2 and SQL 2012 looking to go to 2016. We have Orion platform 2017.3.5, NPM 12.2, SAM 6.6, WPM 2.2.1, NTA 4.2.3, and a few others. I could go 2 routes and I just need to know if there are any gotchas with either one or if one is easier than the other.

1st Route:

Upgrade Orion and components on old 2012 servers make sure everything is running smooth.

Then install all the latest versions on new 2016 servers and cut over (present the database to the new SQL server, run config wizard, etc.)

2nd Route:

Install same versions of everything on new 2016 servers and cut over (same as above).

Make sure everything is up and running smoothly

Then upgrade everything to the newest versions, NPM 12.3, SAM 6.6.1, WPM 2.2.2, NTA 4.4, etc.

I appreciate any and all feedback, experience, gotchas, and what not to do's. Thanks guys!!

Find more posts tagged with

product upgrades

npm 12.3 upgrade

orion upgrade buddy

operating system upgrade

upgrade

os upgrade

Accepted answers

aLTeReGo

I recommend option #3 which allows you to upgrade and migrate at the same time. It also has the added benefit of allowing you to revert easily if needed by simply restoring your Orion database.

#1 Backup your database

#2 Shutdown and Disable services on your old Orion server(s)

#3 Install the latest version of your product modules on your new server

#4 When the Configuration Wizard runs, point your new installation at your old database

#5 Following the remaining steps outlined here > Migrate SolarWinds Orion products to a new server using the same IP and hostname - SolarWinds Worldwide, LLC. Help and S…

#6 Power off your old Orion Server

All comments

aLTeReGo

I recommend option #3 which allows you to upgrade and migrate at the same time. It also has the added benefit of allowing you to revert easily if needed by simply restoring your Orion database.

#1 Backup your database

#2 Shutdown and Disable services on your old Orion server(s)

#3 Install the latest version of your product modules on your new server

#4 When the Configuration Wizard runs, point your new installation at your old database

#5 Following the remaining steps outlined here > Migrate SolarWinds Orion products to a new server using the same IP and hostname - SolarWinds Worldwide, LLC. Help and S…

#6 Power off your old Orion Server

robelk

Thank you aLTeReGo!!

Quick question... is it possible for me to install the latest versions of our product modules on the new servers but not run the config wizard until ready to point to the old database during the change window? I would like to get as much done before hand as to minimize the downtime. Thanks again!

aLTeReGo

Absolutely! You can either let the Configuration Wizard remain open and not proceed until you're ready, or cancel it and re-launch it whenever you're ready to cut over.

martian_monster

I did this kind of upgrade last October but Instead of doing the move and upgrade I moved everything first, made sure it ran fine for a few weeks then did the upgrade. I did it this way just in case something went sideways it was easier for me to figure out if it was the move or the upgrade. Just my $.02.

dgsmith80

You could also do Option 4: Migrate to new DB first, then migrate to new Application Server:

1. Shutdown services on your old Orion server

2. Backup Database & Copy it to the new SQL Server

3. Run Config Wizard on your old Orion server - Point config wizard to the new SQL Server. (This will restart all your services)

Then when you're ready

4. Backup Database on new SQL server

5. Install the latest version of your product modules on your new Orion server.

6. If you're changing the Hostname or IP then follow the steps in the migration guide mentioned, if not

7. Run Config Wizard (which is already pointing to new SQL server) let it update the tables & you're done.

brianj

The last time I spoke with solarwinds support they said this would break things. The tech explained that the configuraiton wizard will only recognize an upgrade and update the database schema if an upgrade happened on the server, so migrating to a box with newer software will result in the database not updating properly. Has this changed?

aLTeReGo

brianj wrote:
The last time I spoke with solarwinds support they said this would break things. The tech explained that the configuraiton wizard will only recognize an upgrade and update the database schema if an upgrade happened on the server, so migrating to a box with newer software will result in the database not updating properly. Has this changed?

I'm afraid you were provided some misinformation. Combined upgrade/migrations occur all the time and are fully supported.