I just did this over the weekend, I’ll try to remember to come back after work and add in my steps. It can be really confusing to parse over a bunch of tutorials
this post was submitted on 30 Jul 2024
20 points (88.5% liked)
Selfhosted
40041 readers
636 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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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 1 year ago
MODERATORS
I'd appreciate it very much!
This is a exercise in network DMZ planning. Assume the NAS will be compromised, so you limit its access to the rest of the network.
put the NAS on its own VLAN in both locations, setup firewall rules so that only select protocols are allowed to/from the NAS.
That'd be the gold standard. Unfortunately, the external network utilizes infrastructure that doesn't support specifying firewall rules on the existing separate VLAN, so all rules would have to be applied on the Pi itself or on yet another device between, which is something I'd like to avoid. Great general advice, though!
so all rules would have to be applied on the Pi itself
Sounds like you'll want to setup IPTables
Go the other way. Have the backup server connect in to the rest of the network.
I was considering doing something similar to OP, but I also think it's better to do it the other way around, having the backup server connect to the network when it's time to do a backup. Then you can just use the trusty ssh/rsync combo for backup.
I think you can have password auth in Samba.
That being said, the more important thing is to protect your VPN network.
Use object storage and enable immutability for the backups. If they compromise your site they shouldn't be able to delete your backups unless they have the NAS password too.
Great suggestion to secure the backups themselfes, but I'm more concerned about the impact an attacker on my network might have on the external network and vice versa.