GaussDB(DWS) Backup and Restoration

• Media formats supported

      Data can be backed up to disks, OBS, EISOO, and NetBackup.

• Multiple backup modes

      Full physical backup, differential incremental backup, and cumulative incremental backup are supported.

• No impact on services

      No tables are locked during the backup. SQL and DDL executions are not affected.

• Global consistency

      Backup sets use globally consistent snapshots to ensure the consistency of restored data.

• Fine-grained backup and restoration

      You can restore an entire cluster or just specific schemas. Data can be restored to a new cluster or the original one.

• High security

      Data is encrypted before transmission to prevent leakage.

      gs_dump and gs_restore are logical backup tools. gs_dump is used to export database object metadata to a text file, a custom-format file, a .tar file, or a separate directory. gs_restore is used to import the files generated by gs_dump to the database for restoration.

      GaussDB(DWS) provides Roach to back up and restore large-scale data in real time. Roach regularly synchronizes data from the production cluster to the backup for disaster recovery purposes, as shown in the following figure.

Figure 4-1 Dual-cluster DR using Roach

      In a large cluster, data backup is likely to be interrupted by cluster restart or primary/standby node switchover. Roach supports resumable backups. If a backup gets interrupted, you can resume your backup from where it left off. There is no need to start from scratch.

     Roach can resume progress for:

• Full backup
• Full restoration
• Data transfer via SCP between clusters
• Backup of an old cluster and restoration to a new cluster executed in parallel