Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Upgrading NPM (12.0.1 to 2024.02)

Hello friends,

I am running Server 2008 R2 SP1 for the main Orion and NTA pollers and have a Server 2008 R2 for my SQL server. I am upgrading:

NPM 12.0.1

NTA 4.2.0

to NPM 2024.2 & NTA 2024.1

Do I install the NPM upgrade first then install the upgrade for my NTA or should I do the NTA first? Is there anything I need to do on my SQL database side besides create backups? My Orion and NTA servers are physical in single server, Any other obstacles or surprises I should expect in this process? I'm trying to have a smooth transition. What is the migration path, Please advise.

Thank you.

Find more posts tagged with

Accepted answers

All comments

W.stanikzai

I have a fresh new server with Microsoft Windows 2022 and SQL Server 2022

vinay.by

Why do you want to upgrade it from such old versions - several things might go wrong (NPM 12.0.1 probably was EOL in 2019 or 2020 and same is the case with NTA 4.2.0). Rather it would be much simpler to install latest versions from scratch on the fresh new server that you are talking about and then onboard your stuff onto the new install.

I understand that you don't want to work on the setting your monitoring, alerting, reporting etc from scratch but then when you upgrade as well several things have been deprecated, lot of things have changed over a period of time. But yes its totally up to you.

I would have installed the new version as a parallel setup - onboard everything that is currently there on the existing SolarWinds setup and then decommission the old one and use the available license on the new install.

Its best to raise a support case if you want to upgrade the existing setup, but then if I am not wrong you will first need to go to 2020.2.X and from there you can further get into the latest versions.

Hope this helps.

__PRESENT

W.stanikzai

@vinay.by SolarWinds product upgrade advice is not accessible, it's in the customer portal, but our account is locked Is there a way to check the SolarWinds upgrade path?

superfly

https://documentation.solarwinds.com/en/success_center/orionplatform/content/install-centralized-upgrade-primary-server.htm

chad.every

+1 to what @vinay.by mentioned. There is no 'single jump' from the version you're on to the latest. There are multiple application versions you have to upgrade to in-between PLUS a few Server OS and SQL Versions that you'll also have to jump through.

The path of least resistance would be to install fresh, export a list of IPs from your current deployment and use that as a seed in Network Discovery on your new deployment. When you do a fresh install on new servers and new DB, it will automatically start a 30-day eval. If you need more time than that, then open a support case and they can provided some extended eval keys.

W.stanikzai

Fresh installation is pretty easy, but we have lots of setting, even map and more

vinay.by

'Product Upgrade advisor' is not available anymore, plus in your case it would be a multi hop upgrade firstly bring it till 2020.X and from there you move into the new world through Orion Installer (this takes care of your upgrade path). Which is why without raising a support case multiple things could go wrong.

https://solarwindscore.my.site.com/SuccessCenter/s/article/End-of-Support-Product-Upgrade-Advisor?language=en_US

https://solarwindscore.my.site.com/SuccessCenter/s/article/SolarWinds-Product-Upgrade-Advisor?language=en_US

Kita

The upgrade from 2020.2.6 is usually the most challenging. NTA and LA database are required after 2020.2.6 which was not the case in previous releases. You'll want to make sure you have access to create the database tables (especially if you have a separate DBA that manages the permissions).