Re: Copy job troubles
Phil Stracchino <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Organization | Fenian House Publishing |
| Message-ID | <[email protected]> |
On 11/4/25 13:51, Martin Simmons wrote: >>>>>> On Tue, 4 Nov 2025 10:42:19 -0500, Phil Stracchino said: >> >> I'm not convinced that this is what's going on here, because I do the >> same thing (disk to NAS disk array to removable ZFS disk pool on the NAS >> host, both using media type File) and copy jobs to create airgapped >> backup copies Just Work. > > The OP seems to have two separate NAS boxes, each with its own bacula-sd (the > source of the copy jobs) and possibly even a third box running the virtual > autochanger (the target of the copy jobs). > > Does your setup have a single bacula-sd process running on the NAS, configured > with multiple Device or Autochanger clauses in the bacula-sd.conf? The would > be a lot simpler, because there is only one source sd for the copy jobs. Aaah, good point, with multiple SDs it could get confused as to which one it needs to talk to — though I'd have thought that specifying the destination Pool would take care of that. If not, perhaps that's something that should be addressed? In my configuration, I have two Storages on the same host, epsilon3-file and epsilon3-archive, both Media Type = File, with different paths as their Archive Devices, and my Copy jobs run from pool Full-Disk (Storage = epsilon3-file, Next Pool = Full-Archive) to pool Full-Archive (Storage = epsilon3-archive). -- Phil Stracchino Fenian House Publishing [email protected] [email protected] Landline: +1.603.293.8485 Mobile: +1.603.998.6958 _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users