Upgrading a Faspex 5 HA environment

To upgrade an existing Faspex 5 HA deployment, you must upgrade each Faspex instance one at a time.

Refer to the database requirements section in the release notes to confirm which versions are supported.

Warning: Upgrading a Faspex 5 HA environment requires expertise in advanced system administration, database management, and network architecture. This guide provides a general framework but will not account for every scenario due to the complexity of HA environments and their numerous components. For a successful upgrade, always exercise caution, rely on sound judgment, and follow best industry practices.

CAUTION:

You should never upgrade the production environment without first performing these steps in a verified test or staging environment that mirrors the production one. Doing so will be at your own risk.

Important: You must stop traffic from a load balancer when upgrading a targeted node. For example, if you have 3 Faspex 5 instances (A, B, and C) stop traffic to A and redirect it only to B and C.

Attention: Before proceeding with any upgrade make sure that the Health > Job health page is showing green checks across the board. If any of the tiles are not showing the green check do not upgrade.

Decrypt the private key on the first node (Node A):
```
faspexctl unseal_secrets
```

Create a backup of the database:

mkdir -p /root/faspex5-backup
faspexctl exec utility mariadb-dump faspex -u\$FASPEX_DB_ASPERA_ADMIN_USERNAME -p\$FASPEX_DB_ASPERA_ADMIN_PASSWORD > /root/faspex5-backup/db-dump.sql

Backup the entire /opt/aspera/faspex directory and the current version of Faspex:

cp -rivp /opt/aspera/faspex ibm-aspera-faspex-5.0.X.x86_64.rpm /root/faspex5-backup

Verify that you have an sql-dump file, a full backup of the faspex directory, and a backup of the current version of Faspex under the /root/faspex5-backup directory. This directory will all the necessary backups to revert to if the upgrade fails:
```
ls -alh
```
Example output:
```
-rw-r--r--   1 root   root    23M Dec 11 13:10 db-dump.sql
drwxrwx---   9 aspweb aspweb 4.0K Dec 10 17:25 faspex
-rw-r--r--  1 root   root   11608800 Dec 10 17:24 ibm-aspera-faspex-5.0.X.x86_64.rpm
```
Download the newest installer and install the RPM file:
```
rpm -Uvh ibm-aspera-faspex-version.build.x86_64.rpm
```
Update Faspex containers and make sure to say no (n) to installing the faspex-db container:
```
faspexctl setup
```
Confirm all containers are present and running:
```
faspexctl status
```
Point the load balancer to the upgraded node (Node A), verify that you can access the environment and no data is lost. After testing everything, proceed with the same steps on Node B and Node C one node at a time.