tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
TencentDB for Redis
    Documentation
    Download PDF

    Migration Scheme Overview

    Last updated: 2023-03-14 15:39:05
    Download PDF
      With the help of DTS as well as redis-sync, redis-dump, and redis-restore tools in the redis-port migration toolkit, TencentDB for Redis offers a variety of data migration schemes for diverse business scenarios.

      Migration tools

      DTS: It helps migrate your database to the cloud without interrupting your business. In its full + incremental data migration mode, historical data in the source database written before migration and incremental data written during migration can be migrated together.
      redis-sync: It supports data migration between Redis instances. It is simulated as a replication node to sync data from the source instance and translate the replicated data into write commands to update the target instance.
      redis-dump and redis-restore: redis-dump can be used to back up Redis data into RDB files in an offline environment, and then redis-restore can be used to import the RDB files into the specified Redis instance.

      Migration schemes

      
      Migration Scenario
      Category
      Migration Tools
      Access Type
      Migration Description
      Migration from self-built Redis to TencentDB for Redis
      Migration from IDC-based self-built Redis to TencentDB for Redis
      DTS (recommended)
      The following three access types are supported:
      Direct Connect: The source database can be interconnected with VPCs through Direct Connect. For detailed directions, see Getting Started.
      VPN Access: The source database can be interconnected with VPCs through VPN Connections. For detailed directions, see VPN Connections.
      Intranet (only suitable for Tencent's internal businesses): You need to submit a ticket to add your account to the allowlist.
      The migration is online, with full + incremental data sync supported.
      Supported source Redis versions are 2.8, 3.0, 4.0, 5.0, and 6.2, and supported target Redis versions are 2.8, 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      Supported architectures include single-node, Redis cluster, Twemproxy, and Sentinel.
      The following two access types are supported:
      Public Network: The source database can be accessed through a public IP.
      Intranet: You need to submit a ticket for application.
      The migration is online, with full + incremental data sync supported.
      The source Redis database must allow the SYNC or PSYNC command.
      Supported source Redis versions are 2.8, 3.0, and 4.0, and supported target Redis versions are 2.8, 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      Offline (the source and target databases don't interconnect over the network).
      The migration is offline, with only full data sync supported. Business downtime will be caused.
      Supported source Redis versions are 2.8, 3.0, and 4.0, and supported target Redis versions are 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      Migration from CVM-based self-built Redis to TencentDB for Redis
      DTS (recommended)
      Self-Build on CVM: The source database is deployed in a CVM instance.
      The migration is online, with full + incremental data sync supported.
      Supported source Redis versions are 2.8, 3.0, 4.0, 5.0, and 6.2, and supported target Redis versions are 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      Supported architectures include single-node, Redis cluster, Twemproxy, and Sentinel.
      VPC: The source database can be accessed through VPC.
      The migration is online, with full + incremental data sync supported.
      The source node must allow the SYNC or PSYNC command. Supported source Redis versions are 2.8, 3.0, and 4.0, and supported target Redis versions are 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      Offline (the source and target databases don't interconnect over the network).
      The migration is offline, with only full data sync supported. Business downtime will be caused.
      Supported source Redis versions are 2.8, 3.0, and 4.0, and supported target Redis versions are 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      Migration from TencentDB for Redis to self-built Redis
      Migration from TencentDB for Redis to self-built Redis (migration off the cloud and multi-cloud sync)
      DTS (recommended)
      The following five access types are supported:
      Public Network: The source database can be accessed through a public IP.
      Self-Build on CVM: The source database is deployed in a CVM instance.
      Direct Connect: The source database can be interconnected with VPCs through Direct Connect.
      VPN Access: The source database can be interconnected with VPCs through VPN Connections.
      CCN: The source database can be interconnected with VPCs through CCN.
      The migration is online, with full + incremental data sync supported.
      You need to submit a ticket for application.
      Supported target instance types include single-node, Redis cluster, and proxy cluster (which can be deployed by using the proxy provided by Tencent Cloud).
      Migration between TencentDB for Redis instances
      Migration between TencentDB for Redis instances in different regions
      DTS (recommended)
      CCN: The source database can be interconnected with VPCs through CCN.
      The migration is online, with full + incremental data sync supported.
      Supported Redis versions are 2.8, 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      Migration between TencentDB for Redis instances in the same region
      DTS (recommended)
      Database: The source database is a TencentDB instance.
      The migration is online, with full + incremental data sync supported.
      Supported Redis versions are 2.8, 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      This scheme is suitable for large-shard cluster architecture upgrade as it can shorten the downtime.
      Migration between TencentDB for Redis instances on different versions
      DTS (recommended)
      Database: The source database is a TencentDB instance.
      VPC: The source database can be accessed through VPC.
      The migration is online, with full + incremental data sync supported.
      Supported Redis versions are 2.8, 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version. For detailed directions, see Version Upgrade with DTS.
      Migration across Tencent Cloud accounts
      DTS (recommended)
      Database: The source database is a TencentDB instance.
      The migration is online, with full + incremental data sync supported.
      Supported Redis versions are 2.8, 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      You need to submit a ticket for application.
      Migration from Tencent Cloud standard architecture to cluster architecture
      DTS (recommended)
      Database: The source database is a TencentDB instance.
      The migration is online, with full + incremental data sync supported.
      Supported Redis versions are 2.8, 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version. Check the command compatibility as instructed in Check on Migration from Standard Architecture to Cluster Architecture in advance to avoid service execution errors after the upgrade.
      Migration from legacy TencentDB for Redis Cluster Edition instance (purchased before January 1, 2018)
      Offline (VPC)
      Only full data sync is supported. Business downtime will be caused. For detailed directions, see Migration Guide for Legacy Cluster Edition.
      Migration from another cloud to TencentDB for Redis
      Migration from Redis in another cloud to TencentDB for Redis
      DTS (recommended)
      The following three access types are supported:
      Public Network: The source database can be accessed through a public IP.
      Direct Connect: The source database can be interconnected with VPCs through Direct Connect.
      VPN Access: The source database can be interconnected with VPCs through VPN Connections.
      The migration is online, with full + incremental data sync supported.
      The third-party cloud vendor must allow the SYNC or PSYNC command.
      Supported source Redis versions are 2.8, 3.0, 4.0, 5.0, and 6.2, and supported target Redis versions are 2.8, 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      Offline (the source and target databases don't interconnect over the network).
      The migration is offline, with only full data sync supported. Business downtime will be caused.
      Supported source Redis versions are 2.8, 3.0, and 4.0, and supported target Redis versions are 4.0, 5.0, and 6.2. The target version must be later than or equal to the source version.
      Migration from another type of database to TencentDB for Redis
      Migration from SSDB to TencentDB for Redis
      The following four access types are supported:
      Direct Connect: The source database can be interconnected with VPCs through Direct Connect.
      VPN Access: The source database can be interconnected with VPCs through VPN Connections.
      VPC: The source database can be accessed through VPC.
      Intranet: You need to submit a ticket for application.
      The migration is online, with full + incremental data sync supported.
      All SSDB kernel versions are supported.
      Migration from Pika to TencentDB for Redis
      The following four access types are supported:
      Direct Connect: The source database can be interconnected with VPCs through Direct Connect.
      VPN Access: The source database can be interconnected with VPCs through VPN Connections.
      VPC: The source database can be accessed through VPC.
      Intranet: You need to submit a ticket for application.
      The migration is online, with full + incremental data sync supported.
      Supported Pika versions are 2.2, 2.3, 3.0, 3.1, and 3.2.
      Only standalone single-database Pika instances are supported.
      Migration from Codis to TencentDB for Redis
      The following four access types are supported:
      Direct Connect: The source database can be interconnected with VPCs through Direct Connect.
      VPN Access: The source database can be interconnected with VPCs through VPN Connections.
      VPC: The source database can be accessed through VPC.
      Intranet: You need to submit a ticket for application.
      The migration is online, with full + incremental data sync supported.
      The source node must allow the SYNC or PSYNC command.
      All versions are supported. For migration of Tencent's internal businesses to the cloud, you need to submit a ticket for application.
      Migration from Tencent istore to TencentDB for Redis
      Intranet: You need to submit a ticket for application.
      The migration is online, with full + incremental data sync supported.
      The source node must allow the SYNC or PSYNC command.
      All istore versions are supported.
      Migration from Memcached to TencentDB for Redis
      -
      -
      Contact Tencent Cloud to customize a migration scheme.
      Migration from Tencent Cloud CKV to TencentDB for Redis
      Offline (the source and target databases don't interconnect over the network).
      Only full data sync is supported. Business downtime will be caused. For detailed directions, see Migration Guide for Legacy Cluster Edition.
      
      Contact Us

      Contact our sales team or business advisors to help your business.

      Contact Us
      Technical Support

      Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

      Submit a Ticket
      7x24 Phone Support
      Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
      Privacy PolicyLegalCookie Policy