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
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
