I would not recommend as complex a set up as I use for the average computer user. I provide web hosting through several owned colocated servers and I also provide 3rd party support for an html authoring software. I have been a computer "hobbyist" since the mid 70's when I soldered together my first s-100 card. I have never purchased a "canned" computer (outside of laptops) and have always assembled all of my own hardware (
including the web servers I use).
So kiddies... DO not try this at home and always have adult supervision
If you're going to start talking about RAID and reliability, then you need to get more specific about it. There is true HW Raid, and then there is the more prevalent (at the consumer level) SW Raid. The latter is not as reliable, imposes significant resource loads on the host system, and is more prone to serious failures and data loss, independent of the HDD status. Unfortunately, it is also the version that comes onboard most consumer MBs these days (and on the sub $200 controllers), and what most households call "RAID". Among techs, it is more commonly known as "fakeraid". A good HW solution will have a powerful separate processor, firmware-level operating systems, large and fast cache banks, and onboard battery backup to safely run the on-board cache operations required to achieve spectacular transfer speeds using many drives, with little to no resource demands made on the host system.
Running an array on non-enterprise and/or drives not rated for RAID duty is the second big mistake most casual users make. A RAID array works the drives in a very different fashion from a desktop drive design.
The other mistake casual users make with RAID arrays is treating them like desktops, cycling them off and on every day and configuring them for maximum energy savings. For maximum reliability, an array should be left running 24/7 with all spin down features disabled, as most HDD failures occur during or shortly after spin up, when the greatest electrical, mechanical and thermal demands occur. It should also be tethered to a high quality network-grade UPS.
And as stated, a RAID array is only protection against local HW failure (and ALL HDDs eventually fail, even the enterprise ones). It is not a data backup in the industry sense; no local model protects against site catastrophes such as fire/casualty events, user errors and malware damage. Even HW Raid controllers occasionally fail. You need a genuine off-site solution with version control for that level of protection.
A quality HW based RAID array running enterprise class drives is not inexpensive. A solid HW Raid controller solution starts at several hundred dollars, and jumps quickly over $1k (excluding HDDs), depending on the drive population. Good raid-rated drives are usually 2x+ the price of their desktop grade cousins. To fully enjoy the benefits also requires complimentary server and network systems. It can get very expensive very quickly, and is a fast moving technology curve not for the financial feint of heart.
Around here, we run a primary server HW Raid 5 array, backed up daily via gigabit lan to a second HW Raid 5 array in another part of the building. The server array is also continuously backed up 24/7 to an off-site depository via Internet, just in case the building burns down. This is a mid five-figure data setup, but it contains over 2 GB of hi-def audio and video (and a lot of irreplaceable personal data over 25 years) that can be simultaneously accessed from every room in the house over wired LAN clients of all sorts. I don't have pictures.
For the more causal user, it is probably easier and cheaper to just run a single drive desktop solution, and subscribe to a continuous off-site backup service such as Backblaze.