search string side menu

BRIX On-Premises > BRIX On-Premises Enterprise / Data migration from embedded to external databases in BRIX Enterprise: customized utility

Data migration from embedded to external databases in BRIX Enterprise: customized utility

You can migrate data from databases within a Kubernetes cluster to external storages using:

The main steps of data migration using Elma365-Backupper utility:

  1. Back up databases.
  2. Update BRIX application parameters.
  3. Restore databases.

начало внимание

After migrating databases to external storages, system reactivation is required.

конец внимание

Step 1: Back up databases

  1. Install the Elma365-Backupper utility and set up its configuration. Read more about it in the Back up and recover databases article.
  2. Back up the BRIX application databases:

elma365-backupper backup <<db-type>>

Where <<db-type>> is the name of the database that you want to back up. Value options:

  • mongo specifies MongoDB.
  • postgres specifies PostgreSQL.
  • s3 specifies S3 storage.
  • all specifies all databases (MongoDB, PostgreSQL, S3).

Step 2: Update BRIX application parameters

  1. Since the Elma365-Backupper utility gets the database path settings from the values-elma365.yaml configuration file, specify the values of external storages in this file.
  2. Update the BRIX application parameters using the values-elma365.yaml configuration file.

Updating parameters via the Internet

  1. Identify the version of the chart from which the BRIX application was installed or updated:

helm show chart elma365/elma365

 
Example of how to execute the command:

embedded-to-external-database-enterprise-1

The chart version will be specified in the version string. Save this value for the next step.

  1. Update the BRIX application parameters using the values-elma365.yaml configuration file. To do this, use the following command, specifying the installed chart version for the --version key instead of <elma365-chart-version>:

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

 

Updating parameters without the Internet connection

 
Go to the folder with the downloaded BRIX chart and run the command:

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

 
The parameter upgrade takes 10-30 minutes. Wait for it to complete.

 

Step 3: Restore databases

  1. Restoring from backup should be done to empty databases and S3 storage. So clean them with the --cleanup-databases key.
  2. Restore the databases from the last backup:

elma365-backupper restore <<db-type>>

Where <<db-type>> is the name of the database for which you want to get a list of backups. Value options:

  • mongo specifies MongoDB.
  • postgres specifies PostgreSQL.
  • s3 specifies S3 storage.
  • all specifies all databases (MongoDB, PostgreSQL, S3).
  1. Reactivate the system.

 

embedded-to-external-database-enterprise.html enable-portable-services.html