Hi everybody, I'm currently using the following config snippet with the intention of preventing new backup jobs from starting while the initial (sometimes very long running) full backup is still ongoing: ``` Allow Duplicate Jobs = no Cancel Lower Level Duplicates = yes Cancel Queued Duplicates = no Cancel Running Duplicates = no ```
This usually works just fine, but the problem is that always-incremental consolidation jobs later on also cause backups to be cancelled, which is not ideal. Does anybody know of a way to prevent duplicate full/incremental backup jobs while ignoring always-incremental consolidation jobs? I don't want the consolidate jobs to cancel/prevent regular backup jobs from starting. Example of an incremental backup (JobId 101657) which was cancelled due to a long ongoing consolidation job (JobId 101090): *list joblog jobid=101657 2024-03-13 22:00:01 bareos-dir JobId 101657: Fatal error: JobId 101090 already running. Duplicate job not allowed. ... *list joblog jobid=101090 ... 2024-03-12 22:12:16 bareos-dir JobId 101090: Start Virtual Backup JobId 101090, Job=... 2024-03-12 22:12:47 bareos-dir JobId 101090: Bootstrap records written to /var/lib/bareos/bareos-dir.restore.294.bsr 2024-03-12 22:12:47 bareos-dir JobId 101090: Consolidating JobIds 95814,100341,97284,98255 containing 598982 files ... Thanks and best regards, Samuel -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/70b53ab4-77b0-4d9c-b0fe-5ac63dd9a89en%40googlegroups.com.
