Upgrading the HA Environment

Stopping All Services for Upgrade

You need to stop Faspex and MySQL services before performing the upgrade.

Stop the cronjob on both the nodes by commenting out the job.

# crontab -e
# * * * * * /opt/aspera/acm/bin/acm 10.0.71.21 20 > /dev/null 2>&1
# 30 3 * * * /opt/aspera/acm/bin/acmtl -b > /dev/null 2>&1
# 45 3 * * 7 echo -n "" > /opt/aspera/common/asctl/log/asctl.log > /dev/null 2>&1

On the active node, back up the database:
```
# asctl faspex:backup_database
```
Stop all Faspex services on the active node.
```
# asctl all:stop
```
Start MySQL service on the passive node and back up the database.
```
# asctl mysql:start
# asctl faspex:backup_database
```
Stop MySQL and ensure all Faspex services are stopped on the passive node.
```
# asctl mysql:stop
# asctl all:stop
```
Download and run through the backup and upgrade process on your local or remote HSTS nodes. See the IBM Aspera High-Speed Transfer Server Admin Guide.

Upgrade Faspex on the Active Node

Download and install the Common Components and Faspex packages.

# rpm -Uvh ibm-aspera-common-version.rpm
# rpm -Uvh ibm-aspera-faspex-version.rpm

Run the Faspex upgrade.
```
# asctl faspex:upgrade
```
Test the upgrade by logging in through the Faspex web UI.
Disable all Faspex services:
First, stop all Faspex services on both nodes:
```
# asctl all:stop
```
Then disable the services by running these commands on both nodes:
```
# chkconfig aspera_mysqld off; chkconfig aspera_httpd off; chkconfig aspera_faspex_np_background off; chkconfig aspera_faspex_mongrel off; chkconfig aspera_faspex_ds_background off; chkconfig aspera_faspex_db_background off; chkconfig aspera_faspex_background off; chkconfig aspera_faspex_email_background off
```
Important: Faspex 4.2.0 and later allows you to install the HTTP gateway service. Before installing HTTP gateway, see HTTP Gateway [BETA] Service for more information and to determine whether to enable this beta service.
If you do not want to use it, you can disable it on both nodes by running:
```
# chkconfig aspera_httpgateway off
```

Upgrade Faspex on the Passive Node

Edit the database.yml configuration file (/opt/aspera/faspex/config/database.yml) and make sure the server IP addressis 127.0.0.1.

Download and install the Common Components and Faspex packages.

# rpm -Uvh ibm-aspera-common-version.rpm
# rpm -Uvh ibm-aspera-faspex-version.rpm

Test the upgrade by logging in through the Faspex web UI.
Disable all Faspex services:
First, stop all Faspex services on both nodes:
```
# asctl all:stop
```
Then disable the services by running these commands on both nodes:
```
# chkconfig aspera_mysqld off; chkconfig aspera_httpd off; chkconfig aspera_faspex_np_background off; chkconfig aspera_faspex_mongrel off; chkconfig aspera_faspex_ds_background off; chkconfig aspera_faspex_db_background off; chkconfig aspera_faspex_background off; chkconfig aspera_faspex_email_background off
```
Important: Faspex 4.2.0 and later allows you to install the HTTP gateway service. Before installing HTTP gateway, see HTTP Gateway [BETA] Service for more information and to determine whether to enable this beta service.
If you do not want to use it, you can disable it on both nodes by running:
```
# chkconfig aspera_httpgateway off
```

Restart the HA Environment

Copy the keystore.jks (/opt/aspera/faspex/lib/daemons/np/etc/keystore.jks) on one node to the other to make sure that they are identical.

Restart the cronjobs on both the nodes by uncommenting the jobs.

# crontab -e
* * * * * /opt/aspera/acm/bin/acm 10.0.71.21 20 > /dev/null 2>&1
30 3 * * * /opt/aspera/acm/bin/acmtl -b > /dev/null 2>&1
45 3 * * 7 echo -n "" > /opt/aspera/common/asctl/log/asctl.log > /dev/null 2>&1