Intelligent Failover between Primary and Secondary WhatsUp Gold Servers
WhatsUp Gold Failover Manager provides intelligent failover capability between a
set of Primary and Secondary servers running WhatsUp Gold. Key features include
the following –
WhatsUp Gold Failover Manager Basics
- Supports all WhatsUp Gold versions – Standard, Premium, Distributed and MSP
- Supports installation on all current Windows operating systems
- Enables both automatic and manual triggering of failover from a Primary to
a Secondary server
- Supports all Active monitors and Performance Monitors for automatic failover
- Automatically supports Passive monitor configurations that are hosted on the same
host system for failover e.g. WinEvents
- Automatically supports Passive monitor configurations where dual message destinations
can be set (e.g. flow sources configured to send traffic information to both Primary
and Secondary servers)
- Supports multiple modes of remote database operation to ensure monitoring data resiliency
WhatsUp Gold Failover Manager Configuration
- Allows set up of multiple trigger conditions for automated failover based
on selective component service failures (e.g. failure of collection, discovery,
Alert Center, Flow Monitor, WhatsConfigured or WhatsVirtual services)
- Failover can be configured to occur in three ways -
- The Primary server initiates failover as it detects failed services and exceeds
the trigger point condition
- The Secondary server initiates failover when it fails to reach the Primary server
for a specified duration and detects that database updates have also stopped
- Manual initiation of failover by an administrator
- Failback from the Secondary server (acting as a Primary) to the original Primary
server can occur in three ways –
- Once the Primary Server comes back up it can automatically be set to become ‘active’
- The Secondary server may continue to act as the Primary server until a failover
event transfers control back to the original Primary server
- Manual failback to the Primary server by an administrator
- Configurable failover trigger settings include Failure Duration (how long the Primary
is unreachable by the Secondary) and Status Query Interval (duration between periodic
database checks to verify that the Primary server is regularly updating data)
WhatsUp Gold Failover Manager Alerting and Reporting
- Thresholds and escalations can be configured for failover events in the WhatsUp
Gold Alert Center
- Failover Workspace Report in Alert Center shows both informational messages (for
manual failover) and error messages (for automatic failover)
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
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
More details on failover architectures