Home / News & Releases / Barclays cuts Dell, HPE and NetApp: what the missing AI cata

Barclays cuts Dell, HPE and NetApp: what the missing AI catalyst means for ONTAP

Barclays says enterprise hardware valuations have outrun an AI revenue inflection. The storage test is concrete: can ONTAP keep GPU data paths fed, governed and recoverable at production scale?

Source boundary The Barclays action and valuation figures below come from BigGo Finance and Foreign Policy Journal coverage of the analyst note. Novus architecture details are NetApp claims, not evidence that AI demand has already produced a revenue inflection. Back to the news index.

Analysis of BigGo Finance coverage, corroborated by Foreign Policy Journal, with NetApp's own Novus materials used only for the technical read-through.

AI ONTAP Finance 2026-10-15

The rating call is about proof, not product absence

Barclays moved Dell Technologies, Hewlett Packard Enterprise and NetApp from Overweight to Equal Weight. The corroborating coverage attributes the call to analyst Tim Long and says he kept NetApp's price target at $219, while cutting Dell's to $574 from $603 and HPE's to $77 from $83. The thesis is that valuations have expanded without a comparable, measurable inflection in enterprise AI demand.

That distinction matters. The note does not establish that NetApp lacks an AI product or that ONTAP cannot serve AI workloads. It says the commercial evidence has not yet caught up with the valuation. Product announcements answer “what can be built?”; bookings, revenue, renewals and deployed utilization answer “is demand changing the business?”

The concrete NetApp announcement behind the AI story

NetApp announced Novus on September 29 as a disaggregated architecture for AI factories. In the initial release, Novus Data Director metadata software runs on qualified Supermicro infrastructure while ONTAP data services run on AFF A90 systems. NetApp says clients use standards-based pNFS/NFS access: a client obtains a file layout from Data Director and then transfers data directly against the storage layer.

NetApp also describes one namespace, independently scalable metadata, bandwidth and capacity, and an architecture designed to exceed 100 TB/s aggregate throughput. Those are material implementation specifics, but the scale number remains a vendor design claim. It is not, by itself, evidence of a customer deployment at that scale or an AI-driven revenue inflection.

What ONTAP actually has to do

In this design ONTAP is not the global metadata director. Its job is still demanding: AFF A90 systems must serve the direct client data path with predictable latency and throughput, preserve availability across storage failures, enforce the supported access and tenant boundaries, protect data, and retain enough capacity and controller headroom for checkpoint bursts and concurrent readers. A fast metadata response cannot compensate for a congested client-to-data-node path.

The operational consequence is a four-plane evidence model:

  1. Metadata: layout-request latency, Data Director availability and namespace operations under small-file pressure.
  2. Client: supported Linux image, NFS/pNFS behavior, retries and observed read/write throughput rather than mount success alone.
  3. Fabric: path utilization, loss, congestion and failure recovery between GPU hosts and storage data interfaces.
  4. ONTAP: node latency, CPU, network, capacity, data protection and HA behavior while the real training, retrieval and checkpoint mix runs.

These are validation categories, not a claim that Novus exposes one finished cross-plane dashboard. Teams should require telemetry and failure tests for each plane and correlate timestamps across them.

The buyer's test for an AI catalyst

A defensible pilot should record GPU idle time attributable to storage, sustained throughput per client and in aggregate, metadata latency at the target file count, checkpoint completion time, recovery time after a metadata, network or ONTAP failure, and useful capacity after the actual dataset is loaded. It should also freeze the supported client, NIC, firmware and mount configuration used in the test.

Only then can an operator connect the architecture to a business outcome: more completed work per GPU hour, fewer dataset copies, a smaller operational surface, or a recovery objective the old platform could not meet. Without that chain, “AI-ready” remains positioning—the gap Barclays is challenging at the company level.

Where the Dell comparison belongs

The analyst grouped three enterprise-hardware vendors, but a storage selection still has to compare specific operating models. The broad NetApp vs Dell guide separates portfolio-level differences; the NetApp vs Dell PowerStore comparison narrows the question to storage architecture and operations. Neither comparison proves AI demand or investment upside. They help a buyer test platform fit after removing the market narrative.

Bottom line

Barclays' “no meaningful AI inflection” call is a demand-and-valuation judgment. The ONTAP-side response should be evidence, not another slogan: demonstrate that the Novus metadata layer, clients, fabric and AFF A90 data path work as one recoverable system on the customer's workload, then show that the result changes GPU economics or operational cost. Until those results convert into repeatable customer revenue, a technically specific AI architecture and a financial AI catalyst remain different claims.

Sources: BigGo Finance via Google News · Foreign Policy Journal · NetApp Novus announcement · NetApp Novus architecture blog. Not investment advice.

Sources and measurement

The rating action is corroborated by two reports; the underlying Barclays note was not available for direct review. Architecture statements are attributed to NetApp. The four-plane model and pilot criteria are NetApp Black Box analysis, not promises made by Barclays or NetApp.

Outcome metric: indexed news page plus first impressions for the story query in Google Search Console; UNKNOWN until data is available.

← Back to the news index