About Network Pipeline

Purchase Training and Services

Hands-On Training Schedule

Register For Class

Training - Deployment and Best Practices Series

Consulting and Professional Services

Ipswitch WhatsUp Gold

Ipswitch Log Management

Ipswitch IMail Server

SystemTools Hyena and Exporter Pro

WUGWorX for WhatsUp Gold SQL Databases

Microsoft System Center Operations Manager

Downloads

Let Network Pipeline Help You Manage Your World
Copyright Network Pipeline Inc., 2000-2012
All Rights Reserved

Network Pipeline Inc.

Click the icon above to download a free 30 day trial

WhatsUp Gold Failover Manager

Primary and Secondary Server Configuration

WhatsUp Gold Failover Manager enables the configuration of a Primary and Secondary server both running the exact same version of WhatsUp Gold. With Failover Manager in place, WhatsUp Gold continues to collect data and run critical monitoring services during planned or unplanned downtime. Planned downtime would typically involve the Primary server being taken offline for maintenance purposes. Unplanned downtime includes situations where the Primary server encounters a performance problem or loses connectivity to the monitoring database. On such occasions, a Secondary server can be set to automatically take over the performance and active monitoring tasks of the Primary server.

Options for Failover Configuration

WhatsUp Gold Failover Manager supports multiple ways for ascertaining whether the Primary server is in a situation that requires triggering of failover.

First, the Primary Server monitors all of its component services to check for performance impairment. It can be automatically configured to failover for selected event occurrences like, say, the failure of the collection, discovery, or Alert Center services. In WhatsUpGold v14.2 and later, an additional layer of resiliency is added by providing the capability for automatic restart of a failed service as required. Often this may solve the problem without requiring failover.

Second, the Secondary Server monitors the heartbeat to the Primary server in two ways. It periodically checks if the Primary server is reachable and also monitors database updates to ensure that new data is being added at set intervals. If both of these conditions fail, it automatically takes over the monitoring tasks of the Primary server.

Lastly, the Secondary server can be manually set to become the Primary server – especially during planned downtime instances.

Check out other Ipswitch products -