build 001f4800 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 232 | 0 skipped |
Service · infrastructure

Storage

Block, hyperconverged or scale-out, depending on what runs on it. The choice is settled by recovery time, not by capacity.

Topics capabilities · idf weight Storage storage 2.53 Data Management data-management 3.53
Vendors vendors · idf weight HPE hpe 2.45
04Solutions
02Capabilities
01Vendors
232Corpus

Three shapes, three use cases

Block storage for virtual infrastructure, attached over Fibre Channel SAN or iSCSI. Continuous availability here comes from synchronous replication with automatic failover.

HCI or dHCI delivers storage, compute and networking from the same box. The main advantage is integrated management, and the price is that compute and capacity grow together.

Scale-out on software-defined storage for file services over CIFS and NFS, or for object storage. Data can sit across several sites, which is how very high availability figures are reached.

What actually decides it

Rarely capacity. Usually the question of how quickly something has to be back when it is gone, and how many sites are involved in making that true. Both belong at the start rather than in the tender.

All-flash with NVMe is the answer to latency, not to availability. Those two get confused regularly.

Experts for this

Focus areas are not yet confirmed, so nobody is suggested here automatically. · 0 experts in corpus (n=232)

You might also like

service 0.78

Data Management

0.7 × caps 0.68 + 0.3 × vendor 1 = 0.78
post 0.59

RAID controllers

0.7 × caps 0.42 + 0.3 × vendor 1 = 0.59
post 0.56

The iTernity iCAS FS solution

0.7 × caps 0.58 + 0.3 × vendor 0.5 (unknown) = 0.56