Grass Valley iControl V.4.43 - Manual (Page 590)

Backup and Redundancy
Auto-failovers
580
Figure 10-1: Auto-failover heartbeat topology example (1 Main Application Server; Main network on eth0
port)
The Main network serves as the medium through which replication occurs between the Main
Application Server and the Backup, as well as being the primary path the Backup Application
Server uses to test the heartbeat of the Main. Only if the Backup does not receive the Main
Application Server’s heartbeat signal through the Main network will the Backup resort to the
Heartbeat network to listen for the Main Application Server’s heartbeat.
When a Redundancy Group is configured and online, any one of the following conditions can
cause a Main Application Server to automatically fail over to its Backup:
Note: When connecting your Application Servers to the networks, use the eth0
port to connect to the Main network. Use eth1 to connect to the Heartbeat network.
Condition Details
The Main Application Server loses network connectivity
on the Main network. The Main Application Server loses its network connection and is
unable to service its clients.
The Backup Application Server loses network
connectivity with the Main Application Server via both
the Main and the Heartbeat network (and the Backup
Application Server has connectivity on the Main
network). In this case, the Backup Application Server has no way of
knowing if the Main server has connectivity on the Main network.
It therefore takes over the Main’s responsibilities.
Secondary path for
Heartbeat signal
Primary path for Heartbeat signal and
Application Server replication