Multiple Product Upgrade And Migration - NPM 12.1 - 12.3, SAM 6.4 - 6.7, NCM 7.6 - 7.8, And NTA 4.2 - 4.4

Please Help!!!

According to Upgrade and Migration Guide, I have to migrate the Engine and SQL servers to Windows 2016 and minimum SQL server 2016.

Current Config
SAM 6.4
NCM 7.6
NPM 12.1
NTA 4.2

Existing Servers
Engine
Windows 2008 R2

Database Server
Windows 2012
SQL Database 2014

New Servers
Engine
Windows 2016

Database Server
Windows 2016
Windows SQL Server 2016

I was wondering if someone can help with the migration steps that I need to take in order to upgrade all of the applications to the latest software.

SAM 6.7
NCM 7.8
NPM 12.3
NTA 4.4

Keep in mind that we have to migrate to new servers for the pollers and the SQL database.

Find more posts tagged with

npm 12.3 upgrade

operating system migration

license migration

sql 2016

orion upgrade

migrate sql

migrate engine

Accepted answers

alexpf

NPM 12.1 works from
SQL Server 2008 up through SQL Server 2016 and stops there (won't work with SQL
Server 2016 SP1):

1. Deactivate license on NPM 12.1 server and shut down.
2. Stand up 2016 server
3. Download installer for NPM 12.1 and install on 2016 server
4. Activate license
5. Download installer for NPM 12.3 and install on 2016 server
6. Migrate database to 2016 server and upgrade database
7. Run configuration wizard on 2016 server with NPM 12.3
8. Remove polling engine from within NPM
9. Stand up 2016 server and install polling engine
10. Add new polling engine in NPM

Here is what I have so far from working with SolarWinds Support. Sweet!

All comments

dgsmith80

Hi Alex,

Firstly don't panic you've come to the right place!

So just to clarify Windows Server 2008 is no longer supported so you would need an upgraded application server. Server 2012 & SQL 2012 are being pulled so whilst they will work it would be advisable to go for 2016 or later for both.

There are various opinions as to the upgrade/migration path personally I would just provision new servers and deploy the latest versions of all your modules then let the configuration wizard upgrade the database.

If your slightly more risk averse then you could migrate first by installing at the existing software level and then once you have it connected to the DB and up and running you can do the upgrade.

What's your preference / thoughts so far?

alexpf

I wanted to install all of the latest modules on a new server (fresh install). I was not sure on how to migrate the existing database to the new server SQL 2016 database/Windows 2016 server for the fresh installation.

alexpf

Here is what I have so far from working with SolarWinds Support. Sweet!

alexpf

I just started the upgrade.

So, far we have:

1. De-activated the software on the old servers. We had to run the license manager five times and then all of our licenses were free on the SolarWinds Customer Portal.

2. Shutdown all our servers.

3. Re-named, changed the IP addresses of the new servers to be the same as the old.

4. Started the 12.1 IPAM installer, and also installing NPM,SAM, and NCM.

alexpf

After working with SolarWinds, we were able to identify the install issue that we had. WPM requires the 3.5 .NET Framework to be installed on the servers. We verified that we did not have that on the newly configured servers. The resolution was to install the 3.5 .NET Framework on the servers and complete the installation again. Everything went smooth.

1. Shutdown the services and release the licenses on the old 2008 servers using the SolarWinds License Manager.

2. Install the same applications minus NTA on the new 2016 servers.

3. License the applications.

4. Upgrade the applications on the new main polling engine.

5. Backup and restore the database on the new SQL 2016 instance.

6. Run the configuration wizard and point it to the new SQL 2016 database server.

7. Install NTA and create new database on new SQL 2016 database server.

8. Install additional polling engines or APEs.

9. Install additional web servers or AWSs.

We also copied some files from the old polling engines to the new polling engines as part of the process.

dgsmith80

Glad you got there in the end

alexpf

I wanted to add that since the upgrade, we also had to install postgres and oracle drivers on the polling engines which we had not identified as part of the upgrade.