Learn about FabricPool for AFX storage systems
Beginning with ONTAP 9.19.1 P3, you can configure FabricPool to extend the usable capacity of your AFX storage system as well as reduce costs and improve efficiency.
FabricPool overview
FabricPool is an ONTAP feature that moves data between a high-performance local tier and lower-cost remote cloud or capacity tier based on the data's activity or "temperature." It keeps the frequently accessed hot data on fast local SSD storage while moving the rarely used cold data to less expensive object storage. FabricPool operates automatically and transparently in the background; it doesn't require application changes or significant ongoing administration. Related ONTAP storage efficiency features, such as compression and deduplication, are preserved when data moves to the cloud tier and back.
FabricPool tiering is supported for AFX storage systems with ONTAP 9.19.1 P3 and later releases, expanding AFX cluster capacity beyond the local tier for data-heavy workloads. Although the AFX implementation of FabricPool introduces a few architectural changes, the core operation and characteristics of the ONTAP feature remain the same.
Administrators continue to control data tiering through per-volume policies as well as a minimum cooling period which defines when inactive data becomes eligible to be moved. This policy-driven model improves storage economics by reclaiming costly flash capacity and offering a simple path to a hybrid storage environment. It keeps the tiered data protected and available with minimal performance impact on the active working set.
Compare AFF and FAS with AFX implementations
While FabricPool behavior is very similar across ONTAP personalities (unified ONTAP for AFF and FAS systems, and the AFX ONTAP personality for AFX systems), the disaggregated AFX architecture introduces several differences. The most important areas for comparison between these two implementations are summarized below.
| Area or operation | AFF and FAS storage | AFX storage |
|---|---|---|
Object store scope |
Configured per aggregate with two steps; config create and then attach |
Configured at the cluster level with a single command; one bucket defined per cluster |
Default tiering policy |
Default policy is |
Default policy is |
Temperature tracking |
Per-volume granularity |
Per-volume granularity |
Cloud tier providers |
StorageGRID, ONTAP S3, and several major public clouds |
Only StorageGRID or ONTAP S3 |
Mirroring with MetroCluster |
Supported |
Not supported |
Volume movement |
Standard and optimized volume move |
Zero Copy Volume Move (ZCVM) without moving capacity tier data |