@mckinley@twtxt.net My process hasn’t changed. (But the Gopher hole is gone. Here’s the file from 2023: https://movq.de/v/72fddfd8fe/2023-05-31–backups.txt )
What is your backup target btw? This NFS drive you’re speaking of is probably hosted on one of your local servers running in your apartment/house?
What I don’t like about my strategy is that it’s so slow. ☹️ I did change a lot of data this time, so it’s slower than usual, but still …
The backup run from my main workstation onto the NAS took 2.5 hours. The one from my laptop to the NAS took 1.75 hours (hmm, why the difference?). (Those two ran one after the other, not at the same time.)
The backup run from my NAS onto one of the USBs disks is still running, I started it 5.5 hours ago. I hope it’ll finish within the next 2 hours.
Most of this is CPU-bound, because I’m using full disk encryption everywhere and that NAS only has a tiny AMD C-60 CPU from ~2011 which runs at 1 GHz and doesn’t even have a CPU fan. I guess I could upgrade this box, but it’s still working, just slow, so I won’t throw it in the trash – and what do I do with it then? Can’t sell it, can’t gift it to anyone. So I’ll keep using it.
@movq@www.uninformativ.de That’s no fun at all. I don’t like to throw away working hardware either, but I wouldn’t wait 7 hours (CPU-bound!) for my manual backup to complete if it could be done faster on a 10 year old laptop with AES-NI. How much data did you add?
@mckinley@twtxt.net Not really sure, to be honest. Probably a couple hundred GB … ? 🤔 With the changed data, it might be half a TB to transfer? I’m just guessing.
Let’s see how it goes next time. I don’t expect to add much data any time soon. (On the other hand, I’ll swap the USB disks for the next run, so it’ll take the same ~9 hours, again. Meh.)
I think the solution is to have less data. 😈
The “annoying” thing about hardware these days is that it basically keeps working “forever”. At least much, much longer that you’d expect.
Now that I think about it … I only remember one PC of mine actually dying because of a hardware failure – and that was probably because I did too much overclocking. 😂 If it wasn’t for changes in software, I could probably still use them all. I mean, why not, my Pentium 133 still works and I use it for gaming regularly.
So … my little NAS probably won’t die any time soon. Hmmm.
$ units -t '500 gigabytes per 9 hours' 'megabytes per second'
15.432099
That’s a very unfortunate speed in the year 2024.
@mckinley@twtxt.net It’s probably a bit faster, but not much. Maybe 20-30 MByte/s (I watched one 40 GB file being copied and it took 20-30 minutes or something like that.)
I need to optimize this. 🥴
Ran a few tests.
Copying data from the NAS’s encrypted ZFS pool to the USB disk’s encrypted btrfs runs at ~20 MByte/s. That is for a single 1 GB file of random data. Cold caches, sync included.
That same USB disk with the same btrfs can sustain ~75 MByte/s when I use it on my workstation (i7-3770).
And indeed, the aes flag does not show up in the output of lscpu on the NAS.
I’ll try to tweak some things about this, but it might be time for an upgrade … 🫤 (Or I’ll have to re-think the entire thing somehow.)