How to migrate APOD-SOD from v.3.2.2 to v.3.4

Overview

This article is for customers who wants to migrate their APOD-SOD (Aspera Platform on Demand) from v.3.2.2 to v.3.4. 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

1) Backup the existing data and configuration

a ) Via Console Web UI, go to Configuration -> Save/Restore -> Download Current Configuration and save the file to your local machine.

b) Connect to your APOD-SOD from a Terminal/Command Prompt via SSH as root

# ssh -i [customer's 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.

c) backup /opt/aspera/etc/aspera.conf to your local machine.

d) backup /root/.ssh to your local machine.

e) backup the mapping between transfer users and API users

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

f) 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.

m) 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 APOD-SOD instance

d) Select the IP address and associate Address with the new APOD-SOD instance