Skip to content

Upgrading Version

Most of the time, upgrading OctoPerf Enterprise-Edition consists simply of upgrading the services stack. Major releases may require manual interactions, but most of the time everything is automated. We follow semantic versioning.

Before any upgrade, as a safety measure, we suggest that you backup all your data.

For special instructions depending on the version you upgrade, please see our Enterprise-Edition Migration Guides.

Patch Version

Example: upgrade from 1.0.0 to 1.0.1. Upgrading to a new patch version is straightforward. A patch version contains only bug fixes.

Minor Version

Example: upgrade from 1.0.2 to 1.1.0. A minor version contains bug fixes and minor enhancements. A Rancher upgrade may be required. A database migration may kick in on server startup.

Major Version

Example: upgrade from 1.2.2 to 2.0.0. A major version contains bug fixes and major enhancements. A Rancher upgrade may be required. A database migration may kick in on server startup. Manual Upgrade instructions may be provided.

Major version upgrades are incremental. Example: directly upgrading from 1.1.x to 3.0.x is not supported. To upgrade from 1.1.x to 3.0.x, upgrade to 2.x first.

Possible Upgrades

Docker-Compose Upgrade

Once volumes are mapped to the local disk (see Data Persistence for more info), you can safely upgrade by simply replacing your docker-compose.yml by newly downloaded one:

Data migration

When upgrading to a newer major version (Example: from 6.4.5 to 6.5.0), a data migration may be required. Data migration is done on server startup and may take some time to execute. During Data migration, the server is unavailable. Data migration happens automatically on server startup when required.

Some upgrades may require you to perform manual steps prior to upgrading, please see our Enterprise-Edition Migration Guides for more information.