Release Notes
Product Announcements
Overview
TDSQL-C for MySQL provides the clone feature to restore an entire 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 original cluster through DTS or use the newly cloned cluster directly. If the original cluster is no longer needed, you can delete it. For more information, see Migrating to TDSQL-C for MySQL.
TDSQL-C for MySQL supports the cluster rollback by time point and backup set. If you choose to roll back by time point, the log retention period you specify will define the selection range of time points. If you choose to roll back by backup set, the data backup retention time you specify will define the selection range of backup files. After a cluster is created, TDSQL-C for MySQL generates backup files every 6–4848 hours on a 24/24 uninterrupted basis, which has no impacts on the instance performance. You can also set the backup retention time in the console as needed. Based on this, when you perform cloning on the cluster, the available time points and backup sets will be directly displayed for your selection in the console.
Process
To roll back by either time point or backup set, you first need to roll back the full backup data to a newly purchased cluster. Once you've verified the data in the new cluster, you can migrate the rolled-back data back to the original cluster and terminate the new one. Alternatively, you can directly move your business to the new cluster and terminate the original one.
The process is as shown below:
Instructions
Cluster Rollback by Time Point
Cluster Rollback by Backup Set
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback