All you need is to use ZFS or BTRFS locally to prevent master version bitrot and provide failover/redundancy, manually sync that to a separate “offline” HDD periodically, then setup a simple pi with tailscale + HDD at a family member or friends house, and rclone all your data to it (encrypted) as a cron job every night or week. This performs the function of a cloud provider (offsite backup); alternately, just manually sync the offline HDD once a month.
With this approach you’re covered for accidental deletion, hard drive failures, bitrot, ransomware, and fire; possibly many natural disasters, depending how far away the offsite is.
Then you can just keep your most important data E2E encrypted in 1 or 2 cloud storage providers.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
All you need is to use ZFS or BTRFS locally to prevent master version bitrot and provide failover/redundancy, manually sync that to a separate “offline” HDD periodically, then setup a simple pi with tailscale + HDD at a family member or friends house, and rclone all your data to it (encrypted) as a cron job every night or week. This performs the function of a cloud provider (offsite backup); alternately, just manually sync the offline HDD once a month.
With this approach you’re covered for accidental deletion, hard drive failures, bitrot, ransomware, and fire; possibly many natural disasters, depending how far away the offsite is.
Then you can just keep your most important data E2E encrypted in 1 or 2 cloud storage providers.
Note: zfs/btrfs cannot repair bitrot without redundancy, only detect it. But if redudancy, is repaired automatically (self-healing).
Raid 1/5/6 cannot repair, only detect bitrot, cannot decide which copy good.
I have never seen an implementation of e.g. a mirror that gives up on disagreements of both disks. Repairing/redundnancy is what raid is there for.
Edit: maybe old hardware raid does not check?
No, raid for disk failure: https://en.wikipedia.org/wiki/RAID
Raid has no checksum, see argument here: https://superuser.com/questions/769104/is-raid1-or-similar-needed-for-btrfs-zfs-to-protect-against-bit-rot
But look like some raid implementation (and lot of drive) have error correction now: https://en.wikipedia.org/wiki/Error_detection_and_correction#Data_storage https://serverfault.com/questions/77710/is-bit-rot-on-hard-drives-a-real-problem-what-can-be-done-about-it