High Availability 2.0 provides the first peek into supporting redundancy for Orion across subnets. This was previously referred to WAN deployment or Disaster Recovery with the Failover Engine, but under High Availability we refer to this simply as a multi-subnet failover configuration. In other words, this provides the same automated, near instantaneous, failover and recovery mechanisms as High Availability does in its first release, but extends that functionality to support pollers spread across different subnets. Those could be different sites, a dedicated disaster recovery location, or possibly even the cloud.
When installing the Primary Orion server you will follow the normal 'Advanced' installation process that you would for any other Orion product. Ensure not to select the 'Express' install option during installation, as a separate server running Microsoft SQL 2012 or later is required. When the Configuration Wizard runs you will be prompted to provide the Username, Password, and IP address of the SQL server you will be using for the installation.
Once the primary server is up and running using the NPM 12.2 installer, you will need to perform a similar installation on the secondary server using the separate High Availability installer which can be downloaded from within the Orion web interface under [Settings -> All Settings -> High Availability Deployment Summary -> Setup A New HA Server -> Get Started Setting Up a Server -> Download Installer Now].
Download the High Availability Secondary Server Installer
Next, execute the installation by double clicking on the "SolarWinds-Orion-Installer.exe" downloaded or copied to the secondary server. Enter the IP address of fully qualified domain name (FQDN) of your main Orion server, along with 'Admin' or equivalent credentials used to log into the Orion web interface and click 'Next'. On the following step of the Wizard, select the additional server role you wish to install. Since this will be a High Availability Backup for the main Orion server, select 'Backup Server for Main Server Protection' and click 'Next'.
Enter IP of Main Orion Server & Provide 'Admin' Credentials
Select Server Role to Install
Once the Installation completes the Configuration Wizard will be started. When prompted to provide information regarding the SQL server database, ensure you utilize the same SQL instance and SQL database that was chosen for the primary Orion server.
The following video, while arguably boring to watch, demonstrates the secondary server installation process.
As soon as both the primary and secondary servers are installed, return to the Orion web interface under [Settings -> All Settings -> High Availability Deployment Summary]. There you will be able to join the two servers into a multi-subnet failover pool.
|Click 'Set up High Availability Pool"|
|Enter a Virtual Hostname and click 'Next'|
|Select your DNS Server Type|
Enter the IP Address of your DNS Server, the DNS Zone (E.G. solarwinds.com) and administrative credentials to the DNS server to create the shared virtual hostname
If you are running BIND DNS, enter the IP address of your BIND DNS server, the DNS Zone, your TSIG secret key name, and the TSIG shared secret key value.
Once complete, review the summary and click "Create Pool"
When done, you will have pooled two Orion servers together across multiple subnets into a redundant, high availability pool
The following short video walks through this process in under a minute.
What will be the Database failover requirements? If I failover to a data center in another geo or the cloud, do I need to rely on MSSQL availability groups for replication? Or does the HA solution replicate the database to another instance?
High Availability 2.0 and Orion 2017.3 support SQL AlwaysOn Availability Groups in a multi-subnet failover configuration. This would be the recommended method for providing redundancy to your Orion SQL database.
Thanks a lot for sharing this.. makes it more easier to understand and implement.
One query on the Virtual hostname part. What all communication on ports needs to be allowed towards/from it? The pre requisites for monitoring any device will have to be opened towards both Primary and Secondary right OR even towards the Virtual host name. If any link is there then please send me that so that i will directly refer that.
For Bind, updating the DNS name is performed over port 53. For WIndows DNS, updating the virtual hostname is done over WMI. In either case, this needs to be allowed from both members of the pool.
is there a description somewhere of how the DNS interaction works? All of the documentation and links are on screenshots of an actual NPM12.2 install which makes it hard to figure out what rights are needed.
Today with the FoE we're running a nsupdate script that adds and removed the IP addresses of the polling engines from a zone, but since we explicitly say what to do, it just works, and I can test it outside of the FoE.
i.e. nsupdate primary.txt
update del app.swo.local A
update add app.swo.local 3600 A W.X.Y.Z
I don't know that I have a way to test what is needed with WAN-HA before I actually do a production upgrade.
yes, but for BIND.
the screen shot
Doesn't tell me what the actual DNS changes are going to be, it wants a zone, but doesn't tell me what records are going to be added or removed.
I can't click on the 'What changes will be made' link until I've done the install, which makes planning harder
I am concerned about it asking for a username and password for setting up access control -- I already have that bit working for an existing domain, I assume I can leave it blank and it'll work?
I've opened a support case asking technical support for the information as well.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.