Quick Take
Quick Take: HPE StoreOnce Gen4+ (3660 / 5260 / 5660) and Quantum DXi are peer dedupe backup targets outside the Dell orbit. Peer on usable retention TB and TB/hr ingest — not brochure ratios or $/TB guesses. Equalize Veeam / Commvault Catalyst vs DXi paths and cloud-tier plans. BENQUAN GLOBAL LIMITED supplies both.
When StoreOnce vs DXi Actually Matters
Quick Answer: Use this bake-off when you want a dedupe disk target outside Dell PowerProtect DD gravity — refreshing aging DXi or StoreOnce, migrating off NAS/VTL, or dual-sourcing secondary storage next to Alletra / MSA / FlashSystem primary arrays. This is the HPE–Quantum peer, not the Dell–HPE page.
- Not the Dell peer: For PowerProtect DD vs StoreOnce, see PowerProtect DD vs StoreOnce — that page covers DD Boost vs Catalyst under Dell gravity.
- HPE gravity: ProLiant + Alletra/MSA primary + StoreOnce secondary under GreenLake-adjacent ops. Specs: StoreOnce Gen4+ specs.
- Quantum gravity: DXi fits sites with tape library adjacency (Scalar/StorNext lineage), multi-vendor primary storage, or a deliberate non-HPE/non-Dell dedupe column.
- Third column — object/cloud: When long retention must land on S3-compatible object, add Cloud Bank (StoreOnce) or DXi object-tier / StorNext copy paths as a copy destination — not the sole primary backup sink. Related: StorageGRID vs ObjectScale.
- Ransomware posture: Both support locked retention and air-gapped copies — state immutability requirements on the brief before you rank vendors.
Related primary AFA bake-offs: PowerStore vs Alletra MP · MSA replacement.
Architecture Fork — Catalyst vs DXi Ingest
Quick Answer: Both are purpose-built inline dedupe appliances. The fork is ecosystem (HPE Catalyst/Cloud Bank vs Quantum DXi ingest and tape adjacency) and how you grow capacity vs concurrent stream performance. Neither replaces a primary AFA — land nightly backups here, keep production on Alletra / PowerStore / FlashSystem.
| Dimension | HPE StoreOnce Gen4+ | Quantum DXi |
|---|---|---|
| Pattern | Purpose-built StoreOnce appliance (3660 / 5260 / 5660) | Purpose-built DXi appliance (4800 / 6800 / 8800 / 9000 class) |
| Source-side path | StoreOnce Catalyst (ISV-dependent) | DXi protocol / OST (ISV-dependent) |
| Other targets | NAS / VTL options; Catalyst preferred for speed | CIFS/NFS, VTL, and DXi-native paths where supported |
| Cloud / object adjacency | Cloud Bank as Catalyst Copy destination | Object-tier / cloud copy targets (confirm SKU set) |
| Tape adjacency | Replication to secondary site; tape via ISV | Strong Scalar tape library lineage for vault/offline |
| Ops plane | HPE StoreOnce + GreenLake-adjacent ops | Quantum DXi management; StorNext where unstructured tier matters |
| Host fabric | 10GbE standard; optional 16/32Gb FC HBAs | Ethernet common; FC where design requires |
Naming traps
StoreOnce Cloud Bank extends usable capacity via object storage as a Catalyst Copy target — not a primary high-speed backup sink. DXi effective capacity marketing multipliers are planning scenarios, not purchase certificates. Quote physical usable TB for on-prem retention you must keep locally.
Peer Mapping (Intent, Not Nicknames)
Quick Answer: Map by retention TB class and ingest window. “5260 vs DXi6800” only works when both quotes answer the same change-rate brief and ISV path. Model ladders move by region and list revision — size from your TB/hr and usable TB brief, then ask for current peer SKUs.
| Intent | StoreOnce Gen4+ path | Quantum DXi path |
|---|---|---|
| ROBO / compact | StoreOnce 3660 (all-HDD, ~25 TB/hr Catalyst class) | DXi4800 / entry DXi class sized to site retention |
| Mid-size DC hub | StoreOnce 5260 hybrid (~60 TB/hr Catalyst class) | DXi6800 class matched to TB/hr + usable TB |
| Enterprise ingest | StoreOnce 5660 hybrid (~105 TB/hr Catalyst class) | DXi8800 / DXi9000 class for concurrent streams |
| Long retention offload | Cloud Bank object target after local Catalyst write | Object-tier / cloud copy + tape vault adjacency |
StoreOnce capacity/throughput figures follow HPE QuickSpecs language and assume Catalyst where noted — confirm revision on every RFQ. DXi model ladders and expansion kits vary by generation; peer on usable TB and certified ingest path, not model nicknames alone.
Ops & ISV Fit — Veeam, Commvault, Others
Quick Answer: The backup application owns the job. Appliance choice must follow certified Catalyst or DXi paths — and the team that will run restores at 2 a.m. Do not assume Veeam or Commvault support is identical across both vendors on every repository type.
- Lean StoreOnce when: HPE ProLiant / Alletra / MSA estates prefer Catalyst + Cloud Bank, or Data Protector / HPE-certified ISV paths are already production.
- Lean Quantum DXi when: Tape vault adjacency matters, primary storage is multi-vendor, or you want a dedupe column without Dell DD Boost or HPE Catalyst lock-in.
- Veeam: Confirm Catalyst vs DXi/OST repository certification on the exact appliance class. Plain NAS fallback works but sacrifices source-side dedupe LAN savings — state which path each quote assumes.
- Commvault: Both vendors appear in Commvault hardware compatibility matrices — verify the exact MediaAgent-to-appliance path (Catalyst vs DXi vs NAS) before freezing SKUs.
- Backup software bake-off: If the ISV choice is still open, see Commvault vs Veeam and Veeam vs Rubrik — then return here to lock the target appliance column.
When object tier is the third column
Add Cloud Bank (StoreOnce) or DXi object copy only when long retention must leave the appliance chassis — e.g. multi-year compliance, cross-region DR, or tape replacement with object vault. Keep the appliance as the high-speed ingest sink; object is the copy tier. See ObjectScale vs ECS for Dell object context.
FC vs Ethernet
Many Catalyst and DXi designs run on 10/25GbE. Add 16/32Gb FC only when the backup fabric already sits on the SAN — see 32Gb FC buying guide.
Sizing Truth — Equal Assumptions
Quick Answer: Force both vendors to quote usable on-prem retention TB under the same reduction confidence, same ingest window, and same support years. Reject $/TB spreadsheet rankings — they hide support, expansion kits, and migration labor. Quote physical usable for the retention you must keep on-prem.
- Usable vs effective: 20:1 marketing multipliers are planning scenarios, not purchase certificates. Both vendors publish “effective capacity” — treat it as a sizing conversation, not a BOM line item.
- Ingest window: Daily change rate and concurrent streams drive TB/hr — not a single peak brochure number.
- Cloud tier: Object copies are for long retention / DR, not the only high-speed target.
- Immutability: State retention lock / cyber vault requirements on both BOMs or you will compare unequal risk postures.
- No fake economics: If a rep quotes $/TB without support years, expansion, and ISV licenses, discard the column and re-issue the brief.
RFQ Checklist — Dual Backup BOM on One Brief
Quick Answer: Issue one data protection brief, then ask for HPE StoreOnce Gen4+ and Quantum DXi line items against it with equal data reduction assumptions and support years. Include the backup software path, the cloud tier plan, and the migration source on every line so both quotes answer the same risk posture.
What to put on the RFQ
- Daily change rate (TB) and full/incremental window (hours)
- On-prem usable retention TB year-1 and year-5
- Required ingest (TB/hr) and concurrent stream count
- Backup ISV and preferred path: Catalyst vs DXi vs VTL/NAS
- Host: Ethernet and/or 16/32Gb FC HBA counts
- Cloud tier / Cloud Bank / object copy plan (or none)
- Immutability / retention lock / vault requirements
- Replication topology (ROBO fan-in, DR site)
- Tape vault adjacency (if Scalar or offline copy matters)
- Support: 3 or 5 years, itemized equally
- Migration source (aging DXi / StoreOnce / NAS / tape) and cutover window
Use SKU Lookup, then submit the dual-vendor brief on rfq.html.
Frequently Asked Questions
Quick Answer: Choose between HPE StoreOnce Catalyst and Quantum DXi by backup software certification and estate gravity, peer both on usable retention terabytes and ingest throughput, and run a dual request for quotation with equal support years. Neither wins universally: StoreOnce fits Catalyst estates, DXi fits tape-adjacent multi-vendor sites.
Not universally. StoreOnce wins when HPE Catalyst and Cloud Bank fit the ops model. DXi wins when tape adjacency, multi-vendor primary storage, or a non-Dell/non-HPE dedupe column matters. Dual-RFQ matched briefs.
Treat cloud object as a copy destination for longer retention. Object latency and throughput usually make it unsuitable as the sole high-speed primary backup sink.
That page is the Dell–HPE peer (DD Boost vs Catalyst). This page is the HPE–Quantum peer for buyers who want a dedupe target outside Dell gravity — or who already standardized away from Data Domain.
Submit one RFQ with the dual-vendor checklist above.
Key Takeaway
Key Takeaway: StoreOnce Gen4+ and Quantum DXi are peer dedupe backup appliances with different ecosystems. Win on ISV path honesty, usable retention TB, and ingest realism — then standardize. BENQUAN GLOBAL LIMITED supplies both with competitive pricing and configuration support for global buyers.