Documentation forSolarWinds Platform Self-Hosted

Migrate SolarWinds Platform products to a new server using the same IP and hostname

Last Updated: November 22, 2022 | Migration Guide

Supports: Orion Platform 2020.2.6 and earlier and SolarWinds Platform 2022.2 and later

 

  See this video: Orion Platform Product Migration With Minimal Downtime. | Read the THWACK Post

When you plan to keep the same IP and hostname of the SolarWinds Platform server after the migration, you only need to install products, move files, and import SSL certificates to the new server.

You do not need to reassign nodes or migrate agents with this type of this migration. Agents continue to run without noticing a change in the server if the IP and hostname remain the same.

If upgrading, complete the upgrades before starting a migration. Make sure to review the SolarWinds Installation and Upgrade Guide and the release notes for your products. 

If you are migrating to a new server using a new IP or hostname, see this article.

How do I migrate?

  1. Prepare the new server.
  2. Migrate your product to the new server.

Task 1: Prepare your new server for the SolarWinds Platform server

Migrating the SolarWinds Platform database, NTA Flow Storage database, or both? Complete the database migration before migrating your SolarWinds Platform products.

1. Prep new hardware for the migration

Build the new server including any changes to the architecture, hardware, and Operating System.

Review the SolarWinds Platform requirements, in multi-module guidelines, and requirements for your product (see release notes and admin guides).

Product requirements include:

For all port requirements, see Port Requirements for all SolarWinds products.
2. Gather credentials Gather the local admin credentials for the current and new server.
3. Get SolarWinds installation files Download the SolarWinds product installation files from the Customer Portal. Copy the files to the new server.

Task 2: Migrate your product to the new server

Depending on the products you migrate, you may have different steps to follow, such as importing SSL certificates and moving files.

1. Back up files (Optional)

(Optional) If you use Report Writer reports (Orion Platform 2020.2.6 or earlier) or still have legacy reports, back up the reports folder to save your custom reports:

  • 64 bit OS: C:\Program Files x86\Solarwinds\Orion\Reports
  • 32 bit OS: C:\Program Files\Solarwinds\Orion

For NCM, you may need to back up the following folders (found in C:\Program Files\SolarWinds\Orion\NCM or C:\Program Files (x86)\SolarWinds\Orion\NCM):

  • Reports
  • Config Archive
  • Scripts
  • Device Command Templates
2. Back up your database

Back up your current database before migration.

If your SQL database is on a VM, create a snapshot of the VM.

If your SQL database is on a server, you can use SQL Management Studio Express for your specific version of Microsoft SQL on your SolarWinds Platform database server. See the Microsoft article Create a Full Database Backup for details (©2019 Microsoft, available at https://www.microsoft.com, obtained on October 10, 2019).

Use the following links to download the installation for the latest version, which is backward compatible with older versions:
3. Release the product license

Use the web-based License Manager when migrating your main SolarWinds Platform server.

  1. Log in to the SolarWinds Platform Web Console.
  2. Click Settings > All Settings > License Manager.
  3. Copy and paste your activation keys to a text file that you can move to the new server.
  4. Select the product and click Deactivate.
  5. Complete the deactivation wizard.
  6. Continue until you have deactivated all your products.

If you are offline, save the deactivation receipt file, and then upload the deactivation file:

  1. Save the deactivation file from the deactivation wizard.
  2. Log in to the Customer Portal, and navigate to the License Management page. Select your product, and click Deactivate license manually.
  3. In the Manage License Deactivation page, browse for the deactivation file you created in License Manager, and click Upload.
´
4. Stop SolarWinds High Availability Service If HA is installed, go to services.msc and stop the SolarWinds.HighAvailability.Service on the old server.
5. Stop SolarWinds services Stop all SolarWinds services on the original polling server by using theSolarWinds Platform Service Manager.
6. Power up the new server Power down the original server and power up the new server with the same IP and hostname.
7. Install products

Unzip and install the new Orion product, running the Configuration wizard. If you migrate as part of an upgrade, follow the upgrade path for your upgrades. Point to the SolarWinds Platform database and (optional) configure the NTA Flow Storage database.

Need more information? Check our SolarWinds Installation and Upgrade Guide.
8. Re-initialize the license store If you are running Orion Platform 2017.3 and later, re-initialize the license store.
9. Enable the product license

Use the web-based License Manager when migrating your main SolarWinds Platform server. 

  1. Log in to the SolarWinds Platform Web Console.
  2. Click Settings > All Settings > License Manager.
  3. Copy and paste your activation keys to a text file that you can move to the new server.
  4. Select the product and click Activate.
  5. Complete the wizard and enter your activation key.

If you are offline, do the following:

  1. Select a product, and click Activate.
  2. Click Copy to Clipboard to copy the unique machine key.
  3. Log in to the Customer Portal, and click License Management > License Management.
  4. In the Customer Portal License Management, expand the product license to activate, and click Activate License Manually.
  5. Paste the unique machine id from the clipboard, and click Generate License File. Save the .lic file locally and transfer it to the offline computer.
  6. In the License Manager on the offline computer, choose the .lic file, and click Activate.

10. Copy legacy reports to the server, upgrade report schemas

Copy other files as needed

(Optional for Orion Platform 2020.2.6 and earlier)

(Optional for Orion Platform 2020.2.6 and earlier) If you use Report Writer or have legacy reports, copy the reports folder to the same directory on the new server:

  • 64 bit OS: C:\Program Files x86\Solarwinds\Orion\Reports
  • 32 bit OS: C:\Program Files\Solarwinds\Orion

Copy over other files as needed. If you have migrated NCM, you may need to merge folder contents with the following folders (found in C:\Program Files\SolarWinds\Orion\NCM or C:\Program Files (x86)\SolarWinds\Orion\NCM):

  • Reports
  • Config Archive
  • Scripts
  • Device Command Templates
11. Update PDF engine settings If you are using a third-party PDF engine to generate PDF reports and upgrade to 2022.4, update the PDF engine settings in the Registry Editor (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SolarWinds\Orion\Core\PdfEngineManager).

Results

In the SolarWinds Platform deployment, you should see the same IP and host name available, using the new server. Polling Engines do not need to be reassigned because they connect to the same IP and host name. You should not encounter issues with SNMP or WMI.

 

Cleaning up

If you were running Orin Platform 2020.2.6 products, uninstall the products from your original server to reuse the server for other needs and products.

Delete the product install zip files to save space.