I have run into a problem several times now where one of my backups will stall. When this happens none of my other scheduled backup jobs will run until I either kill the hung job or just restart the Duplicati service.
This is a situation that requires me to be extremely vigilant about checking if backups were successful and manually correcting if one is hung. I’d like to see the software handle this more gracefully so I have 2 questions.
Is there a setting I’m not seeing to set a maximum execution time on a job so it is automatically killed?
Is there a setting to enable multiple jobs to run concurrently?
I wish I had meaningful logs to send but the job logs aren’t interesting and I don’t see anything for the date this hung up in the server logs.
I’m experiencing the same situation on Duplicati 2. Since not a lot has changed since then I’m continuing this conversation. I have many cases that my backup end point is going offline during backups and this causes the backup to stall (not fail as would be preferred). I’ve captured a screenshot of the “Live” logs to give you an idea. I took this screenshot at 9 AM on the next day. This backup stalled on the 6 PM the previous day already.