Skip to main content
Version: 10.3.2

Migrate Elasticsearch data to Work.AI v10.3.2

Before Work.AI v10.3, the ELK stack was located on MASTER servers. Starting with Work.AI v10.3 it is located on SUPERSET servers.

If you want to preserve Elasticsearh data during the upgrade process, you need to migrate the data manually. Alternatively, you can configure the ELK stack to remain on the MASTER servers.

The guide describes how to migrate Elasticsearch data from MASTER servers to SUPERSET servers when upgrading the platform from version 10.2.x to 10.3.2.

Prerequisites​

The data migration procedure includes the following two stages. You must execute them after preparing the new installer but before executing the upgrade process.

  1. Data backup. All data is copied from the elasticsearch/data directory to a backup location. You can use the existing storage (by default, vds-data/es_backup) or attach a dedicated storage.
  2. Restoration. Data is copied back from the backup location to the new elasticsearch/data directory on the SUPERSET servers.

To estimate the size of files in elasticsearch/data, run the following command from a MASTER server:

du -hs <elasticsearch_home>/data

Note that running the du command might take a significant amount of time. In HA mode, ensure that your backup storage has enough space to hold data from all three MASTER servers.

Back up Elasticsearch data​

Using the new installer, run the following command:

./install.sh backup elasticsearch

By default, Elasticsearch data is backed up to the vds-data/es_backup directory. To specify a different location, run:

./install.sh backup elasticsearch -e backup_dir=/path/to/es_backup
note

For a multipoint installation, make sure to run these commands on each MASTER server, adding -c local --limit ....

Restore Elasticsearch data​

Using the new installer, run the following command:

./install.sh restore elasticsearch

To restore from a different location, do as follows:

./install.sh restore elasticsearch -e backup_dir=/path/to/es_backup
note

For a multipoint installation, make sure to run these commands on each SUPERSET server, adding -c local --limit ....