Introduction to Migration with DCS
Migration Modes
DCS for Redis supports online migration (in full or incrementally) and backup migration (by importing backup files).
- Backup migration is suitable when the source and target Redis instances are not connected, and the source Redis instance does not support the SYNC and PSYNC commands. The data source can be an OBS bucket or a Redis instance.
- Importing data from an OBS bucket: Download the source Redis data and then upload it to an OBS bucket in the same region as the target DCS Redis instance. DCS will read the backup data from the OBS bucket and migrate the data into the target instance.
This migration mode can be used for migrating data from other Redis vendors or self-hosted Redis to DCS for Redis.
- Importing data from a Redis instance: Back up the source Redis data and then migrate the backup data to DCS for Redis.
- Importing data from an OBS bucket: Download the source Redis data and then upload it to an OBS bucket in the same region as the target DCS Redis instance. DCS will read the backup data from the OBS bucket and migrate the data into the target instance.
- Migrating data online: 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.
The following table describes data migration modes supported by DCS.
Data can be migrated only from DCS Redis instances or self-hosted Redis. After data migration, change the instance connection address to the target instance address.
Data migration is not supported if the DCS instance is created by another service, such as ROMA Connect, or by calling an API.
Migration Mode |
Source |
Target: DCS |
||
---|---|---|---|---|
Single-node or master/standby |
Proxy Cluster |
Redis Cluster |
||
Importing backup files |
AOF/RDB file |
√ |
√ |
√ |
Migrating data online |
DCS for Redis: Single-node or master/standby |
√ |
√ |
√ |
DCS for Redis: Proxy Cluster
NOTE:
Proxy Cluster DCS Redis 3.0 instances cannot be used as the source, while Proxy Cluster DCS Redis 4.0 or 5.0 instances can. |
√ |
√ |
√ |
|
DCS for Redis: Redis Cluster |
√ |
√ |
√ |
|
Self-hosted Redis: single-node or master/standby |
√ |
√ |
√ |
|
Self-hosted Redis: proxy-based cluster |
√ |
√ |
√ |
|
Self-hosted Redis: Redis Cluster |
√ |
√ |
√ |
|
Other Redis: single-node or master/standby |
√ |
√ |
√ |
|
Other Redis: proxy-based cluster |
√ |
√ |
√ |
|
Other Redis: Redis Cluster |
√ |
√ |
√ |
|
NOTE:
You can migrate data online in full or incrementally from other cloud Redis to DCS for Redis if they are connected and the SYNC and PSYNC commands can be run on the source Redis. However, some instances provided by other cloud vendors may fail to be migrated online. In this case, migrate data through backup import or use other migration schemes. |
- DCS for Redis refers to Redis instances provided by DCS
- Self-hosted Redis refers to self-hosted Redis on the cloud, from other cloud vendors, or in on-premises data centers.
- Other Redis refers to Redis services provided by other cloud vendors.
- √: Supported. ×: Not supported.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot