Upgrading a Single Node from Orchestrator 2.3.0 to the Current Release

The procedure below is only for those upgrading from Orchestrator 2.3.0 and above to the current release. The upgrade of Orchestrator involves upgrading the .rpm file for the software.

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 4, below).

(Preliminary step) Follow the backup steps 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 package (Orchestrator and Aspera Common Components) and copy them to the server.
1. Go to the Aspera downloads website, http://downloads.asperasoft.com/en/downloads/27.
2. Using your login credentials, download both installers:
  - vversion - Linux RPM x86_64 (Aspera Orchestrator)
  - vversionCom - 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 all Aspera services.

# asctl all:stop
stopping manager, engine and workers..
stopped...
Orchestrator Status:
  -> Orchestrator Manager running with pid: 28796
  -> Orchestrator Engine NOT running
  -> Mongrel serving orchestrator on port 3000 is NOT running
  -> Mongrel serving orchestrator on port 3001 is NOT running
  -> Mongrel serving orchestrator on port 3002 is NOT running
  -> Orchestrator Monitor NOT running
  -> Asynchronous Worker Process 0 is NOT running
....
  -> Synchronous Worker Process 9 is NOT running
MySQL: Stop... done
Apache: Stop... done

Upgrade the Aspera Common Components to the required version.

# rpm -Uvh aspera-common-version-0.x86_64.rpm 
Preparing... ########################################### [100%]
   1:aspera-common warning: /opt/aspera/common/apache/conf/extra/httpd-ssl.conf saved as /opt/aspera/common/apache/conf/extra/httpd-ssl.conf.rpmsave
########################################### [100%]

Note: The warning shown above is expected; it is a note to the user that their Apache configuration has been preserved. It does not indicate a problem with the upgrade.

(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
```
Upgrade Orchestrator.
```
# rpm -Uvh --noscripts aspera-orchestrator-version-0.x86_64.rpm 
Preparing... ########################################### [100%]
   1:aspera-orchestrator    ########################################### [100%]
```
Important: The --noscripts flag in the rpm upgrade command above is necessary due to a bug in the Orchestrator v 2.3 rpm code. Since that code cannot be modified, this flag skips the existing faulty code. This is a safe flag to run and has been tested on all platforms supporting .rpm.
Complete the upgrade by setting up Orchestrator.
```
# asctl orchestrator:setup
```
Confirm whether 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 Technical Support for any questions regarding the handling of capsules after upgrading.
Restart Orchestrator and all Aspera services.
```
# asctl all:restart
```