Inadequate backup strategies leading to potential data loss

Signals over time

2 observed signals across 1 sources, tracked for 9 days. Confidence: low.

What people are saying Observed

• “Doesn't back it up properly . There are too many people, otherwise bright and professional, who do not realise that simply syncing to somewhere else is not an adequate backup arrangement. This problem predates agent based work. Anything an AI agent can accidentally do, malware could purposefully do too, as could a sufficiently careless human (one of the things my backups are intended to protect me from, is me!).”

  Hacker News · frustration

• “Just this weekend I had Claude set up my home lab backups: * every server backs up with kopia to a 120-day locked b2 bucket, * so do the endpoints largely, * larger projects get their own bespoke backups baked into the project itself, * and then every once in a while I download these backups to an offline storage, * every step monitored by kuma, including push notifications from endpoints, * every backup encrypted, versioned, deduplicated, * but most importantly, and something I never had before llms, every backup is tested on every step! It does random hashes of 2% of files, restores databases in local dockers and runs queries from the test suit against them! I am yelling because I never had it this good and it only took a couple of hours of wall-clock-time as Claude likes to say but really only like 40 prompts from me. It's amazing that finally you can do things right . Things have truly changed. > The novice said: "I will save my working files, but not my system and application files, as they can be always be reinstalled from their distribution disks." For example, I did exactly this because that makes backups smaller and faster. And if this means that once in ”

  Hacker News · complaint