Backup and recovery for Lindorm Table protects your data with periodic full backups and continuous incremental synchronization, storing all backup data in Object Storage Service (OSS). You can restore an entire database or individual tables to any point in time.
Use cases
Recover from accidental writes or deletes — restore a table or database to a point before the change was made.
Protect against data corruption — roll back to a known-good state when data integrity issues are detected.
Meet compliance retention requirements — keep backup data in OSS for as long as your policy requires.
How it works
Backup and recovery uses Lindorm Tunnel Service (LTS) to migrate data into OSS. After you enable the feature, the system performs periodic full backups and synchronizes incremental changes in real time, achieving a recovery point objective (RPO) of less than 30 seconds.
Each subsequent full backup replaces the previous one only after the new backup completes, so at least one complete full backup is always available.
Prerequisites
Before you begin, ensure that you have:
A Lindorm instance with the Wide Table Engine enabled
Sufficient OSS storage capacity for both full and incremental backups (see Estimate storage capacity)
If the search index or change tracking feature is already enabled on your instance, backup and recovery activates immediately when you click Activate Now. You do not need to complete the LTS configuration steps (steps 6-7 below).
Estimate storage capacity
If the allocated storage capacity is used up, data backup stops. Estimate your required capacity before enabling the feature.
Use the following formulas to calculate the storage you need:
Total storage = Full backup storage + Incremental backup storage
| Component | Formula | Example |
|---|---|---|
| Full backup storage | (Number of full backups to retain + 1) × Size of one full backup | Retain 3 full backups, each 100 GB: (3 + 1) × 100 GB = 400 GB |
| Incremental backup storage | Retention period (days) × Daily incremental log size | 7-day retention, write throughput of 1 MB/s: 7 × 84 GB = 588 GB |
The "+1" in the full backup formula accounts for the overlap period: the system keeps the previous full backup until a new one finishes.
To find the write throughput of your instance, check the Instance Monitoring page in the Lindorm console, or contact technical support (DingTalk ID: s0s3eg3).
To reduce incremental log size, decrease the interval between full backup operations.
After you enable the feature, verify actual usage by navigating to Wide Table Engine > Backup & Recovery and checking the Data Size column in the Full Backup section.
Enable backup and recovery
Log on to the Lindorm console.
In the upper-left corner, select the region where your instance is deployed.
On the Instances page, click the instance ID or click View Instance Details in the Actions column.
In the left navigation pane, choose Wide Table Engine > Backup & Recovery.
Click Activate Now.
If search index or change tracking is already enabled on the instance, backup and recovery activates immediately. Skip the remaining steps.
Otherwise, you are redirected to the Upgrade/Downgrade page. Continue with the next steps.
On the Upgrade/Downgrade page, configure the LTS settings:
Parameter Description LTS Core Spec Specification for the core nodes in LTS. For details, see Cluster specifications. LTS Nodes Number of core nodes on which LTS is deployed. Click Buy Now to complete the purchase.
What's next
The LTS instance purchased through this feature has the same capabilities as a separately purchased LTS instance. To learn about available features, see Purchase methods.
To log in to LTS from your Lindorm instance, see Log on to LTS from a Lindorm instance.