TDSQL-C for MySQL can roll back databases/tables to the original cluster and roll back an entire cluster (clone) to a new cluster. You can choose different rollback methods based on your business needs. This document describes how to clone a cluster and quickly restore data to the newly purchase cluster in the console.
TDSQL-C for MySQL provides the clone feature to restore a cluster to any time point in the log backup retention period or to the backup set of the specified backup file.
The clone will create a new cluster based on your choice. After the new cluster is verified, you can either migrate the data back to the source cluster through DTS or use the new cloned cluster directly. For more information, see Migrating to TDSQL-C for MySQL.
Note:
Billing will start for the cloned new cluster after the clone succeeds. For more information on billing and pricing, see Billing Overview.
Directions
1. Log in to the TDSQL-C for MySQL console and click a cluster ID in the cluster list to enter the cluster management page.
2. On the cluster management page, select the Backup Management tab and click Clone in the Operation column in the backup list.
3. On the purchase page, complete the Database Configuration settings based on he selected database mode, and click Next.
For Provisioned Resource instance mode
Instance Mode: Provisioned Resources
Rollback Mode: Clone by backup file and clone by time point are supported.
By backup file: A new cluster can be created from the specified backup set for restoration, and the selection range is based on the time when the backup is completed and the retention period.
By time point: A new cluster can be created from the specific time point for restoration, and the time point selection range is based on the backup retention period.
Region: Same as that of the cloned cluster.
AZ: Same as that of the cloned cluster.
Transfer Linkage: High IO.
Network: Select VPC.
Database Version: Same as that of the cloned cluster.
Compute Instance (read/write)Select the compute specifications of the read-write instance. Only one read-write instance can be configured.
Compute Instance (read-only): Select the compute specifications of the read-only instance. You need to select at least two read-only instances to ensure that the cluster is highly available. After the cluster is created, you can expand the read capability of the cluster by adding read-only instances.
Compute Billing Mode: The billing mode is pay-as-you-go by default. Currently, clone doesn't support monthly subscription.
Storage Billing Mode: The billing mode is pay-as-you-go by default.
For serverless instance mode
Instance Mode: Serverless
Rollback Mode: Clone by backup file and clone by time point are supported.
By backup file: A new cluster can be created from the specified backup set for restoration, and the selection range is based on the time when the backup is completed and the retention period.
By time point: A new cluster can be created from the specific time point for restoration, and the time point selection range is based on the backup retention period.
Region: Same as that of the cloned cluster.
AZ: Same as that of the cloned cluster.
Transfer Linkage: High IO.
Network: Select VPC.
Database Version: Same as that of the cloned cluster.
Compute Unit: Select the upper and lower limits of the TDSQL-C compute unit (CCU), and the instance will be automatically and elastically scaled within the selected resource range. CCU is the computing and billing unit for the serverless mode. A CCU is approximately equal to 1 CPU core and 2 GB memory. The number of CCUs used in each billing cycle is the greater of the number of CPU cores used by the database and 1/2 of the memory size. For more information, see Compute Unit.
Auto-Pause: Configure the automatic pause time of the instance. If there is no connection to access the database within the set time, the instance will be automatically paused, with billing stopped.
Billing Mode: Resource pack (monthly subscription) and pay-as-you-go billing are supported.
Note:
The compute resource pack will be used preferably for the deduction of actual usage of pay-as-you-go products. When the pack is used up, the resource usage will be pay-as-you-go. Compute resource packs are deducted based on the actual CCU used per second. The resource pack mode is more cost-effective and flexible than the pay-as-you-go option.
Compute resource pack (displayed when selecting Resource Pack in the compute billing mode): You can bind all valid compute resource packs available in the selected region under the current account. If no resource pack is available, you can purchase a resource package first.
Storage Billing Mode: Resource pack (monthly subscription) and pay-as-you-go billing are supported.
Note:
The storage resource pack will be used preferably for the deduction of actual usage of pay-as-you-go products. When the pack is used up, the resource usage will be pay-as-you-go. Storage resource packs are deducted based on the actual storage used per hour. The resource pack mode is more cost-effective and flexible than the pay-as-you-go option.
Storage resource pack (displayed when selecting Resource Pack in the storage billing mode): You can bind all valid storage resource packs available in the selected region under the current account. If no resource pack is available, you can purchase a resource package first.
4. Configure the Basic Info and Advanced Configuration settings on the page redirected to, such as cluster name, default character set, security group, parameter template, and project. Then, click Buy Now.
5. Return to the cluster list, and you can see the new cluster created through clone. After its status changes from Cloning to Running, it can be used normally.
Note:
After confirming that the data in the new cluster created through clone is correct, you can modify the cluster VIP or click Delete in the Operation column to delete the old cluster on the cluster details page as needed.
Yes
No
Was this page helpful?