Enable the backup and restoration feature for Lindorm - Lindorm

Lindorm Table supports a data backup and recovery feature that uses data migration in Data Ecosystem Services to store data in Alibaba Cloud Object Storage Service (OSS). This feature performs periodic full backups and synchronizes data incrementally in real time to meet your data backup and recovery requirements.

Background information

Benefits

Real-time synchronization for incremental data is supported. A recovery point object (RPO) less than 30 seconds can be achieved.
Note
An RPO indicates the expected time period during which data is lost after an application failure. For example, if a cloud service provides an RPO of 15 minutes, data that is generated within the most recent 15 minutes cannot be restored on the cloud.
By default, the feature backs up full data in databases. You can also use this feature to back up and restore data for one or more tables.
The feature can restore data to a specific point in time.

Estimate the storage space for backup and restoration

Important

We recommend that you estimate the storage capacity required for data backup and restoration. If the specified storage capacity is used up, data backup stops.

Storage capacity for backup and restoration = Storage capacity for full backups + Storage capacity for incremental backups
Storage capacity for full backups = (Number of full backups that you want to retain + 1) × Size of one full backup
Note
An additional full backup is required during data backup because the system does not delete a full backup until a new full backup is created.
After you enable the backup and restoration feature, you can view the storage space used by full backups in the Lindorm console. To do this, navigate to Wide Table Engine > Backup & Recovery. In the Full Backup section, check the value in the Data Size column.
Storage capacity for incremental backups = Retention period of logs (days) × Size of daily incremental logs For example, if the average write speed of your instance is 1 MB/s, the required daily storage capacity for incremental backups is 84 GB.
Note
- You can check the data on the Instance Monitoring page or contact the technical support (DingTalk ID: s0s3eg3) to know the write speed of your instance.
- If an instance receives a large volume of data each day, the size of daily incremental logs is large. In this case, you can decrease the interval for full backup operations to reduce the log size.

Procedure

Log on to the Lindorm console.
In the upper-left corner of the page, select the region where the instance is deployed.
On the Instances page, click the ID of the target instance or click View Instance Details in the Actions column for the instance.
In the navigation pane on the left, choose Wide Table Engine > Backup & Recovery.
Click Activate Now. You are redirected to the Upgrade/Downgrade page.
Note
If the search index or change tracking feature is already enabled for the instance, the backup and restoration feature is enabled immediately after you click Activate Now. You are not redirected to the Upgrade/Downgrade page.
On the Upgrade/Downgrade page, configure the items as needed.
Note
If the search index or change tracking feature is enabled for the instance, this step is not required.
1. LTS Core Spec: Specify the specification for the core nodes in Lindorm Tunnel Service (LTS). For more information, see Cluster specifications.
2. LTS Nodes: Specify the number of core nodes on which LTS is deployed.
After you complete the configuration, click Buy Now.
Note
If the search index or change tracking feature is enabled for the instance, this step is not required.

Related operations

The LTS service that is purchased using the backup and restoration feature has the same features as an LTS instance that is separately purchased. For more information, see Purchase methods.

For information about how to log on to LTS, see Log on to LTS from a Lindorm instance.