‹ BackHN Continuity

Thread

Backups Aren't Simple

359 points · 225 comments · afilipovski

  1. snizovtsev · · focus · HN ↗
    I'm polishing my backup system right now, and found that `tar | zstd | gpg` plus a small vibe-coded wrapper is pretty much all I need.

    GNU tar has its own incremental index via `--listed-incremental=FILE`. Unlike Borg or Restic, which have their own more complicated repository formats, this leaves me with just one additional file (the `.snar`) alongside a dumb, portable full-disk tar archive.

    The nice part is that, unlike repositories that require both read/write access patterns, tar can compute deltas using only the small `.snar` file, while the main `full-disk.tar` can remain buried in write-only Glacier storage. This makes it a much better fit for Glacier's write-once model and 180-day minimum retention.

    My current plan is to upload a full-disk tar to an external HDD + Glacier on a weekly cadence, and the `.snar`-based deltas daily. That gives me a pretty simple cloud backup solution for a few bucks a month (after burning through $100+ of free credits).

    1. cortesoft · · focus · HN ↗
      The problem with using glacier for backups is it's hard to run restore exercises, and without restore exercises, a backup is pretty dangerous
      1. snizovtsev · · focus · HN ↗
        You can exercise it against regular, non-Glacier S3. Same flow; the only difference is that you skip one attribute on upload and one request/wait step on download.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.