Upgrading a Single Node from Orchestrator 1.9–2.2 to the Current Release

The procedure in this topic is only applicable to users upgrading from Orchestrator versions 1.9.build_version–2.2.build_version, to the current release. For upgrades from Orchestrator 2.3.0, see Upgrading a Single Node from Orchestrator 2.3.0 to the Current Release; for upgrades from Orchestrator 2.3.5, see Upgrading a Single Node 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 6).

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 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. Downoad each of the following:
  - 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 being upgraded.
Use SSH or log in to the Linux machine that requires an upgrade and confirm that services are stopped
```
# asctl all:status
```

If the services are not stopped, run the following commands:

# cd /opt/aspera/orchestrator
# bin/orchestrator all kill

If the version of Common currently installed is different from the one supplied from the downloads website, upgrade the Aspera Common .rpm file using the following command:
```
# rpm –UvH  aspera-common-version-0.x86_64.rpm
```
(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
```
If orchestrator is a symlink, remove it from /opt/aspera/, which should be pointing to the existing Aspera Orchestrator installation directory.
```
# rm /opt/aspera/orchestrator
```
Note: If you don’t see a symlink, then move the Orchestrator directory into another location, such as orchestrator_backup.
```
# mv /opt/aspera/orchestrator /opt/aspera/orchestrator_bkp
```
Install the Aspera Orchestrator .rpm file.
```
# rpm -ivh aspera-orchestrator-version-0.x86_64.rpm
```
See the procedure in Installing Orchestrator for more detailed instructions on the process.
Check status of Aspera Orchestrator service; it should be stopped.
```
# asctl orchestrator:status
```
Start the Aspera Orchestrator service and restart Apache.
```
# asctl orchestrator:restart
# asctl apache:restart
```