Thanks Bill, see below... > On 19. Apr 2023, at 22:05, Bill Arlofski <w...@protonmail.com> wrote: > > I just checked and I see that my memory was working correctly this morning... > >>> I will ask my colleagues if they remember this issue in the Enterprise >>> version and if it was address/modified/fixed. >>> >>> Be right back. :) >> >> OK waiting :) > > There was a ticket/bug where a customer had reported this same issue where > the truncate command always used the first Drive > device in the disk Autochanger, but this has since been addressed.
In what version of Bacula has it been fixed? It is still a problem in 11.0.6. At least truncate doesn’t choose an unoccupied drive, you have to explicitly choose one manually. > In bconsole, just type `truncate` and hit tab a few times to see what the > options are: > > *truncate > allpools drive= mediatype= pool= storage= volume= > > > Notice `drive=xxx` can be specified. I think you will need to specify > `DriveIndex=xxxx` (starting at 0) for each drive > device in the Autochanger too. If not for this reason, I am 100% sure there > is another reason I had come across and had to > prove to my colleagues several years back. :) yes, with this it does work. Thanks for your help! _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
