NetApp platform: AFF, FAS and ASA

NetApp builds a shared data platform spanning on-premises, edge and cloud environments. Its foundation is the ONTAP operating system.

ONTAP provides consistent management, data protection, automation and cloud integration. In the hardware portfolio, the three primary families are AFF, FAS and ASA.

• AFF — unified all-flash arrays for file, block and object workloads;
• FAS — hybrid systems optimised for cooler data, backup, tiering and cyber vault economics;
• ASA — specialised all-flash arrays dedicated exclusively to SAN and block workloads.

The simplest selection rule: AFF for multi-protocol consolidation and high performance, ASA for simple and predictable SAN, FAS for economical large-capacity storage and data protection.

Table of contents

What the NetApp platform is

ONTAP — the shared foundation

AFF, FAS and ASA compared

NetApp AFF

NetApp FAS

NetApp ASA

Availability and cyber resilience

Cloud, virtualisation and container integration

How to choose an array family

Pre-project question list

Common misconceptions

Sources and further reading

What the NetApp platform is

The NetApp platform is a data infrastructure layer that combines:

1. Unified Storage — a shared data model on-premises and in public clouds;
2. ONTAP — the operating system and data services set;
3. NetApp Console — central fleet and hybrid-service management; this name replaces the earlier BlueXP brand;
4. Data Resilience — snapshots, replication, business continuity, cyber vault and ransomware protection mechanisms;
5. AI Data Services — discovering, classifying, managing and preparing data for AI solutions.

In practice this means one operational model across many hardware classes and data locations. Not every system supports an identical set of protocols and features. The clearest example is ASA, whose interface and data model are simplified for SAN.

ONTAP — the shared foundation

ONTAP abstracts the hardware layer and gives administrators a consistent feature set. Key concepts include:

• cluster — a group of nodes operating as one jointly managed system;
• HA pair — two controllers that take over for each other after a failure;
• SVM (Storage Virtual Machine) — a logical data server with its own protocols, interfaces and policies;
• local tier / aggregate — a pool of physical media from which logical space is allocated;
• FlexVol / FlexGroup — logical data containers for NAS or SAN workloads;
• LUN / namespace — a block storage unit presented to a host;
• storage unit and consistency group in ASA r2 — a simplified model for presenting and protecting SAN application data.

Key ONTAP services:

• Snapshot — a local read-only point-in-time image that mainly records changes and usually has a small capacity overhead;
• SnapMirror — replication to a second system or site for DR, backup and migration;
• SnapMirror active sync — synchronous protection for block applications and continuous availability between sites;
• FlexClone — fast, space-efficient data clones;
• FabricPool — policy-based movement of cooler data blocks from a performance tier to an object tier;
• deduplication, compression and compaction — reducing the physical data footprint;
• QoS — controlling and isolating workload performance;
• Autonomous Ransomware Protection — detecting unusual activity and supporting incident response;
• SnapLock and immutability mechanisms — protecting data from modification or deletion according to retention policy;
• REST API, CLI and System Manager — automation and operational management.

NetApp AFF

Characteristics

AFF, or All Flash FAS, is a family of unified all-flash arrays. The same cluster can serve block, file and — within a defined scope — object data. AFF is a strong choice when an organisation wants to consolidate workloads without building separate SAN and NAS silos.

AFF A-Series

The A-Series is optimised for high performance and low latency. Typical use cases include:

• critical Oracle, Microsoft SQL Server and SAP HANA databases;
• large VMware and VDI environments;
• Kubernetes clusters and stateful applications;
• analytics and AI/ML processing;
• consolidating workloads that need high IOPS and throughput.

The portfolio verified in November 2026 includes AFF A1K, A90, A70, A50, A30 and A20. For the largest configurations the vendor quotes up to 24 nodes, up to 40 million IOPS and up to 1 TB/s throughput. These are maximum values for specific configurations, not guaranteed performance of a single system.

AFF C-Series

The C-Series uses capacity-oriented flash media and is optimised for density and cost per terabyte. Typical use cases include:

• general-purpose workload consolidation;
• large repositories with moderate performance needs;
• Dev/Test environments;
• backup and DR targets when all-flash is required;
• migration from hybrid arrays to flash while preserving capacity economics.

The current family includes AFF C80, C60 and C30. When comparing offers, separate raw, usable and effective capacity. Effective capacity depends on an assumed data-reduction ratio and may not match every data profile.

AFF strengths and limitations

Strengths:

• multi-protocol NAS/SAN consolidation;
• shared ONTAP data services;
• non-disruptive scaling and data mobility;
• integrations with virtualisation, containers and cloud;
• rich protection and recovery mechanisms.

Limitations and design risks:

• a broad feature set may be unnecessary in a block-only environment;
• performance depends on controllers, drives, front-end and back-end networks and workload characteristics;
• declared effective capacity is not guaranteed usable capacity for arbitrary data;
• ONTAP S3 features do not replace a dedicated object platform such as StorageGRID in every scenario.

NetApp FAS

Characteristics

FAS is a family of hybrid ONTAP-based systems. The priority is storage economics and shared management with the rest of the NetApp environment. FAS fits well where part of the data does not require all-flash performance.

Typical use cases

• automatic tiering of less frequently used data;
• backup repository aligned with a 3-2-1 architecture;
• a second protection tier for AFF or ASA systems;
• a logically isolated cyber vault;
• long-term retention and large file datasets;
• environments with a predictable, moderate performance profile.

The current product line presented by NetApp includes FAS90, FAS70, FAS50, FAS2820 and FAS2750. They differ in scale, drive count and maximum capacity; all run ONTAP.

FAS strengths and limitations

Strengths: shared operational model with AFF, lower cost for cooler data, backup and tiering integration, and suitability as a cyber vault tier.

Limitations: lower and less predictable performance than all-flash systems, greater sensitivity to random I/O profiles, and the need to place data correctly across tiers.

NetApp ASA

Characteristics

ASA, or All SAN Array, is an all-flash family specialised for block data. ASA r2 systems have a simplified ONTAP interface and a management model tailored to SAN administrators. They are not intended to serve NFS, SMB or S3.

ASA r2 supports FC, iSCSI, NVMe/FC and NVMe/TCP. A symmetric active-active architecture lets hosts use all paths as active and optimised, simplifying multipathing and load balancing.

ASA A-Series and C-Series

• ASA A-Series — high performance, consistent sub-millisecond latency and critical transactional applications;
• ASA C-Series — high capacity density for block backup repositories, DR and modernising older hybrid environments.

The vendor positions ASA as a way to simplify provisioning, protection and hypervisor integration. Claims such as 100% availability, a 4:1 efficiency guarantee and ransomware recovery guarantees are subject to separate programme terms. They should not be treated as unconditional technical attributes of every deployment.

When ASA instead of AFF

Choose ASA when:

• all primary workloads are block;
• the team wants the simplest possible SAN operating model;
• symmetric active-active paths are essential;
• the environment is dominated by VMware, SAP or databases;
• there is no requirement to share the array between NAS and SAN.

Choose AFF when NFS, SMB, S3 and block protocols must run on one platform, or when unified-storage flexibility matters more.

Availability and cyber resilience

The NetApp platform combines several protection layers:

1. Controller HA — failover within a pair;
2. Snapshots — frequent local recovery points;
3. SnapMirror — a copy on a second system or site;
4. SnapMirror active sync / MetroCluster — continuity aligned with RPO and RTO requirements;
5. SnapLock and snapshot locking — protection against deletion according to policy;
6. Autonomous Ransomware Protection — anomaly detection in the storage layer;
7. cyber vault — an isolated, controlled copy for post-incident recovery;
8. encryption, RBAC, MFA and multi-admin verification — reducing the risk of administrative takeover.

A snapshot is not a full backup by itself, and HA does not replace DR. A sound design combines local resilience, an independent data copy, tested recovery procedures and monitoring.

Cloud, virtualisation and container integration

ONTAP also runs in software-defined and cloud models, and NetApp services are available natively with major cloud providers. That simplifies replication, migration and consistent data policies in a hybrid environment.

Key integrations include:

• VMware tooling and management from the virtualisation environment;
• SnapCenter for application-consistent protection of databases and apps;
• NetApp Trident for dynamic volume provisioning to Kubernetes;
• REST interfaces and Infrastructure as Code automation;
• NetApp Console for observing and managing hybrid services.

Trident capabilities and data-protection scope depend on version and system type. For example, ASA r2 has its own matrix of supported protocols and operations, so a container project must check current documentation.

How to choose an array family

Scenario A: shared platform for NAS, SAN and containers

Most often AFF. It provides multiple protocols, high performance and the full ONTAP data-services set.

Scenario B: SAN only for VMware and databases

Most often ASA. Simplified operations, active-active paths and modern SAN protocols matter more than multi-protocol flexibility.

Scenario C: backup, long-term retention and cyber vault

Most often FAS when cost per TB matters more than latency. For an all-flash requirement, consider AFF C-Series or ASA C-Series depending on protocol.

Scenario D: AI/ML and very high throughput

AFF A-Series can serve many AI environments, and AFF A90 is certified for NVIDIA DGX SuperPOD. For the largest specialised AI factories NetApp also offers the AFX architecture, covered in a separate article.

Pre-project question list

1. Is the workload file, block, object or mixed?
2. What peak IOPS, throughput and latency are required?
3. What share of data is amenable to deduplication and compression?
4. What RPO and RTO apply to each application?
5. Are two active-active sites required?
6. What expectations exist for immutability, cyber vault and ransomware recovery?
7. Will data be moved or tiered to the cloud?
8. Does the environment include Kubernetes, VMware, SAP or specific databases?
9. Does the organisation prefer purchase, Keystone subscription or a hybrid model?
10. Which OS, hypervisor, HBA, switch and protocol versions are supported in the IMT?

Common misconceptions

• AFF and ASA are not the same. Both families are all-flash, but AFF is unified while ASA is SAN-specialised.
• FAS does not mean slow archive-only storage. It still runs ONTAP and can serve production protocols, but its main advantage is economics.
• Effective capacity is not physical capacity. It depends on data reduction and stated assumptions.
• A snapshot does not replace an independent backup. It is one element of a protection strategy.
• Vendor guarantees have terms. They may require specific configuration, licensing, monitoring and operational procedures.
• The BlueXP name is historical. In current materials the management platform appears as NetApp Console.

Sources and further reading

[1] The NetApp Platform

[2] NetApp AFF

[3] NetApp FAS

[4] NetApp ASA

[5] ONTAP data management software

[6] ASA r2 documentation

[7] ONTAP documentation

[8] NetApp Hardware Universe

[9] NetApp Interoperability Matrix Tool

Authored from official NetApp materials. Confirm parameters, limits and warranty terms before design or purchase.