- 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
- 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)
- 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
- 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)
- 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
TDSQL-C for MySQL supports restoring data from logical backups. Its console provides a convenient operation interface for you to easily achieve fast data restoration. The logical backups can be used for database/table-level rollback to the original cluster and entire cluster rollback to a new cluster. This document introduces how to roll back an entire cluster from logical backups to a new cluster through the console.
Note:
Logical backups of the original cluster also support cross-region storage. If you wish to restore an entire cluster in a different region as a new cluster, you can use a cross-region backup for rollback. This requires enabling cross-region backup and generating a cross-region backup file first. For details, see Cross-Region Backup.
Billing for the new cluster created through rollback will start only after the rollback succeeds. For more information on billing and pricing, see Billing Overview.
During entire cluster rollback to a new cluster, the system will create a new cluster based on your selection. After the new cluster is verified, you can migrate the data back to the original cluster through DTS. In this way, you can continue using the VIP address of the original cluster. Alternatively, you can directly use the new cluster, but you should switch to the VIP address of the new cluster in the application and decide whether to delete the original cluster based on actual situations.
Feature Limits
When an entire cluster is rolled back from logical backups to a new cluster through the console, the VIP addresses of the original cluster and the new cluster cannot be exchanged.
Rollback Modes
Rollback by backup file: Restores a cluster to the dataset state of a logical backup file. The selection range of the backup file depends on the data backup retention period you set.
Rollback by time point: Restores a cluster to any time point. The selection range of the time point depends on the log retention period you set.
Note:
During rollback by time point, the system will preferentially use snapshot backups for rollback. If no snapshot backup file is found, logical backups will be used. If you need to perform rollback strictly based on the backup file type (logical backup or snapshot backup), it is recommended to select rollback by backup file.
Prerequisites
A logical backup is already available for the original cluster. To generate a logical backup, refer to the steps of generating a logical backup in each document under Performing Backup.
The cluster is in the running status.
Directions
1. Log in to the TDSQL-C for MySQL console and click the 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 Roll Back.
3. On the rollback page, complete the following configuration and click Go to the purchase page to roll back the cluster.
Parameter | Description |
Select a rollback type | Select Rollback to New Cluster. |
Select Restore Scope | Select Entire Cluster Rollback. |
Region | Select the region for the new cluster. You can select creating a new cluster in the region of the original cluster or in a different region. The selection range of the different region depends on the cross-region backup files available for your cluster. For more information on cross-region backup, see Cross-Region Backup. |
AZ | Select the availability zone for the corresponding region of the new cluster. |
Rollback Mode | Supports selecting rollback by backup file or by time point. |
Backup File | If the rollback mode is set to rollback by backup file, you need to select an existing logical backup file for rollback and then select the database/table to be rolled back. |
Rollback Time | If the rollback mode is set to rollback by time point, you need to select a rollback time point. |
4. On the pop-up purchase page, complete the corresponding Database Configuration based on the required database mode, and then click Next.
Note:
If your new cluster is created in the Serverless instance mode, make sure that both the region and availability zone of the original and new clusters support the Serverless instance mode, otherwise you can only create a cluster in the provisioned resource instance mode. For specific support details, refer to the purchase page.
For the provisioned resource instance mode
Instance Mode: Provisioned resource.
Rollback Mode: Supports rollback by backup file and by time point.
By backup file: A new cluster can be created through restoration from a specified backup set. The selection range of the backup set is based on the backup completion time and the retention period.
By time point: A new cluster can be created through restoration from the specific time point. The selection range of the time point is based on the backup retention period.
Select Restore Scope: Select Entire Cluster Rollback here.
Region: When cross-region backup is not enabled, the region is the same as that of the cluster rolled back by default. When cross-region backup is enabled and a cross-region backup file has been generated, you can select the region where the backup file is located for rollback. For enabling cross-region backup, see Cross-Region Backup.
Source AZ: When cross-region backup is not enabled, the availability zone is the same as that of the cluster rolled back. When cross-region backup is enabled and a cross-region backup file has been generated, you can select the supported availability zone of the region where the backup file is located for rollback. For enabling cross-region backup, see Cross-Region Backup.
Transfer Linkage: High I/O.
Network: Select VPC.
Database Version: Same as that of the cluster rolled back.
Instance Type: Supports general and dedicated types.
Compute Instance (read-write): Select the compute specifications of the read-write instance. Only 1 read-write instance can be configured.
Compute Instance (read-only): Select the compute specifications and quantity of the read-only instance.
Compute Billing Mode: Supports monthly subscription and pay-as-you-go.
Storage Billing Mode: The default is pay-as-you-go.
For the Serverless instance mode
Instance Mode: Serverless.
Rollback Mode: Supports rollback by backup file and by time point.
By backup file: A new cluster can be created through restoration from a specified backup set. The selection range of the backup set is based on the backup completion time and the retention period.
By time point: A new cluster can be created through restoration from a specific time point. The selection range of the time point is based on the backup retention period.
Select Restore Scope: Select Entire Cluster Rollback here.
Region: When cross-region backup is not enabled, the region is the same as that of the cluster rolled back by default. When cross-region backup is enabled and a cross-region backup file has been generated, you can select the region where the backup file is located for rollback. For enabling cross-region backup, see Cross-Region Backup.
Source AZ: When cross-region backup is not enabled, the availability zone is the same as that of the cluster rolled back. When cross-region backup is enabled and a cross-region backup file has been generated, you can select the supported availability zone of the region where the backup file is located for rollback. For enabling cross-region backup, see Cross-Region Backup.
Transfer Linkage: High I/O.
Network: Select VPC.
Database Version: Same as that of the cluster rolled back.
Serverless Architecture: Supports single-node and cluster editions.
Compute Unit: Select the upper and lower limits of the TDSQL-C compute unit (CCU). The instance will automatically perform scaling within the selected resource range. CCU is the billing unit for the Serverless mode. 1 CCU is approximately equal to 1 CPU core and 2 GB memory. The number of CCUs used in each billing cycle is the greater one between 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.
Compute Billing Mode: Supports pay-as-you-go or resource pack.
Note:
The compute resource packs are used to preferentially deduct the actual usage of pay-as-you-go products. Once the resource pack quota is used up, billing will continue on a pay-as-you-go basis. The compute resource packs are deducted based on the actual CCU used per second. Compared to the pay-as-you-go mode, the resource pack mode is more cost-effective and flexible.
Compute Resource Pack (displayed when Resource Pack is selected for the compute billing mode): You can bind all valid compute resource packs available in the selected region of the cluster under the current account. If no resource pack is available, you can first purchase a resource pack.
Storage Billing Mode: Supports pay-as-you-go or resource pack.
Note:
The compute resource packs are used to preferentially deduct the actual usage of pay-as-you-go products. Once the resource pack quota is used up, billing will continue on a pay-as-you-go basis. The storage resource packs are deducted based on the actual storage used per hour. Compared to the pay-as-you-go mode, the resource pack mode is more cost-effective and flexible.
Storage Resource Pack (displayed when Resource Pack is selected for the storage billing mode): You can bind all valid compute resource packs available in the selected region of the cluster under the current account. If no resource pack is available, you can first purchase a resource pack.
5. On the redirect page, configure basic information and advanced settings, including cluster name, default character set, security group, parameter template, and project. After confirming no errors, click Buy Now.
6. Return to the cluster list, and you can see the new cluster created through rollback. Once its status changes to Running, it can be used normally.
Yes
No
Was this page helpful?