PRODUCT OCI ONTAP Oct 01, 2026
What actually shipped?
An announcement shipped; the service did not. The joint release says OCI NetApp Storage Service is designed as an OCI-native managed service and is planned for GA within the next 12 months. Oracle’s product page labels it “coming soon.” There is no public GA region list, price sheet, service-level matrix or final compatibility document yet. The attached future-product disclaimer says the announcement is not a delivery commitment and must not be used as the basis for purchasing decisions.
What is concrete is the operating model Oracle and NetApp intend to deliver: procurement and support through Oracle; management through the OCI Console and SDKs as well as ONTAP APIs; and ONTAP data services exposed as a first-party OCI service. The stated workload scope includes databases, enterprise applications, virtualized environments, EDA/HPC, regulated applications and AI data pipelines.
What changes versus today?
| Decision point | Cloud Volumes ONTAP | Planned OCI NetApp Storage Service |
|---|---|---|
| Service model | ONTAP software deployed on cloud compute and operated by the customer, commonly through NetApp Console. | First-party OCI service; Oracle and NetApp describe the storage platform as fully managed. |
| Control plane | NetApp Console, ONTAP System Manager, CLI and APIs, subject to deployment. | OCI Console and SDKs plus ONTAP APIs and familiar workflows are announced. |
| Infrastructure lifecycle | Customer retains responsibility for sizing, upgrades and much of HA/platform operation. | The managed-service boundary should remove some platform lifecycle work, but the final responsibility matrix is not published. |
| Availability | Available now in supported clouds and regions. | Not GA; planned within 12 months of the September 29 announcement. |
This distinction is the same architectural fork covered in the Cloud Volumes ONTAP reference: a managed native service trades low-level control for provider-owned lifecycle operations. OCI NetApp Storage Service also complements rather than replaces OCI File Storage, Block Volume, Object Storage and File Storage with Lustre.
Capabilities announced—and not yet guaranteed
Oracle’s technical overview names multiprotocol file, block and object workloads; snapshots and clones; storage-native replication; application-consistent data protection; cold-data tiering; WORM retention; hybrid and multicloud mobility; QoS; FlexCache; FlexGroup; SnapMirror; SnapCenter; SnapLock; FabricPool; and Autonomous Ransomware Protection. These are useful design signals, but until GA documentation defines service tiers, protocol and feature limits, regions and support boundaries, treat every item as planned scope rather than an entitlement.
No ONTAP upgrade is implied. The announcement names no ONTAP version, minimum source release, upgrade path or maintenance window. It also publishes no known-issues list. Existing clusters should not be upgraded, reconfigured or licensed solely because of this news.
Migration and upgrade gates for admins
- Wait for the GA support matrix. Record source ONTAP versions, protocols, SVM topology, encryption, SnapLock mode, snapshot policies, QoS, FlexGroup/FlexCache use and application-consistency tooling. Map each one to an explicitly supported destination capability.
- Demand a responsibility matrix. Confirm who owns ONTAP upgrades, security patches, certificates, keys, backups, replication monitoring, incident response and capacity events. “Fully managed” does not mean the customer stops owning data policy, identity or application recovery.
- Design connectivity before data movement. Validate OCI VCN addressing, DNS, routing, private connectivity, latency and failure domains. Multiprotocol access also requires identity dependencies—such as Active Directory, DNS and time—to work from OCI.
- Test the data path and recovery path. A successful SnapMirror transfer is not application validation. Measure throughput and cutover time, then test host access, permissions, snapshots, restore, failover and failback with representative workloads.
- Model the exit. Obtain pricing, egress, minimum capacity, performance-tier and contract details at GA, and validate a documented route back to on-premises ONTAP or another target.
The broader placement trade-offs are mapped in the on-premises versus cloud guide and hybrid cloud hub.
Operational consequence
If the delivered service matches the announcement, OCI administrators gain a native procurement, support and automation surface while ONTAP teams retain familiar data-management concepts and APIs. The likely day-two shift is from maintaining controllers and ONTAP upgrades to governing service tiers, network access, identities, protection policies, replication and recovery evidence. The boundary is important: Oracle may operate the service infrastructure, but customers still own workload architecture, data classification, retention decisions and recovery outcomes.
Bottom line: put OCI NetApp Storage Service on the architecture watchlist, not the change calendar. Inventory dependencies now; make migration decisions only after GA documentation turns the roadmap into contractual limits and supported configurations.
Read the joint announcement (Oracle) · Hybrid cloud hub · Cloud Volumes ONTAP reference · On-prem vs cloud