 |
Bareos2.png (45,746 bytes) |
|
|
This configuration worked for several years without problems. |
|
|
From which version did you upgrade? From 22? |
|
|
Thanks for the report. We have been able to reproduce the mis-behavior. |
|
|
Upgraded from 22 to 23. Thanks |
|
|
I can already reproduce the issue in a test-case and I even found out why it happens. Starting with Bareos 23 you will get a confirmation dialog when doing "purge volume=XYZ" and for some strange reason purge oldest volume uses the same code path but, of course, doesn't confirm the operation so it is canceled. Sorry for that! |
|
|
See https://github.com/bareos/bareos/pull/1628 However, that's for the yet-to-be Bareos 24, so it needs to be backported first. It also waits for review and other qa before moving forward. |
|
|
Experimental packages are ready: https://download.bareos.org/experimental/PR-1628/ It should be possible to downgrade to Bareos 23 again later when the fix is available in Bareos 23. |
|
|
Fix is available in 23.0.0~pre1334.639dd301d Upgrading to the latest build in current should solve the issue. |
|
|
Hi, thanks for the quick reaction. Sadly it is not fixed. I installed 23.0.0~pre1334.639dd301d on server & client. Made a pool small enough to test the purging. I will try to add a screenshot after reopening. |
|
|
Bareos-Test.PNG (49,550 bytes) |
|
|
Did you restart the sd and the dir after the upgrade ? |
|
|
Yes, every affected server got a restart. |
|
|
Could you share your pool-configuration? As you can see in the pull-request we have a test-case that reproduced your issue and with the patch applied the purging works fine. So maybe there's something else in your pool configuration that we haven't considered? |
|
|
Pool { Name = Location-Diff Pool Type = Backup Recycle = yes AutoPrune = yes Volume Retention = 180 days Maximum Volume Bytes = 10 G Maximum Volumes = 120 Label Format = "Location-Differential-" Purge Oldest Volume = yes } Hope it helps. |
|
|
Hmm. We have pretty much the same configuration for the test (i.e. different names and limits, but essential identical). Did you start the job manually (i.e. in bconsole with the run command) or was it scheduled? While that should not make a difference, I have no idea why this shouldn't work for you. Could you also please triple-check that "status dir" reports a recent enough version that contains the fix? |
|
|
Sorry, my fault. I checked the version with "apt show bareos-director", which showed the new version, but that was not the installed version. WebUI and bconsole showed the old verison. Updating the director fixed the problem. Thanks for your quick reaction. |
|
|
Thanks for the feedback. |
- Anonymous
