This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Migration to new server - Install Sequence

mbrandon32 over 6 years ago

Hello,

New to Thwack and I hope I am hitting the right crowd.

We are looking to migrate our deployment from its current physical infrastructure to a new virtual infrastructure. We will only be performing a migration at this point, and an upgrade at a later date. I have almost all of the steps mapped out - except for the application/module install sequence.

Before running the config wizard, should we install just NPM? Or do we install all modules and THEN run the config wizard?

Current environment that we will be migrating:

NPM 12.0

NCM 7.5

NTA 3.11

IPAM 4.3.2

VNQM 4.2.3

Some modules are dated but we will be upgrading to NPM 12.2 within the next 3-4 weeks, post-migration.

Any insight is greatly appreciated!

Top Replies

danielleh over 6 years ago in reply to danielleh +1

Also, here are some end-user tips on when to execute the config wizard plus some additional insight when migrating to another server: Migration to another server : When to execute the Config Wizard ?

0 danielleh over 6 years ago

Hi mbrandon32 - These articles should help get you started:
Migration Guide - SolarWinds Worldwide, LLC. Help and Support
Orion multi-module system guidelines for a SolarWinds NPM installation - SolarWinds Worldwide, LLC. Help and Support
Cancel
Vote Up 0 Vote Down

Cancel
0 danielleh over 6 years ago in reply to danielleh

Also, here are some end-user tips on when to execute the config wizard plus some additional insight when migrating to another server: Migration to another server : When to execute the Config Wizard ?
Cancel
Vote Up +1 Vote Down

Cancel
0 mbrandon32 over 6 years ago in reply to danielleh

Danielle,
This is exactly what I was looking for. Thank you so much!
- Mike
Cancel
Vote Up 0 Vote Down

Cancel
0 bourlis over 6 years ago

Mike,
I would highly suggest you upgrade first and then migrate. Believe me it would be a lot easier!! The new installer is a "one shot - one kill" kind of approach. It installs all software packages, updates and hotfixes all at once. You don't really have to worry about what to install first. Plus if you have Additional Web Engines or Additional Polling Engines you simply download the installer from NPM and run that on different systems and sit back and let it do it's thing.
Cancel
Vote Up 0 Vote Down

Cancel
0 mbrandon32 over 6 years ago in reply to bourlis

We need to migrate first because our current environment is running on 2008 R2, which is not compatible with NPM 12.2
Cancel
Vote Up 0 Vote Down

Cancel
0 elliott.humphrey over 6 years ago in reply to mbrandon32

Mike, I believe Solarwinds recommended approach is to install the latest versions of Solarwinds products that 2008 R2 supports. Then migrate over to the new server and then you can finish off upgrading to the latest versions at a later date.
Cancel
Vote Up 0 Vote Down

Cancel
0 mbrandon32 over 6 years ago

All,
I wanted to thank each of your for your input on this. The migration was successful.
I ended up running the config wizard after each module install, as they are a little older and didn't want to chance it. Although, I did end up upgrading to NTA 4.2 and bringing the NTA Flow Storage Database online for the first time.
The only issue I ran into was during the NCM install. An error was thrown during the compatibility checker stating:
"An unsupported version of the SAM Database has been detected on the following databases: NetperfMon. Continuing will result in the Configuration Wizard failing. Please contact SolarWinds Support who will provide you with the necessary tool to correct this."
I wasn't around for this but I'm guessing we previously ran a version of SAM - which we no longer have - and the tables were still present in the database. This should've been removed long ago, when SAM was removed, but that never happened. Support ended up running the script found here - Upgrade issue "An unsupported version of the SAM Database has been detected on the following databases..." - SolarWinds … - which cleared the issue.
Thanks again,
Mike
Cancel
Vote Up 0 Vote Down

Cancel