6 Replies Latest reply on Jan 8, 2018 6:11 PM by serena

    Orion Suite upgrade best practice


      Getting ready to upgrade my Orion platform (2015.1.0) and all individual products (NCM, NPM, IVIM, NTA) to current version.  Is it best practice to upgrade the individual products in place for build a new server and perform clean installs?  Is there a significant lift to upgrade/migrate data?  Any huge "got ya"s that I should be aware of?

      Thanks much,


        • Re: Orion Suite upgrade best practice

          Wow that will be a massive upgrade! I recently went from NPM 11.0.1 to 12.1. I also have UDT, IPAM, NCM & VNQM. The product advisor showed me that I had to step through about 17 steps of upgrades to make sure each module was compatible with the other.


          If you follow the upgrade advisor, you should be fine. But set aside some time, as some installs can take an hour or so.


          Obviously if you start from scratch, then it will be a nice clean and easy install. Only downside I see with this is that you'll loose all historical data and you'll need to re-add everything back into your monitoring setup, unless of course you migrate the database. But do some reading up on that as I've never done it.


          Good luck!

            • Re: Orion Suite upgrade best practice

              I believe we're still running a single server with everything on it, except the SQL databases, so I might go with a clean install since I've got a DBA handy for the database migration.






                • Re: Orion Suite upgrade best practice

                  In terms of how much work it would be on your end, upgrading from the old version is likely to be a pretty complex process, I'd expect it to take most of a full day, as there are going to be several intermediate upgrades you would need to pass through.  You can get a plan for most of those using the upgrade advisor here, Product Upgrade Advisor | SolarWinds Customer Portal

                  Although that tool only goes to NPM 12.1, for versions newer than that the upgrade installer itself will assess the environment and let you know what steps it needs to do to get up to date.


                  If you do decide to do a fresh install you usually want to stand up a new database from scratch though, because different changes have been made to the db over the years and you can't just point a new instance of orion at an old database and be confident that you won't end up with potentially buggy artifacts. 

              • Re: Orion Suite upgrade best practice

                I've decided to run through the upgrade from my current installation to current version.  The time it takes is of less concern than resources required to build all new servers and databases.  All installations are in an off-line environment.


                My server is:  Windows 2012-R2

                My DB server is:  MS SQL 2012 (SP4)


                I will install VNQM from scratch.


                How does the below upgrade path look?  Any obvious problems?