Upgrading a Single Node from Orchestrator 2.3.5+ to the Current Release

The procedure in this topic is only for those upgrading from Orchestrator 2.3.5 + to the current release.

Note: Because it is likely that the Aspera Common Components installed with earlier versions of Orchestrator are incompatible with the current released version, IBM Aspera recommends that you upgrade the Aspera Common Components before upgrading (instructions for this are given in Step 5).

Before upgrading Orchestrator, review product release notes.

Aspera strives to maintain compatibility from one release to the next, but sometimes we must make changes that affect a small number of customers. Review the release notes for all Orchestrator versions that have been released since your current version. In particular, the Breaking Changes section highlights changes that may require you to adjust your workflow, configuration, or usage. These issues may impact your new installation.
Follow the backup steps described in Upgrading: Requirements to ensure easy rollback in case there are any issues.
After upgrading, previously installed releases of Aspera Orchestrator are still present in /opt/aspera and can be used for rollback operations. For example:
```
/opt/aspera/Orchestrator_version/
```
Download the installation files for the new release.
1. Go to the Aspera downloads website, http://downloads.asperasoft.com/en/downloads/27.
2. Using your login credentials, download both installers:
  - version - Linux RPM x86_64 (Aspera Orchestrator)
  - versionCom - Linux RPM x86_64 (Aspera Common Components)
  After download, the installers appear with the following formats (aspera-common is the Aspera Common Components):
```
aspera-orchestrator-version-0.x86_64.rpm
aspera-common-version-0.x86_64.rpm
```
3. Save the installers to the machine where Orchestrator is to be upgraded.
Stop Orchestrator services or all Aspera services.
CAUTION:
To avoid any issues with installation, be sure to run the asctl command applicable to your current setup:
- If you don't need to upgrade the Aspera Common Components ("Common"), run the following command:
```
asctl orchestrator:stop
```
- If you must upgrade Common, run the following command:
```
asctl all:stop
```

Upgrade the Aspera Common Components, if needed.

# rpm -Uvh aspera-common-version-0.x86_64.rpm
Preparing...                          ################################# [100%]
Updating / installing...
   1:aspera-common-version-0    ################################# [ 50%]
Cleaning up / removing...
   2:aspera-common-version-0    ################################# [100%]

Upgrade Orchestrator.

# rpm -Uvh aspera-orchestrator-version-0.x86_64.rpm 
Preparing... ########################################### [100%]
   1:aspera-orchestrator    ########################################### [100%]

(High availability upgrade, only) If you are upgrading in a high availability (HA) environment that uses ACM software, turn off the MySQL, Apache, and Orchestrator services with the chkconfig command.
This step is necessary for ACM to function properly.
```
# chkconfig aspera_mysqld off
# chkconfig aspera_httpd off
# chkconfig AsperaOrchestrator off
```
Before completing the upgrade, confirm that the orchestrator symlink still exists.
If the symlink does not still exist, recreate it with the commands in "Setting up Mount Points for Shared Orchestrator /var Data," step 2.
Below is an example of the symlink that you need, and how to locate it.
```
# pwd
/opt/aspera/var/config
# ls -all
lrwxrwxrwx  1 root root   58 Aug 30 10:13 orchestrator -> /mnt2/ha_orchestrator/orchestrator/var/config/orchestrator
```
Complete the upgrade by setting up Orchestrator.
```
# asctl orchestrator:setup
```
A Ruby version selection prompt appears:
```
Orchestrator
  Use Ruby 2.3.0 (y/n)? (current: y) 
```
Enter "y" to use Ruby 2.3.0 in the installation.

CAUTION:
When upgrading from an older version of Orchestrator (which runs Ruby 1.8.7) to Orchestrator 3.0.2, if you choose "y" for "Use Ruby 2.3.0 (y/n)?" and you have work orders with a current status of "In Progress", those work orders will fail after upgrade and you will need to restart any asynchronous steps. (This issue is caused by the older and newer Rails versions handling ActiveRecord in different ways).
If for any reason it will not be possible to restart the asynchronous steps after upgrade, you must select "n" for"Use Ruby 2.3.0 (y/n)?" and continue to use Ruby 1.8.7 with Orchestrator 3.0.2.

Note: If you select "n" at this prompt, Orchestrator will use Ruby 1.8.7 for the installation. You will still have access to all Orchestrator features; however, you will not experience the improved engine performance supported by Ruby 2.3.0.
Check the following directory if there are capsules present in the folder.
```
/opt/aspera/var/config/orchestrator/capsules/
```
Review the current release notes and remove any capsules that are no longer needed. Contact ../general_external/dita/boilerplate/support.html#support for any questions regarding the handling of capsules after an upgrade.
Restart Orchestrator and all Aspera services.
```
# asctl all:restart
```