Migrate a database to Active-Active
With Active-Active databases, applications can read and write to the same dataset from different geographical locations seamlessly and with latency less than 1 ms, without changing the way the application connects to the database. Active-Active databases also provide disaster recovery and accelerated data read-access for geographically distributed users.
If you have data in a single-region Redis Enterprise Software database that you want to migrate to an Active-Active database, you’ll need to create a new Active-Active database and migrate the data into the new database as a Replica Of the existing database. This process will gradually populate the data in the Active-Active database.
Before data migration starts, all data is flushed from the Active-Active database. The data is migrated to the Active-Active instance where you enabled Replica Of, and the data from that instance is copied to the other Active-Active instances. When data migration is finished, disable Replica Of and connect your applications to the Active-Active database.

To migrate an RS database to Active-Active:
-
Create a new Active-Active database.
After the Active-Active database is activated, you see the database’s configuration.
-
Click Edit at the bottom of the database configuration.
-
Enable Migration using Replica Of.
-
Click Continue to confirm that you want to flush the data from the Active-Active database.
-
Enter the URL of the source database endpoint (the order has no impact on replication).
-
For a source database in the same RS cluster - When you click on the box, the available databases are shown in the correct format for the URL of the source endpoint:
<database name>: redis://admin:<database_password>@<database_endpoint>:<database_port>
You can select the database that you want to use as the source.
-
For a source database in a different RS cluster:
-
Log in to the Web UI of the cluster that hosts the source database.
-
In databases, click on the database and go to configuration.
-
Under Endpoint, click on Get Replica Of source URL.
-
Click Copy to Clipboard to copy the URL of the source endpoint.
If you want a different internal password, you can click Regenerate Password.
Warning -If you regenerate the password, replication to existing destinations fails until you update their configuration with the new password. -
In the destination database, paste the URL of the source endpoint in the Replica Of box, and click
.
Note:For a source database on a different Redis Enterprise Software cluster, you can compress the replication data to save bandwidth. -
-
For a source database in an OSS Redis cluster - Enter the URL of the source endpoint in the format:
-
If the database has a password -
redis://:<redis_password>@<hostname>:<database_port>
Where the password is the Redis password represented with URL encoding escape characters.
-
If the database has no password -
redis://<hostname>:<database_port>
-
Note:If you used the mDNS protocol for the cluster name (FQDN), the client mDNS prerequisites must be met in order to communicate with other clusters. -
-
Click Update at the bottom of the page.
-
When the synchronization icon turns green
, the migration is complete. Note that migration can take minutes to hours to complete depending on the dataset size and network quality.
-
Edit the configuration of the Active-Active database and select the Stop button to disable Migration using Replica Of.
-
Redirect your database connections to the Active-Active database.