Waiting for Lock

If multiple machines are scheduled to run jobs against the same repository around the same time, it is entirely possible to end up with failures resulting from other processes having an exclusive lock (prune jobs for example). Would it be possible to add a flag like --wait-lock where every process would keep trying to acquire the lock until it is successful?

Thanks! And fantastic tool!

1 Like

This might be better done as a loop that checks the exit status of restic, and then you can know easier what’s going on and have more control over the retries.

Just want to drop this: “Pull-mode backups” from Status & Roadmap could be something you can eventually make use of for this kind of problem solving.