Before Upgrading or Downgrading

Upgrading

Downgrading

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.

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. If you were using the Aspera Watch Service or Watchfolders, set a docroot for the user running those services, if it is not already set.
    For more information on setting docroots for users, see Updating the Docroot of a Running asperawatchfolderd Service. Ensure that the filepath being watched, or the source_dir configured for the watch folder, is included in the docroot of the user.
  3. Stop all FASP transfer-related applications, services and connections.
    • ascp connections
    • SSH connections
    • The Connect Server application
    • The asperarund service
  4. 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)
  5. 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:
    /opt/aspera/var/webtools/
  6. 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
  7. 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:
    /opt/aspera/etc/aspera.conf

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

    <CONF version="2">
    ...
  8. 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:
    /var/opt/aspera/webpasswd

    After the upgrade, you can restore the file to the following directory:

    /opt/aspera/etc/