AIToday
AI Business & IndustrySiliconANGLE AIPublished: Oct 2, 2026, 04:00 JST

NetApp's Novus splits data, metadata for AI factories

NetApp's Novus splits data, metadata for AI factories

3 Key Points

  1. What happened

    NetApp CTO Arindam Banerjee said the Novus architecture separates data and metadata so each scales independently, keeping GPUs fed during simultaneous transactional and heavy sequential workloads.

  2. Why it matters

    Previous architectures handled one workload type well, not both at once; storage delays can leave costly GPUs underused while still consuming power, the company says.

  3. What to watch

    The design targets agentic workloads where thousands of agents hit data concurrently with temporary permissions. Whether it delivers hinges on the new API-driven control plane Banerjee described.

WHO IT HITSEnterprise storage architects and AI infrastructure teams running GPU clusters will need to evaluate whether separating metadata and data management reduces GPU idle time as agentic workloads scale up.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

NetApp and Nvidia's partnership dates back more than a decade and now includes co-engineering around AI infrastructure. That long relationship matters because the storage problems Banerjee describes are not abstract: as AI moves from experimentation into what Nvidia's Jason Hardy called "phase 2" of mainstream production, the infrastructure has to scale without being redesigned for every new use case.

Banerjee's argument is that AI workloads create a specific conflict. Transactional metadata operations and heavy sequential workloads — checkpoints, for example — happen at the same time, and older architectures could only do one well. When metadata and data share the same resources, data operations queue behind smaller metadata operations, which leaves GPUs underutilized while still burning power. Novus's answer is to split those functions onto separate scaling axes.

Agents raise the stakes further, since thousands may hit data concurrently with temporary permissions, increasing metadata volume. The bet is that API-driven, agent-friendly consumption — rather than storage specialists managing every request — becomes the norm. Whether this matters for any given enterprise hinges on how quickly agentic production workloads arrive and whether the new control plane makes the layer invisible to the AI teams meant to use it.

FAQ
What is NetApp's Novus architecture designed to do?
It separates data and metadata functions so each can scale independently based on different workload demands. This prevents smaller transactional metadata operations from competing with large data transfers for the same resources.
Why does AI storage need to change for agents?
Thousands of agents may access data at the same time with temporary, narrowly scoped permissions. That increases metadata operations alongside throughput demands, creating concurrency requirements that previous architectures did not address.
How will AI teams manage the new storage layer?
NetApp is designing a new control plane that allows consumption of Novus through APIs. Banerjee said AI teams are not storage engineering teams and should be able to consume storage through an API or SDK, with agents potentially doing that work in the future.
SiliconANGLE AIRead Original Article

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleChina OSATs to hit 13% of cloud AI accelerator market in 2026