It Is the Same ONTAP. What You Are Choosing Is the Relationship.
Written and maintained by Haink's infrastructure team · Verified against Lenovo Press, Lenovo's own ONTAP documentation and third-party ecosystem support matrices, 29 August 2026 · we supply both
Buyers find this out at an awkward moment. A Lenovo storage quote comes in noticeably below the NetApp one, someone asks why, and the answer — that the array runs the same operating system — sounds too convenient to be true. So the quote gets treated as suspect, and a defensible saving is left on the table for the wrong reason.
It is true. Lenovo Press states it in the product documentation: "Powered by the ONTAP software, ThinkSystem DM Series Storage Arrays deliver hybrid and all flash storage with enterprise-class storage management capabilities." The question worth asking is not whether the storage is as good. It is which commercial and support relationship you want wrapped around it — because that is the part that genuinely differs.
What is OEM'd, and what runs on what
| Lenovo line | Operating system | NetApp lineage | Role |
|---|---|---|---|
| DM series | ONTAP | FAS / AFF family | Unified file and block, hybrid and all-flash |
| DG series | ONTAP | Same family, QLC all-flash | Capacity-optimised primary and secondary |
| DE series | SANtricity | E-Series | Block / SAN — a different platform, not ONTAP |
| DS series | Block SAN | Reported as based on OEM'd NetApp ASA systems | All-flash SAN, introduced to the portfolio recently |
The DE series is the one people get wrong. It is not ONTAP and never has been — it is E-Series running SANtricity, a block platform with a different feature set, different management and no ONTAP data services. If someone quotes you a DE array as a cheaper route to ONTAP, they have made a mistake or are hoping you will not notice.
How to verify this yourself, in three checks
You should not take a supplier's word for the lineage of a storage platform, including ours. Three independent checks settle it in about five minutes:
- The vendor names the OS. Lenovo Press names ONTAP explicitly in the DM series documentation. There is no ambiguity to interpret.
- Lenovo publishes ONTAP documentation under its own domains. The ONTAP manuals, the compatible-versions guidance for SnapMirror relationships, and the SnapMirror configuration and best-practices guide for ONTAP 9 are all hosted by Lenovo for its arrays. A rebadge with a thin veneer does not come with the full document set.
- Third-party ecosystems treat them as one family. Veeam's integration documentation groups "NetApp ONTAP, Fujitsu ETERNUS HX/AX, Lenovo ThinkSystem DM/DG" under a single set of requirements. Independent software vendors do not merge platforms in their support matrices out of politeness.
What actually differs
This is the part that decides the purchase, and it has nothing to do with the storage OS.
The support relationship
With Lenovo-branded arrays, the storage sits inside the same support relationship as the servers and, frequently, the networking around it. One vendor, one contract, one escalation path, one account team. With NetApp direct you get a storage specialist whose entire organisation is built around that platform, and a deeper bench for the hard problems — performance analysis, complex replication topologies, ONTAP-specific tuning.
Which is better depends on where your risk actually sits. If storage is the most complex thing in the estate and you have had incidents that needed real ONTAP expertise, the specialist relationship earns its premium. If storage is one component among several and your operational pain is coordinating vendors, consolidation is worth real money.
Feature and version timing
Features land on the originating vendor's platform first and reach OEM-branded lines afterwards. In practice this rarely matters, because most estates are not running the newest ONTAP release anyway. It matters a great deal if you have a specific capability in the design. Confirm the ONTAP version available for the exact Lenovo model you are quoted, and confirm that the feature you need is supported on it — in writing, before the order. Do not infer it from a NetApp release note.
The model lines are not a one-to-one rebadge
Lenovo's DM and DG line-up does not mirror every AFF and ASA model. A NetApp configuration you have already sized may not have an exact Lenovo counterpart at the same performance and capacity point, and the nearest equivalent may sit either above or below it. Have both sized independently against your workload rather than asking for "the Lenovo version of this quote".
Licensing packaging
The software bundles differ in name and composition between the two. This is where a like-for-like comparison quietly stops being like-for-like: a bundle that includes a data service on one side may list it separately on the other. Require both quotes to itemise the data services included — replication, cloning, encryption, tiering, whatever your design depends on — rather than comparing bundle names.
The ecosystem around the platform
The partner, consultant and training ecosystem around NetApp-branded storage is larger. If you expect to hire ONTAP skills, use third-party professional services, or hand the platform to a managed service provider, the deeper market is worth weighing. The technology is the same; the availability of people who will say they have worked on it is not.
Replication between the two: verify versions, not brands
The question that decides most mixed-estate purchases: can a Lenovo DM array replicate to a NetApp system already in the estate?
The rule to work from is that SnapMirror compatibility is expressed in terms of ONTAP versions, not brands — Lenovo publishes the compatible-versions guidance for SnapMirror relationships alongside the same configuration and best-practices material as the originating platform. What that means practically is that the question to ask is not "does Lenovo replicate to NetApp" but "are these two specific ONTAP versions a supported pair for the relationship type I need".
Get that answer in writing against your actual version pair and relationship type before ordering. It is a five-minute question with a documented answer, and it is the single most expensive assumption to get wrong in a mixed estate.
When each one is the right buy
| Situation | Lean toward |
|---|---|
| ONTAP is already your standard and the team runs it daily | Lenovo DM/DG — same OS, same skills, generally better commercial terms |
| The storage sits inside a wider Lenovo server and networking estate | Lenovo — one support relationship across the stack is worth real money |
| Storage is the most complex and most business-critical part of the estate | NetApp direct — the specialist bench is the thing you are buying |
| You need a very recent ONTAP feature in the design | NetApp direct, unless the version is confirmed available on the Lenovo model |
| You plan to use third-party ONTAP consultants or an MSP | NetApp direct — deeper market for skills and services |
| You have no ONTAP investment at all | Neither, yet — pick the platform before the label |
That last row matters more than the rest. If ONTAP is not already your standard, choosing between Lenovo-branded and NetApp-branded ONTAP is answering the second question first. Settle the platform against the alternatives — our NetApp versus Pure Storage comparison covers that decision, and the wider selection question is in enterprise storage selection. Then, and only then, is the label a commercial optimisation.
What this means for a storage refresh
If you are replacing ageing ONTAP arrays, the OEM route is the cheapest defensible way to stay on the platform without retraining anyone or rewriting runbooks. Three things to settle before the order:
- The ONTAP version on the quoted model, and whether every data service in your design is supported on it.
- The replication pairing against whatever stays in place during and after the transition.
- The support boundary — who takes the call, who owns escalation, and what the entitlement is at each site rather than in the contract summary.
Where the arrays are part of a wider server refresh, the arithmetic of the whole programme is in server refresh and consolidation, and the procurement mechanics for something at that scale are in buying at project scale.
Get both badges quoted on one requirement
Send this and we price it — no questions back:
- Usable capacity required, and the performance target
- Data services the design depends on: replication, cloning, encryption, tiering
- Whatever ONTAP is already in the estate, with versions — for the replication pairing
- Installation address and target date
You get firm pricing, availability and delivered lead time within one business day.
No specification yet? Send the capacity and performance requirement. We size Lenovo DM/DG and NetApp independently against it, itemise the data services line by line rather than as bundle names, and price both.
Frequently asked questions
Is Lenovo storage really NetApp?
The DM and DG series run ONTAP — Lenovo Press names the operating system explicitly in the product documentation, Lenovo hosts the ONTAP manuals and SnapMirror guidance for these arrays under its own domains, and third-party vendors such as Veeam group Lenovo ThinkSystem DM/DG with NetApp ONTAP in a single integration family. The DE series is different: that is E-Series running SANtricity, not ONTAP.
Is Lenovo DM cheaper than NetApp AFF?
Frequently, yes, but treat headline comparisons carefully. The software bundles differ in composition between the two, so a price gap can partly reflect different data services included. Require both quotes to itemise replication, cloning, encryption and tiering individually rather than comparing bundle names.
Can a Lenovo DM array replicate to our existing NetApp?
SnapMirror compatibility is expressed in terms of ONTAP versions rather than brands, and Lenovo publishes the compatible-versions guidance for its arrays. So the question to put in writing is whether your two specific ONTAP versions are a supported pair for the relationship type you need — not whether the brands interoperate. Confirm it before ordering.
What is the difference between the DM, DG and DE series?
DM and DG both run ONTAP: DM is the unified hybrid and all-flash line, DG is QLC all-flash aimed at capacity-optimised primary and secondary workloads. DE is a separate platform entirely — E-Series with SANtricity, block-oriented, without ONTAP data services.
Do we lose ONTAP features by buying the Lenovo badge?
Not in general, but timing is real: features reach the originating platform first. Confirm the ONTAP version available for the specific Lenovo model quoted and check that every data service in your design is supported on it, in writing, before the order. Do not infer support from a NetApp release note.
When should we buy NetApp directly instead?
When storage is the most complex and most critical part of the estate and you are effectively buying the specialist support bench; when your design depends on a very recent ONTAP feature that is not yet confirmed on the Lenovo model; or when you intend to rely on third-party ONTAP consultants or a managed service provider, where the market for skills around the NetApp badge is deeper.
We have no ONTAP today — does this comparison apply?
Not yet. If ONTAP is not already your standard, choosing between two ONTAP badges is answering the second question first. Settle the platform against the alternatives, then treat the badge as a commercial optimisation.
Related
- NetApp vs Pure Storage — the platform decision that comes before the badge decision
- Enterprise storage selection — all-flash, NAS and SAN, and how to size against the workload
- NetApp selection guide · Lenovo ThinkSystem selection guide
- Which ThinkAgile series for which hypervisor — relevant if storage is moving into or out of the hyperconverged layer
- Server refresh and consolidation — when the arrays are part of a wider programme
- Buying at project scale · Lenovo stock and lead times · NetApp stock and lead times
Sources
- Lenovo Press — ThinkSystem DM Series unified storage arrays ("Powered by the ONTAP software")
- Lenovo Press — DM Series storage index (current DM model list)
- Lenovo Docs — compatible ONTAP versions for SnapMirror relationships · Lenovo — SnapMirror configuration and best practices guide for ONTAP 9
- Veeam — NetApp ONTAP, Fujitsu ETERNUS HX/AX, Lenovo ThinkSystem DM/DG (grouped as one integration family)
- Blocks & Files — Lenovo storage and HCI portfolio (DS Series reported as based on OEM'd NetApp ASA systems)