Oracle, Sun and StorageTek Storage Data Recovery
Oracle's storage estate is really three inherited lineages: Sun's own StorEdge and Unified Storage lines, the StorageTek systems Sun acquired in 2005, and the Pillar Axiom platform Oracle bought in 2011. They share a badge and almost nothing else at the on-disk level, so identifying which lineage an array belongs to is the first step of any evaluation.
Overview
The ZFS Storage Appliance line — sold first as the Sun Storage 7000 Unified Storage System and later as Oracle ZS3, ZS4, ZS5, ZS7 and ZS9 — is by far the most common of these platforms still in production. Data sits in ZFS pools built from vdevs in mirrored or RAID-Z profiles, with separate log and cache devices, so pool geometry, disk order and shelf identity all matter when media is removed.
The Sun StorEdge and StorageTek disk systems are older and more varied. Several were rebadged from other manufacturers — the 99xx high-end arrays are Hitachi platforms, and the 6000-series modular arrays come from the Engenio/LSI lineage that also produced NetApp E-Series — which means the correct recovery methodology follows the original manufacturer's architecture rather than the Sun badge.
Pillar Axiom and its successor, the Oracle FS1 Flash Storage System, use a distinctive Pilot/Slammer/Brick or Pilot/Controller/Drive-Enclosure design with quality-of-service placement that spreads a single LUN across specific regions of each brick. That placement metadata is essential to reconstruction and is held by the management layer, not by the drives alone.
All of these platforms are end-of-life or approaching it, so evaluations frequently involve systems that cannot be repaired with vendor parts. Work is performed on forensic images, and original media is documented in slot order and preserved unaltered.
Platform Families We Evaluate
- Oracle ZFS Storage Appliance Data Recovery — Sun/Oracle unified storage — ZFS pools, RAID-Z, clustered heads and DE-series shelves.
- Sun StorEdge and StorageTek Data Recovery — Legacy Sun/StorageTek disk arrays — StorEdge A/T/3000/6000 series and Hitachi-derived 99xx systems.
- Pillar Axiom Data Recovery — Pillar/Oracle Axiom modular SAN — Pilot controller, Slammers, Bricks and QoS-based placement.
- Oracle FS1 Flash Storage System Data Recovery — Axiom successor with automated flash/HDD tiering — Pilot, Controllers, Drive Enclosures and QoS Plus.
Related Services
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.