Am 06.04.20 um 21:43 schrieb Phil Stracchino: > On 2020-04-06 14:52, Pierre Bernhardt wrote: >> Hi, >> >> schedule your jobs with prio 10 for parallel running. >> schedule a job which starts the copy job with prio >= 11 so it runs after >> all prio 10 jobs has been finished which start the copy job. >> >> Hope it will work as expected ;-) > > > No, this will not work. The execution parameters for a Copy job — > including which jobs it is to copy — are evaluated not at the time the > job actually begins to run, but when it is queued to run, and running > jobs which have not yet completed will not be considered for copying. > The way the selection code currently works, you can schedule and queue a > Copy job only after all of the jobs you want it to copy have completed. You havn't understand me:
The prio 11 job should be scheduled 1 min. after the prio 10 jobs and if start it should start *the new job* by executing the target copy job. This shoiuld prevent the problem. In short, the prio 11 job is only a job which starts the copy job like here: >> Maybe you can deploy an After Job script that can start the copy of the >> original backup job after a few seconds: >> >> run job=copy_job jobid=xx yes | bconsole Cheers, Pierre _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
