# Big server farms -- what do they use for storage?

**URL:** <https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074>\
**Category:** Factual Questions\
**Created:** [February 17, 2020, 2:44pm UTC](https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074 "2020-02-17T14:44:49Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![snfaulkner](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/snfaulkner/32/433_2.png) [@snfaulkner](https://boards.straightdope.com/u/snfaulkner)\
**Post date:** [February 18, 2020, 1:31am UTC](https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074/21 "2020-02-18T01:31:28Z")

</div>

> [@FinsToTheLeft](#):
>
> Just to clarify it’s not SCSI vs SSD. The three main protocols today are SAS, SATA, and NVMe. Hard drives - 2.5” or 3.5” - use one of the first two. SSD can use any one of them. SAS and SATA use the same physical connector but SATA only controllers can only use SATA drives, SAS controllers can use both. SSDs also come in M.2 interfaces.
> 
> The big advantage to SAS is that they can connect to two interfaces at once via a single connector. This allows for redundant controllers to give you highly available access to the disk if a controller or cable fail, which is highly advantageous in a data centre.

Dual channel drives are used in big SANs which have dual controllers for increased availability even if/when a controller dies. Then the B controller will take over all the traffic while you swap out A controller.

To address other various bits upthread…  
As a data center tech, a big part of job is to swap out bad drives when they go amber. SSD’s CAN just die without warning, but as bad as they used to be. Traditional drives can too, but not as often.

As better tech becomes available, generally we’ll either just replace one disk at a time, or just buy a whole new system and retire the old. Not much middle of the road, upgrading a current system a shelf at a time thing.

The trend is absolutely going towards more 2.5" drives. Mostly SAS. Some FC. Depends on what that system is needed for. Lots of SANs will have different tiers. A few loops/shelves of super fast SSD drives, a bunch of 10 or 15k rpm drive loops/shelves, tons of older/cheaper 3.5" high capacity but slower drives, then sometimes even still tape.

Individual servers can have SATA drives too. Usually the cheapo systems that aren’t mission critical.

---

<div class="post-metadata">

**Author:** ![ftg](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ftg/32/2801_2.png) [@ftg](https://boards.straightdope.com/u/ftg)\
**Post date:** [February 18, 2020, 2:46pm UTC](https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074/22 "2020-02-18T14:46:43Z")

</div>

> [@FinsToTheLeft](#):
>
> Just to clarify it’s not SCSI vs SSD. The three main protocols today are SAS, SATA, and NVMe …
> 
> The big advantage to SAS is that they can connect to two interfaces at once via a single connector. This allows for redundant controllers to give you highly available access to the disk if a controller or cable fail, which is highly advantageous in a data centre.

There are a variety of SAS connection standards, but the most common one is sort of like the SATA data and power connectors in one piece. You can’t connect standard SATA connectors to such a SAS drive (and of course it doesn’t do you any good if you could).

Note that the latest SAS-4 standard has speeds of 22.5 Gbit/s. Another note is that SAS is full duplex and SATA is half-duplex. Plus quite a few other nice features.

---

<div class="post-metadata">

**Author:** ![md2000](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@md2000](https://boards.straightdope.com/u/md2000)\
**Post date:** [February 18, 2020, 10:32pm UTC](https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074/23 "2020-02-18T22:32:49Z")

</div>

An important point to note - by running RAID - multiple disks with data spread across them - the overall throughput is faster. SO SAN units and large single servers tend to use RAID (redundant array of disks) and spread the data across them. When reading or writing, a matching sector is read from each of 3 or more disks. One of these sectors is “redundant”, a checksum to ensure that the data is consistent - this check can be done by dedicated hardware so does not significantly slow down the overall throughput. So by reading data from multiple disks simultaneously, the system can read far fasted than a simple PC reading a single disk. Checksum means the data is far more reliable - and if a disk fails, a replacement can be rewritten with the correct content from the surviving disks to restore redundancy. High end disk systems also have better monitoring of disks for reliability problems, giving advanced warning of impending failure.

---

<div class="post-metadata">

**Author:** ![joema](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@joema](https://boards.straightdope.com/u/joema)\
**Post date:** [February 18, 2020, 11:09pm UTC](https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074/24 "2020-02-18T23:09:31Z")

</div>

> [@Musicat](#):
>
> The big server farms serving The Cloud – what do they use for primary data storage?
> 
> Do they merely install thousands of 3.5" hard drives, the kind that work in desktop PC’s? Or is there a larger form-factor just made for server farms?

They use thousands of 3.5" SAS hard drives, packed tightly in special racks. Here is a frame grab of a single drawer of 8TB Seagate SAS drives, total of 42 drives per drawer (336 TB). You can have maybe 8 drawers per rack and of course multiple racks. At 8TB per drive that’s about 2,600 TB (2.6 petabytes) per rack, unformatted capacity.

[![](https://photos.smugmug.com/photos/i-9DmFsx7/0/ac475c70/X2/i-9DmFsx7-X2.jpg) ](https://photos.smugmug.com/photos/i-9DmFsx7/0/ac475c70/X2/i-9DmFsx7-X2.jpg)

3.5" SAS drives are available in 16TB now, and I think 20TB is close. So all the above numbers could be multiplied by 2x using the latest drives – 672 TB per drawer, or 5,200 TB (5.2 petabytes) per rack, unformatted.

Samsung’s latest high-density “NF1” SSD form factor allows up to 567 TB per rack of pure SSD storage: [Server Scalability Enhanced with NF1 SSD | Samsung Semiconductor Global](https://www.samsung.com/semiconductor/newsroom/tech-leadership/server-scalability-enhanced-with-nf1-ssd/)

---

<div class="post-metadata">

**Author:** ![Melbourne](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@Melbourne](https://boards.straightdope.com/u/Melbourne)\
**Post date:** [February 19, 2020, 9:07am UTC](https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074/25 "2020-02-19T09:07:26Z")

</div>

> [@md2000](#):
>
> An important point to note - by running RAID - multiple disks with data spread across them - the overall throughput is faster. .

RAID array are typically slower than individual disks.

---

<div class="post-metadata">

**Author:** ![FinsToTheLeft](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/finstotheleft/32/2930_2.png) [@FinsToTheLeft](https://boards.straightdope.com/u/FinsToTheLeft)\
**Post date:** [February 19, 2020, 10:50am UTC](https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074/26 "2020-02-19T10:50:30Z")

</div>

> [@Melbourne](#):
>
> RAID array are typically slower than individual disks.

Not in my world. RAID 5 may be slower for writes than other configurations, but the throughput (IOPS) is higher. I typically run volumes of 12x 10K SAS disks in RAID 10 and I get roughly 6x the IOPS of a single disk.

---

<div class="post-metadata">

**Author:** ![Doug\_K](https://avatars.discourse-cdn.com/v4/letter/d/b5ac83/32.png) [@Doug\_K](https://boards.straightdope.com/u/Doug_K)\
**Post date:** [February 19, 2020, 1:43pm UTC](https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074/27 "2020-02-19T13:43:59Z")

</div>

Here’s a video tour one of Google’s datacenters:

[![](https://img.youtube.com/vi/XZmGGAbHqa0/hqdefault.jpg "Inside a Google data center") ](https://www.youtube.com/watch?v=XZmGGAbHqa0)

---

<div class="post-metadata">

**Author:** ![Tim\_T-Bonham.net](https://avatars.discourse-cdn.com/v4/letter/t/46a35a/32.png) [@Tim\_T-Bonham.net](https://boards.straightdope.com/u/Tim_T-Bonham.net)\
**Post date:** [February 19, 2020, 7:10pm UTC](https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074/28 "2020-02-19T19:10:28Z")

</div>

> [@Melbourne](#):
>
> RAID array are typically slower than individual disks.

No, that’s a generalization that isn’t always true. like saying Ford trucks are slower than Chevy trucks.

Various types of RAID arrays are made, for various tasks.

Big server farms have arrays to hold vast amounts of data, so using cheap & low-power using disks is more important than the fastest speed.

Other arrays are for super important data, so disk mirroring/recover-ability and highest reliability are most important.

Arrays can be designed for fast response time. (But now, SSD’s are taking over in that area.)

So RAID arrays can be designed for different purposes, and response speed is just one of the parameters the designer can adjust.

[Previous page](https://boards.straightdope.com/t/big-server-farms-what-do-they-use-for-storage/848074.md?page=1)
