Known limitations for Cloud Volumes ONTAP 9.5 Edit on GitHub Request doc changes

Known limitations identify platforms, devices, or functions that are not supported by this release of the product, or that do not interoperate correctly with it. Review these limitations carefully.

HA limitations in Azure

The following limitations affect Cloud Volumes ONTAP HA pairs in Microsoft Azure:

  • Data tiering is not supported.

  • NFSv4 is not supported. NFSv3 is supported.

  • HA pairs are not supported in US Gov regions and in Germany regions.

Pay-as-you-go not available for CSP partners

If you are a Microsoft Cloud Solution Provider (CSP) partner, you cannot deploy Cloud Volumes ONTAP Explore, Standard, or Premium because pay-as-you-go subscriptions are not available for CSP partners. You must purchase a license and deploy Cloud Volumes ONTAP BYOL.

Disks and aggregates must be managed from Cloud Manager

All disks and aggregates must be created and deleted directly from Cloud Manager. You should not perform these actions from another management tool. Doing so can impact system stability, hamper the ability to add disks in the future, and potentially generate redundant cloud provider fees.

Storage Virtual Machine (SVM) limitation

Cloud Volumes ONTAP supports one data-serving SVM and one or more SVMs used for disaster recovery.

Cloud Manager does not provide any setup or orchestration support for SVM disaster recovery. It also does not support storage-related tasks on any additional SVMs. You must use System Manager or the CLI for SVM disaster recovery.

SnapManager licensing limitation

SnapManager per-server licenses are supported with Cloud Volumes ONTAP. Per-storage system (SnapManager suite) licenses are not supported.

Unsupported ONTAP features

The following features are not supported with Cloud Volumes ONTAP for AWS:

  • Aggregate-level inline deduplication

  • Disk maintenance center

  • Disk sanitization

  • Fibre Channel (FC)

  • Flash Pools

  • FlexCache

  • Infinite Volumes

  • Interface groups

  • Intranode LIF failover

  • MetroCluster

  • Multi-tenancy (only one data-serving SVM is supported, as noted in the SVM limitation above)


  • Service Processor

  • SnapLock Compliance mode (Enterprise mode is supported)

  • VLANs