Hi all, I am fiddeling with a problem. I am trying to set things up like mentioned here: https://www.bacula.lat/zimbra-network-edition-backup-with-bacula/?lang=en This means: Bacula (Dir, SD) runs on one server, Zimbra (and bacula-fd) runs on annother server. Backup on Zimbra-Server should be done with Zimbra's native "zmbackup"-tool. When this finishes, Bacula should do it's own backup and after that the native Zimbra Backup should be cleaned up again by zmbackup. For archeiving this, there are those in my Job-Config: Runscript { RunsWhen = "Before" Command = "/etc/bacula/scripts/bacula_zimbra.sh %l" } Runscript { RunsWhen = "After" Command = "/etc/bacula/scripts/bacula_zimbra_delete.sh" This doesn't work unfortunately: Because "RunsOnClient" is used, the Dir can never determine, when zmbackup has finished, so he starts the native Bacula-backup even when zmbackup still runs. Has anybody an idea please how to get out of this? Not using "RunsOnClient" doesn't seem to by an option. Also I have tried several options to catch the status of zmbackup in the scripts, but this wont notify the Dir. Thank you in advance! Bruno
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
