Enabling Cold Data Archiving
Download
フォーカスモード
フォントサイズ
Scenarios
For historical data such as orders, transactions, logs, and audits that require long-term retention but have low access frequency, the unit cost of local high-performance storage is high. After you enable data archiving, you can transparently offload this cold data to COS, allowing local storage to handle only hot data. This significantly reduces long-term storage costs while maintaining business access performance. Archived data can still be queried normally using standard SQL and remains transparent to applications.
Data archiving is suitable for the following scenarios:
Historical data archiving: Data such as orders, transactions, logs, and audits requires long-term retention but has low access frequency.
Partition table rolling cold transition: The table is partitioned by dimensions such as day, week, and month. Recent partitions are retained locally, while historical partitions are gradually transitioned to cold storage.
Hot and cold hybrid storage: Within the same partition table, hot partitions and cold partitions use different storage tiers.
Billing Overview
Use Limits
Prerequisites
Note:
The cold data archiving feature is an experimental feature in version V21.6.3.0. Currently, it can be enabled only on a subset of instances that meet the requirements.
Serverless instances are not currently supported. This feature can be enabled only on provisioned resource instances with a kernel version of V21.6.3.0 or later.
Single RG mode is not currently supported. This means that instances with a node specification below 4C (including 4C 8GB) cannot enable cold data archiving. This feature can be enabled only on instances with a node specification above 4C.
Local disk instances are not currently supported. This feature can be enabled only on enhanced SSD CBS instances.
Single-replica instances are not currently supported. This feature can be enabled only on full-featured instances that have multiple replicas or are deployed across multiple AZs.
Instances with TDE transparent data encryption enabled are not currently supported. This feature can be enabled only on instances without TDE transparent data encryption enabled.
Instances that are part of a DR relationship are not currently supported. This means that neither the primary instance nor the DR read-only instance in a DR relationship can enable the cold data archiving feature. This feature can be enabled only on regular instances.
Instances with Binlog service enabled are not currently supported. Furthermore, the cold data archiving feature and the Binlog service are mutually exclusive; only one of them can be enabled.
Instances with the Read-Only Analysis Engine enabled are not currently supported. Furthermore, the Read-Only Analysis Engine and the cold data archiving feature are mutually exclusive; only one of them can be enabled.
HBase compatibility mode is not currently supported. Only MySQL compatibility mode is supported.
This feature can be enabled only on instances that are in the Running state.
Post-Enablement Constraints
Note:
The cold data archiving feature is an experimental feature in version V21.6.3.0. Currently, it has the following usage restrictions. This feature will be gradually improved. Please stay tuned for updates.
Cold data warming (data recall) is not currently supported. This means that tables or partitions that have been archived to cold storage cannot be migrated back to the original engine.
Automatic identification of cold data and automatic archiving to cold storage are not currently supported.
Backup and recovery are not currently supported. After the COS hot/cold tiering feature is enabled, instance backup and recovery are not supported, and creating disaster recovery instances is also not supported.
Bulk loading data via Bulk Load is not currently supported. Importing data using the LOAD DATA INFILE method is also not supported.
The table creation syntax
CREATE TABLE ... AS SELECT ... FROM ... is not currently supported.Fast Online DDL on cold tables is not currently supported. Only a limited subset of Online DDL operations is supported (specifically, those that go through the thomas write path).
Enabling the KV separation feature is not currently supported. If KV separation is already enabled locally, data cannot be archived to COS.
Enabling the large transaction feature is not currently supported.
Enabling the TDE transparent encryption feature is not currently supported.
Enabling the Binlog service is not currently supported.
Enabling a read-only analysis instance is not currently supported.
Changing the AZ of an instance is not currently supported. Other unsupported operations include adjusting the number of replicas, migration with specification change, and horizontal scale-in (reducing the number of nodes or disk space).
Scheduling tasks such as splitting, merging, or migrating cold RGs are not currently supported.
Steps
1. Log in to the TDSQL Boundless console. In the Instance List, click the target Instance ID to go to the Instance Details page.
2. Navigate to the Data Archiving tab. Carefully read the data archiving feature description. After confirming that everything is correct, select the service agreement checkbox and click Enable Now.
3. Upon successful completion of the enabling task, the data archiving status for the instance is updated to Enabled.
References
フィードバック