Grass Valley iControl Upgrade Guide - Manual (Page 6)

2
iControl Upgrade Guide
Rolling Back
Rolling Back
A rollback operation is the reversal from one version of software to a previously installed version.
Rolling back from any version of iControl above and including version 3.00 to any version below
version 3.00 is not supported. For example, a rollback from iControl version 4.00 to version 2.30 is not
supported. By contrast, a rollback from iControl version 4.03 to version 3.60 is supported.
Upgrading from iControl Version 1.xx
Previous versions (1.xx) of iControl are not compatible with release version 2.00 (and later). An upgrade
from version 1.xx involves a platform change which requires re-imaging the Application Server hard drive.
Configuration files cannot be reused. User-configured items such as iControl Navigator aliases, error log
settings and proc amps must be regenerated (we recommend you record all values before proceeding with
an upgrade). Old iControl Web sites will be converted, but the links will need to be reassigned.
Please contact [email protected] for assistance.
Upgrading from iControl Version 2.xx
To get you started with your upgrade, the Miranda Technical Support team will have provided you with the
upgrade package of the latest version of iControl, which includes the following:
Note: One implication of this is that when upgrading an Application Server to version 4.10 or
higher, you must similarly upgrade ALL Application Servers within the Redundancy Group in
order to ensure redundancy is fully functional.
File Name Description
446-27G01-xxx.sh Application Server platform upgrade script
446-29G01-xxx.sh iControl upgrade preparation script
446-20G01-xxx.zip iControl upgrade installer
iControl_vxxx_ReleaseNotes.pdf iControl Release Notes
iControl_vxxx_UpgradeGuide.pdf iControl Upgrade Guide (this document)