>>>>> On Thu, 6 Sep 2018 09:40:31 +0100, Adam Weremczuk said:
>
> On 05/09/18 10:45, Jérôme Blion wrote:
>
> >> Also, to my surprise, I've just received this message:
> >>
> >> 05-Sep 09:24 backup_dir JobId 0: Max configured use duration=172,800
> >> sec. exceeded. Marking Volume "LTO-M20120606A" as Used.
> >> 05-Sep 09:24 backup_dir JobId 0: There are no more Jobs associated
> >> with Volume "LTO-M20130703A". Marking it purged.
> >> 05-Sep 09:24 backup_dir JobId 0: Recycled volume "LTO-M20130703A"
> >>
> >> I haven't made any config changes, just did a couple of listings and
> >> attempted one restore which I aborted.
> >>
> >> Weird...
> >
> > Check Volume Use Duration in your setup.
> >
> This is all I've found:
>
> Pool {
> Name = lto_archive_pool
> Pool Type = Backup
> Storage = backup_sd_lto
> AutoPrune = yes
> Recycle = no
> Volume Retention = 10 years
> Volume Use Duration = 2 days
> }
>
> So 2 days = 172,800 seconds as expected.
>
> What still puzzles me is why Bacula decided to notify about some ancient
> volumes.
> All I executed was a couple of listing commands and one (subsequently
> aborted) restore request from 2016.
>
> The 3 messages above are not logged in Bacula log so I'm unable to
> examine sequence of events leading to it.
> It doesn't seem important but I'm curious.
The "status dir" and "list nextvol" commands can trigger this.
__Martin
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
