Documentation forOrion Platform

Migrate the SolarWinds Orion SQL database to a new server

Last Updated: November 8, 2018 | 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.

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

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 or requirements for the database have changed

Recommendations

  • Always use a dedicated server for the SolarWinds Orion SQL database. You should not migrate the SQL database to servers already in use.
  • Use SQL Server Authentication with the sa login and password to ensure that Orion can access the SolarWinds Orion database, even if it is hosted remotely on a separate server.

How do I migrate?

  1. Prepare your new database server.
  2. Migrate your SQL database to the new server.
  3. Learn more

Task 1: Prepare your new database server

If you are migrating or upgrading Orion Platform products, plan the migration of your Orin server together with your database migration.

1. Prep new hardware for the migration

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

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

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

Task 2: Migrate your SQL database to the new server

SolarWinds recommends 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.
  • If you have VMware Events Add-on installed, you need to migrate your Log Analyzer database as well. Complete the migration of the Orion Platform database and then repeat the steps for the Log Analyzer database.

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 on all Orion servers. The SQL Service (which is located in Services, not in the Orion Service Manager) needs to be running to make the necessary changes to the database.
2. Back up the SQL 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 Orion SQL 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. Disable your High Availability pool (if HA is deployed)

If you have deployed High Availability (HA), disable the HA pool.

  1. In the Orion Web Console, click Settings > My Orion Deployment.
  2. Select the pool to disable and toggle High Availability to Off.
4. Restore the database to the new server

Copy and restore the database to the new server, for example using the SQL Management Studio Express. Do not install the database on the same server as your Orion Platform products.

5. 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
  • All High Availability backup servers (if you have deployed HA)

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.
6. Start services Start your services on the main and additional polling servers.
7. Enable the HA Pool (if HA is deployed)

If you have deployed High Availability (HA), enable the HA pool.

  1. In the Orion Web Console, click Settings > My Orion Deployment.
  2. Select the pool to enable and toggle High Availability to On.

Results:

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

Learn more...