JBOD vs RAID: Storage Layouts for Small Office Servers

A small office server rarely fails all at once. One drive dies, and the question is what the other drives were doing about it. JBOD and RAID are the two common answers: one leaves every drive on its own, the other spreads data so a single failure does not take the share down.

What JBOD Means

JBOD stands for just a bunch of disks. Wikipedia's definition is an architecture where multiple drives are exposed as individual devices. You can use them independently, or combine them into one logical volume with a volume manager such as LVM or mdadm, or with a spanning filesystem such as btrfs. Windows calls the combined version a spanned volume.

That second option is where tickets start. A spanned volume adds the capacities together but provides no redundancy, so one failed drive fails the whole volume. It does not speed anything up either: unlike RAID 0, the capacity simply adds up and the speed does not multiply. Left as separate drives, JBOD is safer in one narrow way: the drive that dies takes only its own data with it.

The word also names hardware. A JBOD enclosure is a box of drive bays that presents each drive to the server as-is. An r/homelab thread from September 2025 asks what people use for JBOD enclosures and why so few cheap ones turn up secondhand, which tells you how common the box is.

The RAID Levels at a Glance

RAID, redundant array of independent disks, spreads data across drives so the array can survive a failure. The numbers only name layouts. They do not signify performance, reliability or rank, per the SNIA standard Wikipedia cites. Five layouts cover almost every small server.

Parity layouts trade space for protection. RAID 5 gives up one drive's worth of capacity and RAID 6 gives up two, which is why they suit file servers with four or more drives. Mirrors give up half but stay simple, which is why RAID 1 is the usual answer for a two-drive box. RAID 10 mirrors first and stripes second, so it reads and writes fast and recovers by copying one mirror.

PowerCert's animated walkthrough covers RAID 0, 1, 5 and 10 in a few minutes and is a good one to send a new technician.

As a rule of thumb, take RAID 1 for two drives, RAID 6 for four or more drives holding files, and RAID 10 when the workload writes constantly. Treat that as practitioner guidance, not a standard. Pair any of them with monitoring, because an array that runs degraded for weeks looks fine until the next drive goes. Our guide to infrastructure monitoring covers what to alert on.

Storage Spaces Instead of a Controller

Windows Server can do the same job without a RAID card. Storage Spaces pools physical drives into one logical pool and carves virtual disks out of it, and Microsoft describes it as conceptually similar to RAID. It offers three resiliency types per virtual disk: simple, mirror and parity.

A simple space stripes data with no resiliency, so a single drive failure loses data. It suits scratch space only. A mirror space keeps two or three copies: two-way survives one failure and keeps 50 percent of raw capacity, and three-way survives two failures and keeps 33.3 percent. A parity space survives one failure (single) or two (dual) with better space use, at lower write speed. Microsoft's pages are for Windows Server 2016 through 2025 and were checked in October 2026.

Microsoft also notes that Storage Spaces is typically used with standalone servers or clusters attached to external JBOD enclosures over SAS. That is the practical link between the two words in the title: a JBOD enclosure supplies the drives, and Storage Spaces supplies the redundancy that the enclosure leaves out. The drives reach Windows as plain drives, so there is no controller configuration to lose.

RAID Is Not a Backup

Wikipedia puts it plainly: most RAID levels protect well against hardware defects and read errors, but not against fire or water, or against user error, software malfunction and malware. For valuable data, RAID is one building block of a larger recovery scheme and cannot replace a backup plan.

The controller is its own single point of failure. In early February 2026 an r/sysadmin poster reported two Dell servers at different clients dropping their RAID controller and array on the same night. A hard power cycle and clearing the stuck write cache brought the arrays back, and the cause stayed unknown. Replies suspected firmware or update behavior, and one admin described a new server that reported every drive as failed until the controller was reseated and the configuration re-imported. The array came back each time, but only because nobody had to trust it.

Put a copy somewhere the array cannot reach. Our guide to backup solutions for small business covers what to buy.

Then decide what each run copies. Incremental and differential backups compares the two main schemes.

For the copy an attacker cannot delete, read about immutable backups.

Then test the restore. Disaster recovery testing is where plans find out they have a gap.

Picking a Layout

Start from what the data is worth and how fast it must come back.

• Scratch, cache or rebuildable data: JBOD, RAID 0 or a simple space. Speed and capacity matter, and a failure costs a rebuild.
• Two drives, small office files: RAID 1 or a two-way mirror, plus a backup.
• Four or more drives, a file server: RAID 6 or dual parity, plus a backup.
• Write-heavy workloads such as a Hyper-V host: RAID 10 or a mirror, plus a backup.

Every row ends the same way, and the ticket log below shows why. OpenFrame can run Get-PhysicalDisk and Get-StoragePool across a client's devices and collect the output, so degraded arrays and unhealthy drives land in one list.

The Short Version

JBOD keeps every drive separate, so a failure costs one drive, or the whole volume if the drives are spanned. RAID spreads data so an array survives one or two failed drives, and Storage Spaces does the same in software. None of them is a backup. Choose the layout for the data's value, then add the copy that survives the controller, the user and the malware.

FAQ

What does JBOD stand for?

JBOD stands for just a bunch of disks. It means several drives presented to the server as individual devices, with no mirroring or parity. They can be used separately or joined into one spanned volume, which gives more capacity but no protection.

Does JBOD protect against drive failure?

No. JBOD has no redundancy. With separate drives, a failure loses that drive's data. With a spanned volume, one failed drive fails the whole volume, and the capacity adds up without the speed multiplying.

Which RAID level suits a small office server?

RAID 1 for two drives, and RAID 6 or RAID 10 for four or more, depending on whether the workload is mostly storage or constant writes. Storage Spaces mirror and parity types do the same job in Windows. Add a backup in every case.

Is RAID a backup?

No. RAID protects against drive failure and read errors, not against fire, water, deletion, software faults or malware. Wikipedia states that for valuable data, RAID is one building block and cannot replace a backup plan.