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
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
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
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 ;-)
Cheers,
___
Bacula-use
On 2020-04-06 09:41, Richard Laysell wrote:
>
> Hello,
>
> I would like to run a copy job immediately after a set of disk backups
> has completed, but this seems to not work as I expect.
>
> I am scheduling the jobs as follows
>
> Client1 - Disk backup - Priority 10
> Client2 - Disk backup - Pr
Hello Richard
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
Regards,
--
MSc Heitor Faria
CEO Bacula LatAm
mobile1: + 1 909 655-8971
mobile2: + 55 61 98268-4220
América Latina
[ http://ba
