---
# source: src/content/solutions/en/hpe/hpe-storage.md
# route:  /en/solutions/hpe/hpe-storage/
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
---

## 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.