Overview
This guide provides suggestions and instructions on how to migrate Redis data. For details on how to migrate Memcached data, see How Do I Migrate Memcached Data?
Due to variations of Redis application environments and scenarios, migration solutions must be detailed to address actual requirements. The time required for data migration is related to the data volume, the location of source Redis data, and the network bandwidth. Record and evaluate the duration during the rehearsal phase.
DCS Redis 3.0, 4.0, 5.0, and 6.0 (professional edition) instances can be used for data migration. Analyze Redis commands (reference: Redis Command Compatibility) used by your service systems and verify the commands one by one during the rehearsal phase. For technical support, contact Huawei customer service.

- Currently, the data migration function is free of charge in the OBT. You will be notified when data migration starts to be charged.
- Data migration is an important and stringent task requiring high accuracy and timeliness. It varies depending on specific services and operation environments.
- Cases provided in this document are for reference only. Consider your service scenarios and requirements during actual migration.
- Some commands in this document contain instance passwords, which will be recorded in the operating system (OS). Ensure that the passwords are not disclosed and clear operation records in a timely manner.
- DCS for Redis 3.0 is no longer provided. You can use DCS for Redis 4.0 or 5.0 instead.
Migration Mode |
Source |
Target: DCS |
||
---|---|---|---|---|
Single-Node and Master/Standby |
Proxy Cluster |
Redis Cluster |
||
Importing backup files |
OBS bucket: AOF files
NOTE:
AOF files exported from HUAWEI CLOUD Redis 4.0/5.0 instances and other instances with RDB compression enabled cannot be imported. |
√ |
√ |
× |
OBS bucket: RDB files |
√ |
√ |
√ |
|
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 single-node or master/standby Redis |
√ |
√ |
√ |
|
Self-hosted proxy-based cluster Redis |
√ |
√ |
√ |
|
Self-hosted Redis Cluster |
√ |
√ |
√ |
|
Other Redis: single-node or master/standby |
× |
× |
× |
|
Other Redis: proxy-based cluster |
× |
× |
× |
|
Other Redis: Redis Cluster |
× |
× |
× |

- 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 cloud Redis refers to Redis services provided by other cloud vendors.
- √: Supported. ×: Not supported.
- 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. For details, see Migration Tools and Schemes.
Feedback
Was this page helpful?
Provide feedbackFor any further questions, feel free to contact us through the chatbot.
Chatbot