DE · EN

Call us

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: hpe/hpe-storage locale: en labels: vendor: HPE Alletra capability/storage: 2.62 capability/data-management: 2.87 vendor/hpe: 2.04 annotations: source: src/content/solutions/en/hpe/hpe-storage.md route: /en/solutions/hpe/hpe-storage/ schema: /nerd/schema/solutions.json markdown: /en/solutions/hpe/hpe-storage.mdspec: title: HPE Storage tags: [storage, data-management] vendors: [hpe] summary: >- Primary storage for virtualized estates. The choice is settled by availability and recovery time, not by capacity. photoNeed: >- HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable stub: false draft: false kind: product addon: false vendorName: HPE Alletra status: current practice: >- Draft, not yet reviewed. Almost every storage enquiry arrives as a capacity question and leaves as an availability question. The number that ends up deciding the architecture is not how many terabytes, it is how long a restore is allowed to take. practiceReview: true sections: - heading:

What it is

body: | HPE Storage covers several product lines for primary and secondary storage. For virtualized estates, Alletra is the current family, managed from HPE's cloud console and shipping telemetry that flags anomalies before they become outages. - heading:

What it is for

body: | Estates where storage is its own layer rather than something inside the servers. That is the classic split and it has a good reason: compute and capacity do not grow at the same rate. Where vSAN or something like it already does the job, this is the wrong question. - heading:

What to watch

body: | Replication is not backup. A synchronously mirrored estate protects against losing a site and not at all against an attacker encrypting the data, because the damage replicates with everything else. Both are needed, and they are two projects.status: corpus: 267 services: - {ref: services/storage, score: 1.00} - {ref: services/data-management, score: 0.76} - {ref: services/backup, score: 0.54} posts: - {ref: posts/raid-controller, score: 0.63} - {ref: posts/iternity-icas-fs, score: 0.52} - {ref: posts/how-to-storage-performance-test-mit-vdbench, score: 0.48} - {ref: posts/storage-performance-test-mit-iometer, score: 0.48} - {ref: posts/hci-mit-stormagic, score: 0.48} - {ref: posts/iscsi-datastore-not-consumed, score: 0.33} experts: - {ref: experts/oliver-erismann, score: 0.59} - {ref: experts/karl-widmer, score: 0.53} - {ref: experts/dario-doerflinger, score: 0.45} neighbours: - {ref: solutions/hpe/hpe-data-management, score: 1.00} - {ref: solutions/hpe, score: 0.65} - {ref: solutions/hpe/hpe-dhci, score: 0.57}

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "hpe/hpe-storage", "locale": "en", "labels": { "vendor": "HPE Alletra", "capability/storage": "2.62", "capability/data-management": "2.87", "vendor/hpe": "2.04" }, "annotations": { "source": "src/content/solutions/en/hpe/hpe-storage.md", "route": "/en/solutions/hpe/hpe-storage/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/hpe/hpe-storage.md" } }, "spec": { "title": "HPE Storage", "tags": [ "storage", "data-management" ], "vendors": [ "hpe" ], "summary": "Primary storage for virtualized estates. The choice is settled by availability and recovery time, not by capacity.", "photoNeed": "HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable", "stub": false, "draft": false, "kind": "product", "addon": false, "vendorName": "HPE Alletra", "status": "current", "practice": "Draft, not yet reviewed. Almost every storage enquiry arrives as a capacity question and leaves as an availability question. The number that ends up deciding the architecture is not how many terabytes, it is how long a restore is allowed to take.\n", "practiceReview": true }, "sections": [ { "heading": "

What it is

", "body": "HPE Storage covers several product lines for primary and secondary storage. For\nvirtualized estates, Alletra is the current family, managed from HPE's cloud console and\nshipping telemetry that flags anomalies before they become outages." }, { "heading": "

What it is for

", "body": "Estates where storage is its own layer rather than something inside the servers. That is\nthe classic split and it has a good reason: compute and capacity do not grow at the same\nrate.\n\nWhere vSAN or something like it already does the job, this is the wrong question." }, { "heading": "

What to watch

", "body": "Replication is not backup. A synchronously mirrored estate protects against losing a site\nand not at all against an attacker encrypting the data, because the damage replicates with\neverything else. Both are needed, and they are two projects." } ], "status": { "corpus": 267, "services": [ { "ref": "services/storage", "score": "1.00" }, { "ref": "services/data-management", "score": "0.76" }, { "ref": "services/backup", "score": "0.54" } ], "posts": [ { "ref": "posts/raid-controller", "score": "0.63" }, { "ref": "posts/iternity-icas-fs", "score": "0.52" }, { "ref": "posts/how-to-storage-performance-test-mit-vdbench", "score": "0.48" }, { "ref": "posts/storage-performance-test-mit-iometer", "score": "0.48" }, { "ref": "posts/hci-mit-stormagic", "score": "0.48" }, { "ref": "posts/iscsi-datastore-not-consumed", "score": "0.33" } ], "experts": [ { "ref": "experts/oliver-erismann", "score": "0.59" }, { "ref": "experts/karl-widmer", "score": "0.53" }, { "ref": "experts/dario-doerflinger", "score": "0.45" } ], "neighbours": [ { "ref": "solutions/hpe/hpe-data-management", "score": "1.00" }, { "ref": "solutions/hpe", "score": "0.65" }, { "ref": "solutions/hpe/hpe-dhci", "score": "0.57" } ] }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "hpe/hpe-storage"locale = "en"[metadata.labels]vendor = "HPE Alletra""capability/storage" = "2.62""capability/data-management" = "2.87""vendor/hpe" = "2.04"[metadata.annotations]source = "src/content/solutions/en/hpe/hpe-storage.md"route = "/en/solutions/hpe/hpe-storage/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/hpe/hpe-storage.md"[spec]title = "HPE Storage"tags = ["storage", "data-management"]vendors = ["hpe"]summary = "Primary storage for virtualized estates. The choice is settled by availability and recovery time, not by capacity."photoNeed = "HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable"stub = falsedraft = falsekind = "product"addon = falsevendorName = "HPE Alletra"status = "current"practice = '''Draft, not yet reviewed. Almost every storage enquiry arrives as a capacity question and leaves as an availability question. The number that ends up deciding the architecture is not how many terabytes, it is how long a restore is allowed to take.'''practiceReview = true[[sections]]heading = "

What it is

"body = '''HPE Storage covers several product lines for primary and secondary storage. Forvirtualized estates, Alletra is the current family, managed from HPE's cloud console andshipping telemetry that flags anomalies before they become outages.'''[[sections]]heading = "

What it is for

"body = '''Estates where storage is its own layer rather than something inside the servers. That isthe classic split and it has a good reason: compute and capacity do not grow at the samerate.Where vSAN or something like it already does the job, this is the wrong question.'''[[sections]]heading = "

What to watch

"body = '''Replication is not backup. A synchronously mirrored estate protects against losing a siteand not at all against an attacker encrypting the data, because the damage replicates witheverything else. Both are needed, and they are two projects.'''[status]corpus = 267[[status.services]]ref = "services/storage"score = "1.00"[[status.services]]ref = "services/data-management"score = "0.76"[[status.services]]ref = "services/backup"score = "0.54"[[status.posts]]ref = "posts/raid-controller"score = "0.63"[[status.posts]]ref = "posts/iternity-icas-fs"score = "0.52"[[status.posts]]ref = "posts/how-to-storage-performance-test-mit-vdbench"score = "0.48"[[status.posts]]ref = "posts/storage-performance-test-mit-iometer"score = "0.48"[[status.posts]]ref = "posts/hci-mit-stormagic"score = "0.48"[[status.posts]]ref = "posts/iscsi-datastore-not-consumed"score = "0.33"[[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"[[status.neighbours]]ref = "solutions/hpe/hpe-data-management"score = "1.00"[[status.neighbours]]ref = "solutions/hpe"score = "0.65"[[status.neighbours]]ref = "solutions/hpe/hpe-dhci"score = "0.57"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>hpe/hpe-storage</name> <locale>en</locale> <labels> <vendor>HPE Alletra</vendor> <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/solutions/en/hpe/hpe-storage.md</source> <route>/en/solutions/hpe/hpe-storage/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/hpe/hpe-storage.md</markdown> </annotations> </metadata> <spec> <title>HPE Storage</title> <tags> <item>storage</item> <item>data-management</item> </tags> <vendors> <item>hpe</item> </vendors> <summary>Primary storage for virtualized estates. The choice is settled by availability and recovery time, not by capacity.</summary> <photoNeed>HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable</photoNeed> <stub>false</stub> <draft>false</draft> <kind>product</kind> <addon>false</addon> <vendorName>HPE Alletra</vendorName> <status>current</status> <practice>Draft, not yet reviewed. Almost every storage enquiry arrives as a capacity question and leaves as an availability question. The number that ends up deciding the architecture is not how many terabytes, it is how long a restore is allowed to take. </practice> <practiceReview>true</practiceReview> </spec> <sections> <section> <heading>

What it is

</heading> <body>HPE Storage covers several product lines for primary and secondary storage. Forvirtualized estates, Alletra is the current family, managed from HPE's cloud console andshipping telemetry that flags anomalies before they become outages. </body> </section> <section> <heading>

What it is for

</heading> <body>Estates where storage is its own layer rather than something inside the servers. That isthe classic split and it has a good reason: compute and capacity do not grow at the samerate.Where vSAN or something like it already does the job, this is the wrong question. </body> </section> <section> <heading>

What to watch

</heading> <body>Replication is not backup. A synchronously mirrored estate protects against losing a siteand not at all against an attacker encrypting the data, because the damage replicates witheverything else. Both are needed, and they are two projects. </body> </section> </sections> <status> <corpus>267</corpus> <services> <item> <ref>services/storage</ref> <score>1.00</score> </item> <item> <ref>services/data-management</ref> <score>0.76</score> </item> <item> <ref>services/backup</ref> <score>0.54</score> </item> </services> <posts> <item> <ref>posts/raid-controller</ref> <score>0.63</score> </item> <item> <ref>posts/iternity-icas-fs</ref> <score>0.52</score> </item> <item> <ref>posts/how-to-storage-performance-test-mit-vdbench</ref> <score>0.48</score> </item> <item> <ref>posts/storage-performance-test-mit-iometer</ref> <score>0.48</score> </item> <item> <ref>posts/hci-mit-stormagic</ref> <score>0.48</score> </item> <item> <ref>posts/iscsi-datastore-not-consumed</ref> <score>0.33</score> </item> </posts> <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> <neighbours> <item> <ref>solutions/hpe/hpe-data-management</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> </neighbours> </status></manifest>

Solution · HPE

HPE Storage

HPE Alletra

The vendor calls it: HPE Alletra

Primary storage for virtualized estates. The choice is settled by availability and recovery time, not by capacity.

HPE Gold Partner

Topics Storage 2.62 Data Management 2.87

Vendors HPE 2.04

03Services

06Posts

02Capabilities

267Corpus

photograph wantedHPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable

What it is

HPE Storage covers several product lines for primary and secondary storage. For virtualized estates, Alletra is the current family, managed from HPE’s cloud console and shipping telemetry that flags anomalies before they become outages.

What it is for

Estates where storage is its own layer rather than something inside the servers. That is the classic split and it has a good reason: compute and capacity do not grow at the same rate.

Where vSAN or something like it already does the job, this is the wrong question.

What to watch

Replication is not backup. A synchronously mirrored estate protects against losing a site and not at all against an attacker encrypting the data, because the damage replicates with everything else. Both are needed, and they are two projects.

What we do with it

Draft, unreviewed

Draft, not yet reviewed. Almost every storage enquiry arrives as a capacity question and leaves as an availability question. The number that ends up deciding the architecture is not how many terabytes, it is how long a restore is allowed to take.

This paragraph is a draft and nobody at soulTec has confirmed it yet. Everything above it describes the product and is checkable against the vendor.

Posts about it

RAID controllers

13 Mar 2023

If you have configured an HPE ProLiant server, you have almost certainly met a Smart Array or SmartRAID controller. Since Gen10 there is another option: the MegaRAID controllers.

Storage 2.62

The iTernity iCAS FS solution

21 Apr 2023

Companies face a lot at once in the digital age: exponential data growth, a shortage of IT staff, ransomware, data loss, compliance rules and retention management.

Data Management 2.87

Storage performance testing with vdbench

21 May 2024

IOmeter is quick, but its data patterns do not suit a modern storage array. vdbench is the better tool, and this is how to configure it.

Storage 2.62

Storage performance testing with IOmeter

12 Feb 2024

Every successful storage project ends with a storage performance test during system acceptance, checking the array, the storage area network and the hosts.

Storage 2.62

HCI with StorMagic

18 Aug 2022

StorMagic SvSAN is a software-defined storage solution that suits small virtualisation environments with two nodes, turning the SSDs, disks and memory of two servers into a virtual SAN.

Storage 2.62

iSCSI Datastore Not Consumed

24 Jan 2024

On a customer project running current vSphere 8.0 U2, some hosts recognised their iSCSI devices but reported them as “not consumed”, so the ESXi host saw no iSCSI datastores at all.

Storage 2.62