Hello, Probably I do not help with this subject, but I want to clarify some infos:
pon., 28 wrz 2020 o 18:53 <djosip+n...@linuxpages.net> napisał(a): > > I naively tried to use a separate Messages resource with the Copy > job but that didn't help and the results were the same, probably > because the reports for the copied jobs were handled by bacula-sd > and it simply sent its messages to its default Messages handler on > the bacula-dir. > No, SD does not handle this kind of messages. It is a Director responsibility only. I assume you cannot change the Messages target for the Copied job because it is using a Message resource from the original backup job definition. I could be very wrong about it. I assume the second time that this behavior is on purpose to not distinguish copied jobs from originals. I could be very wrong about it. Does anyone know if it's possible to deal with this problem without > the modifications of the Bacula source? Well, to distinguish copied job from original just after cloning you can use "priorjobid/priorjob" column in catalog "job" table which when "not null" discloses the clone. You can prepare a custom email/smtp handling script to verify if a message concern a clone job. This you can do without changes in Bacula source code. I hope it helps. best regards -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
