this post was submitted on 31 Aug 2025
24 points (92.9% liked)

Selfhosted

51260 readers
419 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Over the past few months I've been thinking about what would be the best way to help me and my parents improve privacy and data storage.

With all the posts with cluster PC's recently, I'm wondering if the best option is to make a couple of NAS's with Raspberry Pi's with RAID, keep one at my place and another at my parents' house, and syncing their data with 2 private folders: one for myself and one for my parents.

But that opens up a few more questions. How to sync the data to match? Syncthing? Kubernetes? Should I go ahead and add Nextcloud to the Pi's? Should I make the Pi's expandable so other services can be added later, or plan to hook up a separate Pi to handle that? What else could I be missing?

you are viewing a single comment's thread
view the rest of the comments
[–] mnemonicmonkeys@sh.itjust.works -5 points 1 week ago (1 children)
  1. You clearly didn't read my post
  2. You're rude
  3. You start every single comment with the slightest mention of syncthing with the same lines regardless of context

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

You seem to be missing/ignoring that sync will protect against data loss from lost/broken devices. When that happens, those connections are severed with no deletions propagating through them. Not only that, you can configure syncthing to retain older versions for over a year to avoid issues of unwanted edits.

Or mini pc with one drive.

You have to be joking with this. There is no way I'm letting that tracker-filled ransomware near any of my computers.

having local redundancy (e.g. Mirroring) isn't really necessary.

Simple mirroring doesn't protect against bitrot. RAID 6 does.

You're clearly not suited for giving out advice, so you're getting ignored and blocked. Don't let the door hit you on the way out.

[–] suicidaleggroll@lemmy.world 3 points 1 week ago

You seem to be missing/ignoring that sync will protect against data loss from lost/broken devices. When that happens, those connections are severed with no deletions propagating through them.

Only if you very carefully architect things to protect against it. I have absolutey seen instances where a drive had a fault and wouldn't mount on the source, and a few hours later a poorly designed backup script saw the empty mount location on the source and deleted the entire backup. You have to be VERY CAREFUL when using a sync system as a backup. I don't use syncthing, but if it can be configured to do incremental backups with versioning then you should absolutely choose that option.

You have to be joking with this. There is no way I’m letting that tracker-filled ransomware near any of my computers.

I believe he was talking about a mini PC with a single drive, not Microsoft's "One Drive".

Simple mirroring doesn’t protect against bitrot. RAID 6 does.

Lots wrong with this statement. The way you protect against bitrot is with block-level checksumming, such as what you get natively with ZFS. You can get bitrot protection with a single drive that way. It can't auto-recover, but it'll catch the error and flag the affected file so you can replace it with a clean copy from another source at your earliest convenience. If you do want it to auto-recover, you simply need any level of redundancy. Mirror, RAIDZ1, RAIDZ2, etc. would all be able to clean the error automatically.