Menu

Search

LOGbinder Support


High Availability with Supercharger


bjvista
How To

With the use of Supercharger's Load Balanced Subscriptions, WEC can be setup and configured in a high availability environment. There are three areas that need to be configured for HA.

  1. Using VM replication for the VM where Supercharger Manager is installed
    • There are various ways to configure this depending on your environment.  This would be handled by your hypervisor administration team. They would configure replication of the VM where Supercharger Manager is installed. In the event of an outage, the hypervisor manages the failing and failover VM's.
  2. Modifying which WEC collectors are part of the Load Balancer in Supercharger
    • In Supercharger there are load balanced subscriptions (LBS).  One part of a load balanced subscription is the load balancer. The load balancer has multiple WEC collectors assigned to it. For HA configuration, there will be active and standby load balancers.
  3. Configuring the Target Subscription Manager to include the both active and failover collectors
    • In your GPO (see #2 here) you would include your active and standby load balancers. This does not mean that all of these collectors will automatically start collecting events. Only collectors active in the load balancer will be collecting the events.  

Use Case #1
An entire site goes down 

In the diagram below, Hypervisor A contains the active Supercharger Manager server and active WEC collectors 1 through 3. The load balanced subscription exists on the active manager. Hypervisor B hosts the replicated Supercharger Manager server and 3 WEC collectors that are not yet part of the Load Balancer.

  ​

In the event of an outage of the entire site, hypervisor technology fails over to the standby Supercharger Manager server. The Supercharger admin will edit* the load balancer in Supercharger replacing collectors 1 - 3 with collectors 4 - 6. Since these collectors are also in the GPO's "Target Subscription Manager" setting the event forwarders will begin forwarding their events to these collectors at the next refresh interval.

Use Case #2
The Supercharger Manager server goes down 

In the diagram below, Hypervisor A contains the active Supercharger Manager server and active WEC collectors 1 through 3. The load balanced subscription exists on the active manager. Hypervisor B hosts the replicated Supercharger Manager server and 1 WEC collector that is not yet part of the Load Balancer.

In the event of an outage of the Supercharger Manager, hypervisor technology fails over to the standby Supercharger Manager server. Since the hypervisor keeps the replicated server and its load balanced subscription up to date there is no need to modify the load balancer.

Use Case #3
A WEC collector goes down

In the diagram below, Hypervisor A contains the active Supercharger Manager server and active WEC collectors 1 through 3. The load balanced subscription exists on the active manager. Hypervisor B hosts the replicated Supercharger Manager server and 1 WEC collector that is not yet part of the Load Balancer.

In the event that a WEC collector has an outage (collector 3) the Supercharger admin will edit* the load balancer in Supercharger replacing collector 3 with collector 4.

 Below is a screenshot showing a load balancer in edit mode. Assuming that collector 3 were to go down, your Supercharger admin would select Collector 4 and save/update the load balancer.


On a scale of 1-5, please rate the helpfulness of this article


Not Helpful
Very Helpful
Optionally provide private feedback to help us improve this article...

Thank you for your feedback!


Still have questions - Submit a new ticket