Based on Data Transmission Service (DTS) and the redis-shake synchronization tool, ApsaraDB for Redis provides multiple data synchronization solutions. These solutions apply to the following scenarios: data synchronization between on-premises Redis databases and Alibaba Cloud services, active geo-redundancy, disaster recovery, and data analysis.
Data synchronization tools
- DTS (Recommended)
DTS is a real-time data streaming service. 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 flexible and efficient tool to parse (decode mode), restore (restore mode), back up (dump mode), and synchronize (sync or rump mode) data on ApsaraDB for Redis instances. In scenarios where DTS is not applicable, you can use redis-shake to synchronize data.
The following table describes the differences between DTS and redis-shake in their support for Redis 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 to synchronize data among 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 | Permissions on the source database | Permissions on the destination database |
|---|---|---|---|
| DTS (Recommended) |
|
Read permissions | Read and write permissions |
|
Copy permissions
Note If the source database is a cluster instance or read/write splitting instance, you
cannot create an account that is granted the copy permissions.To create such accounts, submit a ticket.
|
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 |
|
Copy permissions | Read and write permissions |