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. Review product release notes.
    Review the release notes for the versions that were released since your current version. In particular, the Breaking Changes section highlights changes that may require you to adjust your workflow, configuration, or usage.
  3. Confirm your Aspera service account.
    The Aspera service account was created when you first installed Aspera Connect Server on your computer and you will need this account information during the upgrade. By default, the user name for the Aspera services account is svcAspera; however, this is not a requirement and you may have selected a different user to run the services.

    To identify which user is designated as your Aspera service account in Windows 7, 8, and 10, click Control Panel > Administrative Tools > Services. In Windows Server 2008, 2012, and 2016, go to the Server Manager and select Configuration > Services. Find the account associated with the Aspera services (such as Aspera Central) and record the username. If you have forgotten the Aspera service account password or would like to change the designated Aspera service account, follow the instructions described in Managing the Aspera Service Account.

  4. 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.
  5. Stop or allow to complete any FASP transfers that were initiated by the computer that you are upgrading.
    FASP transfers cannot proceed during your Aspera product upgrade.
    • Stop Hot Folders by clicking Stop.
    • Close the application GUI.
    • Stop (and resume after upgrade) or allow to complete any ascp, A4, or Sync transfers in the command line.
  6. Verify the website that runs Web UI.
    During the installation, you will be able to select the website to use. Aspera recommends that you set up the new Connect Server Web UI on the same website on which your current Web UI is running.

    To find out which web site is running Web UI, go to Control Panel > Administrative Tools > Internet Information Services (Manager). In the left panel, click (Computer name) > Web Sites. The website that runs Web UI should contain the aspera folder.

    Find out which website is running Web UI.
  7. If your node is used by IBM Aspera Files, back up the entire Redis database to migrate your Files data.
    Stop the Aspera Node D service by going to Control Panel > Administrative Tools > Computer Management > Services and Applications > Services, clicking Aspera NodeD, and clicking Stop. Create the backup file by running the following command:
    > asredis -p 31415 BGREWRITEAOF
    The backup is stored as appendonly.aof in the following location:
    C:\Program Files[ (x86)]\Aspera\Enterprise Server\var\appendonly.aof
  8. Back up configuration and settings files.
    These files are found in the etc and var folders. Their location depends on the version of your previous installation and the operating system.

    Aspera 2.5+

    • C:\Program Files[ (x86)]\Aspera\Enterprise Server\etc\ (contains Configuration files, Shared Remote Hosts)
    • C:\Program Files[ (x86)]\Aspera\Enterprise Server\var\ (contains Prepost scripts, Connect Server)
    • <APPDATA>\Aspera\Enterprise Server (contains the individual user's remote hosts and hot folder configuration)

      To determine the current user's <APPDATA> path, run the following command in a Command Prompt window :

      > echo %APPDATA%

    Aspera 2.2.x and earlier

    • C:\Program Files[ (x86)]\Aspera\FASP\etc\ (contains Configuration files)
    • C:\Program Files[ (x86)]\Aspera\FASP\var\ (contains Prepost scripts, Connect Server)
    • C:\Program Files[ (x86)]\Aspera\Aspera Scp\etc\(contains Remote Hosts and Hot Folders settings)
  9. 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.
    > asnodeadmin -b C:\filepath\database.backup
  10. 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:
    C:\Inetpub\wwwroot\aspera\
  11. 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:
    C:\Program Files[ (x86)]\Aspera\FASP\etc\aspera.conf

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

    <CONF version="2">
    ...