Managing storage tiering by modifying a volume's tiering policy or tiering minimum cooling period

You can change the tiering policy of a volume to control whether data is moved to the cloud tier when it becomes inactive (cold). For a volume with the snapshot-only or auto tiering policy, you can also specify the tiering minimum cooling period that user data must remain inactive before it is moved to the cloud tier.

Before you begin

Changing a volume to the auto tiering policy or modifying the tiering minimum cooling period requires ONTAP 9.4 or later.

About this task

Changing the tiering policy of a volume changes only the subsequent tiering behavior for the volume. It does not retroactively move data to the cloud tier.

Changing the tiering policy might affect how long it takes for data to become cold and be moved to the cloud tier.

What happens when you modify the tiering policy of a volume in FabricPool

Procedure

Modify the tiering policy for an existing volume by using the volume modify command with the -tiering-policy parameter:
You can specify one of the following tiering policies:
- snapshot-only (default)
- auto
- all
- none
Types of FabricPool tiering policies
If the volume uses the snapshot-only or auto tiering policy and you want to modify the tiering minimum cooling period, use the volume modify command with the -tiering-minimum-cooling-days optional parameter in the advanced privilege level.
You can specify a value between 2 and 63 for the tiering minimum cooling days.

Example of modifying the tiering policy and the tiering minimum cooling period of a volume

The following example changes the tiering policy of the volume myvol in the SVM vs1 to auto and the tiering minimum cooling period to 45 days:

cluster1::> volume modify -vserver vs1 -volume myvol 
-tiering-policy auto -tiering-minimum-cooling-days 45