Upgrading in a High Availability Environment

The upgrade to a cluster environment is first performed on the node where MySQL is active. The steps are then repeated on the other node.

Before you begin the upgrade, follow the backup steps described in Upgrading: Requirements to ensure easy rollback in case there are any issues.

Check the cluster manager status to locate the active node:

$ /opt/aspera/acm/bin/acmctl –i
Checking current ACM status...
Aspera Cluster Manager for Orchestrator - status
------------------------------------------
Local hostname:         orchestrator1
Active node:            orchestrator1 (me)
Status of this node:    active
Status file:            current
Disabled globally:      no
Disabled on this node:  no

In the above STDOUT, the orchestrator1 (active) node has MySQL running.

Back up important files.
On each node, copy the files below to a safe location (for example, /tmp) before the upgrade.
```
/opt/aspera/orchestrator/config/orchestrator.yml
/opt/aspera/orchestrator/config/orchestrator-license*
/opt/aspera/orchestrator/config/database.yml
```
Any custom files, like the ones below, should also be preserved somewhere and restored after the upgrade.
```
/opt/aspera/orchestrator/public/images/aspera_logo_simple.jpg
/opt/aspera/orchestrator/public/stylesheets/aspera.css
```
On both nodes, disable ACM.
```
$ /opt/aspera/acm/bin/acmctl -d
```
Stop Orchestrator services or all Aspera services on both nodes.
CAUTION:
To avoid any issues with installation, be sure to run the asctl command applicable to your current setup:
- If the version of the Aspera Common Components ("Common") installed with your current Orchestrator setup is the same as the Common required to install the new version of Orchestrator (for example, Orchestrator v. 2.7.0, v. 2.7.1 and v. 3.0.1 all use Common 1.2.19), run the following command:
```
$ asctl orchestrator:stop
```
- If the version of Common installed with your current Orchestrator setup is a lower version than the Common required to install the new version of Orchestrator, run the following command:
```
$ asctl all:stop
```
Upgrade Orchestrator.
For both nodes, follow the procedure in one of the following topics, depending on the Orchestrator version prior to upgrade:
Note: Be sure to follow the additional step in the upgrade procedure—for high availability installation only—that turns off the MySQL, Apache, and Orchestrator services after upgrading the Aspera Common Components.
Copy the following files from the backup location (for example, /tmp) to the original locations on both nodes.
- Copy orchestrator.yml, orchestrator-license*, and database.yml to the following directory:
```
/opt/aspera/orchestrator/config/
```
- If found, copy aspera_logo_simple.jpg to the following:
```
/opt/aspera/orchestrator/public/images/
```
- If found, copy aspera.css to the following:
```
/opt/aspera/orchestrator/public/stylesheets/
```
Ensure that the contents of the following files are identical.
```
/opt/aspera/orchestrator/config/database.yml  
/opt/aspera/var/config/orchestrator/database.yml
```
If the files are not identical, use the values in the following file:
```
/opt/aspera/var/config/orchestrator/database.yml
```
Enable ACM on both nodes.
```
$ /opt/aspera/acm/bin/acmctl -e
```
ACM will start MySQL, Apache and Aspera Orchestrator on one node and Apache and Orchestrator on another node.
On one node only, upgrade the plugins as necessary, according to the instructions in Upgrading Plugins and Portlets After an Upgrade of Orchestrator
On both nodes, reload the plugins and execute force maintenance.
Click Engine > Plugins > Reload Plugins, and then click Engine > Processes > Force Maintenance to set the new code.