27
Keeping Backup Costs Down with B2? (lemmy.world)
submitted 2 weeks ago by to c/selfhosted@lemmy.world
19 comments fedilink hide all child comments
 

I'm considering Restic and Backblaze B2 as my backup solution. I'm a little worried having read about the potential for unexpected restore costs. For example, I've read restoring lots of little files adds to the cost (reference). What are the things to look out for when backing up and restoring that can add to the cost? Are there any best practices to keep costs down?

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 weeks ago (1 child)

I doubt that this applies to files smaller than the pack size or a for example bitwise unique 17MB file would result in a (overly simplified) 16 MB and a 1 MB chunk or am i wrong here?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 weeks ago (1 child)

    Most of these backup solutions try to reduce the amount of data backed up, so the system will process each file and determine if the contents changed and only upload new data. In this case if you modify the file you may end up with 2 16 MB chunks that have slightly different data, and only when the old backup expires and the pruning process completes would one of those chunks be deleted.

    Smaller chunks sizes means you get more files written to S3, but less duplicate data when deduping without compression.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •