Great.
I removed the trailing \ (backslash) all good now.
Have a great weekend!
Hector Barrera.
On Fri, Apr 16, 2021 at 12:12 PM Marcin Haba wrote:
> Hello Hector,
>
> Great. Thanks for your positive feedback :-)
>
> For this additional " Changer Device = " string, it is a typo error in
> bac
Hello Hector,
Great. Thanks for your positive feedback :-)
For this additional " Changer Device = " string, it is a typo error in
bacula-sd.conf. In my previous mail, when I sent the autochanger
configuration, I didn't notice that there is a backslash quote character
instead of quote character a
That did it !!!
Thank you so much Marcin for all your help with this.
I'm now able to manage the autoloader magazines from within Baculum itself.
I don't use the Quantum WEB GUI anymore for these tasks.
I did discover a small bug in Baculum though, If you click on Storage ->
Click on "Details" o
Hello Hector,
Many thanks for showing your Bacula configuration. Indeed, it explains why
you experienced the problem with names in Baculum.
I propose to use the following configuration below. I marked changed lines
by "# Change X" marker
bacula-dir.conf
Storage {
Name = "QUANTUM-LTO-changer1"
OK. I believe the problem is how I got the bacula-dir.conf and
bacula-sd.conf files configured.
These are the pertinent parts:
bacula-dir.conf
Storage {
Name = "File1"
SdPort = 9103
Address = "bacula02.imn.ad"
Password = "ZGZjNDMzZTg0OTR"
Device = "FileChgr1"
MediaType = "File1"
Au
Hello Hector,
Thanks for more details. Your tape drive device is already named 'IBMLTO7'
and it causes this collision.
On screenshot, that you sent, I see another autochanger name
"QUANTUM-LTO-Lib1" in storage daemon configuration. Does it mean that you
have two autochangers: IBMLTO7 and QUANTUM-
Hello Hector,
Yes, everything looks correct on the screenshots. Thanks for them. In this
case before looking in logs, I have a question about the autochanger name.
When you run in bconsole the following command:
show storage=IBMLTO7
could you tell me if in received output the 'DeviceName' value
Hello Hector,
At the beginning I would like to invite you to watch a video with the
guide about configuring Autochanger in Baculum:
https://www.youtube.com/watch?v=kPxpDTTD5Mk
Baculum API needs to have access to the Autochanger. You can validate
this access on the Baculum API side in add/edit au
Hello folks,
I just upgraded to Bacula 11.0.1 and Baculum to ver. 11.0.2.1
Everything works, with the exception of being able to control our Quantum
SuperLoader3 autochanger from within the Baculum interface.
When I go to Storage, I don't see the Autochanger that I've configured via
the Baculum
