I can imagine two things that have happened here:
1. you have not run a job targeting that pool after the tape expired.
AFAIC Maximum Use Duration is only evaluated when looking for a volume
to write to. So if you don't write to the pool no expiry will happen.
2. you changed configuration of the pool without updating the volumes
When you change the pool configuration this will apply to new volumes in
that pool or to volumes moved from the Scratch pool into that pool at
the time they're moved to the pool.
All preexisting volumes must be updated with bconsole's 'update volume'
command. If in doubt use the "update all volumes from all pools" option.
After you have done that, re-evaluate case 1 :)
Extra information:
1. you can look at a volume's details using llist volume=<volname>.
2. the expiration algorithm uses (voluseduration < (firstwritten -
now)), so you can calculate yourself if you want to.
Best Regards,
Andreas
Am 27.07.19 um 04:31 schrieb Brock Palen:
--
Andreas Rogge
andrea...@bareos.com
Bareos GmbH & Co. KG Phone:
+49 221-630693-86
http://www.bareos.com
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz