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

Combining two separate Orion instances

Hello,

I am waiting to hear back from Solarwinds support but while waiting for them I was wondering if the community has ever performed what I need to get done.

We have two separate instances of Orion setup. Basically one to monitor our own company and another one to monitor all of our customers. We have gotten to the point where we would like to consolidate everything down to a single Orion instance. I saw a Support entry (Merge two SolarWinds databases - SolarWinds Worldwide, LLC. Help and Support ) that states merging two SolarWinds databases is not possible.

Has anyone had any luck with actually getting this done without having to manually re-entering all the nodes?

Thanks in advanced,

Brian

Find more posts tagged with

Accepted answers

stuartwhyte

Hi,

No, this is not possible. There are links between the element types all in different tables that are connected by ID values. If you have two databases, you will have multiple nodes with the same node ID and multiple (ie) interfaces that link to those ID's. Not to mention all the alerts and reports that will have conflicting ID's.

Your options would be limited to the following:

Exporting a list of IP addresses from one instance, and using discovery to re-import into the second instance
Using Enterprise operations Console to produce an overview of both instances. Whilst possible, I wouldn't recommend this approach as EoC is a legacy product, and hasn't evolved in line with the other Orion modules.

HTH

Stuart

All comments

stuartwhyte

Hi,

Your options would be limited to the following:

Exporting a list of IP addresses from one instance, and using discovery to re-import into the second instance
Using Enterprise operations Console to produce an overview of both instances. Whilst possible, I wouldn't recommend this approach as EoC is a legacy product, and hasn't evolved in line with the other Orion modules.

HTH

Stuart

mbird

Thanks for posting this, I'm potentially facing the same situation as the OP here. It's unfortunate that things are set up this way and there's not an easy way to import/export the database from another site. Fortunately for me they aren't very large so when the time comes it shouldn't be too painful.

bjuliano

So there is no way to migrate the nodes (with all the years of historical data associated with it) to another Orion server?

We currently have EOC but as you stated, it is an old legacy product that we do not plan on continuing with since we are looking to consolidate to one Orion server.

bjuliano

Hi Stuart,

Thanks for the response and that was what SolarWinds support reiterated to me. My Director does not like the answer as we will be losing over 5 years of historical data for about 150 nodes. Bummer.

Thanks!

Brian