Skip to content

Synchronize gpbackup history with the standby coordinator. - #111

Draft
woblerr wants to merge 15 commits into
apache:mainfrom
woblerr:sync_standby
Draft

Synchronize gpbackup history with the standby coordinator.#111
woblerr wants to merge 15 commits into
apache:mainfrom
woblerr:sync_standby

Conversation

@woblerr

@woblerr woblerr commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator

closes: #90

gpbackup_history.db is stored on the active primary coordinator and is not automatically available on the standby. After a failover, the promoted coordinator may have missing or outdated backup history, which affects backup discovery and management.

This change keeps the cluster history database synchronized with an available standby coordinator:

  • gpbackup automatically synchronizes history after a successful backup.
  • gpBackMan automatically synchronizes history after commands that delete backups or clean history.
  • The new gpbackman history-sync command allows synchronization to be started manually.
  • Automatic synchronization is best-effort: failures are reported as warnings and do not change the result of a successful primary command.
  • Automatic synchronization can be disabled with --no-history-sync-standby.

Only gpbackup_history.db is synchronized. Backup data, reports, and other backup artifacts are not included.

Unit and end-to-end coverage were added, and the related user documentation was updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[feature] Sync gpbackup_history.db to standby coordinator after backup.

1 participant