I’m currently backing up my NAS to Backblaze and while Restic proving to be awesome on my desktop backup.
but, I’d like to limit the upload during “office” hours and then do whatever the ISP allows the rest of the time on the NAS
My questions are
if I kill the upload to then run a version of the script to backup with trickle, will Restic carry on from where it was stopped? ( I assume it would prune any half uploaded files and then carry on)
what’s the best way to script/cron job a stop of Restic’s current backup job before starting another?
many thanks
this is something I’ve never done before so I’m not even sure what to google
restic can limit its bandwidth via --limit-upload and --limit-download, but this is a single setting for the whole runtime of the process. Also, trickle won’t work because it uses LD_PRELOAD to insert itself between the program and the main library libc. Restic is written in Go, is statically linked and does not use libc, so there’s nothing trickle can do.
Yes, it’ll continue roughly where it left of. But that’s only for the backup operation: Other operations (especially prune) will restart from the beginning.
You can use flock from the moreutils package to only run a single process by maintaining a lock in the local file system.