Skip to main content

NetApp ONTAP

NetApp ONTAP supports any S3-compatible object storage as a FabricPool capacity tier (cold-data offload) or Cloud Backup target.

Add Filebase as an object store​

storage aggregate object-store config create \
  -object-store-name filebase \
  -provider-type S3_Compatible \
  -server s3.filebase.io \
  -container-name my-ontap-bucket \
  -access-key YOUR_FILEBASE_KEY \
  -secret-password YOUR_FILEBASE_SECRET \
  -is-ssl-enabled true \
  -port 443

Attach to an aggregate (FabricPool)​

storage aggregate object-store attach \
  -aggregate aggr1 \
  -object-store-name filebase

Cold blocks now offload from aggr1 to Filebase as the storage policy dictates.

Tiering policies​

  • auto — ONTAP moves cold data to Filebase based on inactivity.
  • backup — ONTAP tiers backup-pinned data to Filebase.
  • all — all data goes to Filebase (with metadata kept locally).

Choose auto for typical NAS workloads where reads stay hot but cold data dominates capacity.

ONTAP Cloud Backup​

For backup (rather than tiering):

system smbc backup config create \
  -object-store-name filebase \
  ...

Performance considerations​

FabricPool reads from Filebase serve through the Filebase CDN, which keeps cold-block fetches reasonably fast for the geographically nearest user.

What's next​