this post was submitted on 18 May 2026
13 points (100.0% liked)

Selfhosted

59296 readers
174 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Basically what it says in the title: do you pull your backups a backup-manager host, or push them from each machine individually?

My initial inclination is to do it all from one machine, with one unprivileged user and a single cron file. That means, though, that there needs to be a remote user on each machine with g+r to everything, in order for ssh+rsync to do its thing.

Or, would it be simpler for each server to manage its own backups, probably as root, which means not having to change group permissions or identity?

you are viewing a single comment's thread
view the rest of the comments
[–] nibbler@discuss.tchncs.de 8 points 2 hours ago

Push means: if your Server gets compromised, your backup is, too.

So I prefer pull. To not have the same effect I use a restricted ssh account that can only call rrsync.