High Availability Support
To ensure that SCOM users are able to perform end-to-end monitoring of their IT infrastructure at all times. the eG Universal MP for SCOM supports three levels of high availability.
Failover clustering of eG managers
You can have two eG managers operate within a redundant cluster, with one primary manager and one secondary manager. The eG SCOM connector embeds the intelligence to detect a cluster setup, identify which manager in the cluster is currently active, and communicate with it for performance and problem updates on eG-managed components.
Figure 1 : The eG SCOM Connector can discover and work with an eG Manager Redundant Cluster
If you want to configure a SCOM connector for a redundant manager setup that pre-exists in an environment – i.e., a redundant manager setup that was operational before connector was installed – then, post the installation, you just have to point the connector to use the primary manager's URL. The connector automatically discovers secondary managers and if there is a failure in the redundancy, it will automatically switch to the available manager.
On the other hand, if you configure a redundant manager setup post connector deployment, then, you will first have to point the connector to use the primary manager’s URL, and then, restart the eG SCOM Connector – i.e., stop and then start the eG SCOM Connector. Only after the restart will the eG SCOM connector automatically discover the secondary managers
Failover clustering of eG SCOM Connectors
You can also deploy multiple eG SCOM connectors on a Windows failover cluster. You can then register the same eG manager with each of these connectors. Even if one connector is rendered unavailable, the eG manager will continue to communicate with any of the other available connectors in the cluster to transmit problem and performance information to the SCOM console.
Figure 2 : The eG SCOM Connector can be installed on a Windows failover cluster
Failover clustering of SCOM management servers
High availability can also be ensured by configuring two SCOM management servers to operate in a cluster. The eG SCOM connector should be configured to communicate with both the management servers in the cluster. If this is done, then, if the primary SCOM management server is unavailable, the eG SCOM connector will be able to intelligently detect unavailability of the primary, identify which is the secondary management server, and automatically connect to that server to transmit performance updates.
Figure 3 : A single connector communicating with clustered SCOM management servers