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

Manual Backup

PDF
Focus Mode
Font Size
Last updated: 2026-03-04 11:45:45
TDSQL-C for MySQL supports automatic backup and manual backup. This document describes how to create a manual backup in the console.
Note:
To ensure the stability of the backup system, the current system allows initiating a backup only once per hour.
With manual backup, you can use snapshot backup to manually back up the entire cluster or use logical backup to back up the entire cluster or specified databases/tables.
Logical backups in the manual backup can be manually deleted from the backup list to free up backup space and avoid space waste and occupancy. Snapshot backups do not support manual deletion.
Logical backups in the manual backup (entire cluster) supports enabling cross-region backup feature, allowing manual logical backup (entire cluster) CFS to other regions.
If your cluster storage space usage exceeds 2TB, it is not recommended to use the logical backup due to the risk of backup failure.

Directions

1. Log in to the TDSQL-C for MySQL console.
2. Select the region at the top, 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 Manual Backup.

4. In the pop-up dialog box, complete the following configurations and click OK to create a backup task.

Parameter
Description
Backup Type
Snapshot Backup and Logical Backup are supported.
Note:
We recommend you perform a manual logical backup task during off-peak hours, as it will lock the database and affect database use.
Object
Snapshot Backup applies to the Entire cluster, while Logical Backup applies to the Entire cluster or Specify Table. If you select Specify Table, you can choose specific databases and tables for manual backup.
Cross-Region Backup
You can choose whether to enable cross-region backup for Snapshot Backup (for the Entire cluster) and Logical Backup (for the Entire cluster).
If this is enabled, backup files can be saved to other regions.
If not enabled, the reserved region for the manual logical backup is the current cluster's region by default.
Backup Region
If Cross-Region Backup is enabled, you can select up to three different regions to store the backup files.
Store to Vault
If this option is enabled, manual backups will be delivered to the backup vault for storage. For details on the backup vault, see Backup Vault.
Note:
Manual snapshot backups for the entire cluster, manual logical backups for the entire cluster, and manual logical backups for specified databases and tables all support the "Store to Vault" parameter.
Select Vault
If "Store to Vault" is enabled, you can select the target backup vault for storage.
Alias
When you create a manual backup, you can set an alias for the backup file. The alias can contain only digits, uppercase and lowercase letters, Chinese characters, and special characters (-_./()[]()+=:;@), with a maximum length of 60 digits.
5. After creating a manual backup task, you can view the task progress in the Task List on the left sidebar. You can also view the execution status by clicking Backup Details in the Operation column.


Related APIs

API
Description
This API (CreateBackup) is used to create a manual backup for a cluster.

Help and Support

Was this page helpful?

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

Feedback