Incremental backup in gpbackup on Tanzu Greenplum
search cancel

Incremental backup in gpbackup on Tanzu Greenplum

book

Article ID: 296796

calendar_today

Updated On:

Products

VMware Tanzu Greenplum

Environment

Product Version: 6.20

Resolution

Checklist:
Incremental backup in gpbackup on Tanzu Greenplum

This article answers some common questions about incremental backups using gpbackup and gprestore.

Q:  Will gpbackup store the table modification date in a catalog table?
A:  gpbackup uses modcount function to check which table was modified since the last full backup. For modcount function, please refer to below link:
https://github.com/greenplum-db/gpbackup/blob/3f3a6f02117f99907d01efaa8457522c2e306677/backup/queries_incremental.go

Q: Which kind of table will be included in incremental backup when using gpbackup?
A:  Heap tables are always backed up during incremental backups. AO tables are backed up during incremental backups if they have been modified since the latest backup (either full or incremental).

Q: Is the incremental backup on table level or row level ?
A: Backups and restores are always done on table level. It is not possible to use gpbackup/gprestore to backup or restore particular rows.

A: Does gpbackup include index?
Q: gpbackup generates a "create index" statement in the backup dump file. When restores, index will be created by that statement after the data is restored.