Before Upgrading or Downgrading


  • You cannot upgrade directly between different Aspera transfer products (such as from Point-to-Point to Desktop Client, or from Point-to-Point to Enterprise Server). To upgrade, you need to back up the configuration, uninstall the product, and perform a fresh install of the new version of the product.
  • When upgrading from Connect Server versions older than 3.2.1, the Connect Server system-level security settings are not preserved and must be reconfigured. For instructions on enabling or disabling Connect Server system-level security, see Configuring the Apache Server to Host the Connect Server Web UI.


Older installers do not check for newer versions of the application. You must prepare your machine as described below then uninstall the newer version before continuing with your downgrade.

Newer versions of the Redis database are not compatible with older versions of the application. Your downgrade process depends on whether a backup of the older Redis DB is available, either as a separate backup file or as part of your backup of the var directory from the older version.

  • With a backup: Follow the steps below to prepare your machine. Uninstall the application (for instructions, see Uninstalling). Copy the older Redis DB file into the var directory before installing the older (downgrade) version.


  • Without a backup: Follow the steps below to prepare your machine. Uninstall the application (for instructions, see Uninstalling) and delete the var and etc directories from your machine. Then do a fresh installation of the older version. The configuration files in the etc directory may be compatible with older versions, but not all configurations may be read.



Preparing for an Upgrade or Downgrade

  1. Verify the version of your existing product.
    The steps required to prepare for an upgrade may differ depending on your current product version. To view the current product and version, run the following command:
    # ascp -A
  2. Stop all FASP transfer-related applications, services and connections.
    • ascp connections
    • SSH connections
    • The Connect Server application
    • The asperarund service
  3. Back up configuration and settings files.
    These files are found in the etc and var folders.
    • /opt/aspera/etc/ (contains server configuration, web configuration, user settings, license info)
    • /opt/aspera/var/ (contains Pre- and Post-Processing scripts, Connect Server)
  4. Back up the Connect Server customization files.
    Back up the following folder, which you can use as a template to modify the new one after installation:
  5. Back up the Redis database.
    The Redis database is backed up as part of backing up the var directory, but Aspera recommends backing it up separately as well, particularly if it is stored on a different machine.
    # sudo /opt/aspera/bin/asnodeadmin -b /filepath/database.backup
  6. If upgrading from Version 2.1.x: Update Aspera's configuration file version number.
    If you are upgrading from Connect Server version 2.1.x and have HTTP Fallback configured, avoid upgrading errors by modifying the aspera.conf version number. Open aspera.conf with a text editor run with admin privileges:

    Remove the version="2" from the opening tag <CONF>:

    <CONF version="2">
  7. If upgrading from Version 2.0.1 and earlier: Back up and restore Web UI authentication information.
    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, you can restore the file to the following directory:

  8. Remove the existing Aspera package.
    Run the following command to remove the application without affecting your customizations:
    # pkgrm ASPRent

    When you install the upgrade, your settings, license, and other configurations are preserved.