Steps to take before upgrading your IBM Aspera product.
The installer for Aspera Connect Server automatically checks for a previous version of the product on your system. If a previous version is found, the installer automatically removes it and upgrades your computer to the newer version.
Although the installer performs your upgrade automatically, we highly recommend completing the tasks below before starting the installation/upgrade process. If you do not follow these steps, you risk installation errors or losing your former configuration settings. Skip any steps that do not apply to your specific product version.
Depending on your current product version, the upgrade preparation procedure may differ. In a terminal, execute this command:
$ ascp -A
This displays the product name and version number.
Before upgrading the application, close the following applications and services:
Depending on the version of your previous installation, back up the files in the specified locations:
|2.0.2 to 2.7+||
|2.0.1 and earlier||
In particular, be aware that upgrading backs up and deletes the existing sshd_config file before installing the new, default sshd_config. Therefore, you may want to migrate any changes from the backup file (sshd_config.old) to the newly installed sshd_config.
If a previous version of Connect Server (Aspera Web) was set up and customized on your computer, back up the customized Connect Server installation in the following location and use it as a template to modify the new one:
If you are upgrading from Connect Server version 2.1.x and have HTTP Fallback configured, you may need to modify aspera.conf file to avoid upgrading errors. Open aspera.conf with a text editor:
Remove the version="2" from the opening tag <CONF>:
<CONF version="2"> ...
If the existing installation is version 2.0.1 or below, you may need to restore the Connect Server authentication information after the installation. Back up this file:
After the upgrade, restore the file to the following directory: