tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary

Configuring Transition-to-Cold Storage

PDF
Focus Mode
Font Size
Last updated: 2025-10-28 17:55:15
TencentDB for MySQL supports transition-to-cold storage for backup files to reduce the backup storage costs. This document describes how to use this feature.
Note:
The cluster edition of the instance currently does not support the backup archiving feature.
The free space is not applicable to transitioned backups.
The archive storage type isn't available yet.

Overview

Transition-to-cold storage: The feature automatically transitions the storage types of generated data and binlog backup files according to the configured transition-to-cold storage rules to reduce the storage costs.
After you configure the backup retention period in Auto-Backup Settings, backup files will be stored according to the backup policy. Within the configured retention period, you can transition the backup files generated N or X days (customizable) ago to standard or archive storage respectively through the transition-to-cold storage feature.
Backup file storage types
Standard storage: It is suitable for business scenarios with frequent access and use. It can be used for rollback and cloning, uses no free space, and only supports downloads over the private network.
Archive storage: Suitable for business scenarios with lower access frequency, Archive Storage mandates a minimum retention period of 90 days. If the storage duration is less than 90 days, fees will be calculated based on the 90-day minimum. Downloading is not supported.

Feature overview

You can configure to transition backup files generated a certain number of days ago to standard storage. The number can range from 30 days to the configured number of backup retention days.
You can configure to transition backup files generated a certain number of days ago to archive storage. The number can range from 90 days to the configured number of backup retention days.
The backup storage type can only be transitioned from hot to cold (general storage > standard storage > archive storage) but not vice versa.
All the configured transition-to-cold storage policies will be performed at 00:00 (GMT+08:00) on the next day. As lifecycle tasks are executed asynchronously, the execution for backups after the rule is configured will be finished by 24:00 on the next day in most cases. The time is calculated based on the modification time of the transition-to-cold storage configuration.
Transition-to-cold storage can be configured for data backups and binlog backups separately.
Transition-to-cold storage can be used together with periodic archive.
Backup files in standard storage can only be downloaded through the private network. Downloading through the public network is not supported. Backup files in archive storage cannot be downloaded through either the private or public network.

Billing overview

Transitioned backups are stored at lower prices to reduce the storage costs. For billing details, see Backup Space Billing.

Transition-to-cold storage policy

1. When the backup retention period is ≤ 31 days, cold storage for backups cannot be configured. To enable this feature, please set the backup retention period to more than 31 days.
2. When 31 days < backup retention period ≤ 180 days, the number of days for archive storage cannot be configured.
3. The number of days for standard storage cannot exceed or equal the number of days for archive storage.
4. Both the standard storage duration and archive storage duration must be less than the backup retention period.
5. A transition-to-cold storage rule only takes effect after it is selected.

Configuring transition-to-cold storage

1. Log in to the TencentDB for MySQL console, click an Instance ID on the instance list page to enter the management page, and select Backup and Restoration > Auto-Backup Settings.

2. In the Backup Settings pop-up window, configure the data backup retention period and cycle or configure the log backup retention period, select the target transition-to-cold storage policy, and specify the number of days.

3. Read and select Backup Space Billing Notes and click OK.

Examples of transition-to-cold storage

Example 1: Non-archive backup + transition-to-cold storage configurationBackground Company A has a TencentDB for MySQL instance in Guangzhou region. The data backup retention period is 200 days, and the non-archive backup cycle is every Monday, Wednesday, Friday, and Sunday. On December 31, 2022, the following transition-to-cold storage policy is configured: after a backup file is generated for 90 or 180 days, it will be transitioned to standard or archive storage respectively. Transition expectations
The transition-to-cold storage policy takes effect on January 1, 2023.
Existing backup files: Starting from January 1, 2023, existing backup files generated for more than 90 or 180 days are transitioned to standard or archive storage respectively.
New backup files: Starting from January 1, 2023, newly generated backup files are transitioned to standard or archive storage respectively after 90 or 180 days.
Example 2: Archive backup + transition-to-cold storage configurationBackground Company B has a TencentDB for MySQL instance in Guangzhou region. The data backup retention period is 365 days, the non-archive backup cycle is every Monday, Wednesday, Friday, and Sunday, the archive backup retention period is 365 days, and one backup file is retained periodically per month. On January 31, 2023, the following transition-to-cold storage policy is configured: after a backup file is generated for 90 or 180 days, it will be transitioned to standard or archive storage respectively. Transition expectations
The transition-to-cold storage policy takes effect on February 1, 2023.
Existing backup files: Starting from February 1, 2023, existing backup files generated for more than 90 or 180 days are transitioned to standard or archive storage respectively.
New backup files: Starting from February 1, 2023, newly generated backup files are transitioned to standard or archive storage respectively after 90 or 180 days. In the backup retention schedule shown in the figure below, each newly generated backup file will be transitioned according to the time configured in the transition-to-cold storage policy, and backups can be transitioned only from hot to cold.


Help and Support

Was this page helpful?

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

Feedback