ApsaraDB for Lindorm provides low-cost and efficient backup and restoration capabilities.

Features and benefits

  • Supports real-time incremental data synchronization with a recovery point objective (RPO) of less than 30 seconds.
  • Supports the backup of an entire database and the restoration of single tables.
  • Supports data restoration at a scheduled time


Only the wide table engine supports backup and restoration. The time series engine or search engine does not support backup and restoration.


  1. Enable backup and restoration.
    Log on to the ApsaraDB for Lindorm console, and go to the Instance Details page. In the left-side navigation pane, choose Wide Table Engine > Backup & Recovery. Click Activate Now to enable backup and restoration. Enable backup and restoration
  2. Create a backup plan.
    After the backup and restoration feature is enabled, click Backup Settings on the Backup List or Recovery List page to create a backup plan. Create a backup plan
    • Tables for Backup

      Wildcard characters are supported. If you want to back up the entire database, you can enter an asterisk (*). If you set this parameter to default:test, tables whose names start with test in the default namespace are backed up.

      Notice Do not use double quotation marks(").
    • Full Backup Cycle (Days)

      By default, full backups are performed every seven days. You can set this parameter to 3 to 10 days. If you specify a short period, the backup task may fail to be completed within the period. If you specify a long period, the time that the system takes to restore the data may increase.

    • Perform Next Full Backup At

      The time when the next full backup occurs is calculated based on the full backup cycle.

    • Full Backup Reserved

      This parameter specifies the number of reserved copies for the backup. Extra space for a reserved copy is required during the backup process.

  3. Restore data. On the Backup List or Recovery List page, click Initiate Data Recovery to restore data. Data restoration


    • Cluster for Recovery

      Specify the destination cluster to which data is restored.

    • Point in Time

      Specify a point in time for data restoration.

    • Full Database Recovery

      Specify whether to restore the entire database.

    • Tables for Recovery

      Specify table names by line. Each table name cannot contain wildcard characters. Format: namespace:table. The namespace is required. Example: default:testTable. You can restore data to other tables by using the following format: namespace:table/namespace:table2. Example: default:testTable/default:testTable2. After the restoration task starts, you can view the progress on the Recovery List page.

Estimate the storage space for backup and restoration

  • Storage space for backup and restoration = Storage space for full backup + Storage space for incremental backup
  • Storage space for full backup = (Number of reserved copies + 1) × Size of a reserved copy
  • Previous data is not deleted until a copy of the data is created. Therefore, extra space for a reserved copy is required during the backup process.
  • You can view the storage space for full backup on the ApsaraDB for Lindorm cluster management page.
  • Storage space for incremental backup = Number of log retention days × Size of daily incremental logs
  • Assume that data is written at an average speed of 1 MB/s. In this case, 84 GB of storage space is required each day. You can obtain the write speed of the cluster by using CloudMonitor. You can also contact ApsaraDB for Lindorm technical support. If a cluster receives a large amount of data every day, the size of daily incremental logs is large. You can reduce the interval of full backups to reduce the log size.


  • What is the latest point in time to which I can restore data?

    If no pending tasks exist, the latest point in time to which you can restore data depends on the interval of persisting write-ahead logs (WAL) to Object Storage Service (OSS). The default interval is 30 seconds or 30 MB. If a failure occurs, you may fail to restore the data that is written into ApsaraDB for Lindorm databases within 30 seconds before the current time.

  • How much time does the system require to restore data?

    The time that the system requires to restore data depends on the data size and bandwidth.

    • Full data restoration: The maximum bandwidth of OSS is 1 GB per second and each BDS node writes 100 MB per second.
    • Incremental data restoration: Each node in an ApsaraDB for Lindorm cluster receives 30 MB to 40 MB per second and each BDS node writes 100 MB per second.
  • Can I restore a single table?

    Yes, you can restore a single table. If duplicate tables exist in a database, you can restore the table to another table.