Use point-in-time restore to recover a Lindorm Wide Table Engine instance from a full backup. This reduces data loss caused by accidental operations.
This feature is not supported in the new version of Lindorm or in Lindorm standalone instances.
Data restoration involves writing backup data to a table. If you are restoring to the same table, delete its existing data before starting the restore job.
Prerequisites
Before you begin, make sure you have:
A Lindorm instance with the backup and restore feature enabled. See Enable backup and restoration.
At least one completed backup for the instance. See Automatic backup of data in Lindorm wide tables.
Initiate a restore job
Log on to the Lindorm console.
In the upper-left corner, 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.
In the left navigation pane, click Wide Table Engine.
Click the Backup & Recovery tab.
In the Full Backup section, click Initiate Data Recovery.
In the Recovery dialog box, configure the restore parameters.
Parameter Description Cluster for Recovery Select the target instance for the restore. Backup data cannot be restored to an instance after the instance is upgraded to a later version. Point in Time Specify the point in time to restore to. Full Database Recovery Set to Yes to restore all tables. Set to No to restore specific tables only. Tables for Recovery Available when Full Database Recovery is No. Enter one table per line using namespace:tableformat. Asterisks (*) are not supported.Table name formats:
Goal Format Example Restore a table to its original location namespace:tabledefault:testTableRestore a table to a different table namespace:table/namespace:table2default:testTable/default:testTable2Click OK.
On the Recovery List tab, click Details in the Actions column to monitor restore progress.
FAQ
What is the most recent point in time I can restore to?
The cutoff depends on the write-ahead log (WAL) backup cycle to Object Storage Service (OSS). By default, WAL data is backed up every 30 seconds or for every 30 MB of WAL data generated. If a failure occurs, data written in the 30 seconds before the failure may not be recoverable.
How long does a restore take?
It depends on data volume and available bandwidth.
| Restore type | Speed |
|---|---|
| Full restore — read from OSS | Up to 1 GB/s |
| Full restore — write via Lindorm Tunnel Service (LTS) node | 100 MB/s per node |
| Incremental restore — write to destination Lindorm cluster | 30–40 MB/s per node |
| Incremental restore — write to LTS | 100 MB/s per node |
Can I restore a single table instead of the entire database?
Yes. Set Full Database Recovery to No and specify the table in namespace:table format. If a table with the same name already exists at the destination, restore to a different table using namespace:table/namespace:table2 format.