Migration to new Orion/Solarwinds infrastructure

davidb35467

We are well and truly behind int he versions of the modules and the core infrastructure (OS and SQL versions) and therefore we are planning to rebuild from the bottom up our Orion infrastructure, upgrade to the latest Solarwinds modules and make use of SQL AlwaysOn cluster.

We are currently on versions:

SolarWindsOrion Platform 2016.2.100, VNQM 4.2.4, IPAM 4.3.2, SAM 6.3.0, DPA 10.2.0, NCM 7.5.1, IVIM 2.1.2, QoE 2.2.0, NetPath 1.0.1, NPM 12.0.1, NTA 4.2.1

Reasons for this include complete refresh is we are not happy with the original deployment of the Orion infrastructure, its geographical location to our evolved infrastructure and the current versions we are running:

We would like to build out a completely new environment making use of:

1. Windows Server 2016
2. SQL AlwaysOn cluster 2017
3. Start from a clean slate when it comes to:
   1. Alerts
   2. Application Monitoring
   3. IPAM
   4. NCM
   5. Accounts, groups and permissions
   6. Views
   7. etc etc

No configs, databases or alerts will be copied over, we are starting from scratch!

What we would like is for the old and new environments to run in parallel

Question i have is around how best to migrate the monitoring of our servers etc so as to avoid any downtime between monitoring but still allow us to migrate in a controlled and sensible fashion.

Can we use two completely separate Orion infrastructures to query the same servers, at the same time?

Can we use WMI to poll the same servers twice by two completely separate Orion servers?

Has anyone else migrated/cut-over to a completely new infrastructure like this?

Any gotcha's?

serena

davidb35467  wrote: We are well and truly behind int he versions of the modules and the core infrastructure (OS and SQL versions) and therefore we are planning to rebuild from the bottom up our Orion infrastructure, upgrade to the latest Solarwinds modules and make use of SQL AlwaysOn cluster. We are currently on versions: SolarWindsOrion Platform 2016.2.100, VNQM 4.2.4, IPAM 4.3.2, SAM 6.3.0, DPA 10.2.0, NCM 7.5.1, IVIM 2.1.2, QoE 2.2.0, NetPath 1.0.1, NPM 12.0.1, NTA 4.2.1 Reasons for this include complete refresh is we are not happy with the original deployment of the Orion infrastructure, its geographical location to our evolved infrastructure and the current versions we are running: We would like to build out a completely new environment making use of: Windows Server 2016 SQL AlwaysOn cluster 2017 Start from a clean slate when it comes to: Alerts Application Monitoring IPAM NCM Accounts, groups and permissions Views etc etc No configs, databases or alerts will be copied over, we are starting from scratch! What we would like is for the old and new environments to run in parallel Question i have is around how best to migrate the monitoring of our servers etc so as to avoid any downtime between monitoring but still allow us to migrate in a controlled and sensible fashion. Can we use two completely separate Orion infrastructures to query the same servers, at the same time? Can we use WMI to poll the same servers twice by two completely separate Orion servers? Has anyone else migrated/cut-over to a completely new infrastructure like this? Any gotcha's?

I'd recommend you take a look at this product blog post that helps you minimize your downtime during migration.

How to Migrate Orion to a New Server With Zero Downtime

Yes, you can use 2 separate orion infrastructures to query servers, many customers do that to have a running proof of concept before they decommission.