Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.

 

Home > Success Center > Network Performance Monitor (NPM) > Migrate SolarWinds products to a new server using the same IP and hostname

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

Last Updated: 6-7-2016 | Migration Guide

Supports: NPM 12.0, SAM 6.2.4, NCM 7.5, NTA 4.2, SRM 6.3,  and later versions for Orion Platform products

Learn how to prepare your server and migrate products to a new server while keeping the same IP and hostname of the current server. 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 in this migration. Agents continue to run without noticing a change in server if the IP and hostname remains the same.

Use these instructions if you are migrating any of our SolarWinds products, including NPM, SAM, NCM, and NTA.

If you are upgrading as part of your upgrade, make sure to review the SolarWinds Upgrade Guide and the release notes for your products.

We recommend this option as the easiest for migrations, with the least amount of changes within Orion.

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

Prepare your new server

Before backing up data or installing a product, you must prepare your new server. If you are migrating the SolarWinds Orion SQL database or NTA Flow Storage Database, you should plan that database migration with your product migration.

Migrating the Orion SQL database? You need to complete the SQL migration before migrating products.

1. Prep new hardware for the migration

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

Review the minimum SolarWinds Orion platform requirements, multi-module guidelines, and specific product requirements (see release notes and admin guides) for your product.

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.

During migration, SolarWinds recommends backing up your database. If you need software to perform database backups and maintenance, you can install SQL Management Studio Express for your specific version of Microsoft SQL on your Orion SQL database server.

Use one of the following links to download the installation:

Migrate your product to the new server

Follow these step-by-step instructions to install your products 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. Stop services Keep the new server powered down. Stop services on the original polling server.
2. Backup files (Optional)

(Optional) If you use Report Writer reports (NPM 10.5 and 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
3. 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 using the SQL Management Studio Express, do the following:

  1. Open the SQL Management Studio Express on the Orion SQL server using your Windows credentials.
  2. From the Object explorer, expand Databases and locate the SolarWinds (Orion) database.
  3. Right-click on the Orion database and select Tasks then Backup. 
  4. Create a backup of your SolarWinds SQL database.
4. Release the product license
Orion Platform 2016.2 and later products

In Orion Platform 2016.2 and later (example NPM 12.0.1, SAM 6.3), you must use the web-based License Manager when migrating your main Orion server. When migrating an Additional Polling Engine or Additional Web Server, deactivate the license through the main polling engine.

  1. Log in to the Orion 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.

 

Orion Platform 2016.1 and earlier products

Release the product license on the original server. In certain products, you can deactivate licenses through the product internal licensing tool. Or you can use the License Manager.

  1. Start the License Manager from the SolarWinds Program group.
  2. Select your product in the License Manager, and click Deactivate.
  3. Complete the deactivation wizard. If you are online, the deactivation file is handled for you through the wizard.

If you are offline, you need to 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.

The deactivated licenses are now available to activate on a new server.

5. Power up the new server Power down the original server and power up the new server with the same IP and hostname.
6. 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 fo your upgrades. Point to the SolarWinds Orion SQL database and (optional) configure the NTA Flow Storage Database.

Need more information? Check our SolarWinds Upgrade Guide.

7. Enable the product license
Orion Platform 2016.2 and later products

In Orion Platform 2016.2 and later, you must use the web-based License Manager when migrating your main Orion server. If you are migrating an Additional Polling Engine or Additional Web Server, activate the license through the main polling engine and assign it to the correct new server.

  1. Log in to the Orion 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 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.
Orion Platform 2016.1 and earlier products

Enable the product license on the new server.  In certain products, you can activate licenses through the product internal licensing tool. Or you can use the License Manager.
To activate using the License Manager:

  1. First, visit the Customer Portal License Management section.
  2. Browse to your product, and click the + icon. Copy your Activation Key.
  3. Start the License Manager from the SolarWinds Program group.
  4. Select your product in the License Manager, and click Activate.
  5. In the Activation Wizard, select that you have Internet access.
  6. Enter your Activation Key for the product and complete the process following the prompts and options.

If you are offline, you need to complete a few extra steps:

  1. In the Activation Wizard, select This server does not have Internet access, and click Next.
  2. On the Activate Product screen, click Copy Unique Machine ID. Paste this data in a new document using a text editor. Save the file as a .txt document.
  3. Transfer the document to a computer with Internet access or to a shared location to access from a computer with access.
  4. Through the Customer Portal License Management section, click Manually Register License.
  5. Provide the Unique Machine ID from the .txt file. Download and move the license key to the offline computer.
  6. Run the Activation Wizard, browse and select the key from the Activate Product window.

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

Copy other files as needed

(Optional)

(Optional) 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

You will need to upgrade the report schemas in the new install. Updating the report schemas allows Report Writer to display and use custom property information.

  1. Keep the Report Writer closed. In Windows, click Start > All Programs > SolarWinds Orion > Advanced Features > Custom Property Editor.
  2. Right-click on the toolbar, and then click Customize.
  3. Click the Commands tab.
  4. Click the Properties in the category list.
  5. Drag Update Report Schemas to the toolbar to add a new button to the toolbar.
  6. Close the Customize window.
  7. Click Update Report Schemas on the toolbar.
  8. Click OK after the custom properties have been added to the report schemas.
  9. Close Custom Property Editor.

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

Results

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

 

Cleaning up

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.


 

Last modified
13:41, 2 Mar 2017

Tags

Classifications

Public