Upgrading Faspex from 5.X

Warning:

Before proceeding with any upgrade, you should verify the following:

Attention: Review the Secret key management and password protection section before upgrading Faspex 5.

Perform a full environment back up and ensure the back up is successful. In case the upgrade fails, the only reliable, short-term fix is to roll back the environment using the back up.
Test the upgrade in a test environment comparable to the production environment.
If upgrading the test environment is successful, upgrade the production environment, but do not bring the production environment back online.
Prior to bringing the production environment back online, the customer must test the application to determine if an immediate rollback is needed. Otherwise, customers risk losing all data generated between upgrade and rollback. If a rollback is needed to undo the installation of patch containers on a server, you would be able to rollback to a specific version of Faspex that has not been patched via faspexctl set_image_tags VERSION.
Note: You should not attempt to perform a rollback across different patch Faspex versions (ie. from 5.0.5 to 5.0.4).
Review the Docker Compose customizations section.

Fully backup your Faspex instance. See Back up your Faspex instance for detailed instructions.
Install these Podman components: podman-docker, podman-plugins, and skopeo.
Note: If you are performing the upgrade from a podman-docker setup you can skip this step.
```
yum install podman-docker podman-plugins skopeo
```
Download the newest installer and install the RPM file:
```
rpm -Uvh ibm-aspera-faspex-version.build.x86_64.rpm
```
Update Faspex containers:
```
faspexctl setup
```
Note: If you are using a remote database, make sure to say no (n) to installing the faspex_db container.
Confirm all containers are present and running:
```
faspexctl status
```
Open Faspex Utility and login.
Go to Manage database and make sure that Faspex is using the latest schema. If there is a new migration, migrate the database.