3 ms·

I’m praying you have backups. That last paragraph gives me anxiety

• linsomniac 10mo ago
  Well, I haven't lost them in over a decade... So I have a pretty good track record. The system it's hosted on has had at least one, maybe two hardware failures over that time. A system isn't done being set up until it has backups up and running.
  • dotancohen 10mo ago
    ...and tested. I only had to see one machine "that was being backed up" unable to restore from backup. Wasn't mine, but was enough to teach me to test them.
    • linsomniac 10mo ago
      Absolutely! You're preaching to the choir here. However, that said, over ~3 decades I've found that having a successful rsync exit code and alerting when that is not true, along with periodic "full" rsync checksum runs, is effectively a failsafe way of ensuing a good backup. For our less critical systems, this plus "spot checking" by regularly going in and looking at "what did this file look like a few weeks ago" (something we commonly use backups for), has proven pretty effective while also being low work. For critical systems, definitely do test recoveries. Our database server, for example, every week recovers the production database into our staging and dev environments, so backup problems tend to get noticed pretty quickly.
      • jacklein12 9mo ago
        [dead]
  • alfiedotwtf 10mo ago
    When the server goes up in smoke, you won’t be able to restore from your track record. A simple ‘scp remote local’ once a month will save you from years of “damn… if only I had backed up”
    • alfiedotwtf 10mo ago
      Ah. I see below you’re using rsync. Phew!