Upgrade Faspex On Demand from 3.5.4 to 3.6.0

IN THIS ARTICLE:

Summary

This article provides the steps for upgrading your 3.5.4 Faspex On Demand to the 3.6.0 release.

Preparation

Customers coming over from earlier versions may also need new product keys. Before doing the upgrade, please prepare by following the steps below.

Note: The 3.4.6 release had keys that expired on January 31st, 2015. Please email support at support@asperasoft.com for updated product keys.

1. Log into your Faspex. SSH and sudo to the root user. See this article for more details.

2. Back up your Faspex configuration and database. Within the Faspex Web UI, go to Server > Configuration > Save/Restore to save your current Faspex configuration and database.

3. Backup your Apache configuration, which consists of the following files:

  • /opt/aspera/common/apache
  • apache.rb.yml
  • /conf/*.key
  • /conf/*.crt
  • /conf/extra/httpd-ssl_template.conf
  • /custom/


4. Back up 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. Download the latest versions of Aspera software

# wget http://download.asperasoft.com/sw/ondemand/3.6.0/aws/aspera-entsrv-3.6.0.119278-linux-64.rpm
# wget http://download.asperasoft.com/sw/ondemand/3.6.0/aws/aspera-common-1.1.22.117256-0.x86_64.rpm
# wget http://download.asperasoft.com/sw/ondemand/3.6.0/aws/aspera-faspex-3.9.3.110840-0.x86_64.rpm
# wget http://download.asperasoft.com/sw/ondemand/3.6.0/aws/aspera-ondemand-tools-3.6.0-119289.noarch.rpm
# wget http://download.asperasoft.com/sw/ondemand/3.6.0/aws/aspera-ondemand-init-fod-3.6.0-119289.noarch.rpm
# wget http://download.asperasoft.com/sw/ondemand/3.6.0/aws/aspera-ondemand-init-base-3.6.0-119289.noarch.rpm

Procedure - Upgrade

1. Stop all Faspex processes

# asctl all:stop

2. Upgrade Enterprise Server to 3.6.0

# rpm -Uvh aspera-entsrv-3.6.0.119278-linux-64.rpm
# /opt/aspera/bin/asnodeadmin --db-update
# /opt/aspera/bin/alee-admin register CustomerID EntitlementID

3. Create a file named multi-user.target.wants at /systemd/system/multi-user.target.wants

# mkdir systemd
# cd systemd/
# mkdir system
# cd system/
# touch multi-user.target.wants

4. Upgrade the AOD RPMs

# rpm -Uvh aspera-ondemand-init-base-3.6.0-119289.noarch.rpm
# rpm -Uvh aspera-ondemand-tools-3.6.0-119289.noarch.rpm
# rpm -Uvh aspera-ondemand-init-fod-3.6.0-119289.noarch.rpm

5. Upgrade the Common and Faspex RPMs

# rpm -Uvh aspera-common-1.1.22.117256-0.x86_64.rpm
# ln -s /opt/aspera/common/asctl/asctl /usr/bin/asctl
# rpm -Uvh aspera-faspex-3.9.3.110840-0.x86_64.rpm

6. Run the upgrade utility (during this upgrade, you can answer yes to all defaults by typing the letter y)

# asctl apache:upgrade
# asctl mysql:upgrade
# asctl faspex:upgrade

7. Restore your old aspera.conf (in case your transfer server is local)

# mv /opt/aspera/etc/aspera.conf /opt/aspera/etc/aspera.conf.after.upgrade
# cp /opt/aspera/etc/aspera.conf.orig /opt/aspera/etc/aspera.conf
Note: If your Faspex server is deployed on a separate system from your transfer server, then please be sure to copy the new 'token encryption key' from your upgraded faspex to the actual transfer server.

8. Restart asperanoded, asperatrapd, asperahttpd, Apache, MySQL and Faspex services

# service asperanoded restart
# service asperatrapd restart
# service asperahttpd restart
# asctl apache:restart
# asctl mysql:restart
# asctl faspex:restart

9. Login and confirm that Faspex is able to do transfers.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk