All Products
Search

This Product

    ApsaraDB for HBase:Enable data backup and restoration

    Document Center

    ApsaraDB for HBase:Enable data backup and restoration

    Last Updated:Oct 18, 2024

    ApsaraDB for HBase Performance-enhanced Edition supports the data backup and restoration feature. ApsaraDB for HBase Performance-enhanced Edition allows you to back up and restore data at low costs and in an efficient manner. This topic describes how to enable the data backup and restoration feature.

    Benefits

    • Incremental data can be synchronized in real time. Recovery point objective (RPO) is less than 30 seconds.

      Note

      An RPO indicates the expected time period during which data is lost after an application fails. For example, if an RPO is 15 minutes, data that is generated in the last 15 minutes cannot be restored on the cloud.

    • By default, the data backup and restoration feature can be used to back up full data in the database and restore data for a single table.

    • Data can be restored to a specific point in time.

    Limits

    • The data backup and restoration feature is available only for ApsaraDB for HBase Performance-enhanced Edition.

    • If storage space is insufficient, data backups are interrupted. However, data that has been backed up is retained.

    Billing

    If you want to enable the data backup and restoration feature, the fees include cold storage fees and tunnel service fees.

    • The fees for enabling the data backup and restoration feature vary based on regions. The following table describes cold storage fees.

      Region

      Fee

      Regions in the Chinese mainland

      • Subscription: USD 0.2/GB/month

      • Pay-as-you-go: USD 0.00042/GB/hour

      China (Hong Kong)

      • Subscription: USD 0.23/GB/month

      • Pay-as-you-go: USD 0.00048/GB/hour

      Germany (Frankfurt)

      • Subscription: USD 0.45/GB/month

      • Pay-as-you-go: USD 0.00094/GB/hour

    • Tunnel service fees vary based on the number of core nodes.

    Enable data backup and restoration

    1. Log on to the ApsaraDB for HBase console.

    2. In the top navigation bar, select the region where the cluster that you want to manage is deployed.

    3. On the Clusters page, click the ID of the cluster.

    4. In the left-side navigation pane, click Backup and Restoration.

    5. Click Enable Now. The Enable backup recovery dialog box appears.

    6. Set the Number of Core nodes parameter and the Estimated Cold Storage Capacity parameter. For more information, see Cluster specifications.

    7. Click OK.

    Enable the automatic backup feature for an ApsaraDB for HBase Performance-enhanced Edition cluster

    1. Log on to the ApsaraDB for HBase console.

    2. In the top navigation bar, select the region where the cluster that you want to manage is deployed.

    3. On the Clusters page, click the ID of the cluster.

    4. In the left-side navigation pane, click Backup and Restoration.

    5. Click Backup Configuration.

    6. In the Backup Configuration dialog box, set backup parameters based on your business requirements. The following table describes the parameters.

      Parameter

      Description

      Backup table

      An asterisk (*) can be used. It indicates that full data in the database is to be backed up.

      Full backup cycle (days)

      By default, full backups are performed at an interval of seven days. You can set this parameter to a value that ranges from 3 to 10. Unit: day. If you specify a short period, the backup task may fail to be completed in the specified time period. If you specify a long period, the time that the system requires to restore the data may increase.

      Next full backup time

      The point in time when you want to start the next full backup. We recommend that you set the full backup time to a point in time during off-peak hours.

      Number of full backup reservations

      The number of full backups that you want to retain.

    7. Click OK.

    Restore data of the cluster

    1. Log on to the ApsaraDB for HBase console.

    2. In the top navigation bar, select the region where the cluster that you want to manage is deployed.

    3. On the Clusters page, click the ID of the cluster.

    4. In the left-side navigation pane, click Backup and Restoration.

    5. Click Initiate data recovery.

    6. In the Recovery dialog box, set the parameters that are used to restore data based on your business requirements. The following table describes the parameters.

      Parameter

      Description

      Recovery cluster

      Specify the name of the cluster in which you want to restore data.

      Time point

      Specify the point in time for restoration.

      Full database recovery

      Select Yes for Full database recovery.

      Restore table

      If you select No for Full database recovery, you need to set the Restore table parameter. Asterisks (*) cannot be used.

      • You can specify a value in the namespace:table format to restore a table. For example, you can specify default:testTable as the value of this parameter.

      • You can specify a value in the namespace:table/namespace:table2 format to restore data in a table to another table. For example, you can specify default:testTable/default:testTable2 as the value of this parameter.

    7. Click OK.

    Estimate the storage space for data backup and restoration

    Storage space for data backup and restoration = Storage space for full backups + Storage space for incremental backups

    Storage space for full backups = (Number of full backups that you want to retain + 1) × Size of one full backup

    Note

    Storage space for one additional full backup is required during data backups because the system does not delete one previous full backup until one new full backup is created.

    You can check the storage space for full backups on the Cluster Management page.

    Storage space for incremental backups = 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 from the Monitoring and Alerts page or by joining the ApsaraDB for HBase DingTalk group. If a cluster receives a large amount of data every day, the size of daily incremental logs is large. You can reduce the full backup interval to reduce the log size.

    We recommend that you properly evaluate the storage usage. If storage space is insufficient, data backups are interrupted.

    FAQ

    • What is the most recent point in time to which I can restore data after a fault occurs?

      If no pending tasks exist, the most recent point in time to which you can restore data varies based on the interval at which ApsaraDB for HBase Performance-enhanced Edition log data is imported to Object Storage Service (OSS). By default, the log data is imported to OSS once every 30 seconds or every 30 MB. If a failure occurs, you may fail to restore the data that is written to ApsaraDB for HBase Performance-enhanced Edition databases in the last 30 seconds.

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

      The period of time that the system requires to restore data varies based on the data size and the bandwidth.

      • Full data restoration: The maximum speed of OSS is 1 GB/s, and each Lindorm Tunnel Service (LTS) node can write data at a speed of 100 MB/s.

      • Incremental data restoration: Each node in an ApsaraDB for HBase Performance-enhanced Edition cluster can receive 30 MB to 40 MB data per second, and each LTS node can write data at a speed of 100 MB/s.

    • Can I restore a single table?

      Yes, you can restore a single table. If a database contains tables whose names are the same, you can restore the data in one of these tables to another table.