ONTAP On-Premises vs Cloud: FSx, ANF, GCNV, and CVO

Decision guide comparing on-premises ONTAP with FSx for ONTAP, Azure NetApp Files, Google Cloud NetApp Volumes, Cloud Volumes ONTAP, and StorageGRID.

Start with the operating boundary

On-prem AFF/FAS/ASA and Cloud Volumes ONTAP (CVO) expose broad ONTAP control. AWS manages FSx for ONTAP infrastructure. Azure NetApp Files (ANF) and Google Cloud NetApp Volumes (GCNV) are native managed file services, not general ONTAP clusters with unrestricted CLI. StorageGRID is object storage, not an ONTAP placement choice.

# Inventory the control surface before migration
cluster::> system node show
Node   Health Eligibility Model
node1  true   true        AFF-A400
node2  true   true        AFF-A400
cluster::> vserver show
Vserver Type  State
svm1    data  running

Comparison

Choice	Control	Latency/data gravity	Cost model	Protection
AFF/FAS/ASA	Full hardware and ONTAP	Local; potentially sub-ms when full path supports it	CAPEX/subscription + facility/people	Snapshots/SnapMirror by platform and license
FSx for ONTAP	AWS-managed infrastructure; service-limited ONTAP administration	AWS VPC near EC2	Capacity/performance/backups/transfer	Snapshots, backup, supported SnapMirror
ANF	Azure API; no cluster administration	Azure regional service	Capacity pools/service level/transfer	Snapshots, backup, cross-region replication; interoperability varies
GCNV	Google Cloud API; no cluster CLI	GCP regional service	Pool/service level/transfer	Snapshots/backup/replication vary by tier/region
CVO	You operate ONTAP VMs	Cloud compute/disk/network path	License + compute/disks/object/I/O/egress	ONTAP snapshots and supported SnapMirror
StorageGRID	Self-managed object platform	S3, not NAS/SAN latency	Infrastructure/support/operations	Object ILM, not SnapMirror

Features, protocols, regions, performance, replication, and prices change. Check current documentation, region matrices, calculators, and contracts.

Tradeoffs that decide the answer

Control and skills: “same ONTAP everywhere” fits FSx/CVO concepts but managed services reshape the admin surface; ANF/GCNV use cloud control planes. Latency and gravity: on-prem favors nearby large datasets and deterministic paths; cloud favors compute already in-region. Benchmark—sub-ms is not guaranteed. Residency: map primary, replicas, backups, keys, logs, operators, and support access. TCO: compare 3–5 years of purchase, refresh, power, space and people against cloud capacity, tier, compute, backup, cross-region traffic, licensing and egress.

cluster::> volume show -fields size,available,percent-used
vserver volume size   available percent-used
svm1    app    50TB   12.4TB    75%
svm1    archive 200TB 91.2TB    54%
cluster::> statistics show-periodic -object volume -instance app \
  -counter read_ops|write_ops|avg_latency -interval 5

Hybrid patterns

Use SnapMirror for supported on-prem-to-cloud DR/migration and test identity, DNS, routes, clients, and failback—not just replication.

cluster::> snapmirror create -source-path svm1:app \
  -destination-path svm_cloud:app_dr -type XDP -policy MirrorAndVault
cluster::> snapmirror initialize -destination-path svm_cloud:app_dr
Operation is queued.

cluster::> snapmirror show -fields status,healthy,lag-time
source-path destination-path status       healthy lag-time
svm1:app    svm_cloud:app_dr Snapmirrored true    00:14:22
cluster::> snapmirror show -destination-path svm_cloud:app_dr -instance
Relationship Status: Idle
Healthy: true

FabricPool keeps an ONTAP namespace while tiering cold blocks to supported object storage. BlueXP manages supported resources across locations without erasing provider/service boundaries.

cluster::> volume show -fields tiering-policy,cloud-retrieval-policy
vserver volume  tiering-policy cloud-retrieval-policy
svm1    archive auto           default
cluster::> volume show-footprint -vserver svm1 -volume archive
Volume Footprint Total Footprint
108.8TB          109.2TB

When each wins

On-prem

Latency and local data gravity
Existing investment and staff
Air-gapped or specialized designs
Predictable high utilization

Cloud

Elasticity and fast provisioning
Compute already in cloud
No hardware lifecycle
Rapid multi-region DR capacity

Most organizations are hybrid: keep workloads near compute/dependencies and replicate where the support matrix permits.

cluster::> snapmirror list-destinations -source-path svm1:app
Destination Path   Relationship Type Status
svm_cloud:app_dr   XDP               Snapmirrored
cluster::> snapshot show -vserver svm1 -volume app
Vserver Volume Snapshot        Size
svm1    app    daily.2026-08-27 1.2GB

Shortlist worksheet

Question	Evidence
Where is compute?	Site/region, latency budget, dependencies
How much moves?	Seed, change rate, restore and egress
Who operates?	24×7 owner, CLI/API needs, upgrade boundary
Required features?	Protocols, clones, SnapMirror topology, security
What does it cost?	Base, peak, DR test, growth, and exit

cluster::> system license show
Serial Number: 1-80-000000
Owner: prod-cluster
Package Type Description
NFS     license NFS License
CIFS    license CIFS License
SnapMirror license SnapMirror License

Licensing models differ across products and releases; treat this only as inventory evidence.