I have a MySQL database that has 10 years of posts from phpBB and its .sql export is currently at 167MB. I back it up daily “all by itself” to a single B2 Bucket. Bottom line: large text file with very small percentage of changes each day.
Because the Bucket seemed to be growing in size very quickly since I switched to restic from duplicity, I just did a side-by-side test with duplicity, specifying the single file. Here are the Bucket Sizes:
- Day 0 (full backup) - restic 174.2MB; duplicity 47.1MB
- Day 1 (incremental after file changed slightly) - restic 294MB; duplicity 48.9MB
I have read extensively on the efforts to add compression to restic, so I understand and “can live with” that problem, but I could not find anything (though I had trouble searching) on the incremental approach used by restic, other than a few mentions of detecting identical chunks.
Any thoughts on reducing B2 storage required? I couldn’t find any options that might help. The only options that I am using are --cache-dir on backup and b2.connections=7 on init.