Greetings, so far I don’t yet have a nice solution for the problem described earlied (see attached email).
Since verify jobs can only verify the latest job run with a specific name, and since copy jobs have the same name as the original backup job, the only way to verify both, the backup job AND the copy job seems to be: (1) run backup job “examplejob" (2) run verify job for “examplejob” (3) run copy job for “examplejob” (4) run verify job for “examplejob” It is must happen in this order I guess. If I would switch (2) and (3) both verify jobs would verify the volumes of the copy job, correct? So I need to provide priorities accordingly to the 4 jobs to run in this order? (As I don’t want to create a set of schedules for each of these jobs). Happy to hear about better solutions you are using, J/C > On 4. Sep 2022, at 18:27, Justin Case <jus7inc...@gmail.com> wrote: > > Hi there, > > today I switched to using copy jobs to create the tier 2 backup (instead of > backup jobs from the original source). I realized that the copied job on tier > 2 storage has the exact same name as the job on tier from which it was copied. > > I am now unclear how I can schedule verify jobs for the tier copies. > Previously I used the name of the tier 2 back up to identify the job that > should be verified. Now the tier 2 copy job has the same name as the tier 1 > backup job. How do I discern them when scheduling (I could not use the job > IDs as there are not known when the verify job is scheduled). > > Any ideas how to achieve this? > > Thanks for considering my question, > J/C > > _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
