All Products
Search

This Product

    Data Transmission Service:Sync self-managed Redis on ECS to Tair

    Document Center

    Data Transmission Service:Sync self-managed Redis on ECS to Tair

    Last Updated:Aug 27, 2026

    You can use Data Transmission Service (DTS) to synchronize data from a self-managed Redis instance on ECS to a Redis-compatible Tair instance.

    Warning

    Changing the architecture type of the source or destination database after configuring a data synchronization task will cause the task to fail.

    Prerequisites

    • You have a source self-managed Redis instance and a destination Tair instance. To create a destination Tair instance, see Step 1: Create an instance.

      Note

      • DTS supports only Tair instances in direct connection mode. For supported versions, see Synchronization solution overview.

      • DTS also supports one-way synchronization between Tair instances. The configuration is similar, so you can refer to this topic.

    • The destination Tair instance must have more storage space than the source self-managed Redis database uses.

    • If the source Redis uses a cluster architecture, each node must support the PSYNC command, and all nodes must share the same connection password.

    • The repl-timeout parameter of the source Redis instance defaults to 60 seconds. We recommend running config set repl-timeout 600 to set it to 600 seconds. If the source database contains a large amount of data, increase repl-timeout as needed.

    • The source account must have both PSYNC and SYNC permissions.

    Limitations

    Type

    Description

    Source database limitations

    • Do not run FLUSHDB or FLUSHALL on the source database. This causes data inconsistency between the source and destination.

    • If the bind parameter is configured in the redis.conf file of the source database, set its value to the internal IP address of the ECS instance to ensure that DTS can connect to the source database.

    • DTS inserts a key prefixed with DTS_REDIS_TIMESTAMP_HEARTBEAT into the source database to record update timestamps. For clusters, this key is inserted into each shard. The key is filtered during synchronization and expires after the task completes.

    • If the source database is a read-only instance or the DTS account does not have write (SETEX) permissions, the reported latency may be inaccurate.

    • To ensure connection stability, increase the value of the repl-backlog-size parameter in the redis.conf file.

    • If the source database has keys with an expiration policy, the destination database may report fewer keys when checked with a command like info. This is because expired keys may not be immediately deleted.

      Note

      The number of keys that do not have an expiration policy or have not expired is the same in both the source and destination databases.

    • When synchronizing from a standalone to a cluster Redis instance, Redis clusters allow a single command to operate on only one slot. Multi-key operations on keys in different slots return the following error:

      CROSSSLOT Keys in request don't hash to the same slot

      To prevent task interruptions, perform only single-key operations during DTS synchronization.

    • If the source Redis instance uses extended modules such as RedisJSON, RediSearch, RedisBloom, RedisTimeSeries, RedisGraph, RedisAI, RedisGears, RedisCell, RediSQL, redis-tdigest, or RedisCompat, DTS cannot parse their RDB storage formats and the task fails.

    Other limitations

    • To ensure compatibility, use the same version for the source and destination databases or synchronize from an earlier version to a later one.

    • Operations on the source or target Redis instance during synchronization, such as scaling, changing specifications, migrating availability zones, or changing the endpoint or port, can interrupt the task because DTS cannot obtain continuous log data or correct connection information. If this occurs, clear the synchronized data from the target before you reconfigure the task.

    • If the source or destination is a self-managed Redis (where Access Method is not Alibaba Cloud Instance) and its endpoint changes during synchronization (for example, due to a migration or primary/standby switchover), the task may experience retries, latency, or failures, and data inconsistency may occur. Monitor the task status and reconfigure it if abnormalities persist.

    • During an instance migration on a target Redis instance, such as a primary/standby switchover, data may be written only to memory without being replicated to the standby instance, which can cause data loss.

    • Initial full data synchronization increases the load on both the source and destination. If your databases handle high traffic or run on low-spec servers, synchronization may cause service interruptions. Evaluate the performance impact and run the task during off-peak hours.

    • When synchronizing between Redis clusters, do not run FLUSHDB or FLUSHALL on the source cluster. This causes data inconsistency between the source and destination.

    • If the target database runs out of memory, data eviction is triggered, causing data inconsistency because the default eviction policy (maxmemory-policy) of Tair (Redis OSS-Compatible) is volatile-lru. The task continues to run normally.

      To prevent this, set the eviction policy for the target database to noeviction. The task and writes fail when memory is exhausted, but no data is lost to eviction.

    • During DTS synchronization, do not write data to the destination database from any source other than DTS. Otherwise, data inconsistency between the source and destination databases will result.

    • If the destination instance is a cluster and one of its shards reaches its memory limit, or if the destination instance runs out of storage space, the DTS task fails due to an out-of-memory (OOM) error.

    • DTS does not support synchronization if Transparent Data Encryption (TDE) is enabled on the target instance.

    • Full data may be re-synchronized to the destination and cause data inconsistency under the following conditions:

      • A transient connection interruption occurs on the source or destination Redis instance, and resumable transmission fails.

      • A primary/standby switchover or a failover occurs on the source or destination Redis.

      • The endpoint of the source or destination Redis instance changes.

      • The synchronized objects of the DTS instance are modified.

    • If a Tair (Redis OSS-Compatible) instance has Transport Layer Security (TLS) encryption enabled, you must connect to it by using the SSL-encrypted method in DTS. TLSv1.3 is not supported. You cannot connect to an SSL-enabled Tair (Redis OSS-Compatible) instance by setting the Alibaba Cloud Instance to Alibaba Cloud Instance.

    • Restarting a synchronization instance that includes both full and incremental tasks may cause DTS to rerun both.

    • Restarting a synchronization instance may cause commands to execute more than once, leading to data inconsistency if non-idempotent commands such as INCRBY and LPUSH exist, or if full data re-synchronization is triggered.

    • If a task fails, DTS support staff will attempt to restore it within eight hours. During restoration, they may restart the task or adjust its parameters.

      Note

      Only DTS task parameters are modified—not database parameters. Parameters that may be adjusted include those listed in Modify instance parameters.

    Billing

    Type

    Fee

    Full data synchronization

    Free.

    Incremental data synchronization

    Charged. For details, see Billing overview.

    Supported synchronization topologies

    • One-to-one, one-way synchronization

    • One-to-many, one-way synchronization

    • Cascading one-way synchronization

    Topology details and usage notes are covered in Data synchronization topologies.

    Supported synchronization commands

    • APPEND

    • BITOP, BLPOP, BRPOP, BRPOPLPUSH

    • DECR, DECRBY, DEL

    • EVAL, EVALSHA, EXEC, EXPIRE, EXPIREAT

    • GEOADD, GETSET

    • HDEL, HINCRBY, HINCRBYFLOAT, HMSET, HSET, HSETNX

    • INCR, INCRBY, INCRBYFLOAT

    • LINSERT, LPOP, LPUSH, LPUSHX, LREM, LSET, LTRIM

    • MOVE, MSET, MSETNX, MULTI

    • PERSIST, PEXPIRE, PEXPIREAT, PFADD, PFMERGE, PSETEX

    • RENAME, RENAMENX, RESTORE, RPOP, RPOPLPUSH, RPUSH, RPUSHX

    • SADD, SDIFFSTORE, SELECT, SET, SETBIT, SETEX, SETNX, SETRANGE, SINTERSTORE, SMOVE, SPOP, SREM, SUNIONSTORE

    • ZADD, ZINCRBY, ZINTERSTORE, ZREM, ZREMRANGEBYLEX, ZUNIONSTORE, ZREMRANGEBYRANK, ZREMRANGEBYSCORE

    • SWAPDB, UNLINK (supported only if the source Redis instance is version 4.0 or later)

    • XADD, XCLAIM, XDEL, XAUTOCLAIM, XGROUP CREATECONSUMER, XTRIM

    Note

    • The PUBLISH command is not synchronized.

    • For Lua scripts invoked with EVAL or EVALSHA, DTS cannot guarantee that the scripts are successfully executed on the destination during incremental data synchronization. This is because the destination does not explicitly return an execution result.

    • For List data types, DTS does not clear existing data on the destination when retransmitting data with sync or psync. This may result in duplicate data.

    Procedure

    1. Go to the data synchronization task list page in the destination region. You can do this in one of two ways.

      DTS console

      1. Log on to the DTS console.

      2. In the navigation pane on the left, click Data Synchronization.

      3. In the upper-left corner of the page, select the region where the synchronization instance is located.

      DMS console

      Note

      The actual steps may vary depending on the mode and layout of the DMS console. For more information, see Simple mode console and Customize DMS console layout and style.

      1. Log on to the DMS console.

      2. In the top menu bar, choose Data + AI > DTS (DTS) > Data Synchronization.

      3. To the right of Data Synchronization Tasks, select the region of the synchronization instance.

    2. Click Create Task to open the task configuration page.

    3. Configure the source and destination databases.

      Section

      Parameter

      Description

      N/A

      Task Name

      DTS automatically generates a task name. We recommend that you specify a descriptive name for easy identification. The name does not need to be unique.

      Source Database

      Select Existing Connection

      • Select the registered database instance with DTS from the drop-down list. The database information below is automatically configured.

        Note

        In the DMS console, this configuration item is Select a DMS database instance.

      • If you have not registered the database instance or do not need to use a registered instance, manually configure the database information below.

      Database Type

      Select Tair/Redis.

      Access Method

      Select Self-managed Database on ECS.

      Instance Region

      Select the region of the ECS instance where the source Redis database is located.

      Replicate Data Across Alibaba Cloud Accounts

      In this example, data is synchronized within the same Alibaba Cloud account. Select No.

      ECS Instance ID

      Select the ID of the ECS instance where the source Redis database is located.

      Note

      If the source Redis database uses a cluster architecture, select the ID of the ECS instance where the master node of any shard is located. You must also manually add the CIDR blocks of DTS servers in the corresponding region to the security rules of all other ECS instances. For more information, see Create a security group, Associate an instance with a security group, and Add the CIDR blocks of DTS servers to a whitelist.

      Instance Mode

      Select Standalone or Cluster based on the architecture of your source Redis database.

      Port Number

      Enter the service port of the source Redis database. The default value is 6379.

      Note

      If the source Redis database uses a cluster architecture, enter the service port of the master node of any shard.

      Authentication Method

      Select an authentication method based on your requirements. In this example, Password Login is selected.

      Note

      • Only Redis 6.0 and later support Account + Password Login.

      • If you select Secret-free login, make sure that password-free access is enabled for the Redis database. For information about how to enable password-free access for a Tair (Redis OSS-Compatible) instance, see Enable password-free access over a VPC.

      Database Password

      Enter the password used to connect to the source Redis database.

      Note

      • This parameter is optional. If no password is set, leave this field empty.

      • Enter the password in the <user>:<password> format. For example, if the custom username for your Redis instance is admin and the password is Rp829dlwa, enter admin:Rp829dlwa.

      Encryption

      Select Non-encrypted or SSL-encrypted based on your database instance requirements.

      Note

      If you are using a self-managed Redis instance (the Access Method is not Alibaba Cloud Instance) and you select SSL-encrypted, you must also upload a CA Certificate and enter the CA Certificate Password.

      Destination Database

      Select Existing Connection

      • Select the registered database instance with DTS from the drop-down list. The database information below is automatically configured.

        Note

        In the DMS console, this configuration item is Select a DMS database instance.

      • If you have not registered the database instance or do not need to use a registered instance, manually configure the database information below.

      Database Type

      Select Tair/Redis.

      Access Method

      Select Alibaba Cloud Instance.

      Instance Region

      Select the region of the destination Tair instance.

      Replicate Data Across Alibaba Cloud Accounts

      In this example, data is synchronized within the same Alibaba Cloud account. Select No.

      Instance ID

      Select the ID of the destination Tair instance.

      Authentication Method

      Select an authentication method based on your requirements. In this example, Password Login is selected.

      Note

      • Only Redis 6.0 and later support Account + Password Login.

      • If you select Secret-free login, make sure that password-free access is enabled for the Redis database. For information about how to enable password-free access for a Tair (Redis OSS-Compatible) instance, see Enable password-free access over a VPC.

      Database Password

      Enter the password used to connect to the destination Tair instance.

      Note

      Enter the password in the <user>:<password> format. For example, if the custom username for your Tair instance is admin and the password is Rp829dlwa, enter admin:Rp829dlwa.

      Encryption

      Select Non-encrypted or SSL-encrypted based on your database instance requirements.

      Note

      If you are using a self-managed Redis instance (the Access Method is not Alibaba Cloud Instance) and you select SSL-encrypted, you must also upload a CA Certificate and enter the CA Certificate Password.

    4. After you complete the configuration, click Test Connectivity and Proceed at the bottom of the page.

      Note

      • Ensure that the IP address segment of the DTS service is automatically or manually added to the security settings of the source and destination databases to allow access from DTS servers. For more information, see Add DTS server IP addresses to a whitelist.

      • If the source or destination database is a self-managed database (the Access Method is not Alibaba Cloud Instance), you must also click Test Connectivity in the CIDR Blocks of DTS Servers dialog box that appears.

    5. Configure the task objects.

      1. On the Configure Objects page, specify the objects to synchronize.

        Parameter

        Description

        Synchronization Types

        Full Data Synchronization + Incremental Data Synchronization is selected by default.

        Processing Mode of Conflicting Tables

        • Precheck and Report Errors: Checks if the destination is empty. If the destination is empty, the precheck is successful. If the destination is not empty, an error is reported during the precheck, and the data synchronization job does not start.

        • Ignore Errors and Proceed: Skips the Check the existence of objects in the destination database. precheck.

          Warning

          If you select Ignore Errors and Proceed, source data overwrites destination data if the same key exists in both the source and destination. This may cause data loss in the destination. Select this option with caution.

        Source Objects

        In the Source Objects box, click the objects, and then click 向右 to move them to the Selected Objects box.

        Note

        You can select objects only at the database level. To synchronize data for specific keys within a database, use the data filtering feature in the Selected Objects pane.

        Selected Objects

        To specify a destination database (DB 0 to DB 255) or filter data by prefix, use the mapping or filtering features. In the Selected Objects pane, right-click the database to synchronize, and then configure the settings in the Edit Schema dialog box that appears. For more information, see Map object names and Specify filter conditions.

      2. Click Next: Advanced Settings.

        Parameter

        Description

        Dedicated Cluster for Task Scheduling

        By default, DTS uses a shared cluster for tasks, so you do not need to make a selection. For greater task stability, you can purchase a dedicated cluster to run the DTS synchronization task. For more information, see What is a DTS dedicated cluster?.

        Retry Time for Failed Connections

        If the connection to the source or destination database fails after the synchronization task starts, DTS reports an error and immediately begins to retry the connection. The default retry duration is 720 minutes. You can customize the retry time to a value from 10 to 1,440 minutes. We recommend a duration of 30 minutes or more. If the connection is restored within this period, the task resumes automatically. Otherwise, the task fails.

        Note

        • If multiple DTS instances (e.g., Instance A and B) share a source or destination, DTS uses the shortest configured retry duration (e.g., 30 minutes for A, 60 for B, so 30 minutes is used) for all instances.

        • DTS charges for task runtime during connection retries. Set a custom duration based on your business needs, or release the DTS instance promptly after you release the source/destination instances.

        Retry Time for Other Issues

        If a non-connection issue (e.g., a DDL or DML execution error) occurs, DTS reports an error and immediately retries the operation. The default retry duration is 10 minutes. You can also customize the retry time to a value from 1 to 1,440 minutes. We recommend a duration of 10 minutes or more. If the related operations succeed within the set retry time, the synchronization task automatically resumes. Otherwise, the task fails.

        Important

        The value of Retry Time for Other Issues must be less than that of Retry Time for Failed Connections.

        Enable Throttling for Full Data Synchronization

        During full data synchronization, DTS consumes read and write resources from the source and destination databases, which can increase their load. To mitigate pressure on the destination database, you can limit the migration rate by setting Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s).

        Note

        This parameter is available only when Synchronization Types includes Full Data Synchronization.

        Enable Throttling for Incremental Data Synchronization

        You can also limit the incremental synchronization rate to reduce pressure on the destination database by setting RPS of Incremental Data Synchronization and Data synchronization speed for incremental synchronization (MB/s).

        Environment Tag

        You can select an environment tag to identify the instance. No tag is required for this example.

        Extend Expiration Time of Destination Database Key

        Sets an additional expiration time for keys synchronized from the source database to the destination database. To ensure data consistency, we recommend setting an extended expiration time if you use commands such as the following:

        Note

        In scenarios involving distributed locks, this may prevent the locks from being released in a timely manner.

        EXPIRE key seconds
PEXPIRE key milliseconds
EXPIREAT key timestamp
PEXPIREAT key timestampMs

        Use Slave Node

        If the Instance Mode of the source self-managed Redis instance is Cluster, you can choose to read data from the master or slave nodes. The default value is No, which means data is read from the master node.

        Configure ETL

        Choose whether to enable the extract, transform, and load (ETL) feature. For more information, see What is ETL? Valid values:

      3. Click Data Verification to configure a data verification task.

        To use the data verification feature, see Configure data verification.

    6. Save the task and perform a precheck.

      • To view the parameters for configuring this instance via an API operation, hover over the Next: Save Task Settings and Precheck button and click Preview OpenAPI parameters in the tooltip.

      • If you have finished viewing the API parameters, click Next: Save Task Settings and Precheck at the bottom of the page.

      Note

      • Before a synchronization task starts, DTS performs a precheck. You can start the task only if the precheck passes.

      • If the precheck fails, click View Details next to the failed item, fix the issue as prompted, and then rerun the precheck.

      • If the precheck generates warnings:

        • For non-ignorable warning, click View Details next to the item, fix the issue as prompted, and run the precheck again.

        • For ignorable warnings, you can bypass them by clicking Confirm Alert Details, then Ignore, and then OK. Finally, click Precheck Again to skip the warning and run the precheck again. Ignoring precheck warnings may lead to data inconsistencies and other business risks. Proceed with caution.

    7. Purchase the instance.

      1. When the Success Rate reaches 100%, click Next: Purchase Instance.

      2. On the Purchase page, select the billing method and link specifications for the data synchronization instance. For more information, see the following table.

        Category

        Parameter

        Description

        New Instance Class

        Billing Method

        • Subscription: You pay upfront for a specific duration. This is cost-effective for long-term, continuous tasks.

        • Pay-as-you-go: You are billed hourly for actual usage. This is ideal for short-term or test tasks, as you can release the instance at any time to save costs.

        Resource Group Settings

        The resource group to which the instance belongs. The default is default resource group. For more information, see What is resource management?.

        Instance Class

        DTS offers synchronization specifications at different performance levels that affect the synchronization rate. Select a specification based on your business requirements. For more information, see Data synchronization link specifications.

        Subscription Duration

        In subscription mode, select the duration and quantity of the instance. Monthly options range from 1 to 9 months. Yearly options include 1, 2, 3, or 5 years.

        Note

        This option appears only when the billing method is Subscription.

      3. Read and select the checkbox for Data Transmission Service (Pay-as-you-go) Service Terms.

      4. Click Buy and Start, and then click OK in the OK dialog box.

        You can view the progress of the task on the Data Synchronization page.

        Note

        If your DTS instance is configured for both full and incremental data synchronization (meaning Synchronization Types includes both Full Data Synchronization and Incremental Data Synchronization), the task appears as Incremental Data Synchronization in the synchronization task list.