Hi, Oddly, jobs run sequentially as follows rather than duplicates being cancelled:
Running Jobs: Console connected at 29-Mar-20 12:36 JobId Type Level Files Bytes Name Status ====================================================================== 70172 Back Diff 120 36.70 M Backup-pc is running 70173 Back Incr 0 0 Backup--pc is waiting on max Job jobs ==== Are there any pointers to trace why the duplicate job 70173 is not cancelled? The job is configured with: Allow Duplicate Jobs = no Cancel Queued Duplicates = yes Cancel Lower Level Duplicates = yes The file daemon on the PC is default: Maximum Concurrent Jobs = 10 The storage daemon: Maximum Concurrent Jobs = 20 The client: Maximum Concurrent Jobs = 10 The director: Maximum Concurrent Jobs = 6 Versions: Director: 7.4.4 (202Sep16) PC: 7.4.4 (28Sep16) Microsoft Professional (build 9200), 64-bit,Cross-compile,Win64 Director and storage server are same: running Debian old stable PC: Windows 10 Huge thanks Bernie _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
