Migrate data between ApsaraDB for Redis instances across Alibaba Cloud accounts - Data Transmission Service

This topic describes how to migrate data between ApsaraDB for Redis instances across Alibaba Cloud accounts by using Data Transmission Service (DTS). DTS supports full data migration and incremental data migration. When you configure a data migration task, you can select both types to ensure service continuity.

Prerequisites

The available storage space of the destination ApsaraDB for Redis instance is larger than the total size of the data in the source ApsaraDB for Redis instance.
If the source ApsaraDB for Redis instance is a Community Edition instance, the engine version is 4.0 or 5.0. If the source ApsaraDB for Redis instance is an Enhanced Edition (Tair) instance, the engine version is 5.0.

Background information

In this example, two ApsaraDB for Redis instances are created by different Alibaba Cloud accounts. You want to migrate data from the ApsaraDB for Redis instance of Account A to the ApsaraDB for Redis instance of Account B. The following figure shows the architecture of the migration solution.

Redis跨账号迁移架构图

To migrate data between ApsaraDB for Redis instances of different Alibaba Cloud accounts, you must perform the steps described in the following table to configure a data migration task.

Step	Description
1. Use Account A that owns the source instance to log on to the Resource Access Management (RAM) console and grant the required permissions to a RAM role. For more information, see the Preparations section of this topic.	When you configure the RAM role, set Account B as the trusted account and authorize the RAM role to access the cloud resources of Account A.
2. Use Account B that owns the destination instance to log on to the DTS console and configure the data migration task. For more information, see the Procedure section of this topic.	DTS can read the information about the source ApsaraDB for Redis instance across Alibaba Cloud accounts.

Supported source and destination databases

The following table describes the supported databases when you perform data migration between ApsaraDB for Redis instances across Alibaba Cloud accounts.

Source database	Destination database
ApsaraDB for Redis instance Self-managed database that is hosted on Elastic Compute Service (ECS) Self-managed database that is connected over Express Connect, VPN Gateway, or Smart Access Gateway Self-managed database that is connected over Cloud Enterprise Network (CEN)	ApsaraDB for Redis instance Self-managed database that is hosted on ECS Self-managed database that is connected over Express Connect, VPN Gateway, or Smart Access Gateway Self-managed database that is connected over CEN

Limits

Category	Description
Limits on the source database	Bandwidth requirements: The server on which the source database is deployed must have sufficient outbound bandwidth. Otherwise, the data migration speed decreases. You must enable the data logging and append-only file (AOF) logging features for the source database. The database version of the source ApsaraDB for Redis instance cannot be 2.8. Limits on operations: If you perform only full data migration, do not write data to the source database during data migration. Otherwise, data may be inconsistent between the source and destination databases. To ensure data consistency, we recommend that you select full data migration and incremental data migration as the migration types. Limits on data migration from a standalone Redis database to a Redis database deployed in the cluster architecture: Each command can be run only on a single slot in a Redis database deployed in the cluster architecture. If you perform operations on multiple keys in the source database and the keys belong to different slots, the following error occurs: `CROSSSLOT Keys in request don't hash to the same slot` We recommend that you perform operations on only one key during data migration. Otherwise, the migration task is interrupted. To ensure the stability of data migration, DTS inserts a key prefixed with DTS_REDIS_TIMESTAMP_HEARTBEAT into the source database to record when data is updated. If the source database is deployed in a cluster architecture, DTS inserts the key into each shard of the cluster. The key is filtered out during data migration. After the data migration task is complete, the key expires. If the source database is a read-only database or the source database account that is used to run the data migration task does not have the permissions to run the SETEX command, the reported latency may be inaccurate.
Other limits	A storage-optimized instance of ApsaraDB for Redis Enhanced Edition (Tair) cannot be configured as the source or destination database. If data eviction is triggered due to insufficient memory of the destination database, data inconsistency may occur between the source and destination databases. This is because the default data eviction policy (maxmemory-policy) of the destination database is volatile-lru. However, this does not affect the migration task. In this case, we recommend that you set the data eviction policy of the destination database to noeviction. If the memory of the destination database is insufficient, DTS fails to write data to the destination database and the migration task fails, but data of the destination database is not lost due to data eviction. Note For more information about data eviction policies, see How does ApsaraDB for Redis evict data by default? If you call Lua scripts by running the EVAL or EVALSHA command, DTS cannot identify whether these Lua scripts are executed on the destination database. This is because the destination database does not explicitly return the execution results of Lua scripts during incremental data migration. When DTS runs the `PSYNC` or `SYNC` command to transfer data of the LIST type, DTS does not perform the `FLUSH` operation on the existing data in the destination instance. As a result, the destination instance may contain duplicate data records. If an expiration policy is enabled for specific keys in the source database, these keys may not be immediately deleted after they expire. Therefore, the number of keys in the destination instance may be less than that in the source database. You can run the INFO command to view the number of keys in the destination database. Note The number of keys that do not have the expiration policy enabled or have not expired is the same in the source and destination databases. To ensure compatibility, the version of the destination Redis database must be the same as or later than that of the source Redis database. Note If the version of the destination database is earlier than that of the source database, database compatibility issues may occur. Before you migrate data, evaluate the impact of data migration on the performance of the source and destination databases. We recommend that you migrate data during off-peak hours. During full data migration, DTS uses read and write resources of the source and destination databases. This may increase the loads of the database servers. During full data migration, concurrent INSERT operations cause fragmentation in the tables of the destination database. After full data migration is complete, the size of used tablespace of the destination database is larger than that of the source database. DTS attempts to resume the data migration task that failed within the last seven days. Before you switch workloads to the destination database, you must stop or release the failed tasks. You can also execute the `REVOKE` statement to revoke the write permissions from the accounts that are used by DTS to access the destination database. Otherwise, the data in the source database overwrites the data in the destination instance after the task is resumed. If both the source and destination databases are of ApsaraDB for Redis Community Edition or Enhanced Edition, take note of the following limits: If the database configurations are changed, such as the specifications or port number, DTS cannot obtain continuous log data or correct connection information. As a result, the data migration task is interrupted. To ensure data consistency, we recommend that you delete the data in the destination database and reconfigure the data migration task after the database configurations are changed. If the destination instance is deployed in a cluster architecture and the amount of memory used by a shard in the destination instance reaches the upper limit, or if the available storage space of the destination instance is insufficient, the data synchronization task fails due to out of memory (OOM). If the Transparent Data Encryption (TDE) feature is enabled for the destination database, you cannot use DTS to migrate data. If resumable upload fails during data migration due to transient connections that occur on the source Redis database, full data may be migrated to the destination database again. This may cause data inconsistency between the source and destination databases.
Special cases	If the source database is a self-managed Redis database, take note of the following limits: If you perform a primary/secondary switchover on the source database when the data migration task is running, the data migration task fails. DTS calculates migration latency based on the timestamp of the latest migrated data in the destination database and the current timestamp in the source database. If no DML operation is performed on the source database for an extended period of time, the migration latency may be inaccurate. If the latency of the data migration task is excessively high, you can perform a DML operation on the source database to update the latency. Note If you select an entire database as the object to be migrated, you can create a heartbeat table. The heartbeat table is updated or receives data every second. If resumable upload fails during data migration due to transient connections that occur on the source Redis database, full data may be migrated to the destination database again. This may cause data inconsistency between the source and destination databases.

Migration types

Migration type	Description
Full data migration	DTS migrates the existing data of objects from the source database to the destination database.
Incremental data migration	After full data migration is complete, DTS migrates incremental data from the source database to the destination database. Incremental data migration allows data to be migrated smoothly without interrupting the services of self-managed applications during data migration.

Commands that can be incrementally migrated

APPEND
BITOP, BLPOP, BRPOP, and BRPOPLPUSH
DECR, DECRBY, and DEL
EVAL, EVALSHA, EXEC, EXPIRE, and EXPIREAT
FLUSHALL and FLUSHDB
GEOADD and GETSET
HDEL, HINCRBY, HINCRBYFLOAT, HMSET, HSET, and HSETNX
INCR, INCRBY, and INCRBYFLOAT
LINSERT, LPOP, LPUSH, LPUSHX, LREM, LSET, and LTRIM
MOVE, MSET, MSETNX, and MULTI
PERSIST, PEXPIRE, PEXPIREAT, PFADD, PFMERGE, PSETEX, and PUBLISH
RENAME, RENAMENX, RESTORE, RPOP, RPOPLPUSH, RPUSH, and RPUSHX
SADD, SDIFFSTORE, SELECT, SET, SETBIT, SETEX, SETNX, SETRANGE, SINTERSTORE, SMOVE, SPOP, SREM, and SUNIONSTORE
ZADD, ZINCRBY, ZINTERSTORE, ZREM, ZREMRANGEBYLEX, ZUNIONSTORE, ZREMRANGEBYRANK, and ZREMRANGEBYSCORE
XADD, XCLAIM, XDEL, XAUTOCLAIM, XGROUP CREATECONSUMER, and XTRIM

Preparations

Use the Alibaba Cloud account that owns the source ApsaraDB for Redis instance to log on to the Alibaba Cloud Management console. Create a RAM role and set the Alibaba Cloud account that owns the destination Redis instance as the trusted account. Then, authorize the RAM role to access the cloud resources of source Alibaba Cloud account. For more information, see Configure RAM authorization for cross-account DTS tasks.

Procedure

Use the Alibaba Cloud account that owns the destination ApsaraDB for Redis instance to log on to the Data Management (DMS) console and go to the Data Migration Tasks page.
1. Log on to the DMS console.
2. In the top navigation bar, move the pointer over DTS.
3. Choose DTS (DTS) > Data Migration.
Note
- The actual steps that you need to perform may vary based on the mode and layout of the DMS console. For more information, see Simple mode and Customize the layout and style of the DMS console.
- You can also go to the Data Migration Tasks page of the new DTS console.
From the drop-down list next to Data Migration Tasks, select the region in which the data migration instance resides.
Note
If you use the new DTS console, you must select the region in which the data migration instance resides in the upper-left corner.

Click Create Task. In the Create Task wizard, configure the source and destination databases. The following table describes the parameters.

Warning

After you configure the source and destination databases, we recommend that you read the limits that are displayed in the upper part of the page. Otherwise, the task may fail or data inconsistency may occur.

Section	Parameter	Description
N/A	Task Name	The name of the task. DTS automatically assigns a name to the task. We recommend that you specify a descriptive name that makes it easy to identify the task. You do not need to specify a unique task name.
Source Database	Select an existing DMS database instance	The database instance that you want to use. You can determine whether to select an existing instance based on your business requirements. If you select an existing instance, DTS automatically populates the parameters for the instance. If you do not select an existing instance, you must configure parameters for the source database.
	Database Type	The type of the source database. Select ApsaraDB for Redis Enhanced Edition (Tair).
	Access Method	The access method of the source database. Select Alibaba Cloud Instance.
	Instance Region	The region in which the source ApsaraDB for Redis instance resides.
	Replicate Data Across Alibaba Cloud Accounts	Specifies whether to migrate data across Alibaba Cloud accounts. In this example, Yes is selected.
	Alibaba Cloud Account	The ID of the Alibaba Cloud account that owns the source ApsaraDB for Redis instance. Note To obtain the ID of the Alibaba Cloud account that owns the source ApsaraDB for Redis instance, log on to the Account Management console by using this account. The account ID is displayed on the Basic Information page.
	RAM Role Name	The name of the RAM role that you created by following the instructions in the Preparations section of this topic.
	Database Password	The database password of the source ApsaraDB for Redis instance. The database account that corresponds to the password must have the read permissions. If you forget the password, you can reset the password. For more information, see Change or reset the password. If you use the default account whose username is the same as the instance ID, you need to enter only the password. If you use a custom account, specify the password in the `<Custom account username>:<Password>` format. Example: testaccount:Test1234. Note This parameter is optional and can be left empty if no database password is set for the source ApsaraDB for Redis database.
Destination Database	Select an existing DMS database instance	The database instance that you want to use. You can determine whether to select an existing instance based on your business requirements. If you select an existing instance, DTS automatically populates the parameters for the instance. If you do not select an existing instance, you must configure parameters for the destination database.
	Database Type	The type of the destination database. Select ApsaraDB for Redis Enhanced Edition (Tair).
	Access Method	The access method of the destination database. Select Alibaba Cloud Instance.
	Instance Region	The region in which the destination ApsaraDB for Redis instance resides.
	Instance ID	The ID of the destination ApsaraDB for Redis instance.
	Database Password	The database password of the destination ApsaraDB for Redis instance. The database account that corresponds to the password must have the read permissions. If you forget the password, you can reset the password. For more information, see Change or reset the password. If you use the default account whose username is the same as the instance ID, you need to enter only the password. If you use a custom account, specify the password in the `<Custom account username>:<Password>` format. Example: testaccount:Test1234.

In the lower part of the page, click Test Connectivity and Proceed.
If the source or destination database is an Alibaba Cloud database instance, such as an ApsaraDB RDS for MySQL or ApsaraDB for MongoDB instance, DTS automatically adds the CIDR blocks of DTS servers to the IP address whitelist of the instance. If the source or destination database is a self-managed database hosted on an Elastic Compute Service (ECS) instance, DTS automatically adds the CIDR blocks of DTS servers to the security group rules of the ECS instance, and you must make sure that the ECS instance can access the database. If the self-managed database is hosted on multiple ECS instances, you must manually add the CIDR blocks of DTS servers to the security group rules of each ECS instance. If the source or destination database is a self-managed database that is deployed in a data center or provided by a third-party cloud service provider, you must manually add the CIDR blocks of DTS servers to the IP address whitelist of the database to allow DTS to access the database. For more information, see the "CIDR blocks of DTS servers" section of the Add the CIDR blocks of DTS servers topic.
Warning
If the public CIDR blocks of DTS servers are automatically or manually added to the IP address whitelist of a database instance or to the security group rules of an ECS instance, security risks may arise. Therefore, before you use DTS to migrate data, you must understand and acknowledge the potential risks and take preventive measures, including but not limited to the following measures: enhancing the security of your account and password, limiting the ports that are exposed, authenticating API calls, regularly checking the IP address whitelist or ECS security group rules and forbidding unauthorized CIDR blocks, and connecting the database to DTS by using Express Connect, VPN Gateway, or Smart Access Gateway.

Configure the objects to be migrated and advanced settings.

Parameter	Description
Migration Types	We recommend that you select both Full Data Migration and Incremental Data Migration. If you do not have the permissions to run the SYNC or PSYNC command on the source database, select Full Data Migration. For more information, see the Migration types section of this topic.
Processing Mode of Conflicting Tables	Precheck and Report Errors: checks whether the destination database is empty. If the destination database is empty, the precheck is passed. Otherwise, an error is returned during the precheck and the data migration task cannot be started. Ignore Errors and Proceed: skips the precheck on whether the destination database is empty. Warning If you select Ignore Errors and Proceed, the data in the source database overwrites the data in the destination database that has the same keys as the source data. This may cause data loss in the destination database. Proceed with caution.
Source Objects	Select one or more objects from the Source Objects section and click the icon to add the objects to the Selected Objects section. Note You can select only databases as the objects to be migrated. You cannot select keys as the objects to be migrated.
Selected Objects	If you want to select a database to which data is migrated from DB 0 to DB 255 or filter the data to be migrated by prefix, you can use the object name mapping feature or the filtering feature. In the Selected Objects section, right-click the database that you want to migrate. In the Edit Schema dialog box, configure the parameters. For more information, see Map object names and Set filter conditions. Note You cannot map multiple object names at a time.

Click Next: Advanced Settings to configure advanced settings.

Data Verification Settings
For more information about how to configure the data verification feature, see Configure data verification.

Advanced Settings

Parameter	Description
Select the dedicated cluster used to schedule the task	By default, DTS schedules the data migration task to the shared cluster if you do not specify a dedicated cluster. You can also purchase and specify a dedicated cluster of the required specifications to run the data migration task. For more information, see What is a DTS dedicated cluster.
Set Alerts	Specifies whether to configure alerting for the data migration task. If the task fails or the migration latency exceeds the specified threshold, the alert contacts will receive notifications. Valid values: No: does not configure alerting. Yes: configures alerting. If you select Yes, you must also specify the alert threshold and alert contacts. For more information, see Configure monitoring and alerting.
Retry Time for Failed Connections	The retry time range for failed connections. If the source or destination database fails to be connected after the data migration task is started, DTS immediately retries a connection within the retry time range. Valid values: 10 to 1440. Unit: minutes. Default value: 720. We recommend that you set the parameter to a value greater than 30. If DTS is reconnected to the source and destination databases within the specified retry time range, DTS resumes the data migration task. Otherwise, the data migration task fails. Note If you specify different retry time ranges for multiple data migration tasks that share the same source or destination database, the value that is specified later takes precedence. When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time range based on your business requirements. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.
The wait time before a retry when other issues occur in the source and destination databases.	The retry time range for other issues. For example, if DDL or DML operations fail to be performed after the data migration task is started, DTS immediately retries the operations within the retry time range. Valid values: 1 to 1440. Unit: minutes. Default value: 10. We recommend that you set the parameter to a value greater than 10. If the failed operations are successfully performed within the specified retry time range, DTS resumes the data migration task. Otherwise, the data migration task fails. Important The value of the The wait time before a retry when other issues occur in the source and destination databases parameter must be smaller than the value of the Retry Time for Failed Connections parameter.
Enable Throttling for Full Data Migration	Specifies whether to enable throttling for full data migration. During full data migration, DTS uses the read and write resources of the source and destination databases. This may increase the loads of the database servers. You can enable throttling for full data migration based on your business requirements. To configure throttling, you must configure the Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s) parameters. This reduces the loads of the destination database server. Note This parameter is displayed only when Full Data Migration is selected as Migration Types.
Enable Throttling for Incremental Data Migration	Specifies whether to enable throttling for incremental data migration. If you select Yes, you can configure the RPS of Incremental Data Migration and Data migration speed for incremental migration (MB/s) parameters based on your business requirements. This reduces the loads of the destination database server. Note This parameter is available only if you select Full Data Migration and Incremental Data Migration as the migration types.Migration Types
Environment Tag	The environment tag that is used to identify the DTS instance. You can select an environment tag based on your business requirements. In this example, no environment tag is selected.
Extend Expiration Time of Destination Database Key	The extended time period for keys migrated from the source database to the destination instance to remain valid. Unit: seconds. If specific commands are used, such as the following commands, we recommend that you set the parameter to 600 to ensure data consistency: `expire key seconds pexpire key milliseconds expireat key timestamp pexpireat key timestampMs`
Configure ETL	Specifies whether to enable the extract, transform, and load (ETL) feature. For more information, see What is ETL? Valid values: Yes: configures the ETL feature. You can enter data processing statements in the code editor. For more information, see Configure ETL in a data migration or data synchronization task. No: does not configure the ETL feature.

Save the task settings and run a precheck.
- To view the parameters to be specified when you call the relevant API operation to configure the DTS task, move the pointer over Next: Save Task Settings and Precheck and click Preview OpenAPI parameters.
- If you do not need to view or have viewed the parameters, click Next: Save Task Settings and Precheck in the lower part of the page.
Note
- Before you can start the data migration task, DTS performs a precheck. You can start the data migration task only after the task passes the precheck.
- If the task fails to pass the precheck, click View Details next to each failed item. After you troubleshoot the issues based on the error message, you can run a precheck again.
- If an alert is triggered for an item during the precheck:
  If the alert item cannot be ignored, click View Details next to the failed item and troubleshoot the issues. Then, run a precheck again.
  If the alert item can be ignored, click Confirm Alert Details. In the View Details dialog box, click Ignore. In the message that appears, click OK. Then, click Precheck Again to run a precheck again. If you ignore the alert item, data inconsistency may occur and your business may be exposed to potential risks.
Wait until the success rate becomes 100%. Then, click Next: Purchase Instance.

On the Purchase Instance page, configure the Instance Class parameter for the data migration instance. The following table describes the parameters.

Section	Parameter	Description
New Instance Class	Resource Group	The resource group to which the data migration instance belongs. Default value: default resource group. For more information, see What is Resource Management?
New Instance Class	Instance Class	DTS provides instance classes that vary in the migration speed. You can select an instance class based on your business scenario. For more information, see Specifications of data migration instances.

Read and agree to Data Transmission Service (Pay-as-you-go) Service Terms by selecting the check box.
Click Buy and Start to start the data migration task. You can view the progress of the task in the task list.