Upgrading Faspex

Important: If you are running Faspex for Isilon OneFS, do not upgrade to Faspex 3.0+! You should not upgrade until Enterprise Server 3.0+ is released for the Isilon OneFS Maverick platform (64-bit).
Warning: Due to incompatible common components, IBM Aspera Console and Faspex cannot be installed on the same machine. Aspera does not support this combination.
If an older version of Faspex is already installed on your machine, upgrade to the newest version. Aspera supports upgrading from the following versions:
Note: Aspera does not support a direct upgrade from 3.1.1. Instead, first upgrade to 3.9.3 before upgrading to 4.0.0.
  1. If you have not done so already, review the Upgrade Checklist. You must meet the listed prerequisites before attempting to upgrade.
  2. Back up your Faspex database by following the steps in Backing Up Configurations and Databases.
  3. Download the latest Aspera installers.

    Download the latest version of IBM Aspera Enterprise Server,Common Components and IBM Aspera Faspex installers from the following locations:

    You are required to enter your organization's Aspera login credentials to gain access. If you need help determining your organization's access credentials, contact Technical Support.

  4. Manually backup your SSL certificate files.
    Locate and copy the server.crt and server.key files to a different location. The files can be found in the following locations:
    • /opt/aspera/common/apache/conf/server.crt
    • /opt/aspera/common/apache/conf/server.key
  5. Run the latest Enterprise Server installer.
    First see the "Before Upgrading" section in the IBM Aspera Enterprise Server Admin Guide.
    Then run the following command to upgrade Enterprise Server or Connect Server to the latest version:
    $ rpm -Uvh aspera-entsrv-[version].rpm 
    Note: If you would like to configure a remote transfer server with Faspex, you must enable persistent storage (see Persistent Storage) in the aspera.conf file for Enterprise Server. For more information on setting up a remote transfer server, see Working With Remote Servers.
  6. Stop all services.

    Before upgrading, stop all services related to Faspex, including Faspex, MySQL, and Apache. Use the following command:

    asctl all:stop
  7. Launch the Faspex installer.
    Note: The installer attempts to create a faspex system user and the associated home directory at /home/faspex. If your organization does not allow you to use the /home directory, first create the faspex user and configure the user directory with the following commands:
    # mkdir -p /home/faspex/faspex_packages
    # chown faspex:faspex /home/faspex/
    # chown faspex:faspex /home/faspex/faspex_packages 
    The installer uses the faspex user that you created and does not need to create the faspex user directory.

    Use the following commands with proper administrative permissions to run the installers (replacing version accordingly). Order is important; Aspera Common Components must be installed first.

    # rpm -Uvh aspera-common-version.rpm
    # rpm -Uvh aspera-faspex-version.rpm
  8. Launch asctl to continue the Faspex setup process. Run the following command:

    After the packages have been installed, run the following command.

    $ asctl faspex:upgrade

    The terminal asks you to confirm that your previous Faspex settings are still applicable. Enter y to continue.

  9. Back up your new Faspex database by following the steps in Backing Up Configurations and Databases.
  10. If upgrading from a version prior to Faspex 3.0, you may preserve your custom SSH port setting.
    Upgrading Faspex from a release prior to Faspex 3.0 does not preserve SSH port settings which were being used in prior releases. Instead, the installer assumes your server now uses port 33001 for SSH. If you want to preserve the port you were using previously, you can add the following line to the <server> section of your aspera.conf file after the Faspex upgrade:

    The aspera.conf file can be found in the following location:


    After modifying aspera.conf, restart Aspera NodeD and Faspex services.

    # service asperanoded restart
  11. Restore SSL certificate files.
    Locate your existing SSL certificates and replace them with the ones acquired from the certificate authority. Again, your certificates are located at the following paths:
    • /opt/aspera/common/apache/conf/server.crt
    • /opt/aspera/common/apache/conf/server.key
    Restart Apache with the following command:
  12. Restart the Aspera Node Server.

    In order to use Faspex, the Aspera Node Server must be running. If you did not choose to restart the Aspera Node Server when prompted during the setup process, or if it has been stopped, you must restart it before using Faspex.

    You can use the ps command to check whether the node server is running. For example:
    # ps -ef | grep asperanoded
    To restart asperanoded:
    # service asperanoded restart
  13. If you configured Faspex to serve the IBM Aspera Connect Browser Plug-in locally, you must redo all those changes manually after the Faspex upgrade. Otherwise, the upgrade breaks the locally hosted connect.
    For instructions on serving Connect locally, see Serving Connect from a Local Location.
Your Faspex upgrade is now complete. If you have not updated your license, follow the steps in Updating Your License.
Note: If you had SAML configured before upgrading to Faspex 4.0, you need to add your SAML configuration metadata to your SAML Identity Provider (IdP) again. Metadata URLs now contain numbers to support multiple SAML configurations. For information about configuring the IdP, see Configure Your Identity Provider (IdP). For more information about SAML in general, see SAML and Faspex.