• SapphironZA@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    110
    ·
    3 months ago

    We used to say Raid is not a backup. Its a redundancy

    Snapshots are not a backup. Its a system restore point.

    Only something offsite, off system and only accessible with seperate authentication details, is a backup.

    • tetris11@feddit.uk
      link
      fedilink
      English
      arrow-up
      23
      ·
      3 months ago

      3-2-1 Backup Rule: Three copies of data at two different types of storage media, with 1 copy offsite

    • Krudler@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      3 months ago

      Circa 1997 I was making some innovative new games, employed by a dude who’d put millions of his own money into the company. He was completely nonplussed when I brought him 20 CDs in a sealed box to remove from the building and store off site. He thought I’d lost my damned mind and blew it off as ravings of a stressed dev. I pointed out real threats to our IP including the hardware failures and even so far as the building burning down. 2 years of custom art and code gone. “Unlikely. Relax.”

      After I moved on… an ex co-worker who’s still a longtime friend, tells me a different division lost a huge amount of FMV over some whoops-I-destroyed-the-wrong-drive blunder. 20 days to render on an 8 or 10 machine farm. Poof - No backups. In 1997 even with top-of-the-line gear it took an insane investment to render quality 3D.

      The friggin’ carelessness irks the shit out of me as I type ahah

    • OrteilGenou@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      3 months ago

      I remember back when I first started seeing a DR plan with three tiers of restore, 1 hour, 12 hours or 72 hours. I knew that to 1 hour meant a simple redirect to a DB partition that was a real time copy of the active DB, and twelve hours meant that failed, so the twelve hours was a restore point exercise that would mean some data loss, but less than one hour, or something like that.

      I had never heard of 72 hours and so raised a question in the meeting. 72 hours meant having physical tapes shipped to the data center, and I believe meant up to 12 (though it could have been 24) hours of data lost. I was impressed by this, because the idea of having a job that ran either daily or twice daily that created tape backups was completely new to me.

      This was in the early aughts. Not sure if tapes are still used…

      • Passerby6497@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        Not sure if tapes are still used…

        Alive and well depending on the use case. My org has an older backup software that’s entirely tape based and it’s amazing for the Linux systems I hear

    • SreudianFlip@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 months ago

      Fukan yes

      • D\L all assets locally
      • proper 3-2-1 of local machines
      • duty roster of other contributors with same backups
      • automate and have regular checks as part of production
      • also sandbox the stochastic parrot