>>>>> On Fri, 22 Sep 2023 12:23:29 +0200, Marco Gaiarin said:
>
> I've not found info on these section on (current) 9.4 docs; i've followed:
>
> https://www.bacula.org/9.4.x-manuals/en/main/Migration_Copy.html
>
>
> ...
>
> Ah. You defined TWO device, with different media type; i've not found
> anywhere notes about the need of different devices/mediatype; seems also a
> single pool can be used...
It is mentioned in the bullet point "Bacula currently does only minimal
Storage conflict resolution" of the 9.4 manual page you listed above.
You definitely need two devices (one for reading, one for writing). It
usually works if the media types are the same, but I've had one case of a
deadlock in a Copy job.
If you have one media type, then you can define the two devices as a virtual
autochanger like this in bacula-sd.conf:
#
# Virtual autochanger to allow multiple volumes to be used at once
#
Autochanger {
Name = FileStorage
Device = FileStorage-Dev1, FileStorage-Dev2
Changer Command = ""
Changer Device = /dev/null
}
Device {
Name = FileStorage-Dev1
Media Type = File
Archive Device = /var/bacula/volumes
LabelMedia = yes;
Random Access = Yes;
AutomaticMount = yes;
RemovableMedia = no;
AlwaysOpen = no;
}
Device {
Name = FileStorage-Dev2
Media Type = File
Archive Device = /var/bacula/volumes
LabelMedia = yes;
Random Access = Yes;
AutomaticMount = yes;
RemovableMedia = no;
AlwaysOpen = no;
}
and then just have a single storage definition in bacula-dir.conf:
Storage {
Name = backupserver1-File
Address = ...
SDPort = 9103
Password = "..."
Device = FileStorage
Media Type = File
Maximum Concurrent Jobs = 2
}
__Martin
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
