Bulk Storage Array and Disk Shelf Supplier

Send the array model and we will confirm it before you buy. Shelf compatibility is not settled by the connector, and a shelf that plugs in physically can still be unsupported by the head it is attached to.

Three things decide it. The shelf generation, because one array family is commonly sold with two or three different shelf models across its life and they are not interchangeable. The controller firmware level, which sets how many shelves a head will address and sometimes which shelf models it recognises at all. And the drive sleds, because sled design changes between generations even within one manufacturer, so a Dell shelf and an HPE shelf take different caddies and so do two Dell generations.

GTR Supply quotes storage against the array model rather than a general description for exactly this reason. Tell us what is already racked and what you are adding to it, and we will tell you whether the shelf in front of you belongs with it.

A disk shelf is only usable if the parts that make it rackable and populatable are still with it, so the manifest states what is fitted rather than leaving you to assume.

The items that matter are the ones easiest to lose during a decommission. Drive sleds, one per populated bay. Blanking sleds for the empty bays, which are not cosmetic, because an enclosure with open bays loses its airflow path and runs the remaining drives hotter. Both power supplies rather than the one that happened to be seated. Fan modules. The expansion controllers on the rear, and the SAS cabling that links the shelf to the head or to the next shelf in the chain. Rails, and a bezel if you want one.

Tell us which of these you already hold. Buying sleds and rails separately afterwards routinely costs more than people expect, and it is the most common reason a cheap shelf turns out not to be cheap.

A JBOD is an enclosure of drives with no intelligence of its own. It presents the drives to whatever is attached to it, normally a host bus adapter in a server or a controller head, and the RAID, pooling and management all happen somewhere else. A SAN array has controllers that own the disks themselves, present logical volumes over a fabric such as Fibre Channel or iSCSI, and handle caching, tiering and redundancy internally.

The practical difference is where the intelligence and the entitlements live. A JBOD is simple and effectively vendor neutral once you have a supported adapter. An array head carries the firmware, the licensing and the vendor relationship, which is why heads and JBODs behave very differently once they reach the second hand market.

GTR Supply supplies both. Tell us what the storage is feeding and how you intend to present it, and we will say which of the two actually fits.

Every unit is tested and graded before it ships, and every drive is securely wiped. A certificate of data destruction is available on request.

Wiping matters more here than in almost any other category, because an array is where an organisation deliberately concentrated its data rather than where some of it happened to end up. A populated shelf pulled from a production array has held real business data on every drive in it, not on one of them.

Each drive is therefore wiped individually rather than treated as part of a pool, and a drive that cannot be verified as clean does not ship as a drive. Test results and condition grades go on the manifest that travels with the lot, so a populated shelf is described drive by drive rather than as a bay count.

If you need certificates against a specific serial range for your own compliance records, ask GTR Supply at quote stage rather than after delivery.