Both (!) is suboptimal. (You know that, right?)
Technically both options the backup is still available if the host dies, though one is a little harder to recover. I know it's not optimal and is why i have ran bare metal up until now. Just looking at best option short term and know many people run it in a vm on pve.
Thank you, yeah fire and flood would not be good. I do have cold storage off site for more important things to try and help with that.
I understand that those are best practices, but those specs are difficult or too costly for most who are building a homelab, remember that for most it's just a hobby or a learning tool, so the costs matter.
why? having PBS and its payload storage integrated into one device seems like a perfectly reasonable solution... Agreed that option 1 is a non starter.
Yes, it works.
This is completely backwards. PBS doesnt want anything. load is generated by the sender, and is limited by the host storage and network connection. without establishing what your load is, you're not "wasting" anything.
Thank you all for the feedback and understanding this is not the most optimal way of doing it. Leaning more towards option two but am curious about the mini pc thoughts. I had looked into it but was not sure it would be a better option for the cost. Ones I had looked at were the N100 and N150 beelinks but they are 200-300+ from what i could find.
PBS doesn't need much resources (see https://pbs.proxmox.com/docs/installation.html#recommended-server-system-requirements ) so you can easily use a used mini-pc. You can get them for around 100-200 € here. I would recommend to get one with a SATA-Port though since SSDs are recommended as storage for PBS. With that you could setup the system to have the OS on the m2 storage (most of these minis have it) and the backups on the SATA-disc. Or you setup the M2 and the SATA as a ZFS mirror and combined OS/datastore.
