Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 8

Solarwinds upgrade planned on VM , existing Solarwinds application server is physical server.

We have planned to upgrade solarwinds from NPM 11.5.2 to NPM 12.1.

For this, we have built a new server (VM) which will be our solarwinds application server for NPM 12.1, NCM 7.6, NTA 4.2.2.

Will this have any effect on the upgrade process?

1) Old server NPM 11.5.2, NCM 7.4, NTA 4.1.1 is a physical server.

2) Newly built server on which we will install NPM 12.1, NCM 7.6 and NTA 4.2.2 is a Virtual Machine

0 Kudos
6 Replies
Level 7

We are doing similar. But we may P2V the server. Anyone done this and did they experience any issues?

0 Kudos

From the orion side there is nothing that a p2v would really impact directly that should cause problems.   Obviously p2v has the normal baggage it brings with it compared to a fresh server but nothing that would specifically be an issue in orion.  Don't mess with the ip or host name and it well be invisible to orion.

- Marc Netterfield, Github

We went from physical to virtual but built a new server and then our database team moved the database to the new box.  I did not do everything in one shot either, I migrated the database and ran for a couple of weeks and then migrated the rest of the servers.  I did not have any issues migrating the database, it went flawlessly.

0 Kudos

I did the same thing recently except I first moved the Solarwinds from physical to virtual. Made sure everything was ok. I then upgraded the products to the latest version.

I moved from NPM 11.0.1 to 12.1. I also have NTA, NCM, IPAM, UDT and VQNM. So there were lots of upgrades to step through.

Level 9

I actually did a quite similar upgrade back in January on our system. I recommend installing 11.5.2, 7.4 & 4.1.1 on your new server and migrating and then upgrading from there. The new installers will or should actually help you install everything you need to get it up to the newest version and I don't believe you will have to do it manually either. We did have a lot of problems with licensing when I moved everything and it was quite a pain I spent the better part of two days on the phone with support trying to get everything worked out. Once everything was up and running we have had no problems since.

Good luck and feel free to ask questions!

The physical to virtual part should not be an issue.  If you want to keep your historical data you will need to step through several versions to get from where you are to where you need to be.  If you download the installer for the latest version it will let you know the upgrade path you need to do, off the top of my head I think there are 3 steps to get your NPM to the current one, plus the steps for the other modules.  I'd definitely set yourself up for a long maintenance window, might take most of a day of watching the configuration wizards crawl along.  Definitely make backups of the db and test it along the way too because it is very frustrating to get to the end of hours of upgrades to find out something went wrong in the db all the way back at step 2.

- Marc Netterfield, Github