This was the first time I ever installed Arch. I used the Arch wiki installation guide. It’s still running strong, with no problems at all through these years aside from the occasional minor bug (and usually bugs are from KDE).
I use no backup for the system (though of course I manually backup any important data). Never needed it. No btrfs, no snapshot, no rollbacks. Just me and pacman and ext4.
I had my ? first ? (not sure) blue screen this morning on an arch-based system. It looked like btrfs lost it’s mind, but it could be anything. This is on a server, so it’s always on (yes, I am cheeky to run arch on a server).
However, I’m glad to read of your ten year mark!
I have never had an Arch system break but I have never kept any hardware running for 10 years with a consistent OS. I always either have a hardware failure or I change the use case for the machine which triggers an different install.
This installation is on an HDD. It used to be my daily driver, then in 2019 it was replaced with an SSD.
Since then, the HDD sits on my desk. It gets plugged in and updated every few months, and when I update it I run it for a few hours afterwards. On the yearly anniversaries I usually run it for a couple of days.
Had this been installed on an SSD it would still be residing in my main tower.
LANG=C stat / | grep Birth is the trick for a german system …
My result for my oldest running EOS-Installation: Birth: 2019-12-22 13:26:20.000000000 +0100 which is running 24/7 since then …
The first ever EOS installation was from approx. 2019-08. I had to redo the installation last year because of a complete change (ext4 → btrfs, no longer NFS and LDAP auth, additional SSD for /home etc.).