Am 18.08.25 um 20:23 schrieb Rob Gerber:
I found something.
Your autochanger does not reference any of the 'drive' devices that
should be under its management.
oh
Additionally, your 'drive' device 'filestorage' is set to 'readonly =
yes'. This is only good if you want to reserve a drive for restores or
verify jobs or something like that. Will not work for backups.
Don't ask me where *that* flag came from! no clue ... thanks
See this example from my synology-based file changer setup, in bacula
15.0.2. I have multiple drive devices under one autochanger. Pretend
that this is a physical tape library, with multiple tape drives. That
might help it make more sense. Devices 'Synology-Local-001' through 005
are read/write devices. Device Synology-Local-006 is a readonly device,
because it is intended to be used only with restores. This way a drive
is always available for a restore when you want to do one.
At this point, your Storage {} resource from the bacula-dir is very much
like mine from my synology system. I think it's probably good. It should
refer to the autochanger name, not the individual drive devices under
the autochanger.
I can provide a full redacted dump of my configs if that would help.
Thanks a lot for your example, I try to mimic it for 20 minutes now.
You know, in my case it's one directory on the filesystem, containing
files as Volumes (?)
I looked up backups of my working config and took the parts from there,
adjusted a job: same errors. Oh my.
I remember some issue where editing "Autochanger = somename" to "=yes"
and that solved it. I am not sure if this is the same situation right now.
I will look up a server config at a customer where I haven't touched
things for months.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
