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 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. :) This is with the Community version 13.0.2: *ver bacula-dir Version: 13.0.2 (18 February 2023) ... I also checked the Enterprise 16.0.5 and it is the same. Hope this helps. Bill -- Bill Arlofski w...@protonmail.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
