skankhunt42

If you only have 2 and 1 fails, you’ll need to make sure the remaining one can take on 100% of the workload. If you’ve already maxed one and want HA, I’d suggest adding 2 more. Otherwise you’ll need to decide what services are down while you repair

Everything is super expensive these days which is why I’ve got all kinds of nodes. I lurk marketplace, kijiji, etc for “broken” or “for parts” nodes. Laptops with broken keyboards, screens, no battery, etc are perfect for me. I7 11th gen was $90 CAD. Works perfectly for a node. Found a cheap tiny with a locked bios. Removed the CMOS battery to reset and I’m good to go.

If you’re not willing to do that, the working tinys are perfect in my opinion.

The working Synology seems extra to me. You could use software like ceph, or diy it. Storage boxes don’t need crazy specs, just sata ports and power. The only reason I’d consider it is if you just want something “simple that works” and you’re willing to pay for it.

I don’t know about proxmox but I have 6 4 8GB, 5 lenovo Tiny (i5-4x and i7-8x), and 3 laptops in a k8s cluster and love it. I actually have too many hosts but it’s a lot of fun for me to play on them. Storage is longhorn for anything with a database, everything else is over NFS onto a box I built myself. If you use the *arrs try them over the network and watch the logs. They HATE network storage and will complain a lot. If you don’t have any issues there you should be good.

I haven’t had any issues and just use the 1gb network. As for form factor, I think it’s whatever you have room for. The laptops are annoying but they have the best hardware so I put up with it.

Personally, it sounds like you’re overengineering your setup. If it’s to learn then have fun! However, if its ‘prod’ and you care about the data then you should stick to prod tested architecture. You won’t find many people (if any at all) using inode notify to rsync a database on change.

I think the inode rsync is a bad idea. The 2nd DB would be on the NAS but its not being used by the app, so as long as it’s asynchronous writes, you should be okay.

In either case, I hope you have backups, not just the copy

I know it has been 3 days since you posted buy why not set up replication in the database it self? Sounds like you’re over complicating replication.

I run in k8s but I have a database with local disk, and I have another cronjob that takes a backup into the first database docker init folder. Older backups end with -date so they won’t get picked up by the init script. You can do similar with just docker.

I’ll echo everyone else. Database need local disk. I speak from experience of doing it over NFS. Even containers that have a hidden sqlite3 database should get local disk.

I self host matrix.org synapse and bridge all my chats into this. I have a room for alerts and have any issues go into there. I get this on my phone, desktop, etc.

Aside from the notification part, I don’t want anything on my phone. If there’s an outage at 3am for my self hosted stuff, I’m not getting up, I don’t even want it to wake me up. I like sleep.

All I need is that initial notification and maybe a little extra context as to what it is. I need to determine if I’m going to fix it “soon” or if it can wait until I have free time. Doing anything else on my phone is a hard no. I need a keyboard and mouse.

When digging into the problem all I usually look at are the logs.