Release Notes
Product Announcements
Viewing Backup List
Upon cluster creation, TDSQL-C for MySQL generates data backups (automatic snapshot backups) based on factors such as log generation rate and write volume. By default, a backup is performed once per day. If the write volume exceeds 4 GB and more than 24 hours have passed since the last backup, a backup is triggered immediately. You can also configure automatic backup settings or perform manual backups for the cluster in the console. You can view the backup files and related information in the backup list.
This document describes how to view the list of backup files in the console.
Directions
1. Log in to the TDSQL-C for MySQL console.
2. Select the region at the top of the page and click the ID of the target cluster or Manage in the Operation column to enter the cluster management page.
3. On the cluster management page, choose the Backup Management tab. You can view the information for each backup task in the Data Backup List, Binlog Backup List, and Redolog Backup List.
Information in the Data Backup List includes: Backup ID, File Name/Alias, Backup Time, Start Time, End Time, Backup Type, Backup Mode, Backup Size, Backup Region, Destination Vault, Status, and Operation.
Information in the Binlog Backup List includes: Backup ID, File Name, Binlog Backup Start Time, Binlog Backup End Time, Binlog Backup Region, Backup Size, and Operation.
Information in the Redolog Backup List includes: Backup ID, File Name, Backup Time, Backup Size, Backup Region, and Status.
You can filter backup files by time (All, Today, Yesterday, Last 7 or 30 days, or custom time period).
You can filter data backups and binlog backups in the search box on the right.
FAQs
Why can't I find full snapshot backups in the backup list on the console?
By default, the retention period for automatic backups in TDSQL-C for MySQL is 7 days. TDSQL-C for MySQL generates a full backup per calendar week (a seven-day cycle starting from Monday), with the rest being incremental backups. This ensures one full backup per week. Therefore, you may see that the backup list in the console displays only incremental snapshot backups without showing full snapshot backups. If this occurs, please do not worry. Each incremental snapshot backup listed has an associated full snapshot backup in the backend. You can set a longer retention period for automatic backups, such as 14 days or more.
Can I download or restore backup files that exceed the retention period?
Expired backup files (including data and binlog backup files) will be automatically deleted and cannot be downloaded or restored.
You can download logical backup files in the TDSQL-C for MySQL console.
You can also perform backup manually in the console.
Note:
Manual logical backups can be deleted manually, while snapshot backups cannot.
Can I delete backups manually?
Automatic backups cannot be deleted manually. They will be automatically deleted after the retention period ends, which is 7 days and can be customized as needed. For more information, see Setting Backup Retention Period.
Snapshot backups in manual backups cannot be deleted.
Manual logical backups can be manually deleted from the backup list in the TDSQL-C for MySQL console.
How can I reduce the backup capacity cost?
Delete manual logical backups that are no longer used. For detailed directions, see Deleting Backup.
Reduce the automatic backup retention period as needed to implement the regular deletion of automatic backups. For more information, see Setting Backup Retention Period.
Related APIs
API | Description |
This API (DescribeBackupList) is used to query the backup file list of clusters. |
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