Backup your FOD Database

Aspera strongly recommends backing up your IBM Aspera Faspex On Demand (FOD) configuration and database as a precaution in case of system failure. You can also choose to restore Faspex on a completely new workstation on which you've installed Faspex.

  1. SSH into your FOD as root:
    # ssh -i /path/to/your_key.pem -p 33001 ec2-user@ec2_host_IP
    # sudo su -
  2. Create a backup folder.
    # mkdir /backup
  3. Backup node user and transfer user mapping.
    # /opt/aspera/bin/asnodeadmin --backup=/backup/api-xfer-mapping
  4. If you configured SSL for FOD, 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. Obtain your customer ID and entitlement ID.
    You need to know your customer ID and entitlement ID to entitle your new system. If you don't know this information, you can find out by running the following command:
    # /opt/aspera/bin/alee-admin entitlement
  6. If you use S3 storage, back up your aspera.conf file.

    The save and restore feature does not back up a transfer user's docroot to S3 storage. If your transfer user faspex has a docroot set to an S3 bucket, you need to back the aspera.conf file up manually.

    # cp /opt/aspera/etc/aspera.conf.rpmsave /backup/aspera.conf 
  7. Zip up the /backup directory and move the file to a location on your new system.
    To zip up the file, run the following command:
    # tar -cvzf fod_backup_file.tgz /backup

For instructions on restoring your Faspex configuration and database, see Restoring your FOD Database.