Date: Thu, 28 Mar 2024 17:47:20 +0000 (UTC) Message-ID: <1262378205.5437.1711648040384@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5436_716852046.1711648040378" ------=_Part_5436_716852046.1711648040378 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The UIM High Availability feature is not offi= cially supported by Idera. Use at your own risk.
This documentation may be inaccurate and scripts identified may be missi= ng or out-of-date. The Idera support team is unable to provide missing info= rmation, documentation, or scripts. Documentation and scripts are not updat= ed or tested.
Idera cannot guarantee that future product changes or database updates w= on't break working HA instances.
Contents=
The purpose of this article is to outline a few implementation options t= hat provide high availability to an Uptime Infrastructure Monitor environme= nt. The options shown are sample configurations that customers have deploye= d and are not the only options available. Which option to choose will large= ly depend on the desired level of availability and redundancy.
Each option has an Uptime Infrastructure Monitor instance called Sel= f Monitor. The sole purpose of Self Monitor is to monitor vit= al health and performance information of Uptime Infrastructure Monitor and = execute any self-healing actions if needed. It is tuned to consume very lit= tle resources.
The goal of this option is to ensure the availability of the production = Uptime Infrastructure Monitor instance by configuring a Self Monitor instance. Alerts will be sent out when the production instance is down o= r degraded. Moreover, self-healing actions can be performed to minimize dow= ntime of the production instance. This option will ensure the production in= stance does not silently become unavailable.
The advantage of this option is it's simple to setup and it's cost-effec= tive. The downside is it does not offer any redundancy. However, it does pr= ovide alerts and self-healing capabilities that would increase Uptime Infra= structure Monitor availability.
In addition to Self Monitor monitoring the production instance = of Uptime Infrastructure Monitor, this option consists of a Passive instance on standby. The Active and Passive instances s= hare a single database so that the configuration and historical data will b= e consistent. Self Monitor monitors whether the Active in= stance is available and when it's unavailable, Self Monitor will e= xecute actions to failover to the Passive instance by starting the= Uptime Infrastructure Monitor services. Self Monitor also monitor= s the database so alerts will be sent when it's unavailable and self-healin= g actions can be executed.
This option is in the middle of the pack in terms of availability, simpl= icity and budget-friendly. It offers redundancy by having a Passive instance of Uptime Infrastructure Monitor on standby. When needed, Uptime= Infrastructure Monitor can failover to the Passive instance. The = single point of failure is the database in this option. One needs to be cau= tious and make certain the database is backed up regularly.
This option not only has redundant instances of Uptime Infrastructure Mo= nitor, it also utilizes redundant databases. Similar to the previous option= , Self Monitor monitors the Active and Passive i= nstances of Uptime Infrastructure Monitor and the databases. The Master dat= abase is connected to the Active instance and the data is replicat= ed to the Slave database. A few failover scenarios can occur:
As with the other options, alerts will be sent out if any of the compone= nts are down or degraded and self-healing actions can be executed to attemp= t to recover prior to failover.
This option offers the most redundancy due to the pair of Uptime Infrast= ructure Monitor instances and the pair of databases. However, with redundan= cy comes complexity and cost. There is more to configure and one will need = more servers to implement such a configuration.
=
The above chart summarizes how each of the options compares to each othe= r. Any of the options can be used and/or customized to meet the requirement= s.