Migrate the SolarWinds Platform database to a new server
Last Updated: March 23, 2021 | Migration Guide
Supports: NPM, SAM, NCM, NTA, and all other SolarWinds Platform products using the SQL database
This guide details how to migrate your SolarWinds Platform 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
- Always use a dedicated server for the SolarWinds Platform database. You should not migrate the SQL database to servers already in use.
- Use SQL Server Authentication with the
salogin and password to ensure that Orion can access the SolarWinds Platform database, even if it is hosted remotely on a separate server.
How do I migrate?
Task 1: Prepare your new database server
If you are migrating or upgrading SolarWinds Platform products, plan the migration of your SolarWinds Platform 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 SolarWinds 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 SolarWinds 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 SolarWinds Platform database and then repeat the steps for the Log Analyzer database. (recursive snippet)
Do not uninstall the SolarWinds Platform database instance on the original Orion SolarWinds server because this causes issues with the SolarWinds Platform server and settings.
|1. Disable your High Availability pool (if HA is deployed)||
If you have deployed High Availability (HA), disable the HA pool.
|2. Stop SolarWinds Platform services||Open the SolarWinds Platform Service Manager, and stop all SolarWinds services.|
|3. 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 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:
|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 SolarWinds Platform products.
5. Run the Configuration wizard on all servers
Perform the following instructions on all servers in your SolarWinds Platform environment to update the location for the SolarWinds Platform database, starting with the main 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.
|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.
The SolarWinds Platform database should display the new web server.
- Review our database best practices for helpful maintenance tips.
- If you are upgrading, check the SolarWinds Upgrade Guide.