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.

(Preliminary step) 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:
  - 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 Orchestrator and all Aspera services.

# asctl all:stop
stopping manager, engine and workers..
stopped...

Orchestrator Status:
  -> Orchestrator Manager NOT running
  -> 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
  -> Asynchronous Worker Process 1 is NOT running
  -> Synchronous Worker Process 2 is NOT running
  -> Synchronous Worker Process 3 is NOT running
  -> Synchronous Worker Process 4 is NOT running
  -> Synchronous Worker Process 5 is NOT running
MySQL: Stop... done
Apache: Stop... done

Upgrade the Aspera Common Components.

# 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%]

(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 aspera-orchestrator-version-0.x86_64.rpm 
Preparing... ########################################### [100%]
   1:aspera-orchestrator    ########################################### [100%]

Complete the upgrade by setting up Orchestrator.
```
# asctl orchestrator:setup
```
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 Technical Support for any questions regarding the handling of capsules after an upgrade.
Restart Orchestrator and all Aspera services.
```
# asctl all:restart
```