Submit a ticketCall us
Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Orion DB on SQL AlwaysOn Cluster does not reconnect after failover

Orion DB on SQL AlwaysOn Cluster does not reconnect after failover

Created by Robert Stidman, last modified by Caroline Juszczak on Aug 10, 2018

Views: 1,471 Votes: 0 Revisions: 4

Overview

Some users have an AlwaysOn cluster with the Orion DB as a resident DB. Everything works on Node A of the AlwaysOn cluster, but when users failover to Node B SolarWinds reports an error.
If users re-run the Configuration Wizard, they can get Node B of the AlwaysOn cluster to work, but then failover back to Node A fails.

Environment

All Orion Core products

For product modules running on Orion Platform 2017.1 and earlier, the use of SQL AlwaysOn Availability Groups is not supported. Customers are recommended to upgrade their product modules to Orion Platform 2017.3 or later if they plan to take advantage of SQL AlwaysOn Availability Groups.

Cause 

Limitations in how we deal with SQL AlwaysOn.

Resolution

User can try to bypass Orion limitation by setting up DNS alias which points to the currently active SQL instance.
This way DNS alias will be passed to Config Wizard rather than physical instance or Availability Group listener.

 

 

 

 

Last modified

Tags

Classifications

Public