There is plenty of backup management software. You want one that will not only keep a copy of your data, but also save you in the event you accidentally delete one or more files.

I’d upgrade the NAS to full server status and run everything from there. For most people, there’s not much point in separate devices. It just adds a point of failure.

It sounds like they’re not quite using fresh water, but waste water. I presume it’s been treated, but even if it’s not 100% back to potable, if this also helps solve the problem of what to do with the brine after desalination, I think it’s a win all around.

I think you have two goals at odds with each other.

I had a longer reply typed out, but I guess the network ate it. The gist was to consider a second low power device for the always on services that don’t need the big noisy storage.

It’s both.

First of all, a NAS VM is generally considered a bad idea that has been discussed before so I won’t repeat it here.

Anything using those drives is going to keep them awake. Usually, NAS software runs background tasks, as does proxmox. You’ll have to identify and schedule them to shut down during sleep hours.

But that’s going to be a huge pain, because eventually you’ll find it’s gone to sleep when you haven’t, and you want access. I’d see if you could configure proxmox to suspend the VMs and put the whole thing to sleep when you push the power button.

Looks fine to me (Firefox 142.0.1 on GrapheneOS 2025081400 on a Pixel 8).

I’ve seen worse. That shouldn’t have overheating problems.

You haven’t given much detail to go on. I’m pretty sure proxmox has a support dump button (I’m out of the house right now so I can’t check), but you could at least do lshw, lspci, etc., and the VM config file.

You might get better answers from the proxmox support forum. It’s more active than Lemmy.

Ground News isn’t software.

The plural of index is indices.