Network Management

Zero-Downtime Upgrade to the Latest Version of the SolarWinds Platform

This document outlines the requirements, processes and procedures to build a new environment in preparation to migrate from a legacy platform to the latest feature packed version of the SolarWinds Platform. This guide is aimed at individuals who may be using very old and outdated software. Sometimes this may have many iterations of customization and tweaking that may no longer be needed. For example: there are many features that are standard “out-of-the-box” now which would have to be done using Universal Device Pollers in the past. In some instances, it may be preferable to migrate to a new clean environment, where database migration is not necessary.

First published date

5/27/2020 1:50 PM

Last published date

9/3/2025 2:03 PM

Overview

The guide helps you to upgrade to the latest version of the SolarWinds Platform with minimal or zero downtime.
When upgrading from an old version of the SolarWinds Platform there can be many steps to the upgrade, there may be OS upgrades and SQL upgrades also.
This process bypasses all of these by installing the SolarWinds Platform in a new environment with new database(s). The benefit of this is that both the existing legacy system and the newly installed current version can run in parallel while the new system builds up some historical data.
Once there is an ample amount of historical data stored in the new instance of the SolarWinds Platform, the legacy deployment can simply be turned off.

In some situations, it is easier to build a new instance of the SolarWinds Platform rather that upgrade from a very old version. If your SolarWinds Platform instance does not have a lot of customization (custom reports, alerts, dashboards, etc.) it can be just as easy to create a new instance rather than to go through an upgrade process. If this is the case it is possible to upgrade with little to no downtime.

Advantages of moving to a new environment

Zero downtime
Clean build
Easy migration at your own pace
Can be built using the latest OS, SQL and SolarWinds Platform modules
Node list can be taken from the legacy instance and added to the new instance using Network Discovery
Upgrading a legacy instance of the SolarWinds Platform can require multiple upgrades, OS, SQL and maybe interim SolarWinds Platform upgrades

Note:

Any custom, alerts, reports, scripting, etc. will need to be rebuilt on the new system
No Data Migration - Both systems will need to run in parallel while the new system builds up historical data

Product section

Orion Platform

Cause

How to

Resolution

Prepare the Environment

The links below provide all of the required information to enable you to ensure that your environment meets the requirements:

CPU
Memory
OS
SQL configuration
Port requirements
etc

Release notes & requirement guides for all modules

https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Install-Prepare.htm

SolarWinds Platform Requirements

https://documentation.solarwinds.com/en/Success_Center/NPM/Content/System_Requirements/NPM_2019-4_system_requirements.htm

SQL Requirements

https://documentation.solarwinds.com/en/Success_Center/NPM/Content/System_Requirements/NPM_2019-4_system_requirements.htm#Database_requirements

Multi-module system guidelines

https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-Multi-Module-System-Guidelines.htm

Install the SolarWinds Platform

Installing the SolarWinds Platform on a new environment is a simple wizard driven process. The detailed steps are outlined in the guide linked below.
https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Install-New-Deployment.htm

Licensing

Move licenses from the legacy platform to the new instance

https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-Centralized-Licensing-Move-Licenses.htm

Use the temporary license keys obtained from SolarWinds to license the legacy platform while the new system runs on your purchased licenses.

https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-Centralized-Licensing-Activate-Licenses.htm

Add nodes to new environment

Export list of node IP addresses from old database

The query below can be run from Database Manager or SQL Server Management Studio. The query returns the polling IP Addresses for all of the nodes that are currently monitored using the legacy system.

-- Scripts are not supported under any SolarWinds support program or service. 
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further 
-- disclaims all warranties including, without limitation, any implied warranties 
-- of merchantability or of fitness for a particular purpose. The risk arising 
-- out of the use or performance of the scripts and documentation stays with you. 
-- In no event shall SolarWinds or anyone else involved in the creation, 
-- production, or delivery of the scripts be liable for any damages whatsoever 
-- (including, without limitation, damages for loss of business profits, business 
-- interruption, loss of business information, or other pecuniary loss) arising 
-- out of the use of or inability to use the scripts or documentation.

SELECT IP_Address from Nodes

This will return the list of nodes that can be added to the new system.

Add nodes to the new platform

Use Network Discovery to add the nodes from the previously generated list to the new platform
https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-Network-Discovery-Using-the-Network-Sonar-Wizard-sw1574.htm

Syslog/Traps/NetFlow

If using Syslogs, Traps or NetFlow, the devices need to be configured to send the Syslogs, Traps and NetFlow data to the new hostname or IP address. Many devices permit the configuration of multiple collectors for Syslogs, Traps and NetFlow. If your devices support this, you can send the data to both the legacy and new Orion servers while the historical data is building on the new platform.

Alerts

Export and import alerts from the legacy system to the new system
https://support.solarwinds.com/SuccessCenter/s/article/Export-and-import-alerts-via-the-web-interface

Reports

Export and import reports from the legacy system to the new system
https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-Exporting-Reports-sw1547.htm

Universal Device Pollers (UnDP)

Export required UnDPs form the legacy system

https://documentation.solarwinds.com/en/Success_Center/NPM/Content/Core-Exporting-Universal-Device-Pollers-sw503.htm

Import required UnDPs to the new system

https://documentation.solarwinds.com/en/Success_Center/NPM/Content/Core-Importing-MIB-Pollers-sw512.htm

SAM Templates

Export and import SAM templates if used from the legacy system to the new system

https://documentation.solarwinds.com/en/Success_Center/SAM/Content/SAM-Templates-import-export.htm

Cut-over to new system

After a period of time when you have an ample amount of data collected and all alerts, reports, etc. are configured. The old legacy system can simply be turned off.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.