Closed mwang1026 closed 1 year ago
We have marked this issue as stale because it has been inactive for 18 months. If this issue is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 10 days to keep the issue queue tidy. Thank you for your contribution to CockroachDB!
You pause the schedule for your full backup. Your full backups keep failing because of a bug. You decide it's funny to cancel a full backup one day.
It's possible your incremental backup schedule gets longer and longer. We know that as those incremental chains get longer, bad things happen.
We should have a configurable setting that is a multiplier -- if the last full backup is X times older than the full backup frequency, start failing incremental schedules and signal that failure in clear observability for the user. The problem today is people look at
jobs
for their failures, but in this case we'd fail before creating a job. We should think through that UXJira issue: CRDB-9566