My understanding is that SSDs just aren’t well suited to shoveling lots of smaller chunks or lots of r/w access. Those kinds of tasks beat them down pretty hard. For most people no big deal, but if you’re doing a lot of video/music etc then the lifespan of SSDs isn’t going to be what you will expect from a lifetime of using HDs.
Doesn’t mean they should break down in a year or whatever and it always sucks to lose data. But some kinds of workloads really will destroy a disk in a year or less.
I run sort of 3 tiers of disks/arrays:
I use SSDs for working space, for the speed. All the work that I’m doing for the most part is working with files on an SSD. I have a dedicated SSD for the OS and a different dedicated SSD for my user account which is mostly a folder called “Active Projects” and I work out of that folder.
I have a couple sets of HDs configured in RAID 0 (least safety, most speed) for assets I use often and for an available copy of my complete archive. Not as fast as the SSD but pretty damn fast. These exist as a cost compromise from just storing everything on SSD. There is no safety net in RAID 0. If it blows up then I have to rebuild it from…
Slow, gigantic HDs, no RAID, no nothing. If I want a file and this disk boots up then I’m probably going to find that file. These mirror the working space, the archive, the assets, the OS every night. I never touch these unless I need to rebuild a RAID (hasn’t happened in a couple years but it has happened) or unless I’m moving them to off-site archive (try to do that quarterly) and starting a new one. These are giant and slow. Depending on the speed of disk size increases, these have sometimes become slices in a RAID array a year or two after they’ve done time in off-site storage. They are always the largest HD available to me at the time I put them in service.
I manage backups with Carbon Copy Cloner (if you’re on Mac and have never used it, once you use it you will wonder how you ever did backups without it: been bombproof for literally decades, must-have Mac software). It happens after I go to bed. Except for when I’m starting a new drive set I never even notice it.
If the machine starts preparing to run the backup that is my notice that it’s too late for me to be working or looking at a machine. If I was a late-night gamer or worker, then I’d set it to some other time or get a machine for late night gaming/working that I didn’t use for anything else so that my main rig would be able to back up without me getting interfered with.