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.

Active-Active data migration process
During the migration, make sure that any applications that connect to the Active-Active database are read-only to make sure the dataset is identical to the source database during the migration process. You may continue to write to the source database during the migration process.

To migrate a Redis Enterprise Software database to Active-Active:

  1. If you are using the new Cluster Manager UI, switch to the legacy admin console.

    Select switch to legacy admin console from the dropdown.
  2. Create a new Active-Active database.

    After the Active-Active database is activated, you see the database’s configuration.

  3. Click Edit at the bottom of the database configuration.

  4. Enable Migration using Replica Of.

  5. Click Continue to confirm that you want to flush the data from the Active-Active database.

  6. 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:

      1. Log in to the Web UI of the cluster that hosts the source database.

      2. In databases, click on the database and go to configuration.

      3. Under Endpoint, click on Get Replica Of source URL.

        Replica Of source URL

      4. 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.
      5. In the destination database, paste the URL of the source endpoint in the Replica Of box, and click Save.

      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 -


        Where the password is the Redis password represented with URL encoding escape characters.

      • If the database has no password -

    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.
  7. Click Update at the bottom of the page.

  8. When the synchronization icon turns green Synchronization complete, the migration is complete. Note that migration can take minutes to hours to complete depending on the dataset size and network quality.

  9. Edit the configuration of the Active-Active database and select the Stop button to disable Migration using Replica Of. disable migration using replica of

  10. Redirect your database connections to the Active-Active database.