On 7/15/25 09:57, Leandro Saldivar via Bacula-users wrote:
Hi all,
I have a client with ~2TB of data. A full backup job takes about 15
hours. Once the backup finishes, a Copy Job is triggered (Selection
Type = PoolUncopiedJobs) to replicate the volume to a remote Storage
Daemon — which takes another 15 hours per volume in the best-case
scenario. Finally, for each backup, I run a Restore job on a replica
server (same client setup), which adds yet another 15 hours.
The trivial approach to parallelize these jobs (Backup, Copy, Restore)
has been to define a separate Storage + Device pair for each Job. The
only difference between them is the Name. All Devices share the same
Archive Device path — which I'm unsure is a good practice.
I don't believe it is possible to parallelize the Backup job with the
Copy or Restore. The Backup job has the volume(s) opened for writing, so
reading by any other job is not likely allowed until the backup job
completes. After all, the Backup job could fail at any time prior to
completion.
It should be possible to run the Copy and Restore jobs in parallel, once
the Backup job completes, if they are started together with the same
priority and the volume is loaded into a Device that allows concurrent jobs.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
