Comment on Moving db data (MariaDB) to NFS NAS Hello self-hosters! :) I’d like to tap in
ShellMonkey@piefed.socdojo.com 3 days ago
Without getting into things like a SAN it’s generally not a good plan to put anything that needs realtime access remote to the device processing it. DBs are constantly making updates and introducing the odd bit of latency or a disconnect can make for lots of issues. I also have a worker/storage split setup and for a while tried just running the VMs as a whole using remote storage to host the vdisk, it wasn’t pretty even with a separate network dedicated to it.
For NC particularly, if you use their official AIO docker setup there is a built in borg backup you can store remotely and it makes restoration pretty painless.
INeedMana@piefed.zip 3 days ago it’s generally not a good plan to put anything that needs realtime access remote to the device processing it
So in your opinion putting whole nextcloud_data as NFS mount is also a bad idea? Keep NFS as external storage and/or only user data?
AIO docker
It was too blackbox to me. I had some issue and found it hard to debug. fpm+nginx is more my speed
This BorgBackup app is available only in AIO?
Borg is it’s own thing, just handy to have it built in and preconfigured to work. If you run VMs on your working host instead of directly on the machine you could just back those up for pretty much the same effect, though it wouldn’t usually be a realtime backup.
The next cloud data is fine being remote, when I say realtime I guess it could be better said as time sensitive. A database needs to update something and read it back in the right sequence for it to work properly. Just retrieving a file doesn’t have those issues.
If you happened to use it in a way like shared collaboration of a document with realtime updates it might be an issue, but I expect in that case the revisions would hit the DB first and then be put to the file as a secondary operation. Never tried that myself though.
nfms@lemmy.ml 3 days ago
Agree. I’m still not doing proper backups on my homelab but this is what i’m gonna focus on next. OP has a good NAS setup and IMHO the focus should be on backing up the DB for later restoration (if there’s the need because it might never happen) and keep the DB on the most powerful CPU and quickest disk.
Thing is, I expect that NAS to be faster than the SSD on the laptop that runs a bunch of stuff. Even NC log file will take up some IO
But I get the point you are all making here, I’m changing course :)