Migrating Data to Another Cluster

The goal of this document is to describe how to migrate data from one cluster to another.

Before you Begin

Your cluster must be on the Enterprise plan to use this feature.

You need at least two Enterprise clusters with the same configuration. For example, if one cluster contains custom classes, backup, or persistence, you should enable and configure these options for the other cluster as well.

Step 1. Create WAN Replication

In this tutorial, we are going to use a fantastic Hazelcast feature for data migration which is called WAN Replication

In order to create WAN Replication, you can go to Cluster Detail > Settings > Wan Replication and click Create New Replication

WAN Replication settings

WAN Replication configuration

After setting all these parameters, you can click Next to select and configure consumer cluster.

Part 2 of the WAN Replication configuration

Settings on this screen for consumer cluster are same as publisher cluster except Active/Passive section. If you set consumer cluster as Active, data will be synchronized from/to publisher and consumer. If you set consumer cluster as Passive, data will be sent only from publisher to consumer. Once you configured settings for consumer, you can click Save

Wan Replication is being set up

Within seconds, wan replication will be ready there.

Wan Replication is active

Once it is finished, you can verify it by going to Management Center Cluster Detail > Management Center > Enable then Management Center > Open Management Center.

When you connect publish cluster and try to write some data, you will see data will be replicated to consumer cluster.

You can synchronize all data by using Sync button in the WAN replication settings.

Step 2. Connect to a Cluster

After migration is done, you can connect to a new cluster via different clients, e.g. Java Client

Step 3. Delete the Old Cluster

You can delete your old cluster once migration finished and clients connected to a new cluster.

WAN replication must be deleted before cluster deletion