True, but that’s going to really be pushing your network links just to recover. Realistically, something like ZFS or a RAID-6 with extra hot spares would help reduce the risks, but it’s still a non trivial amount of time. Not to mention the impact to normal usage during that time period.
Rebuild time is the big problem with this in a RAID Array. The interface is too slow and you risk losing more drives in the array before the rebuild completes.
I actually started doing that. It’s a living document, shared with others. It’s the best solution I’ve come up with. Knowing whether or not I can convey enough info to make it usable and able to be followed for a less technical person like other family members drives my adoption of software/hardware solutions.
It’s the theoretically part that i haven’t figured out. I know none of my family members would have any idea what to do with anything. I feel like All the Data will just be lost when i go… which is a huge issue as everything moves to digital.
I’d rather new software versions were only released when there was a solid reason. A slow meaningful, well tested release cadence is generally a sign of more mature and stable software.
I’ve heard lots of good things about Ghost. I’ve also hosted Grav for a while and it’s pretty solid. You can do Wordpress, but I’d stay away as it gets bad fast and there are better alternatives. If you needed even more scale, Mediawiki is selfhostable too.
100%. But the post i was responding to was talking about recovering a failed array from other copies, not locally.