Start with the arithmetic. 24 122.88TB QLC NVMe SSDs yield 24 × 122.88TB = 2,949.12TB of raw flash — about 2.95PB — and that is what Nexsan's new Unity NV12000 head unit packs into 2U. Hang 4 U2F226 NVMe expansion shelves (2U, 26 bays each) off it and the full system holds 128 drives and 15,728.64TB — 15.72PB in vendor rounding — across 10U, or roughly 1.57PB per rack unit. That is where the press release's "nearly 3PB" and "approximately 15PB" come from. (The capacity products and per-U density are calculated here; the vendor's published figures are rounded.)
On November 10, 2026, Nexsan announced the Unity NV12000 over Business Wire, running Unity OS 7.4 (rolled out to the entire NV series the same day), available immediately through solution-provider channels. The official workload list is blunt: AI/ML/HPC training datasets, vector databases and RAG, data lakes, analytics and ELT, ultra-HD media assets, and VMware/Proxmox/Hyper-V/Xen virtualization. CEO Vincent Phillips's statement, translated into plain language: data is growing faster than data centers, so petabyte-class all-flash has to fit a smaller footprint — with immutable data protection built in. The launch extends the Unity NV family upward rather than sideways: the story is capacity per rack unit, not a new protocol or a new controller architecture.
Specifications at a glance

| Item | Unity NV12000 |
|---|---|
| Form factor | 2U head unit, dual controllers |
| Bays | 24 × 2.5-inch NVMe in the head unit |
| Drive capacities | 1.92TB–30.72TB, up to 122.88TB QLC NVMe |
| Head-unit raw capacity | 2,949.12TB ≈ 2.95PB (calculated) |
| All-flash maximum | 4 × U2F226 (2U, 26 bays) → 15.72PB/10U |
| Controllers | 512GB DDR5 per controller, end-to-end PCIe 5.0 |
| Rated performance | Up to 3,000,000 IOPS (vendor rating, test conditions unpublished) |
| Protocols | FC/iSCSI block, NFS/SMB/FTP file, S3 object (NexObject) |
| Data protection | Immutable snapshots 2,048/LUN, S3 object lock, AES-256, Kerberos NFS |
| Power | Head unit 2 × 2,000W; U2F226 2 × 3,200W (redundant hot-swap) |
| Weight | Head unit 40.66kg |
What QLC gives up at the capacity tier

The 122.88TB drive is QLC: 4 bits per cell, trading write endurance and sustained write performance for capacity density. That is not a flaw; it is a division of labor. Nearly every workload Nexsan lists is read-heavy: training sets written once and read repeatedly, RAG stores queried far more than mutated, media libraries read sequentially after ingest. For those, QLC's cost per TB and density per U are the deciding factors — not peak write IOPS. For procurement teams, the practical question is not whether QLC counts as "enterprise grade" but whether the workload's write profile lands inside the tier's design envelope.
Two caveats stay on the table. First, the 3,000,000 IOPS figure is a vendor rating; StorageReview notes that Nexsan has not published usable capacity, throughput, or the test conditions behind it. Second, "up to 9x data reduction" depends on the data — deduplication ratios on your dataset may look nothing like the marketing number. The conservative move: run a POC on your own data samples and write the reduction ratio and mixed-workload IOPS into the acceptance criteria. The good news is that Unity OS 7.4 licensing is all-inclusive — immutable snapshots, object lock, compression, deduplication, replication, FASTier caching and MFA no longer carry separate price tags, so software-side TCO is predictable.
Where cold data goes: tiering, not brute force
Nexsan answers this itself: the U2G478 4U SAS shelf chains up to 8 enclosures and 648 drives in 34U, reaching 19.17PB raw with 7,200RPM HDDs up to 26TB, or 22.1PB with SAS SSDs; in hybrid configurations FASTier caches the HDD tier on flash. Below that, Assureon archive integration and S3 object lock handle compliance retention, while tape and object storage keep playing the cold tier.
In other words, the 15.72PB all-flash maximum is not an invitation to move backups and archives onto flash — it compresses the hot and warm tiers into 10U. The right way to spend the density dividend is tiering: flash carries performance, HDD/tape/object carry cost, and immutable snapshots (2,048/LUN) plus object lock carry the ransomware defense. That split also keeps the protection story coherent: immutable recovery points on the performance tier, compliance retention on the cold tier, and no expectation that one box does both jobs.
Space and power math for Pearl River Delta server rooms
The space math is the most direct: at comparable petabyte scale, the all-flash build is 10U against 34U for the HDD build — 24U saved. In colocation facilities that bill per U, that is a line item on every monthly invoice.
Power should be provisioned at the nameplate ceiling and billed at actual draw. Nameplate ceiling (calculated): under N+N redundancy each feed must independently carry the head unit's 2,000W + 4 × 3,200W = 14,800W, i.e. 14.8kW — a planning value for cabling and breakers, while real QLC drive draw sits far below it. If the system truly ran at that ceiling for a year: 14.8kW × 8,760 hours = 129,648 kWh; at an assumed RMB 0.7/kWh, about RMB 90,750/year, multiplied by the facility PUE. The point of that number is not to forecast the electricity bill — it is a reminder that 128 drives in 10U is a power-density event: rack feeds, airflow paths and inlet temperature (spec sheet 10–35°C) all need review before deployment, not after a breaker trips. Teams retrofitting older rooms should treat the per-feed ceiling as the gating item; the energy cost is secondary to whether the rack can deliver the current at all.
Who should buy, and who should wait
A fit: mid-size enterprises and industry clouds whose data grows faster than their space and power budgets, whose workloads are read-heavy, and who want block/file/object on one platform. Wait: sustained heavy-write scenarios (the QLC endurance boundary), and buyers who require a reproducible vendor test report before committing. Density is a genuine selling point, and so are the boundaries — doing the math before procurement is far cheaper than expanding after the fact.
Sources and verification notes (accessed 2026-11-15)
- Nexsan press release, Business Wire, 2026-11-10 11:45 EST: https://www.businesswire.com/news/home/20261110622660/en/ ; full text verified via the FinancialContent mirror: https://www.financialcontent.com/article/bizwire-2026-11-10-nexsan-delivers-nearly-3-petabytes-of-all-flash-nvme-storage-in-a-2u-system-with-latest-addition-to-unity-nv-series
- StorageReview, Harold Fritts, 2026-11-11, with full specification table: https://www.storagereview.com/news/nexsan-unity-nv12000-15pb-nvme-flash-10u
- VMBlog syndication of the same release (headline verified; body truncated by the fetcher): https://vmblog.com/news/nexsan-delivers-nearly-3-petabytes-of-all-flash-nvme-storage-in-a-2u-system-with-latest-addition-to-unity-nv-series/
- The TMCnet link in the original assignment returned HTTP 403 (Cloudflare challenge); cross-replaced with the Business Wire mirror above: https://www.tmcnet.com/usubmit/2026/11/10/10479033.htm
- Calculated values: 2,949.12TB, 15,728.64TB, 128 drives, 1.57PB/U, 14.8kW, 129,648 kWh, RMB 90,750; RMB 0.7/kWh is an assumed tariff. Vendor figures: 3,000,000 IOPS, 9x reduction, 15.72PB.
