Restoring your Faspex Database

You can restore a backed up version of Faspex if you experience a system failure. You can also choose to restore Faspex on a completely new workstation on which you've installed Faspex. If you choose to restore Faspex on a separate workstation, the restored version of Faspex must match the version of Faspex installed on the workstation. To restore Faspex, you need the following files:
  • Faspex MySQL database files
  • The secret.yml file
  • Faspex, Apache, and MySQL application files
  1. Copy the backup directory to the workstation and run the following asctl command:
    # asctl faspex:restore_database /path/to/backup_dir
  2. Set the Faspex hostname to the hostname of the current workstation by running the following asctl command.
    # asctl apache:hostname hostname
  3. Set the hostname or IP address in your faspex.yml file.

    The faspex.yml file can be found at the following location:


    Change Hostname: and BaseUrl: to include the new hostname or IP address.

  4. Update the aspera.conf file with the new hostname using the following asconfigurator command:
    # asconfigurator -x "set_server_data;server_name,hostname"
  5. Create a node user on the workstation. Run the following command:
    # asnodeadmin -a -u node_user -p password -x faspex
  6. If you backed up your SSL certificates and keys, copy them to the following locations on the workstation:
    • /opt/aspera/common/apache/conf/server.crt
    • /opt/aspera/common/apache/conf/server.key
    Keep a backup of those files in that directory.
  7. Copy the secret.yml file from your backup to /opt/aspera/faspex/config/secret.yml. Keep a backup of the original secret.yml file in the directory.
  8. Restart Faspex.
    # asctl faspex:restart
  9. Modify the localhost configuration.
    Launch Faspex from a browser and log in using the Faspex admin account. Go to Server > File Storage and edit the localhost node. (Select the 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.
    Note: Remote nodes should be accessible without changes.
  10. If you experience issues, restart Aspera services.
    Run the following commands to restart the asperacentral, asperanoded, the asperahttpd services:
    # /etc/init.d/asperacentral restart
    # /etc/init.d/asperanoded restart
    # /etc/init.d/asperahttpd restart
Note: If you created post-processing scripts, you must copy and restore them manually. For more information on post-processing scripts, see Enabling Post-Processing Scripts.

Each email template notification you have customized must be customized again from the application. For more information, see Configuring Email Notification Templates.