Backups Aren't Simple(filipovski.net)
345 points by afilipovski 27 days ago | 213 comments
tl;dr: A proper backup strategy quickly balloons in complexity: you need snapshots (not mirrors) to survive ransomware and mistakes, GFS rotation to manage storage growth, deduplication via hard links to save space and bandwidth, database dumps to avoid corruption, and 3-2-1 distribution across media and locations. Cloud object storage adds further wrinkles like metadata loss and per-file costs that push you toward chunked tarballs. The author's conclusion: don't roll your own—use Borg or Restic, and actually test your restores.
HN Discussion:
  • ↑Personal anecdotes of data loss reinforce the article's warning about backup importance
  • ↑Restoration, not backup itself, is the real goal — echoing the article's call to test restores
  • ~ZFS snapshots with sanoid/syncoid handle most backup needs elegantly, an alternative to Borg/Restic
  • ↑Endorses the article's tooling recommendation by adopting Restic for a 3-2-1 setup
  • ↓Questions the empirical basis for the 'everyone will lose data' claim; most people rationally skip backups