Cloud Backup delivers agentless, native backup and restore for Tablestore data tables, with flexible scheduling, data deduplication, and vault-level backup locking.
Introduction
Tablestore is a multi-model structured data storage service from Alibaba Cloud that stores massive volumes of structured data and supports high-performance queries and analytics. Cloud Backup backs up Tablestore data and restores it on demand.
This feature has usage limits. For more information, see Limits.
Benefits
-
Native Tablestore backup
Back up Tablestore data tables directly without installing any backup agents or components.
-
Flexible data versioning
Schedule incremental backups by day, week, month, or year. Specify retention periods for backup points to manage data versions over time.
-
Simple table data restoration
After a system failure or operational error on a Tablestore instance, restore table data from the backup vault to the source Tablestore instance or to another Tablestore instance. Each restore operation handles one table at a time.
-
Data deduplication and compression
Backup data is deduplicated and compressed to reduce storage consumption in the backup vault.
-
Backup locking
Lock a backup vault so that no account or method can delete backup data before the configured retention period expires. This guards against both accidental and malicious deletion.
How it works
Cloud Backup uses an agentless mode that requires no additional computing resources. Add a Tablestore instance to the protected instance list in Cloud Backup, and the system automatically runs full and incremental backups. Cloud Backup leverages the Tunnel Service of Tablestore to create real-time data tunnels for data tables, which enables the following backup types:
-
Full backup: Creates a complete copy of all data in the data tables during the initial backup.
-
Incremental backup: Continuously captures data that has been added or changed since the last backup, keeping the backup in sync with the source data.
A backup chain consists of one full backup followed by multiple incremental backups, which supports point-in-time restore to any historical state. In the event of accidental deletion, system failures, or other exceptions, roll back data quickly to maintain business continuity.
Procedure
To back up Tablestore tables, complete the following steps in the Cloud Backup console:
-
Activating Cloud Backup is free of charge. If you use the Tablestore backup feature, you are charged for the storage usage of the backup vault.
-
Cloud Backup is free for the first 30 days after you use the Tablestore backup feature for the first time.
-
The Tablestore backup feature creates backup vaults. Backup vault fees are included in your Cloud Backup bills. For more information, see Billing methods and billable items.
-
If you restore data to a Tablestore instance, you are charged for the data write throughput. These fees are included in your Tablestore bills. For more information, see Billing overview.
-
-
When you create a backup plan, configure the full backup and incremental backup policies, backup vault, and retention period. Cloud Backup then runs the plan and continuously backs up data from the specified Tablestore instance.
-
-
Cloud Backup does not charge for data restoration. Restoration fees are included in your Tablestore bills.
-
If a system failure or error occurs on a Tablestore instance, you can restore the table data in the backup vault to the source Tablestore instance or another specified Tablestore instance. You can restore only one table at a time.
-
Fees
Tablestore backup incurs the following fees:
-
Storage capacity fee
Billed by the storage capacity that backup data consumes in the backup vault. View vault details on the Overview page of the Cloud Backup console. Cloud Backup supports two storage types: locally redundant storage (LRS) and zone-redundant storage (ZRS). For more information, see Pricing.
-
Restoration fee
Restoring data to a Tablestore instance incurs a data write throughput fee charged by Tablestore. For more information, see Tablestore billing.
Certain configurations or operations incur additional fees. For example, cross-region backup generates storage capacity fees for the destination backup vault and cross-region replication traffic fees. For the full fee breakdown, see Billing methods and billable items.
What to do next
-
To start backing up Tablestore data tables, see Back up Tablestore data tables.
-
For recommended backup strategies, see Best practices.