Grass Valley iControl V.6.02 - Manual (Page 482)

Backup and Redundancy
Sample Workflows
472
Sample Workflows
[Workflow]: Configuring and Managing a Redundancy Group
REQUIREMENTS
Make sure you meet the following conditions before beginning this procedure:
• Upon failover or takeover, if you would like your Backup to take over the IP address of the Main
Application Server, then all Application Servers you would like to assign to a Redundancy Group
are on the same subnet.
• None of your Application Servers currently belong to a Redundancy Group.
• Each Application Server’s eth0 and eth1 interfaces are connected.
• All eth1 interfaces are connected together on the Heartbeat network (and can successfully ping
other eth1 IP addresses).
• All eth0 interfaces are connected together on the Main network (and can successfully ping other
eth0 IP addresses).
• Your network is properly configured on both eth0 and eth1, specifically:
• Make sure the Broadcast IP (used by the Heartbeat mechanism) is correct
• Make sure both eth0 and eth1 are activated on boot.
• Make sure the Backup Application Server has enough hard drive space left to replicate the Main
Application Servers.
Sample workflow: Configuring and managing a Redundancy Group
1. Turn off the iControl services on your intended Backup Application Server (see "Stopping,
Starting, or Restarting a Service" , on page 553).
2. Create a Redundancy Group (see page 479 ).
3. Add an Application Server to your Redundancy Group (see page 483 ).
Perform this step for each remaining Application Server you would like to add to your
Redundancy Group, whether its intended role is Backup or Main.
IMPORTANT: Application Server Installation / Commissioning Notice
After configuring the Redundancy Group for the 1st time, it is highly
recommended that you perform ONE of the following tests, as required:
• For every Main Application Server whose Auto-failover function is disabled, perform
a Manual Takeover followed by a Reverse Takeover to ensure that everything is
properly configured.
• For every Main Application Server whose Auto-failover function is enabled,
disconnect that Application Server’s eth0 port from Main Application Server
followed by a Reverse Takeover.