If the source and target instances are interconnected and the SYNC and PSYNC commands are supported in the source instance, data can be migrated online in full or incrementally from the source to the target.
Table 1 lists the requirements on the network between the online migration task, source Redis, and target Redis.
Source Redis Type |
Target Redis Type |
Network Requirement on Online Migration |
---|---|---|
Redis in the cloud |
Redis in the cloud |
When creating an online migration task, ensure that the online migration task is in the same VPC as the source and target Redis. If they are not in the same VPC, enable cross-network access between the migration task and the source and target Redis. To enable cross-network access, create a VPC peering connection by referring to section "VPC Peering Connection" in Creating a VPC. |
Redis in the cloud |
Self-hosted Redis |
When creating an online migration task, ensure that the migration task and the source Redis are in the same VPC. Then, enable cross-network access between the migration task and the target Redis. To enable cross-network access, create a VPC peering connection by referring to section "VPC Peering Connection" in Creating a VPC. |
Self-hosted Redis |
Redis in the cloud |
When creating an online migration task, ensure that the migration task and the target Redis are in the same VPC. Then, enable cross-network access between the migration task and the source Redis. To enable cross-network access, create a VPC peering connection by referring to section "VPC Peering Connection" in Creating a VPC. |
Self-hosted Redis |
Self-hosted Redis |
After creating an online migration task, enable cross-network access between the migration task and the source and target Redis, respectively. To enable cross-network access, create a VPC peering connection by referring to section "VPC Peering Connection" in Creating a VPC. |
Supported migration types are Full and Full + incremental, which are described in Table 2.
Migration Type |
Description |
---|---|
Full |
Suitable for scenarios where services can be interrupted. Data is migrated at one time. Source instance data updated during the migration will not be migrated to the target instance. |
Full + incremental |
Suitable for scenarios requiring minimal service downtime. The incremental migration parses logs to ensure data consistency between the source and target instances. Once incremental migration starts, it remains Migrating until you click Stop in the Operation column. After the migration is stopped, data in the source instance will not be lost, but data will not be written to the target instance. When the transmission network is stable, the delay of incremental migration is within seconds. The actual delay depends on the transmission quality of the network link. |
If the instance is password-protected, you can click Test Connection to check whether the instance password meets the requirements.
If the source and target Redis instances are connected but are in different regions of DCS, you can only select Self-hosted Redis for Target Redis Type and enter the instance addresses, regardless of whether the target Redis instance is self-hosted or in the cloud.
Go back to the data migration task list. After the migration is successful, the task status changes to Successful.
If the migration type is full+incremental, the migration task status will remain Migrating until you click Stop.