Everpure (formerly Pure Storage) FlashArray Data Recovery
FlashArray is the block platform from Everpure — the company formerly known as Pure Storage, usually running virtualisation and database workloads. Its Purity operating environment keeps deleted volumes in a destroyed state for a retention period, so many cases turn on whether that window has passed or a volume was explicitly eradicated.
Platform Lineage and Naming
The vendor — Pure Storage, renamed Everpure in 2026 — shipped the FA-300 and FA-400 series, then the FlashArray//M generation, followed by //X (NVMe DirectFlash), //C (QLC capacity flash), //XL (high end) and //E. These generations run Purity//FA, which Everpure upgrades non-disruptively across controller replacements.
The vendor's Evergreen model means controllers are replaced in place while the DirectFlash modules and shelves persist, so an array's chassis generation and its media generation often differ — something that must be established before any recovery work.
- Everpure — the vendor's name since the 2026 rebrand from Pure Storage
- Purity//FA — the array operating environment
- DirectFlash Module (DFM) — Pure's proprietary flash module, not a standard SSD
- FlashArray//M, //X, //XL, //C, //E; legacy FA-405, FA-420, FA-450
- Protection groups, snapshots, SafeMode retention
- ActiveCluster (synchronous replication), ActiveDR (async)
Generations and Models We Evaluate
- Current families: FlashArray//X R3/R4, //XL 130/170, //C40/C60/C70, //E
- Earlier: FlashArray//M10, //M20, //M50, //M70; FA-405, FA-420, FA-450
- Shelves: DirectFlash Shelf, SAS expansion shelves on older generations
- Media: DirectFlash Modules (NVMe), SAS SSD on //M and FA-400 generations
Architecture and Data Layout
FlashArray runs an active/passive controller pair over shared NVMe or SAS flash. Purity places data with global inline deduplication, compression and a variable-block layout, and writes RAID-3D protection across the DirectFlash modules.
DirectFlash Modules expose raw flash to Purity rather than presenting a conventional SSD interface with its own FTL — so they cannot be read as standard SSDs, and reconstruction must work with Purity's own placement structures.
Volumes are thin-provisioned objects in a global pool. Deleted volumes move to a destroyed state (recoverable until the eradication timer expires), and explicit eradication or SafeMode configuration determines whether a self-service restore is possible.
- Purity uses RAID-3D, a dual-parity-class protection scheme across DirectFlash modules with additional intra-module protection — not a classic RAID 5/6 stripe.
- Global deduplication means a single physical block can be referenced by many volumes, so partial media loss can touch many volumes at once.
Logical Failures
- Volume deleted and eradicated, or destroyed past the eradication window
- Protection group snapshots removed or expired
- Failed Purity upgrade or controller replacement
- Array reinitialised or factory reset over live data
- ActiveCluster / ActiveDR resynchronised in the wrong direction
- VMFS, vVol or database corruption inside presented volumes
- Host-side deletion where the array itself is healthy
Hardware Failures
- Multiple DirectFlash module failures beyond RAID-3D tolerance
- Both controllers failed or a failed failover
- NVRAM module failure with unflushed writes
- Shelf, midplane or NVMe fabric faults
- Site power events taking down the full chassis
Encryption and Keys
FlashArray encrypts all data at rest by default with array-managed keys — there is no option to disable it. Array key state must be preserved with the media, since encrypted DirectFlash content cannot be interpreted without it.
Frequently Asked Questions
We deleted a volume. Can we get it back ourselves?
If it is still in the destroyed state and has not been eradicated, Purity can usually restore it directly — check that first, it is the fastest route. Once eradicated, self-service recovery is not available.
Can DirectFlash Modules be read like SSDs?
No. DFMs expose raw flash managed by Purity rather than a standard SSD translation layer, which is why generic SSD or RAID tools produce nothing usable.
Does encryption prevent recovery?
It means the array's key state matters as much as the media. Preserve the whole system — controllers and modules together — rather than shipping loose flash modules.
Related
- Everpure / Pure Storage FlashBlade — /services/enterprise-storage/pure-storage/flashblade
- SAN Data Recovery — /services/other-data-recovery-services/san-recovery
- SSD Data Recovery — /services/data-recovery-services/media/ssd-hard-drive-data-recovery
- Enterprise Storage Data Recovery — /services/enterprise-storage-data-recovery