Upgrading the server running as a container

You can upgrade servers that are running as containers by preparing a backup and using helm upgrade.

Before you begin

You must have a maintenance window in place, as scaling the statefulset results in temporary downtime.

Procedure

  1. Prepare a backup:
    1. Cancel or wait for all running deployment processes to complete.
    2. Set the server statefulset resource to 0 to shut down the server.
    3. Back up the database.
      For example, export the schema to a file.
    4. Back up the appdata Persistent Volume.
    5. Scale the server statefulset resource back to 1 to restart the server.
  2. Perform a Helm upgrade on the server.
  3. Verify that deployment processes operate correctly.
    If issues arise, proceed to the rollback steps.
  4. Roll back the upgrade, if required:
    1. Cancel or wait for all running deployment processes to complete.
    2. Set the server statefulset resource to 0 to shut down the server.
    3. Restore the database.
      For example, drop the schema and import the schema from the backup file.
    4. Restore the appdata directory backup to the Persistent Volume.
    5. Perform a Helm rollback to the previous revision of the server.
    6. Set the server statefulset resource back to 1 and verify that your deployment processes operate correctly after the rollback.

Results

You have upgraded the server to the new version.