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

Help Migrate from on prem to azure

comethru2000

Hi,

I figure i post this again. I am trying to figure out what is the best method of migration? We have a very old version of SolarWinds, and I would like to move it into a Windows Server 2019. I have not done a migration like this before, so I was wondering. Here is my current setup:

CURRENT Platform: On-Prem Orion platform 2018.2 HF6

Orion Platform 2018.2 HF6, SRM 6.7.0, SAM 6.7.0, DPAIM 11.1.0, NCM 7.8, VMAN 8.3.0, NetPath 1.1.3, NPM 12.3, NTA 4.4.0, WPM 2.2.2

Windows Server 2012 (Main Polling Engine)

Windows Server 2012 (Additional Polling Engine / different network)

SolarWindsOrion DB – Windows Server 2012 with SQL Server 2014

NTA Flow DB – Windows 2012 with SQL Server 2017

Ideal Platform: Azure with Orion 2019.4

NTA, NCM, NPM, SAM, WPM, (2019.4)

Windows Server 2019 – Main Polling Engine

Windows Server 2019 – Additional Polling Engine

SolarWindsOrion DB – Windows Server 2019 with SQL Server 2017

NTA Flow DB – Windows 2019 with SQL Server 2017

Can I install a 2019.4 Orion platform in Azure (windows server 2019) and transfer the existing database? Does it work like that?

I am using this as a baseline for compatibility reasons:
https://support.solarwinds.com/SuccessCenter/s/article/Windows-Server-2012-2016-and-SQL-Server-2012-...

Or do an in-place upgrade (MPE and APE) on my 2012 boxes to 2016, then migrate to Azure, since my modules are an older version?

Or is there a better method?

Any advice would be greatly appreciated.

Find more posts tagged with

Accepted answers

dgsmith80

Personally I would upgrade and migrate at the same time as inline upgrades for Windows can be problematic and your versions should work fine on newer versions of Windows already (might want to check that to be safe)

If you follow the server migration guide in Success Centre you can just spin up new servers in Azure and then follow the migration steps to exit the DB with new hostnames etc.Copy the DB to the new SQL Server (I’m assuming your using a Windows EC2 running SQL rather than AzureSQL? As that might need different steps)
Then install the latest version on your new server and let the config wizard perform the upgrade to the DB Structure.

All comments

dgsmith80

DRXEONPHSA

Can you please refer to the URL on the success center where it guides the steps to take?

Thank you