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.

(Preliminary steps) IBM Aspera recommends that you complete the following steps before beginning the upgrade:
- Upgrade the Aspera Common Components first, before upgrading Orchestrator, per the instructions in 5.
- Before you begin the upgrade, be sure that you have performed 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 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
```
Stop services on both nodes.
Do one of the following, depending on the currently installed version of Orchestrator.
- On Orchestrator hosts with Orchestrator v2.3.0 amd later, run the following:
```
$ asctl all:stop
```
- On Aspera Orchestrator hosts with a version of Orchestrator that is prior to v2.3.0:
```
$ cd /opt/aspera/orchestrator
$ bin/orchestrator all kill
$ asctl mysql:stop 
$ asctl apache:stop 
```
On both nodes, disable ACM.
```
$ /opt/aspera/acm/bin/acmctl -d
```
Upgrade Orchestrator.
For both nodes, follow the procedure in one of the following topics, depending on the Orchestrator version prior to upgrade:
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
```
Keep services stopped after the upgrade.
Copy files from the backup location (for example, /tmp) to the original locations on both nodes.
- Copy orchestrator.yml to the following:
```
/opt/aspera/orchestrator/config/
```
- Copy orchestrator-license* to the following:
```
/opt/aspera/orchestrator/config/
```
- Copy database.yml to the following:
```
/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/
```
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 Aspera 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.