Before Upgrading

Steps to take before upgrading your IBM Aspera product.

The installer for IBM Aspera Enterprise 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.

Note: 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. If you are upgrading your Enterprise Server to Connect Server, see the appendix in the Connect Server documentation located at http://asperasoft.com/en/documentation/4..
  1. All Versions - Verify the version of your existing product

    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.

  2. All versions - Stop all FASP transfer-related applications and connections.

    Before upgrading the application, close the following applications and services:

    • ascp connections
    • SSH connections
    • The Enterprise Server application
  3. All versions - Back up the files

    Depending on the version of your previous installation, back up the files in the specified locations:

    Version Folder
    2.0.2 to 2.7+
    • /opt/aspera/etc/(Server config, web config, user settings, license info)
    • /opt/aspera/var/(Pre- and Post-Processing scripts, Connect Server)
    2.0.1 and earlier
    • /var/opt/aspera/etc/(Server config, web config, user settings, license info)
    • /usr/local/aspera/var/(Pre- and Post-Processing scripts, Connect Server)

    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.