Creating a volume for FabricPool

You can specify one of the following tiering policies:

• snapshot-only (default)
• auto
• all
• backup (deprecated)
• none

Types of FabricPool tiering policies

The -cloud-retrieval-policy optional parameter enables cluster administrators with the advanced privilege level to override the default cloud migration or retrieval behavior controlled by the tiering policy.

You can specify one of the following cloud retrieval policies:

• default

  The tiering policy determines what data is pulled back, so there is no change to cloud data retrieval with default cloud-retrieval-policy. This means the behavior is the same as in pre-ONTAP 9.8 releases:

  • If the tiering policy is none or snapshot-only, then “default” means that any client-driven data read is pulled from the cloud tier to performance tier.
  • If the tiering policy is auto, then any client-driven random read is pulled but not sequential reads.
  • If the tiering policy is all then no client-driven data is pulled from the cloud tier.

• on-read

  All client-driven data reads are pulled from the cloud tier to performance tier.

• never

  No client-driven data is pulled from the cloud tier to performance tier

• promote

  • For tiering policy none, all cloud data is pulled from the cloud tier to the performance tier
  • For tiering policy snapshot-only, all active filesystem data is pulled from the cloud tier to the performance tier.

The -tiering-minimum-cooling-days optional parameter in the advanced privilege level enables you to specify the tiering minimum cooling period for a volume that uses the snapshot-only or auto tiering policy.

Starting in ONTAP 9.8, you can specify a value between 2 and 183 for the tiering minimum cooling days. If you are using a version of ONTAP earlier than 9.8, you can specify a value between 2 and 63 for the tiering minimum cooling days.