Service Level Agreement
Terms of Service
Execute One-Click Migration
포커스 모드
폰트 크기
This article describes how to migrate from TencentDB for MySQL to TDSQL-C for MySQL with one click via the console.
Note:
The current version of the one-click migration feature temporarily only supports migration within the same region and availability zone.
When the disk count in TencentDB for MySQL is odd, the one-click migration feature is not supported.
Prerequisites
The source TencentDB for MySQL version is MySQL 5.7 or 8.0, in a two-node or three-node edition.
The TencentDB for MySQL instance at the migration source has no disaster recovery instance.
If there are read-only instances under the source TencentDB for MySQL instance, the billing mode of the primary instance and read-only instances must be consistent. To adjust the billing mode of an instance, see Pay-as-you-go to Yearly/Monthly Subscription.
Operation Steps
Using one-click migration, a TDSQL-C for MySQL cluster with specifications corresponding to the migration specification mapping table will be created, and database migration will be performed. After the migration is completed, the connection address needs to be switched. The detailed operation process is as follows.
1. Start Migration
1. Log in to TencentDB for MySQL console.
2. Select one MySQL instance to be migrated in the instance list and click One-Click Upgrade at the top.
Note:
In the instance list, there is also a One-Click Upgrade button under the billing mode field.
Click Instance ID to go to the instance details page. There is also a One-Click Upgrade button in the upper right corner.
3. In the pop-up window, select Migrate to TDSQL-C for MySQL and click Upgrade Now.
4. After entering the migration page, preview the comparison information between the current MySQL instance and the new TDSQL-C for MySQL cluster after migration.
Field | Description |
Instance type | The instance type remains unchanged before and after migration for both read-write instances and read-only instances. |
Specification | Comparing the instance specifications configuration before and after migration. |
AZ | Compare the availability zone deployment status before and after migration. |
Configuration Fees | Compare the configuration fees before and after migration. |
Expiration Time | Compare the expiration time of the instance before and after migration. |
Note:
For the migration source being a TencentDB for MySQL instance with a yearly/monthly subscription billing mode, after migration, the expiration time of the TDSQL-C for MySQL cluster is calculated as follows: After processing the refund for the current TencentDB for MySQL instance, since the refund mechanism is based on usage rather than unused time, the refund amount is small. TDSQL-C for MySQL uses this difference to purchase the cluster. The expiration time is determined by dividing the difference by the price of the corresponding specifications.
When a refund is processed for the source TencentDB for MySQL, the refund mechanism is based on usage. If the refund difference calculated by the system is insufficient to purchase a new TDSQL-C for MySQL cluster, one-click migration cannot be used.
If the remaining balance of the source TencentDB for MySQL cannot support one-click migration, it is recommended that you manually purchase TDSQL-C for MySQL cluster, then import data.
5. On the migration page, click Migration Check, the system will check the information of the TencentDB for MySQL instances to be migrated and the TDSQL-C for MySQL instances after migration. You can perform corresponding operations based on the check results. If there are read-only groups under the source instance, you can choose whether to migrate the read-only groups.
Check items are as follows
Check Item | Description |
AZ | TDSQL-C for MySQL currently does not support certain availability zones. If the source TencentDB for MySQL instance is deployed in an unsupported availability zone, it cannot be migrated at this time. |
TDSQL-C specification inventory | The backend checks whether the inventory of new cluster specifications is sufficient. If so, migration can proceed. |
InnoDB engine | TDSQL-C for MySQL only supports migrating InnoDB engines. If the MySQL instance to be migrated uses the RocksDB engine, it cannot be migrated. |
non-InnoDB tables | TDSQL-C for MySQL only supports migrating InnoDB engines. If non-InnoDB tables exist in the MySQL instance to be migrated, it cannot be migrated. |
TencentDB for MySQL version | The source TencentDB for MySQL edition must be a dual-node or three-node edition of MySQL 5.7 or 8.0. Otherwise, it cannot be migrated. |
Public network enablement | If the MySQL instance to be migrated has public network enabled, then during migration, the public network of the source MySQL instance cannot be disabled. After migration, the public network status of the target TDSQL-C for MySQL cluster is not enabled. If you need to use the source MySQL instance after migration is completed, you can restore the instance from the MySQL recycle bin. After the instance is restored, the public network status is enabled, consistent with the enabled public network status of the MySQL instance before migration. |
With disaster recovery instance | If the MySQL instance to be migrated has a disaster recovery instance, it cannot be migrated. The current version does not support migrating disaster recovery instances. |
Data Encryption | If the MySQL instance to be migrated has data encryption enabled, it cannot be migrated. TDSQL-C for MySQL does not currently support data encryption. |
Database proxy | Whether the source TencentDB for MySQL instance has database proxy enabled or not, the current version supports migration. If the source instance has database proxy enabled, then after one-click migration to TDSQL-C for MySQL, the new cluster also has database proxy enabled by default. However, note that after migration, the kernel minor version of database proxy is the latest supported version, and the relevant access policies and configurations for database proxy are not retained. You need to manually reconfigure them. For details, see View and Modify Access Policies. |
Collation | The system will check whether the collation of the character set is compatible. If it is not compatible, migration is not supported. |
With instances in different availability zones | The system will determine whether the primary instance and read-only instance of the source TencentDB for MySQL instance are in the same availability zone. If they are in the same availability zone, migration is supported; if they are across availability zones, migration is not supported. |
Compute billing mode | The billing mode of the primary instance and read-only instances of the source TencentDB for MySQL instance must be consistent. If they are inconsistent, migration is not supported. |
IP inventory check | The system checks whether the IP inventory is sufficient. If it is insufficient, migration is not supported. |
Custom password complexity | If the MySQL instance to be migrated has the custom password complexity feature enabled, it cannot be migrated. It is recommended to disable it, which allows one-click fixing. |
SSL | If the MySQL instance to be migrated has SSL enabled, it cannot be migrated. It is recommended to disable it, allowing one-click fixing. |
whether to migrate the read-only group
If there is a read-only group under the source instance to be migrated, this option will appear. The toggle is enabled by default. If you do not need to migrate the read-only group, you can manually disable the toggle.
Scenario 1: Migration check failed
If the migration check fails, migration cannot proceed. Some options (custom password complexity, SSL) provide a one-click fix feature. You can click one-click fix to resolve issues. After successful repair, you can restart the one-click migration. Some options do not support one-click fix, such as when the source instance has data encryption enabled, which cannot be fixed automatically and prevents migration.
Note:
Click Download Report to download the migration check results locally.
Scenario 2: Migration check passed
If the migration check passes, you can click One-Click Migration to start the migration.
2. Migration in Progress
One-click migration uses the latest full backup file of the source TencentDB for MySQL instance to create a new cluster in TDSQL-C for MySQL and continuously synchronizes data. During migration, the TencentDB for MySQL instance displays the migration status as Migrating, and the newly created target cluster can be seen in the TDSQL-C for MySQL cluster list with the migration status also as Migrating.
Note:
In the TDSQL-C for MySQL cluster list, if the status of the newly created target cluster changes from Migrating to Pending Switch, it indicates that data synchronization is complete. You can then click Pending Switch or Details to go to the connection address switching page. Based on the target cluster connection address provided on the page, connect to the target cluster to view and verify data. After confirming everything is correct, follow the steps below to switch the connection address.
Switch connection address
1. In the TDSQL-C for MySQL cluster list, locate the newly created cluster and click Details under the cluster status.
2. On the redirected page, click Migration Check, then click Switch Connection Address, and finally click Confirm Switch in the pop-up window.
Note:
Switching will cause a brief disconnection lasting a few seconds. Ensure that your application has a reconnection mechanism.
After clicking to switch the connection address, the IP addresses are swapped, and data will be written to the newly created TDSQL-C for MySQL cluster.
The pending switch status will last for 72 hours. If no operation is performed within the timeout period, it will be considered as abandoning the migration, and the system will automatically cancel the migration process.
III. Migration Complete
After the connection address is switched, the migration is considered complete. Your TDSQL-C for MySQL cluster will obtain the IP address of the TencentDB for MySQL instance, and your business will be switched to the new cluster. The source TencentDB for MySQL instance will enter the recycle bin for isolation. If needed, you can go to the TencentDB for MySQL recycle bin to restore it. Subsequently, you can log in to the TDSQL-C for MySQL console to manage the new cluster after migration.
4. Migration Rollback
Note:
This edition of one-click migration does not currently support the rollback feature. Please perform thorough business checks before switching the connection address. If you need to reuse the source TencentDB for MySQL instance after migration, restore it from the TencentDB for MySQL recycle bin within the retention period. After restoration, the connection address will change, requiring you to reconfigure the application accordingly..
피드백