...
For Universal Controller 7.24.x, upgrading refers to the increase of a currently installed 5.2.0 version of the Controller to a 7.24.x version (for example, upgrading Controller 5.2.0.5 to Controller 7.24.0.0).
You can upgrade to Universal Controller 7.24.x only from Universal Controller 5.2.0; you cannot upgrade to 7.24.x from any version earlier than 5.2.0 (for example, 5.1.1).
Note | ||
---|---|---|
| ||
To increase a currently installed 6.1.x or later release of the Controller to a 7.24.x release, you do not have to perform an upgrade; you only have to apply maintenance to the 6.1.x or later version. |
...
For Universal Controller 7.24.x, applying maintenance refers to the increase from a currently installed 6.1.x or later release of the Controller to a 7.24.x release of the Controller (for example, increase Controller 6.1.3.1 to Controller 7.24.0.0).
The procedures for upgrading differ from the procedures for applying maintenance (see Applying Maintenance to Universal Controller).
...
Upgrade Controller to... | 1.6.0 | 1.7.0 | 5.1.0 | 5.2.0 | 6.1.x | 6.2.x | 6.3.x | 6.4.x | 6.5.x | 6.6.x | 6.7.x | 6.8.x | 6.9.x | 7.0.x | 7.1.x | 7.24.x |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
From 1.5.0 | ||||||||||||||||
From 1.6.0 | ||||||||||||||||
From 1.7.0 | ||||||||||||||||
From 5.1.0 | ||||||||||||||||
From 5.2.0 |
...
These instructions comprise the following procedures:
1 | |
---|---|
2 | |
3 | |
4 | |
5 | |
6 | |
7 | |
8 | |
9 | |
10 | |
11 | |
12 | |
13 | |
14 | |
15 |
Note | ||
---|---|---|
| ||
These instructions assume that you are running a High Availability Universal Controller system: a system configured with Active and Passive Controllers (cluster nodes). If you are running a single Controller, disregard the steps for Passive Controllers. |
...
Warning | ||
---|---|---|
| ||
Before upgrading your Controllers, back up your database. The database backup is a fail-safe measure; you will be using the Controller 5.2.0 export and Controller 7.24.x import, as described below, to migrate your data. |
...
Step 1 | From the navigation pane, select Automation Center Administration > Configuration > Maintenance Scripts. The image below shows export script options for Controller 5.2.0. | ||
---|---|---|---|
Step 2 | Select an export script and click Run. | ||
Step 3 | The Controller prompts for a confirmation. Click Yes. As your data is exported, the output from the script is written to the screen, as shown here. | ||
Step 4 | Check the output for error messages. If there are any, copy the output to a file and email it to Customer Support. | ||
Step 5 | Zip or tar the contents of:
| ||
Step 6 | Copy the zip/tar file to a safe place for use after the upgrade process. | ||
Step 7 | Copy your
| ||
Step 8 | Copy your license key from the Properties list and store it in a safe place. | ||
Step 9 | Copy the LDAP mapping file to a safe place for use after the upgrade process.
|
Anchor | ||||
---|---|---|---|---|
|
...