this post was submitted on 22 Apr 2025
38 points (93.2% liked)
Selfhosted
60451 readers
1161 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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Configure each backup machine to read from the data you are backing up
You can do it that way, but I don't see how that's more secure. Fewer server bits to maintain I guess?
I think what he means is that if your backup is triggered from your main server and your main server is compromised the backups can also be attacked immediately. If the backup is requested from the backup machine you will at least have the time between the attack and the next backup to prevent the attack from reaching your backup machines.
I'm sorry, but I still don't understand what you mean. Could you please elaborate bit? Thanks!
You configure the backup systems to connect to the device to be backed up. The idea is if something bad happens on the main machine it won't impact the backups
Got it, good idea, thanks!