-
Bug
-
Resolution: Low Engagement
-
Low
-
5.0.1, 5.9.3
-
11
-
Severity 2 - Major
-
2
-
Currently, Bamboo does not stop the builds or wait then to finish in order to start a Scheduled Backup.
This may cause backup inconsistencies since new data is created in the DB while it is being flushed into the backup zip.
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
[BAM-8233] Wait all builds to finish before starting a Scheduled Backup
Scheduled Backup doesn't pause the server by design. I think it was a tradeoff between
- completing backup in the middle of the build
- not running the backup on scheduled time (because of long running builds)
We might want to solve it by defining a timeout for pausing the server before running Scheduled Backup.
This issue seems to be back in Bamboo 5.0.1.
1. I created two plans and scheduled them to run at 5:50 PM and added a task with "sleep 10d".
2. Scheduled back up is running at 5:55 PM.
3. Though no back up files get stored under the back up folder, navigating to a different page in the UI shows the warning that an export is running.
4. The "Wait for jobs to complete" checkbox is selected.
Please check the attached screenshots.
If Bamboo should wait until the builds are complete, why do we get the export/back up warning?
This causes running builds to fail, for example on artifact upload.
Should be fixed
Adam Myatt
added a comment - Agreed, a useful feature. However you may want a checkbox option for the admin to specify whether they want scheduled backup to occur regardless of builds, or to wait for all builds to finish.
Adam Myatt
added a comment - Agreed, a useful feature. However you may want a checkbox option for the admin to specify whether they want scheduled backup to occur regardless of builds, or to wait for all builds to finish.
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.
Kind regards,
Bamboo Data Center