I could not for the life of me make the ethernet transfer speeds be more than somewhere around 1-5 MiB/s
That's probably a physical cable issue.
Check the connectors and / or different cables.
It's esp. more important for 1Gbps connections as they're more sensitive than 100Mbps
Ok, fair point
Ahhh, well spotted
Yeah, this is what I'd like clarified too
Am I just setting up a schedule on the server and then pushing out config to the other devices and can then shut down the server? (For example)
Where do I need to install restic?
Is this local only or to an offsite (Hetzner) location?
Let me know which repo this update appears in.
I had a quick look at the docs... so, can I backup my DB version X and restore it to DB version Y?
It's difficult to do security-only updates when the fix is contained within a package update.
Even Microsoft's security updates are a mix with secuirity updates containing feature changes and vice versa.
I usually do an update on 1 random device / VM and if that was ok (inc. watching for any .pacnew files) and then kick Ansible into action for the rest.
And, even further: a rust implementation vulnerability too?
(Waits for C vs Rust war to start...)
I split my loads (gigity) between the power hungry NAS and a passively cooled low power Proxmox host.
For me, most 24/7 activities are low CPU - like Home Assistant, so it needs to be there, but it doesn't need to do anything.
Other VMs are ansible, uptime kuma, smokeping, etc... the most they use is RAM
Then the (relatively) more power hungry NAS powers up 3 times a day to syncthing everything, maybe upload a backup, and if no-one's using Immich, etc. then it'll power back off again.
The only other thing I have yet to downsize is my pfSense box (still a low powered device, but has fans..) and a Raspberry Pi I use for my Zigbee network.
My NAS powers up & down about 3 times a day. Drives are all fine & healthy and some have been in there for years.
I don't disagree with your core point though...
If the drive just finished spinning down and then it's triggered for a 1 byte file, spins down, repeat... yeah, that definitely needs sorting out.
Just the initial spin-up lag would do my head in.
But off & on ~ daily, yeah not a problem.
Yeah, an interesting piece.
As someone who's seen the internet arrive, watched the various battles (best seen on Internet Explorer at 640x320) and tried all the latest things (why use gopher when google can search immediately), then I do think it started out well
But, yep, I've also seen the effects when the bills needed paying and realising that just taking things that are "free" without giving anything back is unsustainable.
That's why I contribute when & where I can... Arch Wiki, Open Street Map, a few payments to developers and independant media sources, helping others...
But it takes some effort and I get it, not everyone has the same priorities. Yet.