Files
cozystack/internal/backupcontroller
Alexey Artamonov 9bd8d12cb8 fix(postgres): hold the WAL archive destination for backups no job tracks
A BackupJob rewrote the shared WAL archive destination while a
cnpg.io/Backup of the Cluster was running if nothing tracked that
Backup through a running BackupJob: one created by hand or by a
ScheduledBackup, or one whose BackupJob was deleted or had already
finished. The base backup then stayed where it started while the WAL
it needs went to the new location, and the backup could not be
restored.

Such a Backup now holds the destination while CloudNativePG executes
it. Only the phases in which CloudNativePG itself starts no other
Backup of the Cluster count, so the hold never outlasts the queue the
operator already imposes: a Backup that waits in pending, or was sent
back to it, starts its base backup over against the destination
current then.

Assisted-by: LLM
Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
2026-11-12 18:44:17 +03:00
..