Upgrading Console to the Current Version

If an older version of IBM Aspera Console is already installed on your machine, upgrade to the newest version. Aspera supports upgrading from the following versions.
 

RHEL 6 (64-Bit) /
CentOS 6 (64-Bit)

CentOS 7 (64-Bit) /
RHEL 7 (64-Bit)

Console and Common Versions
  • Console 3.2.0 + Common >= 1.2.20
  • Console 3.1.1 + Common >= 1.2.18
  • Console 3.1.0 + Common >= 1.2.16
  • Console 3.0.7 + Common >= 1.2.16
  • Console 3.0.6 + Common >= 1.2.15
  • Console 3.0.5 + Common >= 1.2.15
  • Console 3.0.3 + Common >= 1.2.15
  • Console 3.0.2 + Common >= 1.2.14
  • Console 3.0.1 + Common >= 1.2.13
  • Console 2.5.1 + Common >= 1.2.11
  • Console 2.3.2 + Common >= 1.2.10
  • Console 2.3.0 + Common >= 1.2.9
  • Console 2.0.1 + Common >= 1.2.8
  • Console 2.0.0 + Common >= 1.2.8
  • Console 1.7.3 + Common >= 1.2.7
  • Console 1.6.0 + Common >= 1.2.4
  • Console 1.5.6 + Common >= 1.1.0
  • Console 3.2.0 + Common >= 1.2.20
  • Console 3.1.1 + Common >= 1.2.18
  • Console 3.1.0 + Common >= 1.2.16
  • Console 3.0.7 + Common >= 1.2.16
  • Console 3.0.6 + Common >= 1.2.15
  • Console 3.0.5 + Common >= 1.2.15
  • Console 3.0.3 + Common >= 1.2.15
  • Console 3.0.2 + Common >= 1.2.14
  • Console 3.0.1 + Common >= 1.2.13
  • Console 2.5.1 + Common >= 1.2.11
    Note: Upgrading is not supported for versions prior to Console 2.5.1.
If you are upgrading from a version not listed above, contact Aspera Support for further information.
Note: As of Console 3.0.3+, Console stores license information in the database, rather than in a file located at /opt/aspera/console/config/. If a license is added to the directory before the upgrade script is run, the script migrates the license information from the file into the database and deletes the file. To modify your license, see Updating your Console License.
  1. Back up Console's database using the following asctl command in a Terminal:
    $ asctl -v console:backup_database
  2. Stop Console and all related services.
    Run the following asctl command:
    $ asctl all:stop
  3. Back up my.cnf if you have customized it.
    Upgrading the Aspera Common Components overwrites the existing my.cnf with default values.

    Create a backup of the existing file, which can be found in the following location:

    • /opt/aspera/common/mysql/my.cnf

    Save the backup outside the aspera directory.

  4. Download Console installation components.

    Use the credentials provided by Aspera to download both the Console installer and the common components from the Aspera website: http://downloads.asperasoft.com/en/downloads/3

  5. Install components.
    Run the following commands to install the downloaded files:
    $ rpm -Uvh aspera-common-version.rpm
    $ rpm -Uvh aspera-console-version.rpm 
  6. Run the following asctl command to upgrade Console:
    $ asctl console:upgrade
  7. Restore any my.cnf customizations.
    Copy the custom configurations from your backup to:
    • /opt/aspera/common/mysql/my.cnf
  8. Optional: Upgrade legacy nodes.
    Upgrade your legacy nodes (running an Aspera transfer product prior to version 3.4.6) to take advantage of Console features. For more information on converting your legacy nodes, see Converting Legacy Nodes.