Network Management

Orion DB on SQL AlwaysOn Cluster does not reconnect after failover

The Orion database does not reconnect after a SQL cluster fails over to a secondary node in the group.

First published date

10/15/2018 8:29 PM

Last published date

9/22/2023 6:48 PM

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.

Product section

Network Performance Monitor

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 Configuration Wizard rather than physical instance or Availability Group listener.
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.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.