5 ms·
resuming backup after network has disappeared for a while or after sleep is problematic and mostly impossible to do in an atomic way. If you have enough local
by beagle3 6y ago
resuming backup after network has disappeared for a while or after sleep is problematic and mostly impossible to do in an atomic way.
If you have enough local storage, I'd put a local backup process (restic/borg/bup), and then rclone/rsync your backup repository to remote storage.
If you don't have enough local storage, you can restic or bup to a remote server reliably as long as you can complete one scan. On my laptop with a 256GB SSD, a common restic scan with cold caches takes less than 15 minutes; an hourly backup is a few hundred megs, a daily backup is often close to 2 gigs, depends on how many files you have, and how many (and how much) of them change.
Alternatively, you can do an rsync-based snapshot.
- izacus 6y agoThere are multiple Windows and macOS tools that manage to do that - without writing my own bash scripts which can fail in corner cases. I want to avoid writing them - last time I ended up with devices not backed up for months because the backup tools ended up in a partially broken state that caused silent failures. Hence why I want to have a tool designed for this use-case and not a bunch of bash shell scripts in cron.