side menu

Update version of BRIX Enterprise

To ensure data integrity when migrating with a version change of the BRIX edition, it is recommended to update each major version without skipping any. For instance, version X.1.1  can be updated to X.4.1.

The BRIX Enterprise update process consists of the following stages:

  1. Determine the number of update steps.
  2. Copy the configuration file from the currently installed version.
  3. Change the preset timeout values for data migration (optional).
  4. Update using Helm in the Kubernetes cluster for the BRIX application.

Step 1: Determine the number of update steps

  1. Determine the version of the installed chart with which the BRIX application was previously deployed or updated:

helm show chart brix365/brix365

  1. Determine the version of the latest chart:

helm repo add brix365 https://charts.brix365.com
helm repo update
helm search repo brix365/brix365

  1. If you need to update your chart for more than one version, install each major version until you reach the latest chart.

Important: when updating to the next major version, install its latest minor release.

начало примера

Examples

Major On-Premises releases use version numbers X.1, X.4, X.7, and X.10. In the examples, the current minor version is marked as N. When upgrading, use the latest available version:

  1. If the installed chart version is X.1.12 and the latest chart version is X.4.N, upgrade in a single step: directly to X.4.N.
  2. If the installed chart version is X.1.12 and the latest chart version is X.7.N, upgrade in two steps: X.1.12 > X.4.N > X.7.N.
  3. If the installed chart version is X.1.12 and the latest chart version is X.10.N, upgrade in three steps: X.1.12 > X.4.N > X.7.N > X.10.N.

конец примера

Please note that your current version in an LTS version, you can update directly to the next LTS version according to the release life cycle schedule.

To see the list of all BRIX versions, use the following command:

helm repo add brix365 https://charts.brix365.com
helm repo update
helm search repo brix365/brix365 --versions

Step 2: Copy the configuration file from the currently installed version

Copy the configuration file values-elma365.yaml to the current directory. Use this file saved at the installation stage or the last update.

If the values-elma365.yaml file was lost, retrieve the parameters of the current BRIX installation and save them into this file by executing the command:

helm get values brix365 [-n namespace] > values-brix365.yaml

Note that from version 2023.4.30, the structure of the values-elma365.yaml configuration file has been updated.

If you are updating from 2023.4.0-21 or earlier versions to 2023.4.30 or newer versions, you need to:

  1. Obtain the updated values-elma365.yaml configuration file:
  • For the latest version by executing the following command:

helm show values brix365/brix365 > values-brix365.yaml

  • For a certain version by executing the following command with the --version flag:

helm show values brix365/brix365 --version <brix365-chart-version> > values-brix365.yaml

Where <elma365-chart-version> is the system version required.

  1. Manually transfer the application parameters from the old sample values-elma365.yaml configuration file (versions prior to 2023.4.30) to the new configuration file.

Step 3: Change the preset timeout values for data migration (optional)

To ensure correct update, you specify the timeout for data migration in the commands. This time depends on the amount of information accumulated in the databases. Before starting the update:

  1. Estimate the amount of data.
  2. Open the values-elma365.yaml configuration file and change the preset parameters:
  • global.curlMigrationsMaxTime. Default setting is 3000. For example, increase the value to 18000.
  • deploy.appconfig.migrateTimeout. Default setting is 1h. Uncomment the parameter and set a new value, for example, 3h. The value of this parameter should be the same as the --timeout in the update command in step 4.
  1. Proceed to the next step of the update.

Step 4: Update using Helm in the Kubernetes cluster for the BRIX application

Execute the update of the BRIX application using the configuration file values-elma365.yaml. To do this:

  1. Sequentially perform the update for each intermediate minor version if there are intermediate minor versions (two or more update steps):

helm upgrade --install brix365 brix365/brix365 -f values-brix365.yaml --version <brix365-chart-version> --timeout=30m --wait [-n namespace]

The --timeout parameter defines the timeout for data update. It must match the value of deploy.appconfig.migrateTimeout if you changed it in the configuration file in step 3.

If the data volume is small, updating the application takes 10-30 minutes at each step.

  1. Perform the update to the latest version:

helm upgrade --install brix365 brix365/brix365 -f values-brix365.yaml --timeout=30m --wait [-n namespace]

The --timeout parameter defines the timeout for data update. It must match the value of deploy.appconfig.migrateTimeout if you changed it in the configuration file in step 3.

If the data volume is small, updating the application takes 10-30 minutes. Wait for the update of the BRIX Enterprise application version to complete.

affinity-antiaffinity.html offline-version-update-enterprise.html