All Products
Search
Document Center

Cloud Backup:Back up Tablestore tables

Last Updated:Jun 13, 2024

To prevent data loss or damage caused by accidental deletion, modification, or overwriting, we recommend that you use Cloud Backup to back up data tables in your Tablestore instance. Cloud Backup allows you to configure flexible backup policies to back up data to the cloud. You can view and restore data tables at any time. This topic describes how to use Cloud Backup to back up data tables from a Tablestore instance.

Prerequisites

  • Cloud Backup is activated. You are not charged for activating Cloud Backup. If you use the Tablestore backup feature of Cloud Backup, you are charged for the storage usage of backup vaults.

    • If you use Cloud Backup to back up data from Tablestore instances, you are charged for the usage of backup vaults. For more information, see Billing methods and billable items.

    • If you restore data to a Tablestore instance, you are charged for the data write throughput. The fees are included into your Tablestore bills. For more information, see Billing overview.

    • Cloud Backup provides a 30-day free trial for each new user of the Tablestore backup feature. After the free trial period ends, you are charged for Tablestore backup based on backup and restore scenarios:

      • Backup: You are charged for Cloud Backup based on the usage of backup vaults. You are not charged for the read traffic of Tablestore.

      • Restoration: You are not charged for Cloud Backup. You are charged for data restoration of Tablestore.

  • A Tablestore instance is created. For more information, see the "Step 2: Create an instance" section in Manage the Wide Column model in the Tablestore console.

Usage notes

  • If you are using this feature for the first time, Cloud Backup automatically creates the AliyunServiceRoleForHbrOtsBackup service-linked role to obtain your Tablestore instances. You can follow the wizard to complete the operation. For more information, see Service-linked roles for Cloud Backup.

  • Cloud Backup automatically reads all the Tablestore instances that you have created in the specified region and displays them on the Tablestore Backup page. You do not need to install a client.

Create a backup plan to periodically back up Tablestore tables

Note

After you create a backup plan, the first backup job performs a full backup and subsequent backup jobs perform incremental backups.

To create a backup plan for a Tablestore instance, perform the following steps:

  1. Log on to the Cloud Backup console.

  2. In the left-side navigation pane, choose Backup > Tablestore Backup.

  3. In the top navigation bar, select a region.

  4. Find the Tablestore instance that you want to back up, and click Back Up in the Actions column.

  5. In the Create Backup Plan panel, configure the parameters and click OK.

    1. Specify a name for the backup plan, select the objects that you want to back up, and then click Next.

      Parameter

      Description

      Plan Name

      Specify a name for the backup plan.

      Database Instance

      Select the objects that you want to back up. You can select one or more tables.

    2. Configure the backup plan and click Next.

      Backup type

      Parameter

      Description

      Full Backup

      Full Backup

      If you turn on Full Backup, Cloud Backup backs up all historical data.

      Backup Frequency

      This parameter is required only if you turn on Full Backup. This parameter specifies the backup cycle. You can perform scheduled backup on a daily, weekly, or monthly basis.

      Run At

      This parameter is required only if you turn on Full Backup. This parameter specifies the start time of the scheduled backup plan. The time is accurate to seconds.

      Time Interval

      This parameter is required only if you set the Backup Frequency parameter to Daily. This parameter specifies the interval between two consecutive backup jobs.

      Backup Week

      This parameter is required only if you set the Backup Frequency parameter to Weekly. This parameter specifies the days of the week to run backup jobs.

      Backup Month

      This parameter is required only if you set the Backup Frequency parameter to Monthly. This parameter specifies the months to run backup jobs.

      Backup Day

      This parameter is required only if you set the Backup Frequency parameter to Monthly. This parameter specifies the dates in the specified months to run backup jobs.

      Incremental Backup

      Incremental Backup

      If you turn on Incremental Backup, Cloud Backup backs up incremental data. Incremental backup requires less time than full backup because the volume of incremental data is smaller than historical data.

      Backup Frequency

      This parameter is required only if you turn on Incremental Backup. This parameter specifies the backup cycle. You can perform scheduled backup on a minutely, hourly, or daily basis.

      Run At

      This parameter is required only if you turn on Incremental Backup and set the Backup Frequency parameter to Daily. This parameter specifies the start time of the scheduled backup plan. The time is accurate to seconds.

      Time Interval

      This parameter is required only if you turn on Incremental Backup. This parameter specifies the interval between two consecutive backup jobs. The interval can be set to 30 minutes, 1 to 24 hours, or 1 to 5 days.

    3. Configure the backup settings.

      Parameter

      Description

      Backup Vault

      Configure the backup vault to which you want to store the backup data. Valid values:

      • Create Vault: If you select this option, specify a name for the backup vault in the Vault Name field. If you do not configure this parameter, a random name is specified.

      • Select Vault: If you select this option, select a backup vault from the Vault Name drop-down list.

      To maximize the redundancy of your backup data, Cloud Backup uses zone-redundant storage (ZRS)-enabled backup vaults by default in regions that support ZRS-enabled backup vaults. For regions that support only locally redundant storage (LRS)-enabled backup vaults, Cloud Backup uses LRS-enabled backup vaults. You do not need to manually select a backup vault type.

      Vault Name

      Enter a name for the backup vault.

      Vault Resource Group

      This parameter is required only if you set the Backup Vault parameter to Create Vault. This parameter specifies the resource group to which the backup vault belongs.

      You can use resource groups to manage resources owned by your Alibaba Cloud account. Resource groups help you simplify the resource and permission management of your Alibaba Cloud account. For more information, see Create a resource group.

      Backup Vault Encryption Method

      This parameter is required only if you set the Backup Vault parameter to Create Vault. This parameter specifies the method that is used to encrypt the data in the backup vault.

      • Cloud Backup-managed (default): You can use the default encryption method of Cloud Backup.

      • KMS: You can use Key Management Service (KMS) to encrypt the data that is stored in the backup vault. If you select this option, you must specify the KMS KeyId parameter.

      Important
      • If you specify a customer master key (CMK) to encrypt your backup data, you cannot change the CMK after the backup vault is created.

      • To use KMS to encrypt the data in the backup vault, you must create a CMK in the KMS console. For more information, see Create a CMK.

      Retention Period

      Specify the retention period of the backup data. Default value: 2 years. Unit: days, weeks, months, or years.

      Enable Bandwidth Throttling

      To ensure business continuity, you can limit the bandwidth that is used for data backup during peak hours. If you enable bandwidth throttling, you must set the Time Range (Hour) and Max Bandwidth (MB) parameters based on your business requirements and then click Add.

    After the backup plan is created for the Tablestore instance, Cloud Backup runs backup jobs based on the specified start time, end time, and backup interval. You can view the created backup plan on the Backup Plans tab.备份计划

Backup is successful

When the backup execution time is reached, Cloud Backup runs a backup job. If the Status of the backup job is Completed, the backup job is completed.image.png

Cross-region backup

To prevent regional disasters from affecting business continuity, Cloud Backup allows you to create a remote mirror vault for a general-purpose backup vault. Data in the backup vault is automatically replicated to the mirror vault across regions for geo-redundancy. You can create a remote mirror vault for a backup vault that stores the backup data of a Tablestore instance. For more information, see Back up data across regions.

You can also create mirror vaults for general-purpose backup vaults that you create by using the following features: ECS file backup, SAP HANA backup, OSS backup, Apsara File Storage NAS backup, on-premises NAS backup, and on-premises file backup. In addition, you can use enterprise-class features such as cross-account backup and KMS-based encryption.

Troubleshooting

If the Status of the backup plan or backup job is abnormal, you can resolve the issue based on the following instructions.

  • Status of the backup job: Failed

    Modify and confirm the configurations as prompted.

  • Instance Status of the Tablestore instance: Released

    The Tablestore instance has been deleted.

    • If the Tablestore instance is deleted as expected, ignore the backup job status. To prevent additional backup storage fees, we recommend that you perform the following operation to delete the related storage vault: Click Storage Vaults in the left-side navigation pane, and find and delete the storage vault.

    • If the Tablestore instance is deleted unexpectedly, perform the following operation to restore the Tablestore instance: Create a Tablestore instance in the corresponding region and use the Tablestore instance as the restoration destination to restore the Tablestore instance. For more information, see Restore Tablestore tables.image.png

  • Plan Status of the backup plan: Disabled

    The backup plan has been suspended. After the backup plan is suspended, Cloud Backup does not back up data from the Tablestore instance. We recommend that you resume the backup plan at your earliest opportunity.

Related operations

The following table describes the operations that you can perform after you create a backup plan.

Operation

Description

Plan Status

After the backup plan is created, the switch in the Plan Status column is turned on by default. To pause the backup plan, turn off the switch in the Plan Status column.

Edit

If the backup plan does not meet your business requirements, you can click Edit in the Actions column to change the settings of the backup plan.

Perform Full Backup Now

To perform full backup immediately, choose More > Perform Full Backup Now in the Actions column.

Perform Incremental Backup Now

To perform incremental backup immediately, choose More > Perform Incremental Backup Now in the Actions column.

Alert Settings

To specify an alert policy for the backup plan, choose More > Alert Settings in the Actions column. You can specify one of the following alert policies:

  • Disabled: No alert notifications are sent.

  • Same as Backup Vault: The alert policy of the backup plan is the same as the alert policy of the backup vault.

  • Notify Alibaba Cloud Account: The Cloud Backup client sends alert notifications to the owner of the Alibaba Cloud account by using emails.

  • Custom: If you select this option, you must select one or more alert contacts or alert contact groups. If an alert is triggered, the Cloud Backup client sends alert notifications to the selected alert contacts or alert contact groups.

For more information about how to create alert contacts and alert contact groups, see Manage alert contacts.

Delete

To delete the backup plan, choose More > Delete in the Actions column. After you delete the backup plan, Cloud Backup no longer runs backup jobs for the backup plan but retains the backup data.

What to do next

Restore Tablestore tables

References