ApsaraDB for Redis provides multiple solutions for data synchronization. These solutions use Data Transmission Service (DTS) and redis-shake. The solutions apply to the following scenarios: data synchronization between on-premises Redis databases and Alibaba Cloud services, active geo-redundancy, disaster recovery, and data analytics.
Data synchronization tools
- DTS (recommended)
DTS is a real-time data streaming service that is provided by Alibaba Cloud. The service allows you to migrate, subscribe to, and synchronize data by using stable and secure transmission channels. DTS supports one-way and two-way data synchronization. These synchronization solutions apply to scenarios such as active geo-redundancy and geo-disaster recovery.
- redis-shake
Redis-shake is an open source Linux-based tool developed by Alibaba Cloud. You can use this tool to parse (decode mode), restore (restore mode), back up (dump mode), and synchronize (sync or rump mode) data on ApsaraDB for Redis instances. For scenarios in which DTS is not suitable, you can use redis-shake to synchronize data.
The following table describes the differences between DTS and redis-shake based on the support that the services provide for Redis data synchronization. For more information, see the following table.
| Tool | Supported source database | Supported destination database | Supported architecture | Supported synchronization topology |
|---|---|---|---|---|
| DTS (recommended) |
|
|
Note Read/write splitting instances do not support data synchronization between ApsaraDB
for Redis instances that belong to different Alibaba Cloud accounts.
|
Note Only ApsaraDB for Redis Enhanced Edition instances (Redis 5.0) support two-way synchronization.
|
| redis-shake |
|
|
One-way synchronization |
Required permissions
DTS and redis-shake have different required permissions for different synchronization scenarios. Before you configure data synchronization, you must obtain relevant permissions for the source and destination databases based on the synchronization scenarios that are described in the following table.
| Tool | Scenario | Permission on the source database | Permission on the destination database |
|---|---|---|---|
| DTS (recommended) |
|
Read permissions | Read and write permissions |
|
Replication permissions
Note If the source database is a cluster instance or read/write splitting instance, you
cannot create an account that is granted the replication permissions. If the destination database is an ApsaraDB for Redis instance, you can
submit a ticket to create an account that has the replication permissions.
|
Read and write permissions | |
|
Permissions to run the SYNC or PSYNC command. | Read and write permissions | |
| redis-shake |
|
Permissions to run the SYNC or PSYNC command. | Read and write permissions |
|
Replication permissions | Read and write permissions |