Help Center/ GaussDB/ User Guide/ Data Backup/ Backup Execution/ Configuring an Automated Backup Policy for GaussDB Tables
Updated on 2025-09-05 GMT+08:00

Configuring an Automated Backup Policy for GaussDB Tables

Scenarios

When you create a GaussDB instance, the table-level automated backup policy is disabled by default. After your instance is created, no table-level full backup task will be triggered. You can modify the automated backup policy for tables as needed. If such a policy is configured, GaussDB backs up data of specified tables based on the automated backup policy you specified.

Precautions

  • After an instance-level restoration is complete, the databases or tables configured in the table-level automated backup policy may no longer exist. In this case, you need to configure the table-level automated backup policy again.
  • To ensure that data can be restored to a point in time, the latest full backup that exceeds the backup retention period will not be deleted immediately. For example, if Backup Cycle is set to All and Retention Period to one day and backup 1 is generated on November 1, this table backup will not be deleted on November 2 when backup 2 is generated, but will be deleted on November 3 when backup 3 is generated.
  • Tables in the postgres, template0, template1, templatem, templatea, and templatepdb system databases cannot be backed up using the table-level backup method.
  • Tables in system schemas (for example, public) cannot be backed up using the table-level backup method.
  • Tables in M-compatible databases cannot be backed up using the table-level backup method.
  • A maximum of 100 databases or tables can be restored at the same time. If there are more than 100 databases or tables, you are advised to use instance-level backup and restoration.
  • Table-level restoration does not support segment-page tables, column-store tables, tables containing user-defined types, synonym tables, temporary tables (including global tables), encrypted tables, TDE-enabled tables, unlogged tables, compressed tables, tables of private users, and tables of ledger databases.
  • Table-level backup is unavailable to single-node instances.
  • If the name of a table, schema, or database to be backed up is changed, you need to reconfigure the table-level backup policy.
  • Backups are saved as packages in OBS buckets to ensure data confidentiality and durability. Since backing up data affects database read and write performance, you are advised to perform automated backups for tables during off-peak hours.
  • If there is a new table available for backup, the new table will be backed up during the next scheduled full or differential backup.
  • If a table covered by the table-level backup policy is deleted, modify the policy immediately to remove that table. Otherwise, the table-level backup will keep failing.
  • To disable the table-level differential backup policy, submit a service ticket.

Billing

Backups are saved as packages in OBS buckets. For the billing details, see How Is GaussDB Backup Data Charged?

Modifying an Automated Backup Policy for Tables

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click in the upper left corner of the page and choose Databases > GaussDB.
  4. On the Instances page, click the name of the target instance to go to the Basic Information page.
  5. In the navigation pane on the left, choose Backups. On the displayed page, choose Full Backups > Table Backup. Click Modify Backup Policy.
  6. Configure parameters.

    Table 1 Backup policies

    Backup Policy

    Parameter

    Description

    Full Backup Policy

    Retention Period

    Number of days that your automated backups can be retained. Increasing the retention period will improve data reliability. The default value is 7.

    If you shorten the retention period, the new backup policy will be applied for all backup files. The backup files that have expired will be deleted.

    Backups can be retained for 1 to 732 days. To extend the retention period, submit a service ticket. Automated backups can be retained for up to 2,562 days.

    Time Window

    A one-hour period the backup will be scheduled within 24 hours, such as 01:00-02:00 or 12:00-13:00. To minimize the potential impact on services, set the time window to an off-peak hour.

    Backup Cycle

    One or more days from Monday to Sunday when a backup task will be triggered. By default, all options are selected. Select at least one day as required.

    Differential Backup Policy

    Backup Cycle

    Interval at which table-level differential backup is performed. The default cycle is 30 minutes.

  7. Click Modify Backup Policy.