DCS for Redis provides the following migration modes:
This migration mode can be used for migrating data from other Redis vendors or self-hosted Redis to DCS for Redis.
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 and Master/Standby |
Proxy Cluster |
Redis Cluster |
||
Importing backup files |
AOF files in OBS NOTE:
AOF files exported from Redis 4.0/5.0 instances and other instances with RDB compression enabled cannot be imported. |
√ |
√ |
× |
RDB files in OBS |
√ |
√ |
√ |
|
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 |
× |
× |
× |