I have 3 servers:

  • my house
  • my sister house
  • my parents house

My server has a lot of services (Nextcloud and Immich the ones that use more space), the other 2 servers only have Home Assistant, Frigate and some shared folders. On my server I use Backrest to backup locally and on Wasabi, the other 2…well…are not backed up 🙈 …yet!

I was thinking to buy a couple of 14/20TB drives and install them in my parents and sister servers so that each server can backup data on the other 2. The backup will be done locally on all the servers with Backrest. How do I copy the backups across servers? Should I use Syncthing or is it better to use one repository per location on each Backrest? Or…other ideas?

Thanks!

19 points

Configure and Pre backup the drives before bringing them to family members to save yourself some bandwidth

permalink
report
reply
5 points

Definitely a good suggestion!

permalink
report
parent
reply
4 points

As for the other question in thr post: If you are using btrfs or zfs I believe both of those have a send function that operates at a block level and will only send block changes rather than full file changes

permalink
report
parent
reply
6 points

I have an offsite NAS where I run the Restic REST server as a docker container. I connect to it over Nebula but you could also use a traditional VPN, Tailscale, Headscale, Pangolin or whatever.

Works like a charm.

permalink
report
reply
6 points
*

I’d do it like this:

  • borg backup

  • (optional) borgmatic for easier use, but a diy shell script might suffice

  • (optional) https://github.com/Ravinou/borgwarehouse for easier gui based “serverside” setup on each location

  • (if you have no way to reach the servers from the internet yet) set up dyndns for each location so you can reach them by domain

  • might need to setup portforwarding rules in the router of each location

permalink
report
reply
1 point

Didn’t know about borg warehouse. Thanks for the heads up!

permalink
report
parent
reply
6 points

Tailscale+Headscale or Zerotier, use whatever backup software you want for the local backups. Simple script to rsync backups to other sites and remove copies past a certain age.

Pretty simple, and no need to expose machines in any less than safe ways.

permalink
report
reply
3 points

Why Tailscale AND Headscale? Arent’t they the same thing?

permalink
report
parent
reply
3 points
*

Tailscale is both a client and server. If you use only Tailscale, you have to pay for the service after so many devices are connected, which by all means support the company and do so and avoid using Headscale.

Headscale is an open source implementation of the Tailscale service, so it’s free to use with all the usual Tailscale clients published. You setup Headscale somewhere, register your Tailscale clients to it, and use it like usual. It’s just skipping the need to pay for Tailscale servers as a service, and gives you greater control over how traffic routed. Completely optional.

permalink
report
parent
reply
1 point
*

Yeah but it’s like 100 devices, I think. And I believe 3 users (meaning under one account; sharing a device with someone who makes their own account doesn’t count as a “user”). You’re right, but they’re pretty generous.

I don’t think it takes many resources to provide the service to consumers; it’s not like you’re using any of their bandwidth (minus the tiny amount used for coordination between clients). Oh, or if you use their DERP servers (encrypted, but still).

In general, people should know there are self hosted, truly private options, though. So thanks for mentioning Headscale.

permalink
report
parent
reply
3 points

Whatever you end up with

  • test a restore
  • consider how to deal with the source data being corrupted / ransomed / etc, ie multiple versions
permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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!

Community stats

  • 7.5K

    Monthly active users

  • 4.4K

    Posts

  • 100K

    Comments