tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
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
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Setting Backup Retention Period

PDF
Focus Mode
Font Size
Last updated: 2026-03-04 11:45:45
Backups for TDSQL-C for MySQL include data backups and log backups (binlog and redolog). Backup methods are categorized into automatic backup and manual backup. Backups can be stored in the local region or a cross-region location. You can configure the backup retention period for: local or cross-region snapshot backups from automatic backups, local or cross-region logical backups from automatic backups, and local or cross-region log backups.
This document describes how to set the backup retention period in the console.

Directions

Setting the Retention Period for Snapshot Backups in Automatic Backups

1. Log in to the TDSQL-C for MySQL console.
2. Select a region at the top and proceed according to the actually used view mode.
Tab view
List view
Click Target Cluster in the cluster list on the left to enter the cluster management page.

Find the target cluster in the cluster list and click the Cluster ID or Manage in the Operation column to enter the cluster management page.

3. On the cluster management page, select the Backup Management tab and click Auto-Backup Settings.

4. In the Auto-Backup Settings window, click Modify Backup Settings to set the retention period for automatic backups in the pop-up window. After configuration, both local and cross-region automatic snapshot backups for this cluster will be retained according to this period.


Setting the Retention Period for Logical Backups in Automatic Backups

1. Follow Steps 1-3 to enter the Automatic Backup Settings Page.
2. In the automatic backup settings window and under Logical Backup, click Enable and Set.
Note:
If automatic logical backup is already enabled and you need to modify the backup retention period, please click Modify Backup Settings.
3. In the pop-up dialog box, set the retention days for automatic backups (7 - 1830 days), and click OK.

4. After it is enabled and configured successfully, click OK in the lower right corner.

Setting the Retention Period for Log Backups

Note:
Binlog backup retention days: 7 - 1,830 days, which cannot be shorter than the data backup retention period.
If cross-region backup is enabled for binlog, the retention period for local binlog backup files will be consistent with that for cross-region binlog backup files.
Redolog backup is enabled by default. Its retention days are the same as those for automatic snapshot backups, and its cross-region backup settings are the same as those for automatic snapshot backups.
1. Enter the cluster management page according to Step 1-2.
2. On the cluster management page, select the Backup Management tab, click Log Backup Settings.
3. Set the binlog backup retention days, and click OK.


Related APIs

API
Description
This API (DescribeBackupConfig) is used to obtain the backup configuration information of the specified cluster, including the full backup time window and the backup file retention period.
This API (DescribeBinlogSaveDays) is used to query the cluster's binlog retention days.
This API (DescribeBinlogConfig) is used to query binlog configuration.
This API (ModifyBinlogConfig) is used to modify binlog configuration.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback