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

Handle Microsoft Availability Group failover

The support for a Microsoft availability group (SQL Cluster) needs to be improved. When running thru the configuration wizard I do not have to specify which node of the availability group the SQL database for NPM is running on. However, when I fail the database to the other Availability group member the database connection fails. I then have to re-run the configuration wizard and remove the node name from the database connection string (the wizard must add this info when validating the connection). Once I do this and run thru the wizard again it works properly until the group is failed over again.

Find more posts tagged with

Status: None

Comments

chad.every

Agreed. This is some info I heard about Orion and SQL AAG.

Orion does work with Always On Availability Group with the caveat that it leverages Microsoft OLEDB connections to the DB. This is currently the least compatible connection method for AAG. The best work around is to use DNS Aliasing as the connection string in the Configuration Wizard as opposed to SQL VIP IP. More info on OLEDB can be found here.

sum_giais

I use local host file edits to point my Orion servers to the SQL AG vIP. Not sure if I'm just lucky but I've failed over numerous times without issue on my AG (and SQL cluster previously too). The SQL cluster would have about a 15 second blip, and AG I really haven't noticed any yet.

aLTeReGo

is was implemented in Core 2017.3

mivy00

Hey aLTeReGo,

I was reading through the release notes for Core 2017.3 (See Below) and I dod not see where SolarWinds addressed this issue. Can you point me to another link that shows they have corrected it?

NPM 12.2 Release Notes - SolarWinds Worldwide, LLC. Help and Support

Matt