Same ONTAP. Same integration.
Lenovo-branded ONTAP systems connect exactly as NetApp’s do: ProLion registers as an external FPolicy engine, nothing is installed on the controller, and the data path does not change.
Connected through FPolicy, as an external engine
How it connects.
Register a system and the platform discovers its topology. Monitoring runs through the file system’s own interface, by way of lightweight collectors in each data center, and analysis scans run on the schedule you set. Nothing is installed on endpoints, and everything stays on your own hardware, including at sites with no outbound connection.
What you get on Lenovo ONTAP.
Let’s solve your data challenges.
Connect with our engineers to find the right approach for your infrastructure.
A mixed estate is still one estate.
Most Lenovo ONTAP sites have NetApp somewhere too, and usually a Windows file server nobody mentions. They all land in one landscape tree, under one ruleset and one audit trail, so a question about a share does not start with working out whose badge is on the box.
- NetApp ONTAP— the same connector, side by side
- ClusterLion— automatic, audited failover for MetroCluster
- One console— Lenovo, NetApp, Dell and Windows in one tree
Talk to an engineer who knows your data.
Four fields, and somebody who knows ONTAP, PowerScale and what FPolicy does. Not a qualification call.