tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

TDSQL-C Data Backup

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-02-10 16:43:04

Introduction

TDSQL-C MySQL data backup is a database backup feature provided by Tencent Cloud COS (Cloud Object Storage, COS) based on SCF (Serverless Cloud Function, SCF) for users, which can assist users in transferring backup files on TDSQL-C MySQL cloud database to COS for persistent storage to prevent data loss or corruption. When users configure backup function rules in a specified bucket, SCF will periodically scan your TDSQL-C MySQL backup files and transfer the files to the bucket.

Must-Knows

The TDSQL-C MySQL data backup function backs up the binlog backup files of the Tencent Cloud TDSQL-C MySQL database. If you have not enabled scheduled binlog backup for the TDSQL-C MySQL database, you cannot execute this backup function. For more information about Tencent Cloud TDSQL-C MySQL database backup, see Overview of TDSQL-C MySQL Backup and Rollback.
Logical backup and snapshot backup are temporarily not supported for backup to COS via this feature.
If you previously added a TDSQL-C MySQL data backup rule for a bucket on the COS console, you can see the TDSQL-C MySQL data backup function you created on the SCF console. Please do not delete this function, otherwise, it may cause your rule to become ineffective.
TDSQL-C MySQL data backup supported regions include: Guangzhou, Shanghai, Beijing, Chengdu, Hong Kong (China), Singapore, Silicon Valley, and so on. For more supported regions, see TDSQL-C MySQL region documentation.

Operation Steps

Configure Backup In Application Integration

1. Log in to the COS Console.
2. In the left navigation, click Application Integration > Data Backup, and find TDSQL-C MySQL Backup.
3. Click Configure Backup Rules to go to the rule configuration page.
4. Click Add Function.
Note:
If you have not activated SCF service, please go to the SCF console to activate the service and follow the prompts to complete the service authorization.
5. In the pop-up window, configure the following information:
Function Name: As the unique identifier of the function, it cannot be modified after creation. You can view this function on the SCF Console.
Associated Bucket: the bucket that stores TDSQL-C MySQL backup files.
Note:
The region where the TDSQL-C MySQL data to be backed up resides must be the same as the region of the associated bucket.
Trigger Cycle: The TDSQL-C MySQL data backup function triggers backup offloading operations through timer triggers. Supported trigger cycles include daily, weekly, and custom intervals.
Cron Expression: When the trigger cycle is set to custom, you can specify the trigger cycle rules via Cron. Cron currently runs on local standard time. For detailed configuration policies, see Cron-related documentation.
Database Instance: the list of TDSQL-C MySQL database instances in the current bucket's region.
Delivery Path: The prefix of the delivery path for backup files. If left blank, files will be saved by default at the root path of the bucket.
SCF Authorization: TDSQL-C MySQL data backup requires authorizing the cloud function to read database instances and their backup files from your TDSQL-C MySQL backups, and offload the backup files to your specified bucket. This authorization is thus required.
6. After the configuration is added, click Confirm, and you will see that the function has been successfully added. You can perform the following operations on the newly created function:
Click Logs to view the historical operation status of TDSQL-C MySQL data backup. When backup errors occur, you can also click Logs to quickly navigate to the SCF Console and view log error details.
Click More > Edit to modify TDSQL-C MySQL data backup rules.
Click More > Delete to remove unused TDSQL-C MySQL data backup rules.

Set up backup in the bucket configuration item

1. Log in to the COS Console.
2. In the left navigation, select Bucket List, click the bucket that requires TDSQL-C MySQL data backup setup, and go to the bucket management page.
3. Click Function Compute on the left and locate the TDSQL-C MySQL Backup Function configuration item.
Note:
If you have not activated SCF service, please go to the SCF console to activate the service and follow the prompts to complete the service authorization.
4. Click Add Function.
5. In the pop-up window, configure the following information:
Function Name: As the unique identifier of the function, it cannot be modified after creation. You can view this function on the SCF Console.
Trigger Cycle: The TDSQL-C MySQL data backup function triggers backup offloading operations through timer triggers. Supported trigger cycles include daily, weekly, and custom intervals.
Cron Expression: When the trigger cycle is set to custom, you can specify trigger cycle rules via Cron. Cron currently runs on UTC+8 China Standard Time (CST), which is Beijing Time. For detailed configuration policies, see Cron-related documentation.
Database Instance: the list of TDSQL-C MySQL database instances in the current bucket's region.
Delivery Path: The prefix of the delivery path for backup files. If left blank, files will be saved by default at the root path of the bucket.
SCF Authorization: TDSQL-C MySQL data backup requires authorizing the cloud function to read database instances and their backup files from your TDSQL-C MySQL backups, and offload the backup files to your specified bucket. This authorization is thus required.
6. After adding the configuration, click Confirm, and you will see that the function has been successfully added. You can perform the following operations on the newly created function:
Click Logs to view the historical operation status of TDSQL-C MySQL data backup. When backup errors occur, you can also click Logs to quickly navigate to the SCF Console and view log error details.
Click More > Edit to modify TDSQL-C MySQL data backup rules.
Click More > Delete to remove unused TDSQL-C MySQL data backup rules.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan