On this page

Show all

Help Center/ GaussDB/ User Guide/ Data Backup/ Backup Execution/ Configuring an Automated Backup Policy for GaussDB Tables

Configuring an Automated Backup Policy for GaussDB Tables

Updated on 2025-02-17 GMT+08:00

View PDF

Scenarios

When you create a GaussDB instance, the table-level automated backup policy is disabled by default. After your instance is created, you can modify the automated backup policy for tables as needed. GaussDB backs up data of specified tables based on the automated backup policy you specified.

Backups are saved as packages in OBS buckets to ensure data confidentiality and durability. Since backing up data affects the database read and write performance, you are advised to perform automated backups for tables during off-peak hours.

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.

Modifying an Automated Backup Policy for Tables

Log in to the management console.
Click in the upper left corner and select a region and project.
Click in the upper left corner of the page and choose Databases > GaussDB.
On the Instances page, click the name of the target instance to go to the Basic Information page.
In the navigation pane on the left, choose Backups. On the displayed page, choose Full Backups > Table Backup. Click Modify Backup Policy.
Configure parameters.
- Full backup policy:
  Specify Retention Period, which indicates the number of days that your automated backups can be retained. Increasing the retention period will improve data reliability. The default value is 7.
  
  Specify Backup Cycle. At least one day must be selected.
  NOTE:
  
  If you shorten the retention period, the new backup policy takes effect for all backup files. The backup files that have expired will be deleted.
  
  The backup retention period is from 1 to 732 days. To extend the retention period, contact customer service. Automated backups can be retained for up to 2,562 days.
  
  The time window is one hour. You are advised to select an off-peak time window for full backups. By default, each day of the week is selected for Backup Cycle. You can change the backup cycle. At least one day must be selected.
  
  After a DB instance is created, a full backup for tables is not triggered. After a table backup policy is configured, full backups and differential backups for tables are performed based on the backup time window and backup cycle specified in the policy. We recommend that you set the full backup time window to off-peak hours.
  
  If a new table needs to be backed up, the new table will be backed up at the next automatic full backup or differential backup.
  
  If a table in the table-level backup policy is deleted, modify the table-level backup policy immediately to delete the deleted table. Otherwise, the table-level backup will always fail.
- Differential backup policy
  You need to select a backup cycle for differential table backups. 30 minutes is used by default.
  
  To disable the table-level differential backup policy, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
Click Modify Backup Policy.