How to upgrade and migrate APOD-SOD from v.3.2.1 to v.3.2.2

Overview

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

 

2) Download the Common and Console installers

# wget http://downloads.asperasoft.com/download/sw/common/1.2/aspera-common-1.2.7.67719-0.x86_64.rpm --user=your-login  --password=your_password
# wget http://downloads.asperasoft.com/download/sw/console/1.7/aspera-console-1.7.3.69014-0.x86_64.rpm --user=your-login  --password=your_password

  f you don't know your customer login and password, please contact Aspera Support at support@asperasoft.com to obtain your login credentials.

3) Upgrade Console by running the following commands

# asctl all:stop
# rpm --nodeps -Uvh aspera-common-1.2.7.67719-0.x86_64.rpm
# rpm --nodeps -Uvh aspera-console-1.7.3.69014-0.x86_64.rpm
# asctl console:upgrade

   When prompted to enter port number for Apache, enter 81 for http and 8444 for https. 

# /etc/init.d/aspera_shares_nginx restart 

 

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

console_save_restore.jpg

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

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

 

         d) backup the mapping between  transfer users and API  users

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

e) 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/shares/conf/cert.key  /backup/cert.key
# cp /opt/aspera/shares/conf/cert.pem /backup/cert.pem

 

5) Launch a new v.3.2.2 APOD-SOD instance with the same SSH Key, Region and Security Group and entitle the new system

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.

3.2.2console.jpg

 

6) Backup and restore the new machine

a) Backup Console data and configuration (to preserve some ami specific configurations)

Go to Configuration -> Save/Restore, Download Current Configuration and save the file to your local machine.

b) Stop Console processes

Go to Configuration -> Background and stop these processes:

   AsperaBackground::SshTunnelManager
   AsperaBackground::DatabaseIngest
   AsperaBackground::SoapPoller
   AsperaBackground::CustomField
   AsperaBackground::DataCanonicalizer
   AsperaBackground::DatabaseUtility
   AsperaBackground::Email
   AsperaBackground::Report

 

 stop_console_bkgd.jpg

 

c) Restore the Configuration via Save/Restore

Go to Configuration -> Save/Restore, click Browse and upload the configuration you saved from the old machine, click Restore.

console_save_restore.jpg

d) Change directory to /opt/aspera/console/config and replace the following files with the same files that you saved in Step 6-a.

                  secret.yml

console.yml

database.yml

 

e) Restart mysql and console

# asctl mysql:restart
# asctl console:restart

 

f) Copy the content in /root/.ssh/aspera_console_id.pub on the old server and paste to /root/.ssh/authorized_keys on the new server.

 

g) Update the <server_name> section in /opt/aspera/etc/aspera.conf with the host name of the new server.

server-ip.jpg

 

h) Run the following commands to create mysql user for DB Logger

 # cd /opt/aspera/console
# export PATH=/opt/aspera/common/ruby/bin:$PATH
# export RAILS_ENV=production
# ruby ./script/console
>> FaspNode.all.each {|n|n.grants_for_central}
>> exit

 


i) Login to Aspera on Demand Console with the login credentials that you use on the old machine.  Go to Nodes -> edit,  update node name and connect node to Console

 

update-node-name.jpg

 

connect_node_to_console.jpg

j) Restart asperacentral

    # service asperacentral restart

 

k)  Restore the mapping between transfer users and API users

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

l) Restore SSL Certificate files

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/shares/conf/cert.key  /opt/aspera/shares/conf/cert.key.org
# mv /opt/aspera/shares/conf/cert.pem /opt/aspera/shares/conf/cert.pem.org

Copy your back up SSL files to /opt/aspera/shares/conf

# cp  cert.key /opt/aspera/shares/conf/
# cp  cert.pem /opt/aspera/shares/conf/

Restart Nginx

# /etc/init.d/aspera_shares_nginx restart 

 

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

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk