Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > How to rebuild SolarWinds High Availability

How to rebuild SolarWinds High Availability

Updated August 3, 2018

Overview

Here is a quick run-through on the steps to rebuild SolarWinds High Availability (HA). Some examples of when you might need to rebuild HA due to failovers not occurring, incorrect service member types, or problems making members active. 

Environment

  • Orion Platform 2018.2 or later
  • NPM 12.3 or later

Steps

This procedure involves updating to the Orion database. SolarWinds recommends backing up your database before proceeding. See Backing Up, Restoring, and Migrating Your Orion Database.

SolarWinds strongly recommends that you back up your registry before making any edits to your system registry. You should only edit the registry if you are experienced and confident in doing so. Using a registry editor incorrectly can cause serious issues with your operating system, which could require you to reinstall your operating system to correct them. SolarWinds cannot guarantee resolutions to any damage resulting from making registry edits.

Details

Globally disable and rebuild HA

  1. Back up the registry on the Primary and Secondary servers.
  2. Log in to the Orion Server.
  3. Open Services.msc on the Primary server.
  4. Stop the HA service to prevent others from writing to the database while you are rebuilding HA.
  5. Repeat step 2 through step 4 on the secondary server. 
  6. Open a command prompt and navigate to the default Orion directory located at:
    C:\Program Files (x86)\SolarWinds\Orion 
  7. Execute the following command to disable HA across all servers: 
    HAEnableDisable /DisableHA
  8. Use the Database Manager to run the following SQL query and truncate the following HA tables:
    Truncate table  HA_Pools
    Truncate table  HA_PoolMembers
    Truncate table  HA_PoolMemberInterfacesInfo
    Truncate table  HA_FacilitiesInstances
    Truncate table  HA_ResourcesTypes
    Truncate table  HA_ResourcesInstances
  9. Check the High Availability registry on the Orion server and all Additional Polling Engines (APEs).
    1. Launch the Registry Editor.
      Open a command prompt and execute:
      regedit.
    2. Navigate to:
      HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > SolarWinds > High Availability
    3. Examine the InstallType and RunType values and double-click them to update (if necessary). Verify the following:
      • On the active primary polling engine, both InstallType and RunType values must be MainPoller.
      • On the standby primary polling engine, both InstallType and RunType values must be MainPollerStandby.
      • On an active APE, both InstallType and RunType values must be AdditionalPoller.
      • On a standby APE, both InstallType and RunType values must be AdditionalPollerStandby.
      • Restart the SolarWinds High Availability Service on the primary server.
  10. On the Orion server (which serves as the main polling engine), check the registry to ensure it displays the proper values for its respected member type of the pool (in this case, MainPoller, MainPollerStandby, and so on).
  11. Restart the SolarWinds High Availability service on the second server.
  12. On the second server, check the registry to ensure it displays the proper values for its respected member type of the pool (AdditionalPoller, AdditionalPollerStandby, and so on)

    If you have servers beyond the main and standby servers, repeat these steps to restart the SolarWinds High Availability service and check the register for each server.

  13. Open a command prompt in the default Orion directory located at:
    C:\Program Files (x86)\SolarWinds\Orion)
  14. Execute the following command to re-enable HA globally: 
    HAEnableDisable /EnableHA
  15. In the Orion Web Console, navigate to the High Availability Deployment Summary page.
  16. Check the status of the pool member in the Orion Web Console.
    The pool member should be up and running with a Green status. 

Verify that HA is running  

  1. Start the Database Manager.
  2. Add the default Server.
  3. Navigate to the HA_PoolMembers table.
  4. Rght-click the table and select Query table.
  5. Click Execute query.
  6. Make sure the servers exist.
  7. Verify that in PoolMemberType, there is both MainPoller and MainPoller Standby, and AdditionalPoller and AdditionalPollerStandby.
    HA_Error5_DatabaseManager.png

 

 

 

Last modified

Tags

Classifications

Public