Taking a snapshot of one Elasticsearch cluster and restoring it to another

Important

Elasticsearch is only supported up to version 6.8, which is no longer supported by Elastic. We therefore recommend using Storage as a Service instead, or if you do want to continue using self-hosted storage, using OpenSearch.

1. Prepare the source and target Elasticsearch clusters by following the steps under Preparing and configuring the repositories.

   Note

   • If there are multiple nodes per Elasticsearch cluster, make sure the first step in Preparing the source Elasticsearch cluster has been properly executed before proceeding with the remaining steps.
   • Verify that an Elasticsearch repository was created on the source Elasticsearch cluster.

   The snapshot repository has now been initialized on both Elasticsearch clusters.

2. Stop both DataMiner Agents.

   Note

   If you have configured to have your data offloaded to multiple Elasticsearch clusters, DataMiner must be stopped before continuing with the procedure to avoid the active DMA from continuing to write data to the nodes that will become increasingly more out of sync.

3. Take a snapshot on the source Elasticsearch cluster.

4. Copy the snapshot and initialize the target repository.

   Tip

   To speed up the process, you may need to archive files and copy the archive instead of the files. Make sure the target Elasticsearch cluster can unzip the archive when it is copied to the server.

5. Restore the snapshot on the target Elasticsearch cluster, as instructed under Restoring the snapshot

   Note

   If there is data on the remote Elasticsearch cluster that should be overwritten, delete it using the delete index API.