Can I point NPM 10.4.x to SQL DB from previous NPM 10.1.2 installation?

Question

Hi all,

I currently have NPM 10.1.2 and I need to upgrade to 10.4.x.

I also need to upgrade to newer hardware so I thought I would just build NPM 10.4.x from scratch on new hardware and then point it to my old NPM 10.1.2 DB. Will this work?

Will it also work for NCM, IPAM & NTA?

currently installed versions of all products are

NPM 10.1.2

IPAM v2.0

NCM 6.1

NTA 3.7

I realise that NTA 3.7 is not compatible with NPM 10.4.x so I will need to upgrade to NPM 10.3.1 first and then upgrade NTA to 3.8 and then upgrade NPM to 10.4.x.

Any advice on this would be great!

thanks

Mario

mazydizzle2K10 · Answer

Hi Jan, thanks for the reply...

reading the following KB http://knowledgebase.solarwinds.com/kb/questions/1888/Compatibility+of+SolarWinds+Orion+Products+for+Installation+and+Upgrade#npm+ it advises that NCM 6.0 is compatible right through to NPM 10.4.x. So am I right in thinking that I do NOT have to upgrade NCM 6.1 to version 7 prior to upgrading NPM to 10.4.x.

thanks

Mario

Jan_Pelousek · Answer

Hi mazydizzle2K10,

about the migration: I think the documentation you are looking for is http://www.solarwinds.com/documentation/Orion/docs/OrionServerMigration.pdf . - The migration is possible ONLY within the same version.

To the integration part: Unfortunately NTA is not the only module that should be upgraded before upgrade to NPM 10.4.

IPAM is supported since 2.0 - OK

NCM is supported since 7.0 - needs to be upgraded before upgrade to NPM 10.4

NTA is supported since 3.8 - needs to be upgraded before upgrade to NPM 10.4

I hope it helped.

bsciencefiction.tv · Answer

We did a similar thing, last April.  We needed to upgrade and move to new equipment.  We were told by support that it was necessary to upgrade the existing NPM first because the schema on the database changes.  So to my understanding you will need to upgrade in place, run configuration manager, install in the new environment and then point the new NPM to the database.  And remeber back the database up before upgrading and before moving.