Restoring Aspera Faspex

Steps to take when restoring Aspera® Faspex™from a backup.

As described in the topic Save/Restore, you can create a backup file of your Faspex configuration folder and database by going to Server > Configuration > Save/Restore. From this screen, you may also restore your Faspex configuration folder and database on a new machine. In addition to uploading the backup file and selecting the Restore button, there are additional steps that need to be followed when restoring Faspex on a new machine.

Warning:

Use caution when restoring your Faspex configuration and database. The restore version (that which you saved) must match your currently installed version of Faspex.

Important:

If you created post_processing scripts, you must copy and restore them manually. Faspex does not automatically save them for you.

  1. Install your Faspex license file on the new server.

    Copy the license file to the new server. (If this is an On-Demand system, you must rerun the entitlement.) For information on installing a license, or obtaining a new one from Aspera, see License.

  2. Copy your SSL certificates and keys.
    If you have a custom SSL Certificate, or want to preserve the existing one, copy the SSL certificates and keys to the following locations:
    /opt/aspera/common/apache/conf/server.crt
    /opt/aspera/common/apache/conf/server.key  
    Keep a backup of those files in that directory.
  3. Reset your Faspex hostname.

    To change your Faspex hostname (since it does not get carried over during the backup/restore process), run the following command:

    # asctl apache:hostname HOSTNAME 
  4. Update aspera.conf with the new hostname.

    Open aspera.conf, which you can find in the following location:

    /opt/aspera/etc/

    Modify aspera.conf to include the new hostname:

    ...
    <server>
        <server_name>HOSTNAME</server_name>
    </server>
    ...
  5. For Faspex On-Demand systems: Update aspera.conf to provide the Faspex user's S3 docroot setting.
  6. Restart Aspera services.

    After changing aspera.conf, restart the following services:

    • Aspera NodeD
    • Aspera HTTPD
    • Faspex

    To restart asperahttpd and asperanoded, run the following commands:

    $ /etc/init.d/asperahttpd restart
    $ /etc/init.d/asperanoded restart

    To restart Faspex, run the following command in a Terminal:

    $ asctl faspex:restart
  7. Migrate the server to the new public IP (or EIP in Amazon if you're using an On-Demand system), or change your DNS to point the hostname to the new server IP.