You should create volumes that are of the same size as the aggregate on which they are located and check that they are thinly provisioned. Volumes on AFA systems also have different efficiency policies than volumes on Hybrid systems.
About this task
Volumes created in aggregates owned by an AFA node have inline compression and inline deduplication enabled by default.
- Create a volume that is of the same size as the aggregate on which they are located:
| If you want to use... | Then do this... |
|---|
| Storage Manager | Create volumes by using the UI. |
| CLI | Enter the following command: volume create -vserver vserver_name -volume volume_name -aggregate aggregate_name [- size volume_size] [-autosize-mode {off | grow | grow_shrink}] [-space-guarantee {none|volume}] [-snapshot-policy snapshot policy] |
Example
The following example displays a volume being created with autosize mode off, no Snapshot policy, no space guarantee, and a fractional reserve equaling zero:
volume create -vserver vs0.example.com -volume user_jdoe -aggregate aggr0 - size volume_size -autosize-mode off -space-guarantee none -snapshot-policy none - Create the volume efficiency policy by using the default policy, daily schedule, and best-effort QoS policy:
| If you want to use... | Then do this... |
|---|
| Storage Manager | Create the efficiency policy by using the UI. |
| CLI | Enter the following command: volume efficiency policy create -vserver vserver name -policy text [-type Efficiency policy type] [-schedule schedule] [-qos-policy Efficiency QoS policy] |
Example
The following example displays a volume efficiency policy being created with the default policy, daily schedule, and best-effort QoS policy:
volume efficiency policy create -vserver vserver name -policy default -type scheduled -schedule daily -qos-policy best effort