I just started using restic and it is great! However, I am a bit surprised about the slow incremental backup speed.
I am backing up a large photo library to a B2 bucket and the plan is to do regular incremental backups where there will be practically no changes. This is the kind of results I am getting (with
restic 0.9.3 compiled with go1.11.2 on darwin/amd64, using only standard settings as far as I am aware) when backing up from a USB 3.0 HDD:
scan finished in 25.037s: 8097 files, 97.860 GiB Files: 8097 new, 0 changed, 0 unmodified Dirs: 3 new, 0 changed, 0 unmodified Data Blobs: 0 new Tree Blobs: 4 new Added to the repo: 1.493 KiB processed 8097 files, 97.860 GiB in 35:28
With 1 TB of data I expect an incremental backup without changes to take more than 5 hours. Thus I wonder:
- Is this the speed to be expected of restic?
- Why is it so slow, compared to e.g. borg (at least from my experience)?
- Can I do anything about it?
- Are there any plans to do anything about it as development of restic continues?
- Also: Should I file an issue on GitHub?
For comparison, this is the speed I’m getting when backing up similar data from an internal SSD drive:
scan finished in 22.084s: 5219 files, 49.629 GiB Files: 2667 new, 1 changed, 2551 unmodified Dirs: 0 new, 3 changed, 0 unmodified Data Blobs: 1 new Tree Blobs: 4 new Added to the repo: 9.476 KiB processed 5219 files, 49.629 GiB in 2:36