Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
111578: backupccl: pause scheduled backup if resumed on different cluster r=dt a=msbutler Previously, after cluster restore or c2c cutover, a backed up/ replicated backup schedule would begin executing on the new cluster. If the backup / source cluster was still available and executing the schedule, then the two schedules would compete to run, as outlined in #108028. This patch prevents this poor UX by pausing the backup schedule if the schedule realizes it is running on a new cluster. It is then up to the user to resume backups on the new cluster and prevent the backup collision problem. Fixes #108028 Release note (sql change): if a scheduled backup resumes on a new cluster (e.g. after C2C cutover or a tenant restore), the backup schedule will pause. The user may resume the schedule without changing it, but should take special care to ensure no other schedule is backing up to the same collection. The user may also want to cancel the paused schedule and start a new one. Co-authored-by: Michael Butler <butler@cockroachlabs.com>
- Loading branch information
Showing
3 changed files
with
127 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters