How to migrate Faspex on Demand (FOD) 3.6.0 to a new instance


This article is for customers who want to migrate their FOD (Aspera Faspex on Demand) 3.6.0 to a new instance. If you are still investigating Aspera on Demand options and want to learn more, please view the Aspera Cloud site for more info.

Migration Procedure

I. Backup Faspex data on your FOD server

1) Download the Current Configuration from the FOD UI

Log on to the FOD web UI as admin, go to Server > Configuration > Save/Restore and download the configuration file on your local machine.


2) Connect to your FOD from a Terminal/Command Prompt via SSH as root

#  ssh -i customer_perm -p 33001 ec2-user@ec2_host_IP
# sudo su -

If you are not sure how to login to your Aspera Server, please see this article.

a) Create a backup folder

# mkdir /backup

b) Backup node user and transfer user mapping

# /opt/aspera/bin/asnodeadmin --backup=/backup/api-xfer-mapping

c) Backup your purchased SSL certificate files (if applicable)

If you have your own purchased SSL certificate, please back up the files by running the following commands.

# cp /opt/aspera/common/apache/conf/server.crt /backup/server.crt
# cp /opt/aspera/common/apache/conf/server.key /backup/server.key

d) Obtain 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

e) Backup your aspera.conf only if you use S3 storage

The save/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 

f) Zip up the "/backup" directory and move the file to a location on your new system

# tar -cvzf fod-backup.tgz /backup

II. Restore procedure on your new FOD 3.6 server

1) Launch a new Faspex On Demand AMI with the same SSH key, Region and Security group and run entitlement


If you are not sure how to launch a new AMI, please see this article. Enter your customer ID and entitlement ID from the Web UI.

2) Restore Faspex via the Faspex Web UI

Log on to Faspex Web UI as admin, go to Server > Save/Restore, select the configuration you had downloaded and click Restore.


After restore is completed, restart your Faspex by running the following command:

# asctl faspex:restart

4) Untar your backup folder

# tar -zxvf fod-backup.tgz

5) Restore Node API users

# /opt/aspera/bin/asnodeadmin --restore=/path/tothe/api-xfer-mapping
# service asperanoded restart

6) Restore encryption key and S3 docroot

You can skip this step if your transfer user faspex does NOT have a docroot set to a S3 bucket.

Open /opt/aspera/etc/aspera.conf file and find the user faspex section:

# vi /opt/aspera/etc/aspera.conf


Update the values in the <absolute> and <encryption_key> tabs with the ones shown in the backup aspera.conf


Restart the Node server and asperahttpd (for httpfallback)

# service asperanoded restart
# service asperahttpd restart

7) Restore your Apache SSL Certificate

You can skip this step if you use a self-signed certificate. This step is only necessary if you have a purchased SSL certificate.

Rename your existing SSL files

# mv /opt/aspera/common/apache/conf/server.crt /opt/aspera/common/apache/conf/
# mv /opt/aspera/common/apache/conf/server.key /opt/aspera/common/apache/conf/

 Copy your back up SSL files to /opt/aspera/common/apache/conf

# cp server.crt /opt/aspera/common/apache/conf
# cp server.key /opt/aspera/common/apache/conf

Restart Apache using the following command:

# asctl apache:restart 

8) Restore the hostname of your Faspex

You can skip this step if you DO NOT have a hostname for your server. This step is only necessary if you use a hostname rather than an IP address to connect to your server.

Update the hostname using the following command:

# asctl apache:hostname

DO NOT install new SSL cert when prompted as the cert has been moved over.

9) Update the <server> section in aspera.conf to reflect the new hostname

You can skip this step if you DO NOT use a custom hostname for your server.

10) Restore the transfer server

Within the Faspex Server Web UI, go to Server > Configuration > Transfer Server > edit > Test Connection.

If you cannot connect to the transfer server, update the Username and Password to match with what you have on the original system and point the package directory to the right path and click Update.



11) Migrate the Elastic IP address

You can skip this step if you DO NOT use Elastic IP address for your server. If you use a unique hostname with a dynamic IP address, you will need to update your DNS entry.  The following steps are only necessary if you use an Elastic IP address from AWS.

a) Use the AWS interface to reassign the Elastic IP from the old instance to the new instance.

b) Navigate to AWS Elastic IP menu.

c) Select the IP address and disassociate the address from the old Faspex instance

d) Select the IP address and associate Address with the new Faspex instance

Powered by Zendesk