This repository has been archived by the owner on Sep 3, 2021. It is now read-only.
Prevent multiple restic backup
s from running at once
#4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm doing an initial backup of ~2.5TB which is far more than my home bandwidth can upload offsite in a 24 hour period. I noticed on the 2nd day of running, cron had launched a second
restic backup
process. Per comments in this issue thread in the Restic repo, restic/restic#519 (comment), it's not necessarily an issue to have multiple Restic backups of the same data going on at once, however it will waste some space.Rather than wasting space on B2 and using additional system resources on a resource constrained system, I made the following modifications:
do_backup.sh
is launched, and therefore only a singlerestic backup
is launched as well.