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

iControl
User Guide
473
[Workflow]: Managing and Recovering from a Manual Takeover or Auto-failover
Detailed Directions
Manually Backing Up an Application Server
IMPORTANT: If you configure your Redundancy Group NOT to take over the Main’s IP address
upon failover or takeover, make sure you keep the Backup Application Server’s
IP address configured in System tools | Edit service locations | Service and
alarm discovery on all Application Servers that belong to the Redundancy
Group.
REQUIREMENTS
Make sure you meet the following conditions before beginning this procedure:
• You have already configured your Redundancy Group and all required Application Servers are
associated with it (see "[Workflow]: Configuring and Managing a Redundancy Group" ,
on page 472).
• If you are not performing a Manual Takeover, then an Auto-failover has already occurred.
Sample workflow: Managing and recovering from a manual takeover or auto-failover
1. If you are performing a Manual Takeover from a Main Application Server to a Backup
Application Server, do so now (see
"Initiating a Manual Takeover to a Backup Application
Server" , on page 488).
2. Perform any required maintenance work on the configured Main Application Server
(currently offline).
3. If you would like to return the configured Main Application Server to an active Main role,
see
"Restoring an Offline, Configured Main Application Server to Online Status" ,
on page 490.
4. If you would like to reconfigure the configured Main Application Server in a Backup role,
see
"Reconfiguring an Offline, Configured Main Application Server in a Backup Role" ,
on page 492.
5. If you would like to replace a failed Main Application Server, see "Replacing an Application
Server in a Redundancy Group" , on page 496.
IMPORTANT: All iControl services, Web sites, GSM, and scripts must be backed up for
restorations to be possible.