DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get service/storage -o yaml$ soultec get service/storage -o json$ soultec get service/storage -o toml$ soultec get service/storage -o xml$ python3 storage.pyPS> ./storage.ps1$ go run storage.go$ node storage.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: storage locale: en labels: group: infrastructure capability/storage: 2.36 capability/data-management: 2.87 vendor/hpe: 1.99 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 audience: [enterprise, provider] 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. As a backup target, object storage adds the part that matters: **S3 Object Lock** protects what has been written from being changed, including when production credentials are already compromised. Spread across several sites, an architecture like that reaches data availability of up to 14 nines. - heading:

What actually decides it

body: | Usually the recovery time and the number of sites involved, less often the capacity. We settle those two values at the start, because they determine the shape of the build. All-flash with NVMe brings the latency down. It does nothing for availability; replication and failover do that. Hybrid systems with flash and disk remain the right choice where capacity matters more than latency.status: corpus: 315 solutions: - {ref: solutions/hpe/hpe-storage/alletra-storage-mp-b10000, score: 1.00} - {ref: solutions/hpe/hpe-storage/alletra-storage-mp-x10000, score: 1.00} - {ref: solutions/hpe/hpe-storage/greenlake-for-file-storage, score: 1.00} - {ref: solutions/hpe/hpe-data-management, score: 1.00} alsoLike: - {ref: solutions/hpe/hpe-storage, score: 1.00} - {ref: services/data-management, score: 0.77} - {ref: solutions/hpe, score: 0.67} experts: - {ref: experts/karl-widmer, score: 0.49} - {ref: experts/fabian-faessler, score: 0.47} - {ref: experts/patrick-pletscher, score: 0.46} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "storage", "locale": "en", "labels": { "group": "infrastructure", "capability/storage": 2.36, "capability/data-management": 2.87, "vendor/hpe": 1.99 }, "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", "audience": [ "enterprise", "provider" ], "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.\n\nAs a backup target, object storage adds the part that matters: **S3 Object Lock** protects\nwhat has been written from being changed, including when production credentials are already\ncompromised. Spread across several sites, an architecture like that reaches data\navailability of up to 14 nines." }, { "heading": "

What actually decides it

", "body": "Usually the recovery time and the number of sites involved, less often the capacity. We\nsettle those two values at the start, because they determine the shape of the build.\n\nAll-flash with NVMe brings the latency down. It does nothing for availability; replication\nand failover do that.\n\nHybrid systems with flash and disk remain the right choice where capacity matters more than\nlatency." } ] }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-storage/alletra-storage-mp-b10000", "score": "1.00" }, { "ref": "solutions/hpe/hpe-storage/alletra-storage-mp-x10000", "score": "1.00" }, { "ref": "solutions/hpe/hpe-storage/greenlake-for-file-storage", "score": "1.00" }, { "ref": "solutions/hpe/hpe-data-management", "score": "1.00" } ], "alsoLike": [ { "ref": "solutions/hpe/hpe-storage", "score": "1.00" }, { "ref": "services/data-management", "score": "0.77" }, { "ref": "solutions/hpe", "score": "0.67" } ], "experts": [ { "ref": "experts/karl-widmer", "score": "0.49" }, { "ref": "experts/fabian-faessler", "score": "0.47" }, { "ref": "experts/patrick-pletscher", "score": "0.46" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "storage"locale = "en"[metadata.labels]group = "infrastructure""capability/storage" = 2.36"capability/data-management" = 2.87"vendor/hpe" = 1.99[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"audience = ["enterprise", "provider"]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[[spec.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.As a backup target, object storage adds the part that matters: **S3 Object Lock** protectswhat has been written from being changed, including when production credentials are alreadycompromised. Spread across several sites, an architecture like that reaches dataavailability of up to 14 nines.'''[[spec.sections]]heading = "

What actually decides it

"body = '''Usually the recovery time and the number of sites involved, less often the capacity. Wesettle those two values at the start, because they determine the shape of the build.All-flash with NVMe brings the latency down. It does nothing for availability; replicationand failover do that.Hybrid systems with flash and disk remain the right choice where capacity matters more thanlatency.'''[status]corpus = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/hpe/hpe-storage/alletra-storage-mp-b10000"score = "1.00"[[status.solutions]]ref = "solutions/hpe/hpe-storage/alletra-storage-mp-x10000"score = "1.00"[[status.solutions]]ref = "solutions/hpe/hpe-storage/greenlake-for-file-storage"score = "1.00"[[status.solutions]]ref = "solutions/hpe/hpe-data-management"score = "1.00"[[status.alsoLike]]ref = "solutions/hpe/hpe-storage"score = "1.00"[[status.alsoLike]]ref = "services/data-management"score = "0.77"[[status.alsoLike]]ref = "solutions/hpe"score = "0.67"[[status.experts]]ref = "experts/karl-widmer"score = "0.49"[[status.experts]]ref = "experts/fabian-faessler"score = "0.47"[[status.experts]]ref = "experts/patrick-pletscher"score = "0.46"

<?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.36</entry> <entry key="capability/data-management">2.87</entry> <entry key="vendor/hpe">1.99</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> <audience> <item>enterprise</item> <item>provider</item> </audience> <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> <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.As a backup target, object storage adds the part that matters: **S3 Object Lock** protectswhat has been written from being changed, including when production credentials are alreadycompromised. Spread across several sites, an architecture like that reaches dataavailability of up to 14 nines. </body> </section> <section> <heading>

What actually decides it

</heading> <body>Usually the recovery time and the number of sites involved, less often the capacity. Wesettle those two values at the start, because they determine the shape of the build.All-flash with NVMe brings the latency down. It does nothing for availability; replicationand failover do that.Hybrid systems with flash and disk remain the right choice where capacity matters more thanlatency. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/hpe/hpe-storage/alletra-storage-mp-b10000</ref> <score>1.00</score> </item> <item> <ref>solutions/hpe/hpe-storage/alletra-storage-mp-x10000</ref> <score>1.00</score> </item> <item> <ref>solutions/hpe/hpe-storage/greenlake-for-file-storage</ref> <score>1.00</score> </item> <item> <ref>solutions/hpe/hpe-data-management</ref> <score>1.00</score> </item> </solutions> <alsoLike> <item> <ref>solutions/hpe/hpe-storage</ref> <score>1.00</score> </item> <item> <ref>services/data-management</ref> <score>0.77</score> </item> <item> <ref>solutions/hpe</ref> <score>0.67</score> </item> </alsoLike> <experts> <item> <ref>experts/karl-widmer</ref> <score>0.49</score> </item> <item> <ref>experts/fabian-faessler</ref> <score>0.47</score> </item> <item> <ref>experts/patrick-pletscher</ref> <score>0.46</score> </item> </experts> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "storage", "locale": "en", "labels": { "group": "infrastructure", "capability/storage": 2.36, "capability/data-management": 2.87, "vendor/hpe": 1.99, }, "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", "audience": ["enterprise", "provider"], "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.\n" "Continuous 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\n" "advantage is integrated management, and the price is that compute and capacity grow\n" "together.\n" "\n" "**Scale-out on software-defined storage** for file services over CIFS and NFS, or for\n" "object storage. Data can sit across several sites, which is how very high availability\n" "figures are reached.\n" "\n" "As a backup target, object storage adds the part that matters: **S3 Object Lock** protects\n" "what has been written from being changed, including when production credentials are already\n" "compromised. Spread across several sites, an architecture like that reaches data\n" "availability of up to 14 nines." ), }, { "heading": "

What actually decides it

", "body": ( "Usually the recovery time and the number of sites involved, less often the capacity. We\n" "settle those two values at the start, because they determine the shape of the build.\n" "\n" "All-flash with NVMe brings the latency down. It does nothing for availability; replication\n" "and failover do that.\n" "\n" "Hybrid systems with flash and disk remain the right choice where capacity matters more than\n" "latency." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-storage/alletra-storage-mp-b10000", "score": "1.00", }, { "ref": "solutions/hpe/hpe-storage/alletra-storage-mp-x10000", "score": "1.00", }, { "ref": "solutions/hpe/hpe-storage/greenlake-for-file-storage", "score": "1.00", }, { "ref": "solutions/hpe/hpe-data-management", "score": "1.00", }, ], "alsoLike": [ { "ref": "solutions/hpe/hpe-storage", "score": "1.00", }, { "ref": "services/data-management", "score": "0.77", }, { "ref": "solutions/hpe", "score": "0.67", }, ], "experts": [ { "ref": "experts/karl-widmer", "score": "0.49", }, { "ref": "experts/fabian-faessler", "score": "0.47", }, { "ref": "experts/patrick-pletscher", "score": "0.46", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Service' metadata = [ordered]@{ name = 'storage' locale = 'en' labels = [ordered]@{ group = 'infrastructure' 'capability/storage' = 2.36 'capability/data-management' = 2.87 'vendor/hpe' = 1.99 } annotations = [ordered]@{ source = 'src/content/services/en/storage.md' route = '/en/services/storage/' schema = '/nerd/schema/services.json' markdown = '/en/services/storage.md' } } spec = [ordered]@{ title = 'Storage' group = 'infrastructure' audience = @('enterprise', 'provider') 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 = @( [ordered]@{ 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.As a backup target, object storage adds the part that matters: **S3 Object Lock** protectswhat has been written from being changed, including when production credentials are alreadycompromised. Spread across several sites, an architecture like that reaches dataavailability of up to 14 nines.'@ } [ordered]@{ heading = '

What actually decides it

' body = @'Usually the recovery time and the number of sites involved, less often the capacity. Wesettle those two values at the start, because they determine the shape of the build.All-flash with NVMe brings the latency down. It does nothing for availability; replicationand failover do that.Hybrid systems with flash and disk remain the right choice where capacity matters more thanlatency.'@ } ) } status = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/hpe/hpe-storage/alletra-storage-mp-b10000' score = '1.00' } [ordered]@{ ref = 'solutions/hpe/hpe-storage/alletra-storage-mp-x10000' score = '1.00' } [ordered]@{ ref = 'solutions/hpe/hpe-storage/greenlake-for-file-storage' score = '1.00' } [ordered]@{ ref = 'solutions/hpe/hpe-data-management' score = '1.00' } ) alsoLike = @( [ordered]@{ ref = 'solutions/hpe/hpe-storage' score = '1.00' } [ordered]@{ ref = 'services/data-management' score = '0.77' } [ordered]@{ ref = 'solutions/hpe' score = '0.67' } ) experts = @( [ordered]@{ ref = 'experts/karl-widmer' score = '0.49' } [ordered]@{ ref = 'experts/fabian-faessler' score = '0.47' } [ordered]@{ ref = 'experts/patrick-pletscher' score = '0.46' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": map[string]any{ "name": "storage", "locale": "en", "labels": map[string]any{ "group": "infrastructure", "capability/storage": 2.36, "capability/data-management": 2.87, "vendor/hpe": 1.99, }, "annotations": map[string]any{ "source": "src/content/services/en/storage.md", "route": "/en/services/storage/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/storage.md", }, }, "spec": map[string]any{ "title": "Storage", "group": "infrastructure", "audience": []any{"enterprise", "provider"}, "order": 9, "tags": []any{"storage", "data-management"}, "vendors": []any{"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": []any{ map[string]any{ "heading": "

Three shapes, three use cases

", "body": "**Block storage** for virtual infrastructure, attached over Fibre Channel SAN or iSCSI.\n" + "Continuous 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\n" + "advantage is integrated management, and the price is that compute and capacity grow\n" + "together.\n" + "\n" + "**Scale-out on software-defined storage** for file services over CIFS and NFS, or for\n" + "object storage. Data can sit across several sites, which is how very high availability\n" + "figures are reached.\n" + "\n" + "As a backup target, object storage adds the part that matters: **S3 Object Lock** protects\n" + "what has been written from being changed, including when production credentials are already\n" + "compromised. Spread across several sites, an architecture like that reaches data\n" + "availability of up to 14 nines.", }, map[string]any{ "heading": "

What actually decides it

", "body": "Usually the recovery time and the number of sites involved, less often the capacity. We\n" + "settle those two values at the start, because they determine the shape of the build.\n" + "\n" + "All-flash with NVMe brings the latency down. It does nothing for availability; replication\n" + "and failover do that.\n" + "\n" + "Hybrid systems with flash and disk remain the right choice where capacity matters more than\n" + "latency.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/hpe/hpe-storage/alletra-storage-mp-b10000", "score": "1.00", }, map[string]any{ "ref": "solutions/hpe/hpe-storage/alletra-storage-mp-x10000", "score": "1.00", }, map[string]any{ "ref": "solutions/hpe/hpe-storage/greenlake-for-file-storage", "score": "1.00", }, map[string]any{ "ref": "solutions/hpe/hpe-data-management", "score": "1.00", }, }, "alsoLike": []any{ map[string]any{ "ref": "solutions/hpe/hpe-storage", "score": "1.00", }, map[string]any{ "ref": "services/data-management", "score": "0.77", }, map[string]any{ "ref": "solutions/hpe", "score": "0.67", }, }, "experts": []any{ map[string]any{ "ref": "experts/karl-widmer", "score": "0.49", }, map[string]any{ "ref": "experts/fabian-faessler", "score": "0.47", }, map[string]any{ "ref": "experts/patrick-pletscher", "score": "0.46", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Service", metadata: { name: "storage", locale: "en", labels: { group: "infrastructure", "capability/storage": 2.36, "capability/data-management": 2.87, "vendor/hpe": 1.99, }, 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", audience: ["enterprise", "provider"], 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.\n" + "Continuous 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\n" + "advantage is integrated management, and the price is that compute and capacity grow\n" + "together.\n" + "\n" + "**Scale-out on software-defined storage** for file services over CIFS and NFS, or for\n" + "object storage. Data can sit across several sites, which is how very high availability\n" + "figures are reached.\n" + "\n" + "As a backup target, object storage adds the part that matters: **S3 Object Lock** protects\n" + "what has been written from being changed, including when production credentials are already\n" + "compromised. Spread across several sites, an architecture like that reaches data\n" + "availability of up to 14 nines.", }, { heading: "

What actually decides it

", body: "Usually the recovery time and the number of sites involved, less often the capacity. We\n" + "settle those two values at the start, because they determine the shape of the build.\n" + "\n" + "All-flash with NVMe brings the latency down. It does nothing for availability; replication\n" + "and failover do that.\n" + "\n" + "Hybrid systems with flash and disk remain the right choice where capacity matters more than\n" + "latency.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/hpe/hpe-storage/alletra-storage-mp-b10000", score: "1.00", }, { ref: "solutions/hpe/hpe-storage/alletra-storage-mp-x10000", score: "1.00", }, { ref: "solutions/hpe/hpe-storage/greenlake-for-file-storage", score: "1.00", }, { ref: "solutions/hpe/hpe-data-management", score: "1.00", }, ], alsoLike: [ { ref: "solutions/hpe/hpe-storage", score: "1.00", }, { ref: "services/data-management", score: "0.77", }, { ref: "solutions/hpe", score: "0.67", }, ], experts: [ { ref: "experts/karl-widmer", score: "0.49", }, { ref: "experts/fabian-faessler", score: "0.47", }, { ref: "experts/patrick-pletscher", score: "0.46", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 73 lines · YAML · validated at build# 100 lines · JSON · validated at build# 107 lines · TOML · validated at build# 125 lines · XML · validated at build# 123 lines · Python · read back at build, equals the JSON record# 120 lines · PowerShell · read back at build, equals the JSON record# 131 lines · Go · read back at build, equals the JSON record# 116 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/storage.md

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.36 Data Management 2.87

Vendors HPE 1.99

04Solutions

02Capabilities

01Vendors

315Corpus

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.

As a backup target, object storage adds the part that matters: S3 Object Lock protects what has been written from being changed, including when production credentials are already compromised. Spread across several sites, an architecture like that reaches data availability of up to 14 nines.

What actually decides it

Usually the recovery time and the number of sites involved, less often the capacity. We settle those two values at the start, because they determine the shape of the build.

All-flash with NVMe brings the latency down. It does nothing for availability; replication and failover do that.

Hybrid systems with flash and disk remain the right choice where capacity matters more than latency.

Experts for this

Karl Widmer

Senior System Engineer

Data Management

0.49

Fabian Fässler

Senior Solution Architect

Data ManagementStorage

0.47

Patrick Pletscher

Senior Solution Architect

Data ManagementStorage

0.46

Maybe you? Take a look at our open roles.

HPE 1.00

HPE Storage

Infrastructure 0.77

Data Management

HPE 0.67

Three shapes, three use cases

What actually decides it

Three shapes, three use cases

What actually decides it

Three shapes, three use cases

What actually decides it

Three shapes, three use cases

What actually decides it

Three shapes, three use cases

What actually decides it

Three shapes, three use cases

What actually decides it

Three shapes, three use cases

What actually decides it

Three shapes, three use cases

What actually decides it

Storage

Three shapes, three use cases

What actually decides it

Experts for this

Karl Widmer

Fabian Fässler

Patrick Pletscher

You might also like

HPE Storage

Data Management

HPE