On 2020-04-07 04:10, Pierre Bernhardt wrote: > 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
Aah, I see what you're saying. The problem here is that your copy-job-running-job needs to know in advance, or extract, the id of the job it is to copy. With that proviso, yes, that seems as though it OUGHT to work. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
