Hello, pt., 13 gru 2019 o 18:26 Martin Simmons <mar...@lispworks.com> napisał(a):
> Apologies, I was getting frustrated because I didn't see any evidence > (e.g. in > the documentation) that it was designed to work that way. > No problem. :) > Yes, I understand the difference between a design and an implementation. > It > is also useful to note that an implementation can sometimes become the > design > by accident or inertia! > So true... > > No. The priority mechanism is to prohibit concurrent job execution for > jobs > > of different priority. It is not a synchronization mechanism, there is no > > "related situations". > > I have already mentioned a related situation: a VolumeToCatalog verify job, > which must run after the corresponding backup job. The priority can be > used > to enforce this "must run after" requirement, so that makes it a > synchronization mechanism. > I could be used as a sync when you have a single job defined in your config, then you can sync other job to this single job, etc. If you have multiple jobs then it is not a proper sync. It could run as expected but in some edge situations it could fail. > > > It doesn't work for copy jobs because > > > Bacula chooses the jobs to be copied at the scheduled time. > > > > > > > Job priority mechanism works perfectly with copy jobs. Unfortunate you > > expect a different behavior of this mechanism which was never > implemented. > > This is a main issue. > > True -- it all depends on whether it was designed like that or if someone > implemented it like that without considering it. > > I did not designed it, so all I can say here it is a speculation. As Bacula Systems added a special parameter to allow dependent jobs execution then I suspect the current implementation is correct with a design. I think. > > Could you please prepare a patch which implement this behavior in a that > > way? > > I think it is best to wait until the design is agreed, otherwise the patch > will just be rejected. > OK. > > - all you need for your copy job policy with priorities is to create a > job > > which just execute a copy job at the right time > > Yes, but as Phil mentioned, it is difficult to choose the right time. > Bu you can add a script which can do it for you or wait for "dependent job functionality" to be ported to Community. best regards -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
