A friend called me one Sunday morning almost in tears. His four-bay Synology had been humming along for three years with a RAID 5 array, and the night before he had run a folder cleanup script that went sideways. Twelve years of family photos, gone in about nine seconds, and the array itself was perfectly healthy.
That is the trap. RAID did exactly what it was designed to do, and it still could not save him.
I have lost count of how many people tell me their data is safe because they run RAID. It is one of the most expensive misunderstandings in home storage, and it usually only reveals itself on the worst possible day. So let me pull apart what RAID actually does, why it is not a backup, and what the belief costs when it breaks.
What RAID actually promises
RAID stands for Redundant Array of Independent Disks. The whole point is to spread your data across multiple drives so that if one drive physically dies, the array keeps running and you lose nothing.
That is genuinely useful. Drives fail. A 4TB WD Red might run for six years or drop dead in eight months, and RAID buys you time to swap the bad one without downtime.
But notice the narrow thing it protects against: hardware failure of a disk. That is the entire scope. RAID is an availability feature, not a safety net for your files. If you want the formal definition, the Wikipedia entry on RAID lays out the levels clearly, and none of them describe backup.
The myths that lose data every week
These are the beliefs I see over and over. Each one sounds reasonable, and each one has a hole big enough to drive a truck through.
Myth: "RAID protects me if I delete something by accident"
It does the opposite. When you delete a file, RAID faithfully mirrors that deletion across every drive in the array, instantly. There is no second copy hiding on the other disk, because the other disk was updated at the same moment.
My friend's photo disaster was exactly this. The array was flawless the entire time it was erasing his memories.
Myth: "Ransomware can't touch a RAID array"
Ransomware does not care about RAID at all. It talks to the file system, encrypts your files in place, and RAID dutifully writes those encrypted versions to all the disks.
I watched a small home office get hit by a variant that appended .locked to everything on a mapped NAS share. The RAID 6 array had two-drive fault tolerance and it made absolutely no difference. Every file was encrypted, redundantly.
Myth: "My data is safe because the array is healthy"
A healthy array only means the disks are readable and the parity is consistent. It says nothing about whether the contents are the files you want. Corrupted, overwritten, and encrypted data all live happily on a green-status array.
I once had a client email me a screenshot of his dashboard, all green ticks, asking why I kept nagging him about backups. Two weeks later a bad SATA cable was silently corrupting his writes, and every one of those healthy drives held the same broken files.
The failures RAID cannot save you from
Once you stop thinking of RAID as protection and start thinking of it as uptime, the gaps become obvious. Here is the short list of things that will still ruin your day.
- Accidental deletion and bad scripts, the number one cause of home data loss I see.
- Ransomware and malware that encrypt files through a mapped drive.
- File corruption from a bad cable, failing RAM, or a power cut mid-write.
- Controller or NAS failure, where the box itself dies and the array becomes unreadable on other hardware.
- Fire, flood, theft, and surges, which take the whole appliance regardless of how many drives are inside.
- Rebuild failures, where a second drive dies while the array is straining to rebuild the first.
That last one deserves attention. When a drive fails and you replace it, the array has to read every block on the surviving drives to rebuild. On a set of aging 8TB drives bought in the same batch, that stress is exactly when a second drive tends to fail, and then the array is dead.
RAID versus backup, side by side
People conflate these because both involve extra drives and both cost money. They solve different problems. Here is the difference laid out plainly.
| Scenario | RAID protects you? | A real backup protects you? |
|---|---|---|
| A single drive dies | Yes | Yes |
| You delete the wrong folder | No | Yes |
| Ransomware encrypts your files | No | Yes (if versioned) |
| The NAS controller fails | No | Yes |
| Fire, flood, or theft | No | Yes (off-site copy) |
| Silent file corruption | Sometimes | Yes (with versions) |
Read that middle column again. RAID wins exactly one row. Everything else needs a genuine backup, and the row it wins is the least common failure of the bunch.
What actually keeps your data safe
None of this means RAID is bad. I run it myself, because I like my NAS to stay online when a drive fails. It just needs a backup sitting behind it.
Here is the setup I recommend to almost everyone, and it does not cost a fortune.
- Keep your RAID array for uptime, that part is fine.
- Add a local backup on a separate device or an external USB drive. A single 8TB external runs around 130 US dollars and covers most home libraries.
- Add an off-site copy to the cloud. A service like Backblaze handles the fire-and-theft scenario for a few dollars a month, and NAS makers like Synology with Hyper Backup make the local copy nearly automatic.
- Turn on versioning so an encrypted or corrupted file does not overwrite your only good copy. This is the single feature that beats ransomware.
The mindset shift that fixes it
The reason this myth is so sticky is that RAID feels like protection. You bought extra drives, you configured redundancy, you saw the green status light. It looks like safety.
Safety is having a second copy of the data somewhere the first copy cannot reach. RAID keeps both copies in the same box, at the same instant, mirroring every mistake you make.
So keep the array, and stop trusting it. Add a backup you have actually restored from, put one copy somewhere else entirely, and turn on versions. Do those three things and the next time a folder vanishes at 2am, it will be a ten-minute annoyance instead of a phone call ending in tears.
Frequently asked questions
If RAID is not a backup, should I stop using it?
No. RAID is genuinely useful for keeping your NAS online when a drive dies, which saves you downtime and a full rebuild from backup. Just treat it as an availability feature and put a real backup behind it. The two work together rather than replacing each other.
Does RAID 6 or RAID 10 count as a backup since it has more redundancy?
No. More parity or mirroring only means more disks can fail before the array goes offline. It does nothing against deletion, ransomware, corruption, or the whole box being stolen. Every RAID level shares the same blind spot because they all write your changes, good or bad, to all the disks at once.
Will ransomware really spread to my RAID array?
If the array is reachable as a mapped drive or open share, yes. Ransomware encrypts files through the file system, and RAID writes those encrypted files across all disks like any other change. Versioned backups and a Recycle Bin with history are what actually let you roll back to clean copies.
What is the cheapest way to back up a NAS properly?
Start with a single external USB drive, around 100 to 140 US dollars for 8TB, plugged into the NAS and set to run a scheduled backup. Then add a cloud copy such as Backblaze for a few dollars a month to cover fire and theft. That gets you the 3-2-1 rule for well under 200 dollars up front.
Why do RAID rebuilds sometimes fail and lose everything?
Rebuilding forces the array to read every block on the surviving drives, which is heavy stress. Drives bought in the same batch tend to age similarly, so a second drive often fails mid-rebuild and takes the array with it. This is exactly why a separate backup matters even with redundancy.
