Moving a volume to FabricPool

When you move a volume to FabricPool, you have the option to specify or change the tiering policy for the volume with the move.

Before you begin

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

What happens to the tiering policy when you move a volume

Step

Use the volume move start command to move a volume to FabricPool.
The -tiering-policy optional parameter enables you to specify the tiering policy for the volume.
You can specify one of the following tiering policies:
- snapshot-only (default)
- auto
- backup
- none
Types of FabricPool tiering policies

Example of moving a volume to FabricPool

The following example moves a volume named "myvol2" of the "vs1" SVM to the "dest_FabricPool" FabricPool-enabled aggregate. The volume is explicitly set to use the none tiering policy:

cluster1::> volume move start -vserver vs1 -volume myvol2 
-destination-aggregate dest_FabricPool -tiering-policy none