Infinidat doubles all-flash array capacity in Infinibox SSA G4 F24 | Computer Weekly
Briefly

Infinidat doubles all-flash array capacity in Infinibox SSA G4 F24 | Computer Weekly
"Infinidat has expanded its Infinibox family to double the capacity of its biggest all-flash array while cutting its physical footprint. The move will see the Infinibox SSA G4 F24 now hold up to 33PB (petabytes), up from 17PB, while rack space is down from 14U to 11U. Even more density will be gained when Infinidat offers the option of quad-level cell (QLC) drives - in place of current triple-level cell (TLC) flash drives - for the G4 later this year."
"Infinidat has doubled G4 storage density mostly by squeezing in more drives of a higher capacity. Where previously in the 17PB iteration there were eight enclosures of 60 20TB drives, now there are eight enclosures of 78 24TB drives. This is also where the footprint shrink comes from. When Infinidat brings in QLC drives later this year, that capacity density will likely increase by a further 33%."
"Also new in this version of the G4 array is object storage natively delivered by the OS. That is in addition to existing file and block access. Object storage is an important and increasingly popular protocol. It's the predominant means of storage in the cloud and is often used for AI data because of its ability to scale well. Object storage will be included in the InfuzeOS and customers can turn it on per volume as they configure their system."
Infinidat increased the Infinibox SSA G4 F24 capacity from 17PB to 33PB and reduced rack space from 14U to 11U by using higher-capacity drives and denser enclosures. The G4 now uses eight enclosures of 78 24TB drives instead of 60 20TB drives. A forthcoming option to use QLC drives could raise capacity density by about 33% because QLC stores four bits per cell versus three for TLC, though QLC reduces drive lifespan and durability. InfuzeOS now includes native object storage alongside file and block access, and object can be enabled per volume.
Read at ComputerWeekly.com
Unable to calculate read time
[
|
]