WhatsUp Gold Failover Manager
Ensuring High Availability of Your WhatsUp Gold Platform

Negotiate Planned or Unplanned Downtime of your WhatsUp Gold Server without Losing Monitoring Visibility

The WhatsUp Gold Failover Manager plug-in is designed to make your network monitoring and management tasks even more resilient for high availability operation. It ensures continuous visibility into the health of the monitored infrastructure when the performance or connectivity of the primary WhatsUp Gold server is impaired. In such cases a secondary 'failover' server can be automatically set to take over monitoring tasks. WhatsUp Gold Failover Manager is fully integrated into the Alert Center for appropriate notifications and escalations.

With WhatsUp Gold Failover Manager you can:

• Set up Primary and Secondary WhatsUp Gold servers for manual or automatic failover
• Select specific event occurrences and conditions that can trigger 'failover' and 'failback'
• Ensure monitoring data protection through the support for remote database operation
• Remotely manage the failover process from anywhere on the network
• Report failover actions in the Alert Center for single console operations management
• Virtually eliminate the risk of 'dark periods' or monitoring data loss

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.

Benefits of Failover Manager

Ensuring Continuous Infrastructure and Application Visibility

• Assurance of high availability and resilient infrastructure and applications monitoring
  • Automatic failover capability ensures that a secondary system is always ready to take over if the functioning of the Primary WhatsUp Gold server is impaired
• Minimized risk of "dark periods" when there is complete lack of visibility due to failure of the monitoring system
  • Protects business operations at all times by maintaining infrastructure visibility even when the primary monitoring system is down
  • Maintains integrity of SLA (Service Level Agreement) reporting through continuous visibility of monitored infrastructure and services
• Reduced risk of monitoring data loss
  • Continuous monitoring data may be useful for historical analysis or in cases, be mandated by regulatory requirements
• Efficient and highly productive operation
  • Automation and intelligent failover and failback without the need for manual intervention
• Flexible coverage across all WhatsUp Gold component services
  • Protects against impairment to the whole WhatsUp Gold system or specific components like data collection, alerting, discovery or individual plug-in services

Powerful 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 WhatsUp Gold 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.

Intelligent Bi-Directional Failover and Failback

WhatsUp Gold Failover Manager supports intelligent bi-directional failover and failback. Once failover is triggered, the Secondary Server takes over the tasks of the Primary server. When the Primary server comes back up, it can be set to automatically 'failback' from the Secondary system, which then reverts back to standby mode. If the Primary is not set to automatically take over from the Secondary, it continues as the Secondary until a failover event transfers responsibility to it - providing true bi-directional failover capability. A network administrator can also manually set the Secondary server (that has taken over as Primary) to standby mode giving control back to the original Primary server.

Consolidated Failover Alerting in Alert Center

Each Failover action generates an event message that is reported via the WhatsUp Gold Alert Center. Manual changes in Primary and Secondary server status from "Active" to "Standby" modes generate "Informational" events. Automatic changes based on failure detection by the Primary or the Secondary server and subsequent triggering of failover action generates "Error" events. This enables WhatsUp Gold administrators to have complete visibility into the IT infrastructure and the management system from a single console. Both errors and informational events are also viewable via the Failure Workspace report for customized time intervals.

How does automated failover work?

Failover automation takes place using a "heartbeat" mechanism that connects the Primary and Secondary server. As long as a regular "pulse" or "heartbeat" connects the main (Primary) server to the second (Secondary) server, the latter does not initiate its systems.

The Secondary server takes over the work of the first server as soon as it detects and validates an alteration in the "heartbeat" of the first machine. Alternatively, an intelligent primary system can request the secondary server to take over its role, if it detects issues with its own functioning.

Which versions of WhatsUp Gold does Failover Manager support?

WhatsUp Gold Failover Manager supports all WhatsUp Gold versions - Standard, Premium, Distributed and MSP running on all current Windows operations systems.

It is important to note that both the Primary and Secondary machines need to be running the same version of WhatsUp Gold in order to operate properly.

Can WhatsUp Gold Failover be deployed as a Virtual Machine?

WhatsUp Gold and WhatsUp Gold Failover Manager can operate on virtual machines powered by VMware and Microsoft Virtual Server, as long as the virtual server's resources meet the WhatsUp Gold system requirements.

Which monitor types are supported by WhatsUp Gold Failover Manager?

WhatsUp Gold Failover Manager supports all Active and Performance Monitors.

Passive monitors like Syslog and SNMP traps are typically not supported as they require a destination IP address to be set in the monitored device. When the system fails over from Primary to Secondary, the WhatsUp Gold server IP address changes - and it no longer receives the messages from the devices.

For Flow Monitor, the flow sources (including Flow Publisher installations) can be configured with both Primary and Secondary IP addresses so that they route flow statistics to both destinations. The Secondary merely discards the flow records until it takes over as the Primary system.

Windows Event based passive monitors are supported by Failover as they are configured on the same host system running WhatsUp Gold and Failover.

How does WhatsUp Gold Failover Manager help protect against monitoring data loss?

The WhatsUp Gold Failover Manager deployment architecture can involve two or three separate hardware or virtual machine instances in two separate configurations. This helps guard against monitoring data loss when the functioning of the Primary server is impaired.

In the first kind of deployment architecture, the monitoring database can be hosted on the Secondary server itself. Thus loss of connectivity to the Primary system does not affect the data collection and updates to the database.

Alternate deployment architecture would involve running the Primary and Secondary servers on different hardware or virtual machine instances. The database operates on a third machine instance that is remotely accessed by either the Primary or the Secondary server.