Help with my Proxmox-Setup
from doctorflynt@feddit.org to selfhosted@lemmy.world on 04 Jul 09:28
https://feddit.org/post/32166037
from doctorflynt@feddit.org to selfhosted@lemmy.world on 04 Jul 09:28
https://feddit.org/post/32166037
I‘ve got 2 Machines with Proxmox on both installed. One hosts my data and media and runs Services like Jellyfin, NAS,… The other one is a Mini-PC that hosts my Services like Adguard, Home Assistant,…
Whats the best way to Backup the data and configs of those 2 machines? Installing Proxmox Backup Server on each and store the Backups on a seperate HDD? Or would it be better if a move all the services to a single machine and use the second only for backups?
thank you!
threaded - newest
I have different vms which all write to an smb mount.
Then I have another VM that runs duplicati and mounts that smb share, but also another one just for the backups. And only this duplicati container has access to the backup share, which isolates my backups for security reasons. The only thing still involved and able to read and manipulate my data is the router which can see all the traffic.
Now idk if this is the best setup, but it feels secure to me and it works for me. Maybe more experienced people can chime in to agree or disagree.
I use 1 host running Proxmox VE (PVE) with a VM for Proxmox BS (PBS). Datastores are located on a USB HDD with passthrough of that specific USB ID to the PBS VM.
It works really well and the only actual downside is that, for a complete-restore (e.g. reinstall PVE or new server or hard drives) you need to set up the PBS VM again before you can use your backups.
For the host-config on PVE, I use a systemd service and timer starting a simple proxmox-backup-client backup of /etc. That is enough to restore the configuration in case of some emergency.
Also: Is there a benefit for splitting your services on 2 hosts? Shouldn’t 1 host with all VMs consume less electricity than the same VMs split on multiple hosts?
I don’t know about OPs situation, but I have a mini-PC as proxmox hypervisor too addition to my main server. Mini-PC is located middle-ish of the house as it’s running home assistant with ZWA-2 and the location helps a lot with Z-wave coverage. But added benefit is that I can (within the pretty strict resource limits) move VMs to the mini-pc when doing maintenance on main server. It’s pretty handy to move PiHole and some other small stuff to another host so that everything on network still functions even if one hypervisor is down.
Interesting. I do not know a lot about Home Assistant devices, but I thought they would just be communicating via standard WIFI + data encryption. I definitely didn’t suspect there to be a whole new standard of wireless communication to that.
I understand the thing about downtime, running
piholemyself. My setup is rather simple and centralized on purpose and I don’t really mind the few minutes of “filtered DNS” downtime whilepiholeandpveare rebooting. As my UniFi Dream Router 7 is the firewall / gateway / DHCP server anyway, I just usepiholeas primary DNS and1.1.1.1as secondary DNS. It’s not filtering “bad domains” via DNS, sure, but I gotadblock originand other browser extensions dealing with whatever comes along anyway.But, yeah, for redundancy and always-online-production-setups it’s actually great having a secondary
pveas a temporary stop-gap. Plus, it’s a nice and kinda fancy setup, of course. Always appreciated in selfhosted :)There’s multiple. Some devices are on wifi, some on z-wave and as zigbee is getting quite a lot of support from vendors I’ll likely add that to the mix soon-ish. Also I could use bluetooth for some automations, but at least for now I don’t really see any advantages over that.
As for pihole, it’s main DNS server for devices in my network and rest of the family uses the net quite a lot too (IPTV and streaming services included) so any longer downtime would cause at least annoyance for them so it’s nice to have an option to keep things running and take my time to maintain hardware or whatever. I of course could change DHCP server to offer something else too, but it’s simpler and faster to just migrate a VM to another host.
Install one pbs on the big server. If you have the space, set up replication so you have another local copy. Best practice is to also keep an offsite copy, either with cloud storage or external drives you rotate, in case something happens to the stuff at your house.