To provide you with a higher-quality and more efficient backup and rollback experience, the TencentDB for SQL Server development team has optimized and upgraded the backup and rollback feature. This enhancement aims to deliver a better user experience through improved backup and rollback speeds. This announcement informs you of the release policy for the new backup and rollback feature, comparisons between the new and old versions, and performance improvements of the new architecture. The details are as follows:
Release Policy for the New Backup and Rollback Feature
● Release date: Starting from January 28, 2026 (Wednesday) (UTC+8).
● Gradual release policy: The new backup and rollback feature will be gradually rolled out starting from January 28, 2026 (UTC+8). The platform will proceed in batches grouped by Tencent Cloud account (UIN). Only users included in the gradual release will be able to see the new feature page. If you do not see the new feature page, please wait for the release process to complete. We will work to release it for all users as soon as possible. If you have multiple Tencent Cloud accounts, the time you see the new feature may vary across accounts due to the gradual release.
Sub-account Authorization for Fine-Grained Scenarios
If your sub-account only has permissions for part of the backup APIs, you need to re-authorize the sub-account with your root account after you switch to the new backup and rollback version. If your sub-account has permissions for all backup APIs, the sub-account does not require re-authorization.
Comparison Between the New and Old Backup and Rollback Versions
1. Architecture Comparison
The new backup and rollback feature adopts a new streaming backup and streaming rollback architecture, which enhances backup and rollback efficiency by optimizing the mechanisms for backup upload and disk writing.
|
Comparison Item |
Old Version |
New Version |
|
Backup upload method (system level) |
After backup files are generated, they are written to the local disk for intermediate storage and then uploaded to Cloud Object Storage (COS). |
After backup files are generated, they are directly uploaded to COS. |
|
Rollback download method (system level) |
During rollback operations, backup files stored in COS are written to the local disk before the rollback is performed. |
During rollback operations, data is rolled back directly from COS to the instance. |
2. Feature Comparison
|
Feature |
Old Version |
New Version |
|
Instance-level backup overview |
Not supported. |
Supported. |
|
Backup file format for log backups |
Only supports archived backup files. |
Supports archived backup files and unarchived backup files. |
|
Manual sorting of backup list fields |
Not supported. |
Supported. |
|
Backup overview with multi-format preview |
Only supports overview by data. |
Supports overview by data and distribution by file. |
|
Backup trend with multi-format preview |
Only supports trend preview by type. |
Supports trend preview by type and by instance distribution. |
|
Data backup list (region) |
Not supported. |
Supported. |
|
Log backup list (region) |
Not supported. |
Supported. |
|
Data/Log backup retention period |
Up to 1830 days. |
Up to 7300 days. |
|
Log backup frequency |
Frequency cannot be changed. |
Default frequency is 10 minutes. Value range: 10 minutes - 60 minutes. |
|
Conversion from regular backups to scheduled backups |
Not supported. |
Supported. |
|
Scheduled backup retention policy |
Number of retained backups cannot be set on a weekly basis. |
Number of retained backups can be set on a weekly basis. |
|
Data backup list |
List fields do not include "Backup Progress" and "Expiration Time".” |
List fields include "Backup Progress" and "Expiration Time".” |
|
Log backup list |
List fields do not include "Backup Duration", "Backup File Format", and "Expiration Time".” |
List fields include "Backup Duration", "Backup File Format", and "Expiration Time".” |
|
Download |
Download permissions and download link validity period cannot be configured. |
Download permissions and download link validity period can be configured. |
3. Performance Comparison of the New and Old Architectures
Compared to the old architecture, the new architecture improves the average backup speed by 123%and the average rollback speed by 150%.
Compared to the old architecture, the average CPU utilization of the new architecture is reduced by 40%
Documentation
For documentation on the new backup and rollback feature, see View Backup Overview (Instance) and View Backup Overview (Region)
