- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on Release of New Upgrade Mechanism for Kernel Minor Version
- Announcement on Optimization of Instance Storage Capacity, IOPS, and I/O Bandwidth
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Sales Suspension of Some General Specifications
- Announcement on Some APIs Integrated with CAM Authentication
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Change of Part of Parameters
- Announcement on Update of Database Audit Feature
- Announcement on Authentication of a Newly Added API Interface of Database Audit
- Announcement on Change of Public Network Linkage
- TDSQL-C for MySQL Audit Service Update
- Announcement on Supplementary Charge for Clusters with Pay-as-You-Go Storage Billing Mode
- Announcement on New APIs Integrated with CAM Permissions
- Announcement on the Release of New Version of Database Proxy
- Emergency Fix for Certain Monitoring Metrics
- Monitoring Metric Optimization
- Change to Database Audit Resource ID
- Ops Change
- Storage Price Adjustment Notification
- Beginner's Guide
- Product Introduction
- Kernel Features
- Kernel Overview
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Columns Syntax
- Correlated Subquery Result Cache
- Global Index
- Binlog Write Optimization
- Large Transaction Binlog Optimization
- Binlog Purging Performance Optimization
- Optimization of Plan Caching Point Query
- Auto-Increment Column Persistence
- Invisible Index
- Computation Pushdown
- Parallel Initialization of InnoDB Buffer Pool
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Getting Started
- Database Audit
- Serverless Service
- Operation Guide
- Switching Cluster Page View in Console
- Database Connection
- Instance Management
- Configuration Adjustment
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Overview
- Use Limits
- Database Proxy Kernel Features
- Managing Database Proxy
- Enabling Database Proxy
- Setting Database Proxy Address
- Modifying or Deleting Connection Addresses
- Viewing and Changing the Access Policy
- Rebalancing the Load
- Transaction Split Feature
- Access Mode
- Adjusting Database Proxy Configuration
- Switching Database Proxy Network
- Viewing Database Proxy Monitoring Data
- Disabling Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Read-Only Analysis Engine
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Operation Log
- Data Migration
- Parallel Query
- Database Security and Encryption
- Monitoring and Alarms
- Basic SQL Operations
- Connecting to TDSQL-C for MySQL Through SCF
- Tag
- Practical Tutorial
- Classified Protection Practice for Database Audit of TDSQL-C for MySQL
- Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
- Usage Instructions for TDSQL-C MySQL
- New Version of Console
- Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
- Strengths of Database Proxy
- Selecting Billing Mode for Storage Space
- Creating Remote Disaster Recovery by DTS
- Creating VPC for Cluster
- Data Rollback
- Solution to High CPU Utilization
- How to Authorize Sub-Users to View Monitoring Data
- White Paper
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Billing APIs
- Instance APIs
- CloseClusterPasswordComplexity
- CopyClusterPasswordComplexity
- DescribeClusterDetail
- DescribeClusterPasswordComplexity
- ModifyClusterPasswordComplexity
- OpenClusterPasswordComplexity
- UpgradeClusterVersion
- UpgradeInstance
- SetRenewFlag
- OfflineCluster
- ModifyMaintainPeriodConfig
- IsolateInstance
- IsolateCluster
- DescribeMaintainPeriod
- DescribeInstanceSpecs
- DescribeClusters
- CreateClusters
- AddInstances
- OfflineInstance
- DescribeInstanceDetail
- DescribeClusterInstanceGrps
- DescribeInstances
- ActivateInstance
- ModifyInstanceName
- ModifyClusterName
- SearchClusterTables
- SearchClusterDatabases
- RestartInstance
- Multi-AZ APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- CloseWan
- CreateClusterDatabase
- DeleteClusterDatabase
- DescribeClusterDetailDatabases
- ModifyClusterDatabase
- OpenWan
- SwitchClusterVpc
- OpenReadOnlyInstanceExclusiveAccess
- OpenClusterReadOnlyInstanceGroupAccess
- ModifyDBInstanceSecurityGroups
- DescribeProjectSecurityGroups
- DescribeDBSecurityGroups
- SwitchProxyVpc
- DescribeFlow
- DescribeZones
- ModifyVipVport
- Data Types
- Error Codes
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
- Glossary
- Contact Us
- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on Release of New Upgrade Mechanism for Kernel Minor Version
- Announcement on Optimization of Instance Storage Capacity, IOPS, and I/O Bandwidth
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Sales Suspension of Some General Specifications
- Announcement on Some APIs Integrated with CAM Authentication
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Change of Part of Parameters
- Announcement on Update of Database Audit Feature
- Announcement on Authentication of a Newly Added API Interface of Database Audit
- Announcement on Change of Public Network Linkage
- TDSQL-C for MySQL Audit Service Update
- Announcement on Supplementary Charge for Clusters with Pay-as-You-Go Storage Billing Mode
- Announcement on New APIs Integrated with CAM Permissions
- Announcement on the Release of New Version of Database Proxy
- Emergency Fix for Certain Monitoring Metrics
- Monitoring Metric Optimization
- Change to Database Audit Resource ID
- Ops Change
- Storage Price Adjustment Notification
- Beginner's Guide
- Product Introduction
- Kernel Features
- Kernel Overview
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Columns Syntax
- Correlated Subquery Result Cache
- Global Index
- Binlog Write Optimization
- Large Transaction Binlog Optimization
- Binlog Purging Performance Optimization
- Optimization of Plan Caching Point Query
- Auto-Increment Column Persistence
- Invisible Index
- Computation Pushdown
- Parallel Initialization of InnoDB Buffer Pool
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Getting Started
- Database Audit
- Serverless Service
- Operation Guide
- Switching Cluster Page View in Console
- Database Connection
- Instance Management
- Configuration Adjustment
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Overview
- Use Limits
- Database Proxy Kernel Features
- Managing Database Proxy
- Enabling Database Proxy
- Setting Database Proxy Address
- Modifying or Deleting Connection Addresses
- Viewing and Changing the Access Policy
- Rebalancing the Load
- Transaction Split Feature
- Access Mode
- Adjusting Database Proxy Configuration
- Switching Database Proxy Network
- Viewing Database Proxy Monitoring Data
- Disabling Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Read-Only Analysis Engine
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Operation Log
- Data Migration
- Parallel Query
- Database Security and Encryption
- Monitoring and Alarms
- Basic SQL Operations
- Connecting to TDSQL-C for MySQL Through SCF
- Tag
- Practical Tutorial
- Classified Protection Practice for Database Audit of TDSQL-C for MySQL
- Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
- Usage Instructions for TDSQL-C MySQL
- New Version of Console
- Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
- Strengths of Database Proxy
- Selecting Billing Mode for Storage Space
- Creating Remote Disaster Recovery by DTS
- Creating VPC for Cluster
- Data Rollback
- Solution to High CPU Utilization
- How to Authorize Sub-Users to View Monitoring Data
- White Paper
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Billing APIs
- Instance APIs
- CloseClusterPasswordComplexity
- CopyClusterPasswordComplexity
- DescribeClusterDetail
- DescribeClusterPasswordComplexity
- ModifyClusterPasswordComplexity
- OpenClusterPasswordComplexity
- UpgradeClusterVersion
- UpgradeInstance
- SetRenewFlag
- OfflineCluster
- ModifyMaintainPeriodConfig
- IsolateInstance
- IsolateCluster
- DescribeMaintainPeriod
- DescribeInstanceSpecs
- DescribeClusters
- CreateClusters
- AddInstances
- OfflineInstance
- DescribeInstanceDetail
- DescribeClusterInstanceGrps
- DescribeInstances
- ActivateInstance
- ModifyInstanceName
- ModifyClusterName
- SearchClusterTables
- SearchClusterDatabases
- RestartInstance
- Multi-AZ APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- CloseWan
- CreateClusterDatabase
- DeleteClusterDatabase
- DescribeClusterDetailDatabases
- ModifyClusterDatabase
- OpenWan
- SwitchClusterVpc
- OpenReadOnlyInstanceExclusiveAccess
- OpenClusterReadOnlyInstanceGroupAccess
- ModifyDBInstanceSecurityGroups
- DescribeProjectSecurityGroups
- DescribeDBSecurityGroups
- SwitchProxyVpc
- DescribeFlow
- DescribeZones
- ModifyVipVport
- Data Types
- Error Codes
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
- Glossary
- Contact Us
Overview
Last updated: 2023-05-31 15:01:45
This document describes how to perform the quick migration from TencentDB for MySQL to TDSQL-C for MySQL in the console.
Background
TDSQL-C for MySQL is fully compatible with TencentDB for MySQL. It can deliver a high throughput of over one million QPS and a smart storage capacity up to the petabyte level, fully ensuring data security and reliability. TDSQL-C for MySQL also delivers better cost-effectiveness and performance in the same specifications.
Quick migration allows you to migrate full or incremental data in the console. which is suitable for migration from TencentDB for MySQL to TDSQL-C for MySQL. This feature can achieve smooth migration without downtime and retain original configurations such as original IP address, monitoring ,and parameters.
Source Database: TencentDB for MySQL
Target Database: TDSQL-C for MySQL
Use Limits
Quick migration is only supported from TencentDB for MySQL 5.7 or 8.0 in the single-node, two-node or three-node architecture to TDSQL-C for MySQL.
Note:
Quick migration is supported for all kernel minor versions. The cluster will automatically be upgraded to the latest kernel minor version when the migration succeeded.
Currently, the quick migration is only supported for the source TencentDB for MySQL instance, and the migration of read-only instance and disaster recovery instance are in beta testing.
Strengths
All features are free of charge, and DTS is not required.
No data loss in migration.
Incremental migration is supported.
Online migration is supported. When the connection address is switching from TencentDB for MySQL to TDSQL-C for MySQL, one momentary disconnection will occur.
You can switch to TDSQL-C for MySQL without modifying any connection configuration in your application as the original connection address of the TencentDB for MySQL database will be retained after the migration.
Migration Specification Mapping Table
The mapping between the specifications of TencentDB for MySQL instance and the TDSQL-C for MySQL instance after migration is as follows:
Note:
Specification differences are marked in blue in the table.
TencentDB for MySQL Single-Node Instance Specification | TencentDB for MySQL Two-Node Instance Specification | TencentDB for MySQL Three-Node Instance Specification | TDSQL-C for MySQL Instance Specification |
1-core 1000 MB MEM | 1-core 1000 MB MEM | 1-core 1000 MB MEM | 1-core 1 GB MEM |
1-core 2000 MB MEM | 1-core 2000 MB MEM | 1-core 2000 MB MEM | 1-core 2 GB MEM |
2-core 4000 MB MEM | 2-core 4000 MB MEM | 2-core 4000 MB MEM | 2-core 4 GB MEM |
2-core 8000 MB MEM | 2-core 16000 MB MEM | 2-core 16000 MB MEM | 2-core 16 GB MEM |
4-core 8000 MB MEM | 4-core 8000 MB MEM | 4-core 8000 MB MEM | 4-core 8 GB MEM |
4-core 8000 MB MEM | 4-core 16000 MB MEM | 4-core 16000 MB MEM | 4-core 16 GB MEM |
| 4-core 24000 MB MEM | 4-core 24000 MB MEM | 4-core 24 GB MEM |
| 4-core 32000 MB MEM | 4-core 32000 MB MEM | 4-core 32 GB MEM |
| 8-core 16000 MB MEM | 8-core 16000 MB MEM | 8-core 16 GB MEM |
| 8-core 32000 MB MEM | 8-core 32000 MB MEM | 8-core 32 GB MEM |
| 8-core 48000 MB MEM | 8-core 48000 MB MEM | 8-core 48 GB MEM |
| 8-core 64000 MB MEM | 8-core 64000 MB MEM | 8-core 64 GB MEM |
| 12-core 48000 MB MEM | 12-core 48000 MB MEM | 12-core 48 GB MEM |
| 12-core 72000 MB MEM | 12-core 72000 MB MEM | 12-core 72 GB MEM |
| 12-core 96000 MB MEM | 12-core 96000 MB MEM | 12-core 96 GB MEM |
| 16-core 32000 MB MEM | 16-core 32000 MB MEM | 16-core 64 GB MEM |
| 16-core 64000 MB MEM | 16-core 64000 MB MEM | 16-core 64 GB MEM |
| 16-core 96000 MB MEM | 16-core 96000 MB MEM | 16-core 96 GB MEM |
| 16-core 128000 MB MEM | 16-core 128000 MB MEM | 16-core 128 GB MEM |
| 24-core 96000 MB MEM | 24-core 96000 MB MEM | 24-core 96 GB MEM |
| 24-core 128000 MB MEM | 24-core 128000 MB MEM | 24-core 144 GB MEM |
| 24-core 144000 MB MEM | 24-core 144000 MB MEM | 24-core 144 GB MEM |
| 24-core 192000 MB MEM | 24-core 192000 MB MEM | 24-core 192 GB MEM |
| 24-core 244000 MB MEM | 24-core 244000 MB MEM | 32-core 256 GB MEM |
| 24-core 256000 MB MEM | 24-core 256000 MB MEM | 32-core 256 GB MEM |
| 32-core 128000 MB MEM | 32-core 128000 MB MEM | 32-core 128 GB MEM |
| 32-core 192000 MB MEM | 32-core 192000 MB MEM | 32-core 192 GB MEM |
| 32-core 256000 MB MEM | 32-core 256000 MB MEM | 32-core 256 GB MEM |
| 48-core 192000 MB MEM | 48-core 192000 MB MEM | 48-core 192 GB MEM |
| 48-core 288000 MB MEM | 48-core 288000 MB MEM | 48-core 288 GB MEM |
| 48-core 384000 MB MEM | 48-core 384000 MB MEM | 48-core 384 GB MEM |
| 48-core 488000 MB MEM | 48-core 488000 MB MEM | 48-core 488 GB MEM |
| 64-core 256000 MB MEM | 64-core 256000 MB MEM | 64-core 256 GB MEM |
| 64-core 384000 MB MEM | 64-core 384000 MB MEM | 64-core 384 GB MEM |
| 64-core 512000 MB MEM | 64-core 512000 MB MEM | 88-core 710 GB MEM |
| 80-core 690000 MB MEM | 80-core 690000 MB MEM | 88-core 710 GB MEM |
| 90-core 720000 MB MEM | 90-core 720000 MB MEM | 88-core 710 GB MEM |
Backup Policy
As TDSQL-C for MySQL backup space is free of charge, you can use backup feature for free.
TDSQL-C for MySQL does not support automatic logical backup and physical backup, but after the migration it will support the snapshot backup that features imperceptibility during backup and data restoration within seconds.
Note:
Snapshot backup period rules: Backup file is generated every 6-48 hours on a 24/7 uninterrupted basis, which has no impacts on the instance performance.
TDSQL-C for MySQL allows you to set a retention period for the snapshot backup file, and you can roll back the instance data to any time point within this period.
Yes
No
Was this page helpful?