maybe this migration guide will help you to build your own runbook to upgrade all your systems:
Thank you for reply! We are using NPM 12.2 (1 main polling engine, 3 additional web servers, 12 additiona webservers) ,
But still i have few questions like: Please correct me if this correct process: We will follow this process for both Test and Prod System.
Solarwinds Windows Server upgradation from 2012 R2 to 2016 for same server? is this first step right ?
Solarwinds SQL Server migration/ upgradation from 2014 to 2016 on Same server ? is this second?
Solarwinds installation on same server? - do we need to again install the Solarwinds (all installed modules)Software post Solarwinds windows upgradation?
When we need to take Solarwinds SQL backup?
Hi, Please update on this?
2 of 2 people found this helpful
personally this is what I would do.
all in LAB first stage:
 build new servers with 2016 O/S
 configure and set up SQL 2016
 install the exact like for like modules on the new main polling engine, so both version match.
 run configuration wizard as if you was going to set up a completely NEW solarwinds
now you should have:
windows servers 2016
Microsoft SQL 2016
main polling engine that has same solarwinds modules installed
solarwinds running without any issues.
second stage is the database back up:
 back up SQL database
 restore database to your new lab SQL Backup and restore SQL database instance using a .BAK file - SolarWinds Worldwide, LLC. Help and Support
 onces restored you need to change some details in the database so it checks for the new polling engine IP and engineID(step 7) Migrate SolarWinds products to a new server with a new IP and hostname - SolarWinds Worldwide, LLC. Help and Support
 run the configuration wizard and point it at the newly restored database from step 2
 run the configuration wizard on all APE and AWS and point at new SQL form step 2
then licencing etc
hope that helps
Thank you for reply.
now you should have:
windows servers 2016 We have almost 12 windows Servers (1 main polling Engine, 9 additional pollers, 2 additional Web server). basically we have large Production Environment. So, I just wanted to know, can we do Windows server up-gradation like one server per day (and run the solarwinds configuration Wizard) because we cant down production for long time is there any impact and I want to upgradae SQL windows server at the end of upgradation?
np, i am wondering are you locked down to only these 12 servers? ideally, an perhaps building one new addition poller with the 2016 O/S first, then migrate all your nodes to another additional poller to keep up with polling, of course networking will need to be configured for this polling, this will now give you time to upgrade or migrate to a new server then re run the install package from the (APE) run the configuration wizard select DB etc.. and assign all nodes back.
you can also find some information here:
personally i would do SQL last and again i will opt to build a new SQL server rather then upgrade i dunno why i just like to have new servers to replace rather then upgrading, perhaps its because its easier for me to troubleshoot a new server then troubleshoot an upgraded one.
this link should also help at that stage: