Redis
UDTS can perform full + incremental task transfers, using native Redis or proxy-based distributed versions (including Surfercloud Redis distributed version, Codis, Twemproxy) as data sources/targets. The currently supported versions are 3.0 to 6.0 and 7.0 master-slave version. There may be compatibility issues with cross-major version migration, and it is recommended to migrate through a transit database. For example, when migrating from 3.x/4.x to 7.x, you need to create a 5.x/6.x version of the transit database, first migrate from 3.x/4.x to 5.x/6.x, and then migrate from 5.x/6.x to 7.x.
Function Limitations
- If the source is a read-write separation version, you need to use rump mode for migration. The migration can only be done in full, incremental is not supported. Version 7.0 does not support rump mode.
Attention
- The number of nodes in the source and target clusters does not need to be consistent.
- When the source Redis address is a public network address, and the source Redis is in cluster mode, it is necessary to bind NATGW to the subnet ID under the target VPC.
- Ensure that the
repl-diskless-syncconfiguration of the source database is set toNO. - If the source database is a distributed version (including Surfercloud Redis distributed version, Codis, Twemproxy), multiple tasks need to be created, and the source database of each task fills in the address of a distributed node, and the type selects the master-slave version.
- When the target database is Surfercloud Redis distributed version, select the distributed version for the target database type, and fill in the proxy address for the address.
- When the target database is Surfercloud Redis distributed Cluster version and a proxy address is provided, select the distributed version for the target database type, and fill in the proxy address for the address.
- When the target database is Surfercloud Redis distributed Cluster version and no proxy address is provided, select the cluster version for the target database type, and fill in the shard address for the address, connecting multiple addresses with ';'.
- When the target database is a cluster version, only migration of db0 is supported.
Redis Form Filling
| Parameter Name | Description |
|---|---|
| Address | Database address, only fill in the master address. In cluster mode, multiple addresses are connected with ";", for example: 192.168.1.100:6379;192.168.1.120:6379;192.168.1.130:26379 |
| Password | Redis password, not required |
| Redis Type | Cluster Mode/Master-Slave Mode/Distributed Version |
| VPC ID | VPC ID, the VPC that redis belongs to |
| Subnet | The subnet under the VPC, the subnet that redis belongs to |
| Enable Rump Sync | Rump sync is needed when the user does not have psync permission. |
Breakpoint Resume
The breakpoint resume feature will be automatically enabled under the following conditions
- The task has reached the incremental phase
- The source and target types are consistent, such as master-slave mode transferred to master-slave mode, cluster mode transferred to cluster mode
- When both the source and target are in cluster mode, the number of nodes in the source and target clusters are the same
- The source database version is from 3.0 to 6.0.
