this post was submitted on 18 Oct 2025
17 points (100.0% liked)

Selfhosted

53242 readers
1032 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
 

G'day,

tl;dr - have two unraid servers in geographically independant locations, want to use them as duplicate / redundancy storage of some shares.

  • Unraid server at home, 120TB of storage but only need to sync ~10TB total which is spread over 3 shares.
  • Bare metal Ubuntu server at work, 12TB of storage, but only need to sync ~6TB total over the equivalent of a single share.
  • Have a second Unraid server with 26TB of storage I plan on taking to work. I want to backup my ~10TB from home to work, and my ~6TB from work to home.

Currently have Crashplan running on both ends which keeps up fine with the work data size, but will take literally years to upload home volume as it is so dang slow (~3Mbps, constantly stopping to rescan millions of files) so want something else in place ASAP. Will leave Crashplan running too. It'll catch up eventually.

Home has 400Mbps upload, work has 100Mbps upload so speed shouldn't be the issue.

Is Syncthing the answer? Was thinking of doing a read-only share on the sending end.

you are viewing a single comment's thread
view the rest of the comments
[–] ieGod@lemmy.zip 2 points 1 month ago

So I did some digging, and it's less clear than I thought.

I come from the embedded development world, where bare metal has been in use for a long time. Pre-2000s, this is exclusively what the term meant. Sometime around the mid 2000s, the virtualization services starting coopting the term.

So I guess it does indeed mean both, but being a stickler for tradition it doesn't sit right with me. The term just makes more sense when you're applying it to the hardware; bare. No middleman, and that includes an OS.