Hello, pt., 13 gru 2019 o 21:05 Phil Stracchino <ph...@caerllewys.net> napisał(a):
> Evaluating selection queries when queued, which may be many hours ahead > of when it actually runs, almost ensures that when the job finally runs, > it runs with stale and probably-incorrect data. You have to remember that a copy job is in reality a three different jobs: copy control, copy read and copy write. > Radosław, you didn't answer Martin's question: Can you describe a > realistic case where it is ever better for the user that a Copy job > evaluate its selection criteria when it is queued, rather than when it > actually starts? > I show you my case. I run a cyclic copy job every hour and copy all new jobs which are available right now. I never use a priorities. 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
