Comment

Comment on Prioritizing de-clouding efforts

just_another_person@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

The biggest thing I’m seeing here is the creation of a bottleneck for your network services, and potential for catastrophic failure. Here’s where I forsee problems:

Running everything from a single HDD(?) is going to throw your entire home and network into disarray if it fails. Consider at least adding a second drive for RAID1 if you can.
You’re going to run into I/O issues with the imbalance of the services you’re cramming all together.
You don’t mention backups. I’d definitely work that out first. Some of these services can take their own, but what about the bulk data volumes?
You don’t mention the specs of the host, but I’d make sure you have swap equal to RAM here if youre not worried about disk space. This will just prevent hard kernel I/O issues or OOMkills if it comes to that.
Move network services first, storage second, n2h last.

source

Sort:hotnew top

Cerothen@lemmy.ca ⁨2⁩ ⁨weeks⁩ ago
Proxmox backup server is my jam, great first party deduplicated incremental backups. You can also spin up more than 1 and sync between them

source
meyotch@slrpnk.net ⁨2⁩ ⁨weeks⁩ ago
I have a fine backup strategy and I don’t really want to go into it here. I am considering my ecosystem of services at this point.

I am skeptical that this will overload my i/o if I build it slowly and allocate the resources properly. It may be the rate-limiting factor in some very occasional situations, but never a real over-load situation. Most of these services only sit and listen on their respective ports most of the time. Only a few do intense processing and even then only on upload of new files or when streaming.

I really resist throwing a lot of excess power at a single-user system. It goes against my whole ethos of appropriate and proportional tech.

source