Release Notes and Announcements

Release Notes

Announcements

User Tutorial

Product Introduction

Overview

Product Strengths

Use Cases

Storage Engine

Product Series

Product Versions

Specifications and Performance

Read/Write Separation

Multi-AZ Deployment

Regions and AZs

Terms

Service Regions and Service Providers

Purchase Guide

Billing Overview

Pricing Center

Instance Purchasing

Renewal (Yearly/Monthly Subscription)

Refund (Yearly/Monthly Subscription)

Overdue Payments

Switching from Pay-as-You-Go to Yearly/Monthly Subscription

Getting Started

Quickly Creating an Instance

Connecting to Redis Instance

Operation Guide

Operation Overview

Connecting to a Database Instance

Managing Instances

Upgrade Instance

Management Node (Redis/ValKey Edition)

Multi-AZ Deployment Management

Backup and Restoration

Managing Accounts

Parameter Configuration

Slow Query

Access Management

Network and Security

Monitoring and Alarms

Event Management (Redis/ValKey Edition)

Data Migration

Global Replication for Redis Edition

Database Audit

Performance Optimization

Sentinel Mode

Development Guidelines

Naming Rules

Basic Usage Guidelines

Design Principles of Key and Value

Command Usage Guidelines

Design Principles of Client Programs

Connection Pool Configuration

Command Reference

Command Reference Overview

Redis Edition and Valkey Edition Command Compatibility

Version Command Usage Differences

Differences Between the Proxy Architecture and Direct Connection Mode

More Command Operations (Redis/Valkey Edition)

Memcached Edition Command Compatibility

Practical Tutorial

Building TencentDB for Redis® Client Monitoring Based on Spring Boot

Redis Client Connection Configuration Policy and Practice

Global SCAN Guide for Cluster Architecture

Eliminating Instances Securely

Hot Key and Big Key

AZ Migration Scheme

Troubleshooting

Connection Exception

Exception Analysis and Solution of Redisson Client Timeout Reconnection

Performance Troubleshooting and Fine-Tuning

API Documentation

History

Introduction

API Category

Making API Requests

Instance APIs

Parameter Management APIs

Other APIs

Backup and Restoration APIs

Region APIs

Monitoring and Management APIs

Log APIs

Data Types

Error Codes

FAQs

General

Connection and Login

Purchase

Service Agreement

Service Level Agreement

Glossary

Migration Scheme Overview

PDF

포커스 모드

폰트 크기

마지막 업데이트 시간: 2026-03-18 17:16:05

With the help of DTS as well as redis-sync, redis-dump, and redis-restore tools in the redis-port migration toolkit, Tencent Cloud Distributed Cache 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 Tencent Cloud Distributed Cache 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 Tencent Cloud Distributed Cache data into RDB files in an offline environment, and then redis-restore can be used to import the RDB files into the specified Tencent Cloud Distributed Cache instance.
Migration schemes
Migration Scenario
Category
Migration Tools
Access Type
Migration Description
Migration from self-built Redis to Tencent Cloud Distributed Cache﻿
Migration from IDC-based self-built Redis to Tencent Cloud Distributed Cache﻿
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: 2.8, 3.0, 4.0, 5.0, 6.2, 7.0, Valkey 8.0.
Supported architectures include single-node, Redis cluster, Twemproxy, and Sentinel.
Supported architectures include single-node, redis cluster, twemproxy, sentinel, and so on.
﻿
﻿
redis-sync
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 4.0, 5.0, 6.2 and 7.0. The target version must be later than or equal to the source version.
Target Redis versions: 2.8, 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
﻿
﻿
redis-dump and redis-restore
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, 6.2 and 7.0. The target version must be later than or equal to the source version.
Target Redis versions: 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
﻿
Migration from CVM-based self-built Redis to Tencent Cloud Distributed Cache﻿
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 include 2.8, 3.0, 4.0, 5.0, 6.2, 7.0, and Valkey 8.0.
Target Redis versions: 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
Supported architectures include single-node, redis cluster, twemproxy, sentinel, and so on.
﻿
﻿
redis-sync
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.
NC command. Only Redis versions 2.8, 3.0, and 4.0 are supported for the source.
Target Redis versions: 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
﻿
﻿
redis-dump and redis-restore
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, 6.2 and 7.0. The target version must be later than or equal to the source version.
Target Redis versions: 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
Migration from Tencent Cloud Distributed Cache to self-built Redis
Migration from Tencent Cloud Distributed Cacheto 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 Redis instances
Migration between Tencent Cloud Distributed Cacheinstances 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, 6.2 and 7.0. The target version must be later than or equal to the source version.
﻿
Migration between Tencent Cloud Distributed Cacheinstances 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, 6.2 and 7.0. 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 Tencent Cloud Distributed Cache 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, 6.2 and 7.0. 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, 6.2 and 7.0. The target version must be later than or equal to the source version.
You need to submit a ticket for application.
﻿
Tencent Cloud Distributed CacheMigration from 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, 6.2 and 7.0. 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 Tencent Cloud Distributed CacheCluster Edition instance (purchased before January 1, 2018)
redis-restore
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 Tencent Cloud Distributed Cache﻿
Migration from Redis in another cloud to Tencent Cloud Distributed Cache﻿
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 include 2.8, 3.0, 4.0, 5.0, 6.2, 7.0, and Valkey 8.0.
Target Redis versions: 2.8, 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
﻿
﻿
redis-dump and redis-restore
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, 6.2 and 7.0. The target version must be later than or equal to the source version.
Target Redis versions: 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
Migration from another type of database to Tencent Cloud Distributed Cache﻿
Migration from SSDB to Tencent Cloud Distributed Cache﻿
Siphon
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 Tencent Cloud Distributed Cache﻿
pika-migrate
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 Tencent Cloud Distributed Cache﻿
DTS
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 Tencent Cloud Distributed Cache﻿
DTS
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 Tencent Cloud Distributed Cache﻿
-
-
Contact Tencent Cloud to customize a migration scheme.
﻿
Migration from Tencent Cloud CKV to Tencent Cloud Distributed Cache﻿
redis-restore
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.

도움말 및 지원

문제 해결에 도움이 되었나요?

더 자세한 내용은 문의하기 또는 티겟 제출 을 통해 문의할 수 있습니다.

피드백

tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Migration Scheme Overview

Migration Tools

Migration schemes

도움말 및 지원

Migration Scenario	Category	Migration Tools	Access Type	Migration Description
Migration from self-built Redis to Tencent Cloud Distributed Cache	Migration from IDC-based self-built Redis to Tencent Cloud Distributed Cache	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: 2.8, 3.0, 4.0, 5.0, 6.2, 7.0, Valkey 8.0. Supported architectures include single-node, Redis cluster, Twemproxy, and Sentinel. Supported architectures include single-node, redis cluster, twemproxy, sentinel, and so on.
				redis-sync	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 4.0, 5.0, 6.2 and 7.0. The target version must be later than or equal to the source version. Target Redis versions: 2.8, 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
				redis-dump and redis-restore	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, 6.2 and 7.0. The target version must be later than or equal to the source version. Target Redis versions: 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
		Migration from CVM-based self-built Redis to Tencent Cloud Distributed Cache	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 include 2.8, 3.0, 4.0, 5.0, 6.2, 7.0, and Valkey 8.0. Target Redis versions: 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version. Supported architectures include single-node, redis cluster, twemproxy, sentinel, and so on.
				redis-sync	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. NC command. Only Redis versions 2.8, 3.0, and 4.0 are supported for the source. Target Redis versions: 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
				redis-dump and redis-restore	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, 6.2 and 7.0. The target version must be later than or equal to the source version. Target Redis versions: 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
Migration from Tencent Cloud Distributed Cache to self-built Redis	Migration from Tencent Cloud Distributed Cacheto 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 Redis instances	Migration between Tencent Cloud Distributed Cacheinstances 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, 6.2 and 7.0. The target version must be later than or equal to the source version.
		Migration between Tencent Cloud Distributed Cacheinstances 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, 6.2 and 7.0. 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 Tencent Cloud Distributed Cache 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, 6.2 and 7.0. 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, 6.2 and 7.0. The target version must be later than or equal to the source version. You need to submit a ticket for application.
		Tencent Cloud Distributed CacheMigration from 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, 6.2 and 7.0. 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 Tencent Cloud Distributed CacheCluster Edition instance (purchased before January 1, 2018)	redis-restore	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 Tencent Cloud Distributed Cache	Migration from Redis in another cloud to Tencent Cloud Distributed Cache	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 include 2.8, 3.0, 4.0, 5.0, 6.2, 7.0, and Valkey 8.0. Target Redis versions: 2.8, 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
				redis-dump and redis-restore	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, 6.2 and 7.0. The target version must be later than or equal to the source version. Target Redis versions: 4.0, 5.0, 6.2, 7.0, Valkey 8.0. The target version must be later than or equal to the source version.
Migration from another type of database to Tencent Cloud Distributed Cache	Migration from SSDB to Tencent Cloud Distributed Cache	Siphon	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 Tencent Cloud Distributed Cache	pika-migrate	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 Tencent Cloud Distributed Cache	DTS	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 Tencent Cloud Distributed Cache	DTS	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 Tencent Cloud Distributed Cache	-	-	Contact Tencent Cloud to customize a migration scheme.
		Migration from Tencent Cloud CKV to Tencent Cloud Distributed Cache	redis-restore	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.