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 at the end of the Changer Command directive and
it causes that bsdjson prints wrong value:
Autochanger {
Name = QUANTUM-LTO-Lib1
Description = "Quantum SuperLoader 3"
Device = "IBMLTO7"
Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a"
Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d\"
<===== HERE IT IS
# Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a" # Change 5
(line to remove)
}
Please change this line:
Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d\"
into the following line:
Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d"
and the redundant Changer Command = should disappear.
Best regards,
Marcin Haba (gani)
On Fri, 16 Apr 2021 at 20:55, Hector Barrera <hector.barr...@imncreative.com>
wrote:
> 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" of your storage device -> Configure Autochanger
> You'll see in the ChangerCommand field this:
> /opt/bacula/scripts/mtx-changer %c %o %S %a %d" *Changer Device = *
> The "Changer Device =" part does not exist in the bacula-sd.conf file,
> this is being added by Baculum.
>
> The same happens when you add the Autochanger in the Baculum API after you
> click "Copy from Bacula SD config:"
> If you don't remove the "Changer Device =", it won't let you save.
> Do you want me to open a Bug report for this?
>
> Cheers!
>
> Hector Barrera.
>
> On Thu, Apr 15, 2021 at 7:23 PM Marcin Haba <ganius...@gmail.com> wrote:
>
>> 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" # Change 1
>> Description = "Quantum SuperLoader 3 Tape Library" # Change 2
>> Address = "bacula02.imn.ad"
>> Password = "XXXXXXXXXX"
>> Device = "QUANTUM-LTO-Lib1" # Change 3
>> MediaType = "LTO-7"
>> Autochanger = yes # Change 4
>> MaximumConcurrentJobs = 1
>> }
>> -------------------------------
>>
>> bacula-sd.conf
>>
>> Autochanger {
>> Name = QUANTUM-LTO-Lib1
>> Description = "Quantum SuperLoader 3"
>> Device = "IBMLTO7"
>> Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a"
>> Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d\"
>> # Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a" # Change 5
>> (line to remove)
>> }
>>
>> Please note that after doing Change 1 (IBMLTO7 => QUANTUM-LTO-changer1 in
>> Storage resource) you will need to update all jobs that were using this
>> Storage to use the new name. I mean changing in Job and JobDefs (and Pool)
>> resources:
>>
>> Storage = IBMLTO7
>>
>> into:
>>
>> Storage = QUANTUM-LTO-changer1
>>
>> After doing it and reloading daemons configuration, please create
>> Autochanger configuration in Baculum API by selecting "Copy from Bacula SD
>> config" drop down list item "QUANTUM-LTO-Lib1". Auto-filled values will be
>> correct and will not cause any name's collision.
>>
>> Best regards,
>> Marcin Haba (gani)
>>
>> On Fri, 16 Apr 2021 at 00:27, Hector Barrera <
>> hector.barr...@imncreative.com> wrote:
>>
>>> 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"
>>> Autochanger = "File1"
>>> MaximumConcurrentJobs = 10
>>> }
>>> Storage {
>>> Name = "IBMLTO7"
>>> Description = "IBM LTO7 Inside Quantum SuperLoader 3 Tape Library"
>>> Address = "bacula02.imn.ad"
>>> Password = "XXXXXXXXXX"
>>> Device = "IBMLTO7"
>>> MediaType = "LTO-7"
>>> Autochanger = "IBMLTO7"
>>> MaximumConcurrentJobs = 1
>>> }
>>> -------------------------------
>>>
>>> bacula-sd.conf
>>>
>>> Device {
>>> Name = "FileChgr1-Dev1"
>>> MediaType = "File1"
>>> ArchiveDevice = "/home/bacula/backups"
>>> RemovableMedia = no
>>> RandomAccess = yes
>>> AutomaticMount = yes
>>> LabelMedia = yes
>>> AlwaysOpen = no
>>> MaximumConcurrentJobs = 5
>>> }
>>> Device {
>>> Name = "IBMLTO7"
>>> Description = "IBM LTO7 in Library 1 Drive 1"
>>> MediaType = "LTO-7"
>>> DeviceType = "Tape"
>>> ArchiveDevice = "/dev/tape/by-id/scsi-35005076312156b6c-nst"
>>> RemovableMedia = yes
>>> RandomAccess = no
>>> AutomaticMount = yes
>>> LabelMedia = yes
>>> AlwaysOpen = yes
>>> Autochanger = yes
>>> AutoSelect = yes
>>> ChangerDevice = "/dev/tape/by-id/scsi-3500e09efff10c86a"
>>> AlertCommand = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
>>> MaximumBlockSize = 512K
>>> MaximumFileSize = 20000000000
>>> Spool Directory = "/home/bacula/spool"
>>> MaximumSpoolSize = 2000000000
>>> }
>>> Autochanger {
>>> Name = "FileChgr1"
>>> Device = "FileChgr1-Dev1"
>>> ChangerDevice = "/dev/null"
>>> ChangerCommand = ""
>>> }
>>> Autochanger {
>>> Name = QUANTUM-LTO-Lib1
>>> Description = "Quantum SuperLoader 3"
>>> Device = "IBMLTO7"
>>> Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a"
>>> Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d\"
>>> Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a"
>>> }
>>>
>>> This is the only way I got the LTO7 IBM Drive inside the Quantum
>>> Superloader3 to work and change tapes automatically.
>>>
>>> What should I change?
>>>
>>> Hector B.
>>>
>>>
>>> On Thu, Apr 15, 2021 at 1:35 PM Marcin Haba <ganius...@gmail.com> wrote:
>>>
>>>> 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-LTO-Lib1? If yes, then why you
>>>> didn't add 'QUANTUM-LTO-Lib1'it to the Director configuration as a
>>>> storage/autochanger?
>>>>
>>>> To solve the problem with autochanger setting, I propose to look to
>>>> bacula-dir.conf for Autochanger configuration that you would like to
>>>> manage, for example:
>>>>
>>>> Storage {
>>>> Name = "AAA"
>>>> Device = "BBB"
>>>> Autochanger = "yes"
>>>> ...
>>>> ...
>>>> }
>>>>
>>>> and use name BBB as Autochanger name in Baculum API autochanger
>>>> configuration, which basically is almost the same as you choose the
>>>> Autochanger name from the drop down list with label "Copy from Bacula SD
>>>> config".
>>>>
>>>> Best regards,
>>>> Marcin Haba (gani)
>>>>
>>>> On Thu, 15 Apr 2021 at 21:55, Hector Barrera <
>>>> hector.barr...@imncreative.com> wrote:
>>>>
>>>>> Thanks Marcin.
>>>>>
>>>>> The bconsole output is:
>>>>> *show storage=IBMLTO7
>>>>> Autochanger: name=IBMLTO7 address=bacula02.imn.ad SDport=9103
>>>>> MaxJobs=5 NumJobs=0
>>>>> DeviceName=IBMLTO7 MediaType=LTO-7 StorageId=6 Autochanger=1
>>>>> AC group=6 ShareStore=*none*
>>>>>
>>>>> So the name of the Device should be *IBMLTO7 *
>>>>>
>>>>> When I try to change the Autochanger on the API side, I get an error
>>>>> message: "Autochanger with the given name already exists" See attached
>>>>> picture.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Apr 15, 2021 at 11:31 AM Marcin Haba <ganius...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> 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 is
>>>>>> "QUANTUM-LTO-SuperLoader3" ?
>>>>>>
>>>>>> If it isn't then please edit Autochanger config on the Baculum API
>>>>>> side and please set in place "QUANTUM-LTO-SuperLoader3" a value that you
>>>>>> have in the 'DeviceName'. In other words the Autochanger name from
>>>>>> bacula-sd.conf has to be the same as the Autochanger name defined in the
>>>>>> Baculum API.
>>>>>>
>>>>>> Best regards,
>>>>>> Marcin Haba (gani)
>>>>>>
>>>>>> On Thu, 15 Apr 2021 at 20:04, Hector Barrera <
>>>>>> hector.barr...@imncreative.com> wrote:
>>>>>>
>>>>>>> Thank you MArcin for replying back about this.
>>>>>>>
>>>>>>> Yes, I did follow the video, this is how I configured the
>>>>>>> autochanger on the Baculum API.
>>>>>>> The username on the API and WEB are the same.
>>>>>>>
>>>>>>> I also ran the test in the API settings, please see attached
>>>>>>> pictures.
>>>>>>>
>>>>>>> What logs should I send you?
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> Hector Barrera.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Apr 14, 2021 at 6:47 PM Marcin Haba <ganius...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> 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 autochanger window.
>>>>>>>> There is a button to test. Did this test finish OK on your side?
>>>>>>>>
>>>>>>>> Described problem can also occur if you have the Autochanger
>>>>>>>> configured on one API host but the user, that you are logged in, is
>>>>>>>> assigned (on the Security page) to another API host. For example:
>>>>>>>> Autochanger on API host A, and user logged to API host B.
>>>>>>>>
>>>>>>>> On the last reason we are currently working on. It is a feature that
>>>>>>>> will enable assigning more than one API host to a user.
>>>>>>>>
>>>>>>>> Please let us know if it helped to solve the Autochanger problem. If
>>>>>>>> not, then it can be useful to provide Baculum API and Baculum Web
>>>>>>>> logs.
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> Marcin Haba (gani)
>>>>>>>>
>>>>>>>> On Wed, 14 Apr 2021 at 22:30, Hector Barrera
>>>>>>>> <hector.barr...@imncreative.com> wrote:
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > 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 API interface. I only see the device that I
>>>>>>>> configured via the bacula-sd.conf file.
>>>>>>>> > If I select "Details" on the device that I configured via
>>>>>>>> bacula-sd.conf file, and then click Manage Autochanger, I get this
>>>>>>>> error:
>>>>>>>> > Autochanger management is unavailable. To manage autochanger from
>>>>>>>> here, add it to the API host devices on the API host side.
>>>>>>>> >
>>>>>>>> > Any idea why the Baculum API is not passing the autochanger
>>>>>>>> config to Baculum WEB?
>>>>>>>> >
>>>>>>>> > Please advise.
>>>>>>>> >
>>>>>>>> > --
>>>>>>>> > Hector Barrera | IMN CREATIVE
>>>>>>>> > DIRECTOR OF TECHNOLOGY
>>>>>>>> > 622 West Colorado Street
>>>>>>>> > Glendale, California 91204
>>>>>>>> > O: 818 858 0408
>>>>>>>> > M: 562.413.5151
>>>>>>>> > W: imncreative.com
>>>>>>>> > _______________________________________________
>>>>>>>> > Bacula-users mailing list
>>>>>>>> > Bacula-users@lists.sourceforge.net
>>>>>>>> > https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> "Greater love hath no man than this, that a man lay down his life
>>>>>>>> for
>>>>>>>> his friends." Jesus Christ
>>>>>>>>
>>>>>>>> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje
>>>>>>>> kładzie
>>>>>>>> za przyjaciół swoich." Jezus Chrystus
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> "Greater love hath no man than this, that a man lay down his life for
>>>>>> his friends." Jesus Christ
>>>>>>
>>>>>> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
>>>>>> za przyjaciół swoich." Jezus Chrystus
>>>>>>
>>>>>
>>>>
>>>> --
>>>> "Greater love hath no man than this, that a man lay down his life for
>>>> his friends." Jesus Christ
>>>>
>>>> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
>>>> za przyjaciół swoich." Jezus Chrystus
>>>>
>>>
>>
>> --
>> "Greater love hath no man than this, that a man lay down his life for his
>> friends." Jesus Christ
>>
>> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za
>> przyjaciół swoich." Jezus Chrystus
>>
>
--
"Greater love hath no man than this, that a man lay down his life for his
friends." Jesus Christ
"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za
przyjaciół swoich." Jezus Chrystus
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
