LindormTable supports the data backup and restoration feature. This feature can store data in Object Storage Service (OSS) based on a data ecosystem service named Data Transport. The feature can back up full data and synchronize incremental data in real time to meet the requirements of data backup and restoration.Lindorm
Background information
Benefits
Real-time synchronization for incremental data is supported. A recovery point object (RPO) less than 30 seconds can be achieved.
NoteAn 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
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
NoteAn 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 capacity for full backups in the Lindorm console by performing the following steps: In the left-side navigation pane, choose
. In the Full Backup section, view the value of Data Size.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.
NoteYou 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.
Usage notes
The data backup and restoration feature is not supported by Lindorm New Edition and single-node Lindorm instances.
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 instance that you want to manage or click Manage in the Actions column corresponding to the instance.
In the left-side navigation pane, choose
.Click Activate Now. Then, the Upgrade/Downgrade page appears.
NoteIf the search index or change tracking feature is enabled for the instance, the backup and restoration feature is immediately enabled after you click Activate Now. In this case, the Upgrade/Downgrade page does not appear.
On the Upgrade/Downgrade page, specify the following configuration items based on your requirements:
NoteIf the search index or change tracking feature is enabled for the instance, this step is not required.
LTS Core Spec: Specify the specification for the core nodes in Lindorm Tunnel Service (LTS). For more information, see Cluster specifications.
LTS Nodes: Specify the number of core nodes on which LTS is deployed.
Read and select Lindorm Terms of Service.
After you specify the configuration items, click Buy Now.
NoteIf the search index or change tracking feature is enabled for the instance, this step is not required.
References
The LTS service that is purchased by 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 more information about how to log on to the LTS console, see Log on to the web UI of LTS.