HPE StoreEasy and StoreOnce Data Recovery
HPE StoreEasy and HPE StoreOnce are both positioned as secondary storage, but they are architecturally unrelated: StoreEasy is a Windows Storage Server-based NAS appliance built on standard Windows storage technologies, while StoreOnce is a purpose-built deduplication backup target with its own proprietary data format. Because they are frequently deployed alongside each other in the same backup environment, this page covers both, treated separately below.
Platform Lineage and Naming
HPE StoreEasy is a line of Windows Storage Server-based NAS appliances spanning the StoreEasy 1000, 3000 and 5000 series, aimed at file serving and as a Windows-native backup target. It builds on Microsoft's Windows Storage Server operating system and HPE's Smart Array RAID controllers, rather than a proprietary storage operating system.
HPE StoreOnce is a separate, purpose-built family of deduplicating backup appliances spanning the StoreOnce 3000, 5000 and 6000 series, plus the StoreOnce VSA virtual appliance. It presents deduplicated storage to backup software as Catalyst stores or as virtual tape/NAS targets, using HPE's own deduplication engine and on-disk format rather than a general-purpose file system.
The two products are commonly deployed together — a StoreEasy NAS for general file shares and a StoreOnce appliance as the backup repository — but they do not share an architecture, and a recovery evaluation for one has no bearing on the other.
- StoreEasy 1000, 3000, 5000 series — Windows Storage Server NAS appliances
- StoreOnce 3000, 5000, 6000 series — deduplication backup appliances
- StoreOnce VSA — virtual StoreOnce appliance
- Catalyst store — StoreOnce's native deduplicated storage target used by supported backup applications
- Smart Array — HPE's RAID controller family used in StoreEasy and other HPE servers
Generations and Models We Evaluate
| Generation / family | Models |
|---|---|
| StoreEasy | StoreEasy 1000 (entry), 3000 and 5000 series (scale-out and higher-capacity), running Windows Storage Server with Storage Spaces or Smart Array RAID |
| StoreOnce physical | StoreOnce 3000, 5000 and 6000 series appliances, sized by front-end capacity and deduplication throughput |
| StoreOnce virtual | StoreOnce VSA, a software-defined deployment of the same deduplication engine |
Architecture and Data Layout
StoreEasy runs Windows Storage Server on standard server hardware, using either HPE Smart Array hardware RAID or Windows Storage Spaces for its data layout, and NTFS or ReFS as the file system. Because it is fundamentally a Windows file server, its logical structures and typical failure modes are the same as any Windows Server NAS built on those technologies: RAID/Storage Spaces layout beneath a standard NTFS or ReFS volume.
StoreOnce is architecturally unrelated: it runs HPE's own deduplication engine, ingesting backup data over Catalyst, VTL emulation or NAS protocols and storing it as deduplicated, chunked objects in a proprietary repository rather than as conventional files. Backup software addresses StoreOnce through Catalyst stores, which manage their own internal indexing of deduplicated chunks.
Because StoreOnce's repository format is proprietary and its deduplication indexing is central to reconstructing any given backup set, recovery from a damaged or corrupted StoreOnce store is evaluated case by case; the extent to which a given repository can be reconstructed depends on which internal structures survived, and this cannot be assumed in advance.
Protocols and formats: SMB, NFS, NTFS, ReFS, Catalyst, VTL (virtual tape library) emulation, iSCSI
- StoreEasy: Smart Array hardware RAID or Windows Storage Spaces beneath NTFS or ReFS, consistent with general Windows Server storage layout.
- StoreOnce: a proprietary deduplicated chunk store with its own indexing, not a conventional file system, addressed by backup applications through Catalyst or emulated tape/NAS interfaces.
Failure Scenarios
Logical failures
- StoreEasy: accidental share, volume or Storage Spaces pool deletion; NTFS/ReFS corruption; failed Windows Server or Storage Spaces update
- StoreEasy: RAID configuration lost or rebuilt incorrectly on the Smart Array controller
- StoreOnce: Catalyst store deleted or a backup job overwritten before the retention period was understood
- StoreOnce: deduplication database or index corruption following an interrupted housekeeping or replication operation
- StoreOnce: failed firmware or software upgrade affecting the repository's internal state
Hardware failures
- Multiple drive failures beyond RAID or Storage Spaces resiliency tolerance
- Smart Array controller failure or cache/battery failure on StoreEasy
- StoreOnce node or shelf failure in multi-node configurations
- Power loss during active deduplication or garbage-collection operations on StoreOnce
- Chassis, backplane or controller failure common to enterprise disk arrays generally
Encryption and credentials
Where StoreEasy volumes use BitLocker or StoreOnce stores use appliance-level encryption, key material must be preserved and supplied for an evaluation, since encrypted repositories cannot be interpreted without it.
What Not To Do Before an Evaluation
- Do not run rebuilds, reconstructions or re-initialisations against an array that has already lost more drives than its protection level allows.
- Do not recreate pools, aggregates, disk groups, storage pools or clusters — these operations write new metadata over the structures a recovery needs.
- Do not swap drives between slots, and do not reorder shelves. Record the original slot and shelf positions before removing anything.
- Do not run file-system repair tools against production volumes before the underlying storage layer has been evaluated.
- Do not restore a backup or replication set over the affected volumes until the recovery scope has been assessed.
- Do not eradicate deleted volumes or empty recycle/destroyed states on platforms that hold deleted data for a retention window.
Our Evaluation and Recovery Process
- Intake and platform identification — array model, generation, firmware, protection layout and the sequence of events that led to the failure.
- Read-only evaluation of the media and array structures, including assessment of drive health and the extent of any physical damage.
- Forensic imaging of all contributing media, with cleanroom work where drives require it. Originals are preserved unaltered.
- Reconstruction of the storage layer — pools, aggregates, parity groups, chunklets, extent groups or objects — from the images.
- Extraction of the layers above: file systems, virtual machines, databases, mailboxes and shares.
- Verification against a file list and customer-nominated critical data, followed by secure return on encrypted media.
Frequently Asked Questions
Are StoreEasy and StoreOnce recovered the same way?
No. StoreEasy is a Windows Storage Server NAS using standard RAID/Storage Spaces and NTFS or ReFS, evaluated like any Windows file server. StoreOnce is a proprietary deduplication repository and needs an approach built around its own indexing and chunk store rather than file system tools.
Can a damaged StoreOnce Catalyst store always be rebuilt?
Not necessarily. Reconstructing a Catalyst store depends on how much of the deduplication index and underlying chunk data survived the event, which is why this is assessed through an evaluation of the specific appliance rather than assumed.
If a StoreOnce store fails, is the StoreEasy NAS it backs up also affected?
Not directly — the two are separate architectures. A StoreOnce failure affects the backup copies it holds, while the StoreEasy NAS and its live data are a separate system with their own recovery considerations.
Does StoreOnce VSA fail differently from the physical appliances?
It uses the same deduplication engine and repository format, so logical causes such as index corruption are similar; hardware causes instead become failures of the underlying virtual infrastructure and its storage.