Re: adding a CIFS-share as autochanger
"Stefan G. Weichinger via Bacula-users" <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Message-ID | <[email protected]> |
Am 03.02.25 um 15:05 schrieb Marcin Haba: > On Mon, 3 Feb 2025 at 13:45, Stefan G. Weichinger via Bacula-users > <[email protected]> wrote: >> --- is that correct? >> >> If I then go to that host-API page I try to import the settings but >> somehow I never get the slots displayed in bacularis etc >> >> Something is missing and I lost track here. >> >> Pls advise ... thanks a lot ... > > Hello Stefan, > > The manage autochanger features in Bacularis are used for the SCSI changers. > > Your autochanger configuration is the Bacula virtual disk changer that > is not displayed on the manage autochanger tab. > > To use the autochanger on CIFS share, that will be possible to use > with this extended Bacularis autochanger support, you could use VTL > software that emulates tape devices on the SCSI bus. It can be > realized for example by mhVTL virtual tape library that you can find > here: > > https://github.com/markh794/mhvtl So do I *need* that to use CIFS as Storage? I don't use that for my local installation where I use virtual disks local to the bacula-sd ... I'd assume that as soon as I mount the share via fstab it would be simply the same behavior ... Sure, I don't see these tapes in the "manage autochanger tab" ... but it doesn't matter, I just didn't remember correctly. My understanding/plan: * setup fstab with cifs-UNC-path and creds * let bacula-user mount that * add that mount-command to the storage def proceed from there ;-) So I can completly skip that Autochanger-term in this case (maybe) ?