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

Expand Solarwinds HA on the current environment

Hi Guys,

I would like to ask if our current environment is already have the SolarWinds deployed. The Orion platform and the Orion Database is in the same Windows server box. If we would like to expand SolarWinds HA on the other environment. But the second environment SolarWinds will be connect to the new HA database.

Note: 2 environment is different subnet. The SolarWinds HA will be connect to the VIP with the hostname.

I attached the high level design as below

My question for the will be.

1) Does this setup is valid ?

2) If we would like to setup the Database HA on our environment 2, will the Orion Platform will have problem or lost connection to the Database.

3) What will be the recommended option to do Database HA.

New Design

Please advice on this

Thanks.

Find more posts tagged with

Accepted answers

All comments

dgsmith80

Well, firstly SolarWinds do NOT recommend running SolarWinds and SQL Database on the same server for any Production environments because of scale and resiliency. If you're considering HA then it already tells me you consider your platform necessary enough to make it resilient in which case you should STRONGLY consider putting the SQL Database onto a dedicated server.

SolarWinds HA does NOT provide any HA or DA functionality for your SQL Server it will ONLY move active SolarWinds services from one server to the other. The SQL Connection string does not change during HA Failover, so whatever SQL String it was connected to in Env1, is what it will try to connect to in Env2.

To get around this you can deploy SQL Clustering or Always On which will allow for Split Node Database availability - However, that is a Microsoft function and isn't something SolarWinds provide any guidance or support for.

Hope this helps.