RAID Is Not a Backup

A Destin property management company had a server with 4 hard drives in RAID 5 configuration. RAID 5 means data is striped across drives with parity information — if one drive fails, the data can be rebuilt from the remaining drives.

One drive failed on a Tuesday. They ordered a replacement. The replacement drive was defective — this happens more often than vendors admit. While they waited for a second replacement, a second drive failed. RAID 5 can survive one drive failure. Not two.

Six years of rental contracts, tenant records, and accounting data — gone. All RAID, no backup.

They thought they were protected. They were protected against one specific scenario: a single hard drive failure. They were completely exposed to everything else.

What RAID Actually Is

RAID (Redundant Array of Independent Disks) is a hardware configuration that spreads data across multiple drives for either performance or redundancy.

RAID levels that matter for small businesses:

• RAID 0 (striping): Splits data across drives. Fast. No redundancy. If one drive fails, everything is gone.
• RAID 1 (mirroring): Copies data to two drives simultaneously. If one drive fails, the other has everything. Simple redundancy.
• RAID 5 (striping with parity): Stripes data across drives with distributed parity. Can survive one drive failure. Most common in small business NAS devices.
• RAID 6 (striping with double parity): Can survive two drive failures. More expensive, more resilient.
• RAID 10 (mirrored + striped): Combines RAID 1 and RAID 0. Requires 4+ drives minimum. Fast and redundant.

What RAID does:

• Keeps your server running when a hard drive fails (RAID 1, 5, 6, 10)
• Reduces downtime from hardware failures
• Gives you time to order replacement drives without immediate data loss

What RAID does NOT do:

• Protect against accidental deletion
• Protect against file corruption
• Protect against ransomware
• Protect against the same power surge that kills drive 1 killing drive 2
• Protect against software bugs that corrupt data
• Protect against theft of the entire NAS
• Protect against the person who reformats the wrong volume

Why This Distinction Matters

Scenario: Accidental deletion. An employee deletes a folder of client files. RAID doesn't help. The deleted files are gone from all drives. You need a backup to restore them.

Scenario: File corruption. A software bug corrupts your accounting database. The corrupted data is written to all drives. RAID doesn't save you. You need a backup from before the corruption.

Scenario: Ransomware. Ransomware encrypts your files. It runs on your server. It has access to all the drives. RAID doesn't stop it. The encryption spreads to all drives simultaneously. You need an offline or immutable backup to restore from.

Scenario: The defective replacement drive. This is the Destin property management company. RAID assumes drives fail one at a time. In reality, a power surge or manufacturing defect can take out multiple drives in quick succession. RAID 5 survived one drive failure. It didn't survive one drive failure followed immediately by a defective replacement.

Scenario: Theft or fire. Your building is broken into and the NAS is stolen. Or a fire destroys the server room. All drives — RAID or not — are gone. You need an offsite backup.

The Specific RAID Mistakes Gulf Coast Businesses Make

Mistake 1: "We have a NAS with 4 drives in RAID, we're protected."

This is the most common misconception. The NAS keeps you running when a drive fails. It does not protect your data. Add a backup.

Mistake 2: "We mirrored our drives, we have a backup."

Mirroring (RAID 1) copies data to two drives. If you accidentally delete a file, it's deleted from both drives. If ransomware hits, it encrypts both drives. Mirroring is redundancy, not backup.

Mistake 3: "Our server has redundant power supplies and RAID, we're bulletproof."

Redundant power supplies keep the server running through a single power supply failure. They don't protect data. RAID keeps the server running through a single drive failure. It doesn't protect data. You still need backups.

Mistake 4: "We have UPS battery backup, our data is safe."

A UPS keeps your server running through brief power outages. It doesn't protect data. A UPS with surge protection can reduce some power-related failures, but it doesn't replace backups.

What It Costs

NAS with RAID (one-time):

• Synology DS223 (2-bay): $300-350
• Synology DS423+ (4-bay): $500-600
• QNAP TS-464 (4-bay): $500-600
• Drives additional: $80-150/drive for 4-8TB drives

Cloud backup (monthly):

• Backblaze B2: $6/TB/month
• Backblaze Personal: $7/month unlimited (for single computer)

Combined approach:

• 4-bay NAS with 2 drives (RAID 1): $500-700 one-time
• Backblaze B2 for offsite backup: $12-18/month for 2-3TB
• Total first year: ~$650-850 | Year 2+: ~$144-216/year

What Can Go Wrong

You rely on RAID and lose data to deletion. You delete a file. It's gone from all RAID drives. If it's not in your backup, it's gone permanently.

You rely on RAID and ransomware hits. Ransomware encrypts your files. Because the files are on a NAS connected to your network, the ransomware encrypts all drives. Your "redundancy" becomes "redundant encryption." Restore from backup only.

You rely on RAID and the rebuild fails. Rebuilding a RAID array after a drive failure is risky. If the rebuild fails or another drive fails during rebuild, all data is lost. This happens in 2-5% of RAID rebuilds. No RAID level eliminates this risk.

You rely on RAID and your vendor goes out of business. If your NAS vendor disappears and you need to recover data, you might face compatibility issues. Cloud backups are vendor-neutral.

Vendor Questions (Copy/Paste)

1. "We have a NAS with RAID 5. Are our backups covered, or do we still need separate backup software?"
2. "If one drive fails and the rebuild takes 12 hours, are we protected if another drive fails during the rebuild?"
3. "What happens to our data if ransomware encrypts our NAS? Will our backup software protect us?"
4. "How do we back up the NAS itself? Can we restore to a different NAS if this one fails?"
5. "If we use cloud backup, can we restore individual files from the NAS backup, or only full system restores?"

Minimum Viable Implementation

1. If you have a NAS with RAID: Keep it. It's good for uptime. Add a cloud backup (Backblaze B2 or similar) that backs up the NAS to the cloud. Most NAS devices have built-in backup apps for this. Enable it this week.

2. If you have a server with internal drives: Add a backup solution. Veeam Community (free) + Backblaze B2 works for most small businesses. Or use a managed backup service if you don't want to manage it yourself.

3. If you have a single external drive for backups: Add a second external drive and rotate weekly. Keep one offsite at all times. Consider adding cloud backup for better protection.

4. Test a restore from your backup — not from your RAID. The next time you need to restore a file, restore from your backup solution, not from a RAID mirror. Prove the backup chain works.

When to Hire Help

• You have a NAS with more than 2TB of data and no cloud backup
• You've been relying on RAID without testing a restore from backup
• You've had a data loss incident
• You have databases on your NAS that need application-aware backup
• You're unsure whether your backup solution actually covers your NAS data

The thinking is simple: RAID keeps your server running. Backups let you recover from problems. You need both.

The Destin property management company now has a Synology NAS with RAID 5 AND Backblaze B2 cloud backup. Monthly restore tests. They calculated the $20/month cloud backup was worth it after losing six years of data.

They were right.