JBOD Enclosures Explained: What They Are and What You Need
A JBOD is the simplest way to add a lot of drive bays to a server, and buyers frequently confuse it with a storage array. This covers what a JBOD actually is, what it needs on the server side, and when it is the right answer.
What is a JBOD enclosure?
Just a bunch of disks. A chassis with drive bays, power supplies, fans and a SAS expander, and nothing else.
There is no RAID controller in a JBOD. It does not create arrays, does not manage redundancy, and has no intelligence about the drives beyond presenting them. It connects to a server over a SAS cable, and the server sees every drive in the enclosure as if it were plugged in directly.
That is the whole product. Everything clever happens on the server.
JBOD vs storage array: what is the difference?
Where the intelligence lives.
A storage array has its own controllers, its own RAID, its own management, and presents finished volumes to servers over a network or fabric. The array is a system in its own right. Our storage architecture guide covers where arrays fit.
A JBOD presents raw drives to one server (or two, with dual expanders). The server’s controller or software does all the work.
Consequences. A JBOD is much cheaper than an array. A JBOD depends entirely on the server it is attached to. And a JBOD is the natural home for software-defined storage — ZFS, Storage Spaces, Ceph and similar — which want raw drives rather than controller-managed volumes.
What do I need on the server to use a JBOD?
Three things.
A SAS HBA with an external port. The JBOD connects to the server via external SAS (SFF-8088 or SFF-8644 connectors, depending on generation). The HBA needs an external port, and it needs enough bandwidth for the drive count. Our HBA guide covers the internal equivalent; the external versions follow the same rules.
The right cable. External SAS cables come in several connector types and the JBOD and HBA must match. Our cables guide covers the connector families.
Software that manages the drives. Either a RAID controller with an external port (which then manages the JBOD’s drives as an array) or software-defined storage on the server. A JBOD behind an HBA with no software layer is just loose drives.
Single expander vs dual expander
The specification that decides whether the JBOD can be made highly available.
Single expander means one path from the server to the drives. Simpler, cheaper, and if the expander or the cable fails, every drive disappears.
Dual expander means two independent paths, which can connect to two HBAs in one server or to two separate servers. With dual-port SAS drives, that gives a path failure something to fail over to. Our dual-port SAS guide covers what the drives need to support this.
For a single-server capacity expansion, single expander is fine. For anything where the JBOD holds data that must stay available through a component failure, dual.
Can I daisy-chain JBODs?
Usually, up to a limit.
Most JBODs have an output port that connects to the next enclosure, allowing several to hang off one HBA port. The limits are the HBA’s maximum device count, the bandwidth of the single link shared across all drives, and the vendor’s stated chain depth.
Two practical points. Bandwidth is shared across the chain, so a long chain of fast drives on one link will bottleneck. And a failure early in the chain takes down everything after it, which is an argument for shorter chains or dual paths where availability matters.
When is a JBOD the right choice?
Four situations.
Capacity expansion for a server that has run out of bays. The cheapest way to add drives.
Software-defined storage that wants raw drives.
Backup targets and archive, where the server is doing the work and the JBOD just holds disks.
Building a storage server from parts, where a server plus a JBOD is a fraction of the cost of an equivalent array. Our build versus buy guide covers that decision.
When it is not: anywhere you need storage that multiple servers share over a network, storage that survives the server failing, or storage with its own management and support. Those need an array or a NAS.
And one thing to size: JBOD drive bays need carriers, which are enclosure-specific and frequently not included with used units. Our caddies guide covers this.
Frequently asked questions
Does a JBOD have a RAID controller?
No. A JBOD is drive bays, power, fans and a SAS expander. It presents raw drives to the server, and the server’s controller or software does all the RAID and management.
What is the difference between a JBOD and a NAS?
A NAS is a complete system with its own operating system, sharing storage over the network. A JBOD is just drive bays attached to a server by SAS cable, with no intelligence of its own. A JBOD plus a server can become a NAS; a JBOD alone cannot.
What do I need to connect a JBOD to a server?
A SAS HBA or RAID controller with an external port, the correct external SAS cable for both connector types, and software on the server to manage the drives. Without the software layer, a JBOD is just loose drives.
Can two servers share a JBOD?
With a dual-expander JBOD and dual-port SAS drives, two servers can each have a path to the drives. Whether they can both use them at once depends on the software; it is a failover or clustering configuration, not simple sharing.
How many JBODs can I chain together?
Up to the HBA’s device limit and the vendor’s stated chain depth, but bandwidth is shared across the chain and a failure early in the chain takes down everything after it. Shorter chains or dual paths where availability matters.
Do used JBODs come with drive caddies?
Frequently not. Carriers are enclosure-specific and are often removed before resale. Confirm the count included and budget for the rest.
Tell us the server model, HBA and how many drives you need to add, and we will confirm the JBOD, cable and carriers together.
