DE · EN

Call us

apiVersion: soultec.ch/v1kind: Servicemetadata: name: storage locale: en labels: group: infrastructure capability/storage: 2.62 capability/data-management: 2.87 vendor/hpe: 2.04 annotations: source: src/content/services/en/storage.md route: /en/services/storage/ schema: /nerd/schema/services.json markdown: /en/services/storage.mdspec: title: Storage group: infrastructure order: 9 tags: [storage, data-management] vendors: [hpe] summary: >- Block, hyperconverged or scale-out, depending on what runs on it. The choice is settled by recovery time, not by capacity. photoNeed: >- Storage hardware being handled: a disk shelf open, or a drive being seated, hands visible stub: false draft: false sections: - heading:

Three shapes, three use cases

body: | **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. - heading:

What actually decides it

body: | 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.status: corpus: 267 solutions: - {ref: solutions/hpe/hpe-data-management, score: 1.00} - {ref: solutions/hpe/hpe-storage, score: 1.00} - {ref: solutions/hpe, score: 0.65} - {ref: solutions/hpe/hpe-dhci, score: 0.57} alsoLike: - {ref: services/data-management, score: 0.76} - {ref: posts/raid-controller, score: 0.63} - {ref: experts/oliver-erismann, score: 0.59} experts: - {ref: experts/oliver-erismann, score: 0.59} - {ref: experts/karl-widmer, score: 0.53} - {ref: experts/dario-doerflinger, score: 0.45}

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "storage", "locale": "en", "labels": { "group": "infrastructure", "capability/storage": "2.62", "capability/data-management": "2.87", "vendor/hpe": "2.04" }, "annotations": { "source": "src/content/services/en/storage.md", "route": "/en/services/storage/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/storage.md" } }, "spec": { "title": "Storage", "group": "infrastructure", "order": 9, "tags": [ "storage", "data-management" ], "vendors": [ "hpe" ], "summary": "Block, hyperconverged or scale-out, depending on what runs on it. The choice is settled by recovery time, not by capacity.", "photoNeed": "Storage hardware being handled: a disk shelf open, or a drive being seated, hands visible", "stub": false, "draft": false }, "sections": [ { "heading": "

Three shapes, three use cases

", "body": "**Block storage** for virtual infrastructure, attached over Fibre Channel SAN or iSCSI.\nContinuous availability here comes from synchronous replication with automatic failover.\n\n**HCI or dHCI** delivers storage, compute and networking from the same box. The main\nadvantage is integrated management, and the price is that compute and capacity grow\ntogether.\n\n**Scale-out on software-defined storage** for file services over CIFS and NFS, or for\nobject storage. Data can sit across several sites, which is how very high availability\nfigures are reached." }, { "heading": "

What actually decides it

", "body": "Rarely capacity. Usually the question of how quickly something has to be back when it is\ngone, and how many sites are involved in making that true. Both belong at the start rather\nthan in the tender.\n\nAll-flash with NVMe is the answer to latency, not to availability. Those two get confused\nregularly." } ], "status": { "corpus": 267, "solutions": [ { "ref": "solutions/hpe/hpe-data-management", "score": "1.00" }, { "ref": "solutions/hpe/hpe-storage", "score": "1.00" }, { "ref": "solutions/hpe", "score": "0.65" }, { "ref": "solutions/hpe/hpe-dhci", "score": "0.57" } ], "alsoLike": [ { "ref": "services/data-management", "score": "0.76" }, { "ref": "posts/raid-controller", "score": "0.63" }, { "ref": "experts/oliver-erismann", "score": "0.59" } ], "experts": [ { "ref": "experts/oliver-erismann", "score": "0.59" }, { "ref": "experts/karl-widmer", "score": "0.53" }, { "ref": "experts/dario-doerflinger", "score": "0.45" } ] }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "storage"locale = "en"[metadata.labels]group = "infrastructure""capability/storage" = "2.62""capability/data-management" = "2.87""vendor/hpe" = "2.04"[metadata.annotations]source = "src/content/services/en/storage.md"route = "/en/services/storage/"schema = "/nerd/schema/services.json"markdown = "/en/services/storage.md"[spec]title = "Storage"group = "infrastructure"order = 9tags = ["storage", "data-management"]vendors = ["hpe"]summary = "Block, hyperconverged or scale-out, depending on what runs on it. The choice is settled by recovery time, not by capacity."photoNeed = "Storage hardware being handled: a disk shelf open, or a drive being seated, hands visible"stub = falsedraft = false[[sections]]heading = "

Three shapes, three use cases

"body = '''**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 mainadvantage is integrated management, and the price is that compute and capacity growtogether.**Scale-out on software-defined storage** for file services over CIFS and NFS, or forobject storage. Data can sit across several sites, which is how very high availabilityfigures are reached.'''[[sections]]heading = "

What actually decides it

"body = '''Rarely capacity. Usually the question of how quickly something has to be back when it isgone, and how many sites are involved in making that true. Both belong at the start ratherthan in the tender.All-flash with NVMe is the answer to latency, not to availability. Those two get confusedregularly.'''[status]corpus = 267[[status.solutions]]ref = "solutions/hpe/hpe-data-management"score = "1.00"[[status.solutions]]ref = "solutions/hpe/hpe-storage"score = "1.00"[[status.solutions]]ref = "solutions/hpe"score = "0.65"[[status.solutions]]ref = "solutions/hpe/hpe-dhci"score = "0.57"[[status.alsoLike]]ref = "services/data-management"score = "0.76"[[status.alsoLike]]ref = "posts/raid-controller"score = "0.63"[[status.alsoLike]]ref = "experts/oliver-erismann"score = "0.59"[[status.experts]]ref = "experts/oliver-erismann"score = "0.59"[[status.experts]]ref = "experts/karl-widmer"score = "0.53"[[status.experts]]ref = "experts/dario-doerflinger"score = "0.45"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>storage</name> <locale>en</locale> <labels> <group>infrastructure</group> <entry key="capability/storage">2.62</entry> <entry key="capability/data-management">2.87</entry> <entry key="vendor/hpe">2.04</entry> </labels> <annotations> <source>src/content/services/en/storage.md</source> <route>/en/services/storage/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/storage.md</markdown> </annotations> </metadata> <spec> <title>Storage</title> <group>infrastructure</group> <order>9</order> <tags> <item>storage</item> <item>data-management</item> </tags> <vendors> <item>hpe</item> </vendors> <summary>Block, hyperconverged or scale-out, depending on what runs on it. The choice is settled by recovery time, not by capacity.</summary> <photoNeed>Storage hardware being handled: a disk shelf open, or a drive being seated, hands visible</photoNeed> <stub>false</stub> <draft>false</draft> </spec> <sections> <section> <heading>

Three shapes, three use cases

</heading> <body>**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 mainadvantage is integrated management, and the price is that compute and capacity growtogether.**Scale-out on software-defined storage** for file services over CIFS and NFS, or forobject storage. Data can sit across several sites, which is how very high availabilityfigures are reached. </body> </section> <section> <heading>

What actually decides it

</heading> <body>Rarely capacity. Usually the question of how quickly something has to be back when it isgone, and how many sites are involved in making that true. Both belong at the start ratherthan in the tender.All-flash with NVMe is the answer to latency, not to availability. Those two get confusedregularly. </body> </section> </sections> <status> <corpus>267</corpus> <solutions> <item> <ref>solutions/hpe/hpe-data-management</ref> <score>1.00</score> </item> <item> <ref>solutions/hpe/hpe-storage</ref> <score>1.00</score> </item> <item> <ref>solutions/hpe</ref> <score>0.65</score> </item> <item> <ref>solutions/hpe/hpe-dhci</ref> <score>0.57</score> </item> </solutions> <alsoLike> <item> <ref>services/data-management</ref> <score>0.76</score> </item> <item> <ref>posts/raid-controller</ref> <score>0.63</score> </item> <item> <ref>experts/oliver-erismann</ref> <score>0.59</score> </item> </alsoLike> <experts> <item> <ref>experts/oliver-erismann</ref> <score>0.59</score> </item> <item> <ref>experts/karl-widmer</ref> <score>0.53</score> </item> <item> <ref>experts/dario-doerflinger</ref> <score>0.45</score> </item> </experts> </status></manifest>

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 Storage 2.62 Data Management 2.87

Vendors HPE 2.04

04Solutions

02Capabilities

01Vendors

267Corpus

photograph wantedStorage hardware being handled: a disk shelf open, or a drive being seated, hands visible

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.