|
|
|
|
|
by al_biglan
3436 days ago
|
|
caveat: I'm in the storage/file system industry. Everyone in the industry is looking at this. There is a great graph out there by one drive manufacturer that overlays $/GB for different HDDs and SSD technologies. For example, 15K and 10K RPM drives no longer are cost effective to produce. You are better going with SSDs. 7.2K will be next and some of the "lower end SSDs" are encroaching on that. 5.4K will likely live a longer time and if you keep "HDD as archive" you might project these drives to be alive in the foreseeable future (then factor in SMR, HAMR, then SMR plus HAMR.... and $/GB gets pretty cheap). After all, if you aren't keeping 100% of your data "in flight" keeping it at rest on a cheaper medium seems a sane thing. (Tape backup systems are _still_ for sale and in use...) Another interesting back of the envelope to do is look at Fab capacity for SSDs and compare it against HDD capacity sold. How much Fab capacity has to be available to serve the total storage demand? If there is a shortage of Fab plants, then a price premium for SSDs is easier to maintain (and may benefit some flash manufacturers in the short term to keep the price premium in place). Looking at the economics of building enough Fab capacity gets interesting quick. |
|
LTO seems to tick a lot of boxes in the archive business. I remember people trying to sell a MAID (massive array of idle disks) some years ago -- something like 100 disks in 4U of space. They came of blades that each held about 8 disks, and there were about 15 of them in a 4U row. With a controller in the middle it meant you could get somewhere in the region of 1000 disks in a rack.
The power consumption would be obscene, but that was fine, as the disks were kept idle, in fact the system could only power about 25% of the disks at once. The idea was you don't need access to the majority of files, and a 10 second latency when you do isn't going to hurt (far faster than tape)
At the same time tape manufacturers were pushing LTO-5 and LTFS, arguing that was the better solution for archive, and after a misstep with LTO6 (launching at 2.5T rather than 3T), LTO7 recovered.