Upgrading the HA Environment
To upgrade an IBM Aspera Shares HA deployment, you must upgrade each Shares node individually and then reconfigure them to run in an HA environment.
Review the following prior to performing any upgrade:
- 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.
The standard, non-HA upgrade does not account for the many variations in customer network configurations needed for HA installation. The non-HA upgrade may alter configuration settings required for ACM-based Aspera HA.
Every upgrade of an ACM-based HA installation should include, after upgrade, a manual re-check of all the HA configuration by a deployment engineer that is knowledgeable about Aspera ACM-based HA and also knowledgeable about IP networking. The deployment engineer needs to understand and be able to configure the particular network configuration of the individual customer, including load balancers, firewalls, and so on.
Stopping the Cronjobs for Upgrade
# 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
Back Up Shares on Both Nodes
Upgrade Shares on the Active Node
Manually Fail Over to the Passive Node and Upgrade Shares
Stop services to perform Shares upgrade.