nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Migrating the SolarWinds database to a different or second Orion platform/environment

bootneck1111

Hi Guys

We have 2 Orion environments, 2 separate instances.

The current Main Production platform (On-Prem) is on 2016 Servers (MPE, 6xAPEs, 4xWeb)

We have provisioned new 2022 servers in our 'Test/BCP' environment and want to test SW.

We have Restored a copy of the SW-DB into the Cloud, and now want to connect the Test/BCP 2022 Orion Polling Engine to the Restored copy of the SW-DB, so that we can test and make sure that there are no issues with the 2022 servers.

When running through the Configuration Wizard, we point the BCP Orion 2022 MPE to the Restored copy of the SW-DB in the Cloud, and we receive the below message;

**Couldn't connect to database SolarWindsOrion!

The database is not an SolarWinds Platform

database or configuration is not finished.**

I'm not sure this is the correct way because we're trying to connect the BCP (2022) Orion MPE, to a copy of the Main Production DB

Any advice would be grateful.

Find more posts tagged with

Accepted answers

osvict

my recomendations will be use, database backup, clean servers with the same IP same name, turn off the old ones and install from scrash, in case the upgrade fail, restore de database and turn of the old servers.

bijuk

@bootneck1111 Please do the below tests are successfull.

1. telnet the DB port from your main poller, (If perfect move on to next)

2. Make sure your DB is confifured to accept the request from the Poller IP (allow remote conn)

3. Update the New IP on DB config.

4. test with user credentials that can be successfully connected from local server and main poller and check the difference.

5. If all test successfull then, run the conf wizard again.

All comments

jmodjeski

There is a migration plan required to Upgrade from older versions of Orion 2020 and before to Orion 2021 and newer.

https://documentation.solarwinds.com/en/success_center/orionplatform/content/install-centralized-upgrade-primary-server.htm

ecklerwr1

I'm going to be doing an Orion 2020.2.6 to HCO 2024.x.x upgrade soon myself. Fingers crossed it'll go pretty smoothly.

bootneck1111

We are already running Orion 2024.2 on our environment.

We need to connect one Primary Polling Engine to the database from our secondary SolarWinds Polling Engine in a different environment.

MMinion24

check the backup, that you are restoring from

osvict

good luck!

jokerfest

oh wow, best of luck!

bijuk

@bootneck1111 Please do the below tests are successfull.

1. telnet the DB port from your main poller, (If perfect move on to next)

2. Make sure your DB is confifured to accept the request from the Poller IP (allow remote conn)

3. Update the New IP on DB config.

4. test with user credentials that can be successfully connected from local server and main poller and check the difference.

5. If all test successfull then, run the conf wizard again.

bootneck1111

Hi Guys

Thank you for your input.

We have run through some of the new migration process on the new servers, new hostnames, and running the PS-Script to update a new IP.

We then used SQL Studio to connect to the restore/copy of the DB and couldn't connect, but after updating the SQL credentials, and granting permissions, we were able to see the DB restore and browse tables etc.

We then run through the Config-Wizard on the New Polling Engine, pointed the instance to the DB Restore, and the Config Wizard completed successfully.

We now have 2 SolarWinds Orions instances running side-by-side, the original on the 2016 servers (on-prem), and the secondary on the 2022 servers (on=prem) but the SW-DB is on Google Cloud GCP. The reason for this is because later on down the line we'll be moving over to SolarWinds HCO, and eventually host 2 SW Main Polling Engines in GCP, side-by-side (HA), with APEs & scalability Engines located in remote sites.

We are going to deal with licenses this week, using a 30-free temporary license to enable us to Test Orion in the new environment, then looking at completing the migration over the next 10 days.

I'm going to run another Restore, or create another restore copy of the SW-DB late next week getting the data-set current, and then shortly followed by the below tasks.

We'll firstly transfer the Module Licenses across to the new polling engine which should automatically run the install.

Test functionality, Observability, and Configuration after the following tasks.

Restore DB and Grant Permission to SolarWinds_Monitoring SQL account
Run scripts to replace all old hostnames of APE’s and AWS’s.
Run Configuration Wizard on MPE
Run Configuration Wizard on APE’s
Run Configuration Wizard on AWS’s
Fix License store (use temp license)
Check if all APE’s are UP and running.
Mute Alerts***
Check all Modules if they are added to the instance
Update KIWI NG Rules to new APE IP addresses
Fix all scripts and Automation
Migrate SFTP monitoring
Test all modules
Install new SSL cert
Check Deployment Health
Migrate License
Decom OLD instance