Restoring your Faspex Database

Aspera strongly recommends backing up your IBM Aspera Faspex on Demand configuration and database as a precaution in case of system failure. You may also want to restore your Faspex configuration folder and database on a new machine where you've installed Faspex.

CAUTION:
The restore version (which you saved) of your Faspex configuration and database must match the version of Faspex on the machine to which you are restoring.
  1. Restore your Faspex database.

    After backing up your database (Follow the steps in Backing Up Configurations and Databases), restore the database by copying the backup directory to the new location and run the following, where dir is the directory where the backup has been copied:

    # asctl faspex:restore_database dir
  2. Reset the Faspex hostname.
    Change the hostname by running the following from a Windows command prompt:
    # asctl apache:hostname hostname
  3. Change the hostname or IP address in your faspex.yml file.
    In your new installation, open the faspex.yml file, located in the config folder, and change Hostname: and BaseUrl: to include the new hostname or IP address.
  4. Copy and update aspera.conf.
    Open aspera.conf, which you can find in the following location: /opt/aspera/etc/aspera.conf.

    Modify aspera.conf to change to the new hostname:

    ...
    <server>
        <server_name>hostname</server_name>
    </server>
    ...

    Note that you can combine aspera.conf files. For Faspex, the important parts to copy are related to the faspex user and especially the faspex user's authorization token.

    Update aspera.conf to provide the Faspex user's S3 docroot setting.
  5. Create a new node admin user
    To create a new node admin user, run the following:
    # asnodeadmin -a -u nodeadmin -p password -x faspex
  6. Restart Aspera services.

    After updating aspera.conf, restart the following services:

    • Aspera Central
    • Aspera NodeD
    • Aspera HTTPD
  7. 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.
  8. Restart Faspex
    # asctl faspex:restart
  9. 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.
  10. Modify the localhost configuration
    Launch Faspex from a browser and log in using the Faspex administrator account. Go to Server > File Storage and edit the localhost node. (Click the box icon next to localhost and select Edit.) In the Basic Configuration section, enter the username and password you specified when you created the node admin user in the steps above.
    Note: Remote storage locations should be accessible without changes.
Note: If you created post-processing scripts, you must copy and restore them manually.

Each email template notification you have customized must be regenerated from the UI. For details, see Configure Notifications.