• 0 Posts
  • 44 Comments
Joined 9 months ago
cake
Cake day: January 2nd, 2025

help-circle









  • The over-regulation courtesy of oil companies (via ill-informed environmental groups in the 70’s) is a major issue.

    Then for some reason* people see the Three Mile Island incident as a failure rather than the fail-safe success that it was, and seem to see it in the same light as Chernobyl which was the opposite in every way: design, process, oversight, management, leadership.

    *That reason is partly informed by the dumbass movie “China Syndrome” which was outrageously wrong on how reactor safety is designed everywhere except the Soviet Union.



  • What are you trying to guard against with backups? It sounds like your greatest concern is data loss from hardware failure.

    The 3-2-1 approach exists because it addresses the different concerns about data loss: hardware failures, accidental deletion, physical disaster.

    That drive in your safe isn’t a good backup - drives fail just as often when offline as online (I believe they fail more often when powered off, but I don’t have data to support that). That safe isn’t waterproof, and it’s fire resistance is designed to protect paper, not hard drives.

    If this data is important enough to back up, then it’s worth having an off site copy of your backup. Backblaze is one way, but there are a number of cloud based storages that will work (Hetznet, etc).

    As to your Windows/Linux concern, just have a consistent data storage location, treat that location as authoritative, and perform backups from there. For example - I have a server, a NAS, and an always-on external drive as part of my data duplication. The server is authoritative, laptops and phones continuously sync to it via Syncthing or Resilio Sync, and it duplicates to the NAS and external drives on a schedule. I never touch the NAS or external drives. The server also has a cloud backup.






  • Generally a good point, but…

    Flash isn’t permanent. Data storage mediums at any scale are impermanent.

    Vinyl is pretty stable, provided it’s stored out of light and extreme temps.

    CD’s are the same.

    For me to store my (currently) 5TB of data (and have it be accessible) requires about 15TB of actual storage (3 copies to prevent loss, because hardware fails). Plus at leas one always-on device to play the media from. Each of these storages requires manufacturing, and then power to run them, and maintenance (new drives as old ones fail, new hardware, etc).

    No solution is perfect, each of these approaches has it’s own pros/cons.




  • Sync is not backup.

    Let’s repeat that - sync is not backup.

    If your sync job syncs an unintentional deletion, the file is deleted, everywhere.

    Backup stores versions of files based on the definitions you provide. A common backup schedule for a home system mat be monthly full, Daily incremental. In this way you have multiple versions of any file that’s changed.

    With sync you only have replicants of one file that can be lost through the sync.

    Now, you could use backup software to a given location, and have that synchronized to remote systems. Syncthing could do this, with the additional safety of “send only” configured, so if a remote destination gets corrupted, it won’t sync back to the source.

    Edit: as for Pi NAS, I’ve found Small-Form-Factor desktops to be a better value. They don’t have much physical space for drives, but I’ve been able to use two 3.5" drives or four 2.5" drives in one. My current one idles at <15w.

    Or mini pc with one drive. Since you’re replicating this data to multiple locations, having local redundancy (e.g. Mirroring) isn’t really necessary.

    Of course this assumes your net backup requirements are under about 12TB (or whatever the latest single drive size is).