I can second the 'copy job' route---it's great for disk-to-disk-to-tape
scenarios and means the data transfer is only between SDs.
Just use console command "list jobs copies" to see their IDs.
The manual's description of the "Copy" type is pretty good:
https://www.bacula.org/13.0.x-manuals/en/
On 5/18/23 18:37, Chris Wilkinson wrote:
I'm not sure I'm getting the motivation for using a copy job in
preference to a duplicate job to a second SD. This would also create a
second backup. The only reason I can think of is that a duplicate job
might be different if the files changed in betwee
I'm not sure I'm getting the motivation for using a copy job in preference
to a duplicate job to a second SD. This would also create a second backup.
The only reason I can think of is that a duplicate job might be different
if the files changed in between. That shouldn't be an issue.
I read that a
Thank you Bill, a comprehensive reply as always 🙏. I'll need to study this
some more.
-Chris-
On Thu, 18 May 2023, 16:45 Bill Arlofski via Bacula-users, <
bacula-users@lists.sourceforge.net> wrote:
> On 5/18/23 08:07, Chris Wilkinson wrote:
> > I have not used a copy job before so I thought I wo
On 5/18/23 08:07, Chris Wilkinson wrote:
I have not used a copy job before so I thought I would try one. I used Baculum
v11 to set one up that copies a job from a
local USB drive to a NAS. The setup was straightforward. I created a new pool
to receive the copy, defined the source and
destinatio
I have not used a copy job before so I thought I would try one. I used
Baculum v11 to set one up that copies a job from a local USB drive to a
NAS. The setup was straightforward. I created a new pool to receive the
copy, defined the source and destination job, pool and SD/storage. This
worked just
