woblerr opened a new issue, #90: URL: https://github.com/apache/cloudberry-backup/issues/90
The `gpbackup_history.db` is only stored on the active primary coordinator. If failover occurs and the standby is promoted to primary, the backup history is lost. The idea is to sync `gpbackup_history.db` to stanby coordinator after performing a backup. After the history DB is updated during backup cleanup (`DoCleanup`), sync it to the standby coordinator using rsync over SSH: * Detect whether the cluster has a standby coordinator. * If standby exists — `rsync` to the corresponding `datadir` on standby coordinator. * If no standby — do nothing. `rsync` is already used in project. The operation should be non-fatal — if it fails, log a warning and don't break the backup. It should be enabled by default, but could be disable by `--no-sync-standby` flag (or similar). Does this approach seem valid and reasonable? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
