Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Network Performance Monitor (NPM) > Migrate the SolarWinds Orion SQL database to a new server

Migrate the SolarWinds Orion SQL database to a new server

Last Updated: 3-28-2017 | Migration Guide

Supports: NPM, SAM, NCM, NTA, and all other SolarWinds Orion products using the SQL database
 

This guide details how to migrate your SolarWinds Orion SQL database to new hardware. You can also upgrade your database to a new version as needed for changing Orion product requirements and supported SQL versions. Migrating allows you to keep all relevant data and history without having to start with a fresh database on a new server. You should always migrate to a dedicated server, physical or VM.

 

You may need to migrate if...

  • The database shares a server with a poller or other products
  • The database is encountering performance and disk space issues
  • The supported version and requirements for the database have changed

We recommend always using a dedicated server for the SolarWinds Orion SQL database. You should not migrate the SQL database to servers already in use.

We recommend using SQL Server Authentication with the sa login and password to ensure that Orion can always access the SolarWinds Orion database, even if it is hosted remotely on a separate server.

To upgrade without migrating to a new server, see Upgrade the Orion SQL server version without migration.

Prepare your new server

Before backing up data, make sure to prep your new server. If you are migrating or upgrading products, you should plan that migration with your database migration.

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.

You can also review this article for specific Microsoft SQL Server versions per Orion Platform product versions.

2. Gather credentials Gather the local admin credentials for the current and new server
3. Install SQL Management Studio Express (optional)

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 SQL database to the new server

We recommend discussing database migrations with a DBA. You should also schedule a maintenance window to migrate, during non-peak hours (recommended), and notify your company when taking services offline to migrate.

When you migrate your database, your services are down and not collecting polling data.

Do not uninstall the Orion SQL database instance on the original Orion SolarWinds server because this causes issues with the Orion server and settings.

1. Stop Orion services Open the Orion Service Manager, and stop all services except the SQL service. The SQL Service needs to be running to make the necessary changes to the database.
2. Back up the SQL database

Back up your SolarWinds Orion SQL database. If you need help, please check your vendor's site for documentation and instructions.

If you have your database on a VM, create a snapshot or copy of your 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.
3. Restore the database to the new server

Copy and restore the database to the new server. Do not install the database on the same server as your Orion Platform products.

If using the SQL Management Studio Express, do the following:

  1. Open SQL Management Studio on the new SQL server and connect using your SQL administrator account.
  2. In the Object browser, right-click Database, and click Restore Database.
  3. Locate the SolarWinds database backup file and then click OK.

4. Run the Configuration Wizard on all servers

Perform the following instructions on all servers in your Orion Platform environment to update the location for the Orion SQL database:

  • Main Orion server (main polling engine)
  • Every Additional Polling Engine
  • Additional web server

If you are using a custom port for your SQL server, see Using Orion with a MS SQL server listening on a custom port.

  1. Run the Configuration Wizard to update the database location.
  2. Select Database, click Next. Specify your new database server in the SQL Server field.
  3. To use SQL authentication, select Use SQL Server Authentication, provide the SA account credentials, and click Next.
  4. Select Use an Existing Database and select or type the existing database name, and click Next. If you are prompted to use the existing database, click Yes.
  5. Select Create a New Account, and provide a New Account name. Creating a new account ensures that Orion has required access to your migrated database. The New Account must be a member of the securityadmin server role. The sysadmin role and the sa user account are always members of securityadmin.
  6. Provide and confirm an account Password, and click Next. Click Finish to complete the update.
5. (Optional) Update the SolarWinds Orion SQL server in the NTA Flow Storage Database

(Optional) If you have NTA Flow Storage Database in your environment, adjust the SolarWinds Orion SQL database server in the NTA Flow Storage Database Configurator. To configure, point the NTA FastBit service to the new SQL server. Enter the new information for the SQL server and/or database instance.

File:Success_Center/New_Articles/Release_Notes_CHM_Import_Area/Upgrade-Mindtouch-CHM/010/migrations-NTA-DB-config.png

6. Start services Start your services on the main and additional polling servers.

Results:

The SolarWinds Orion SQL database should display the new web server.

Learn more...

 

Last modified
13:18, 4 Apr 2017

Tags

Classifications

Public