You should be aware of rules that dictate how you can assign storage objects to Storage QoS policy groups.
A storage object must be contained by the Storage Virtual Machine (SVM) to which the policy group belongs. You specify the SVM to which the policy group belongs when you create the policy group. Multiple policy groups can belong to the same SVM.
In the following illustration, the policy group pg1 belongs to SVM vs1. You cannot assign volumes vol2 or vol3 to policy group pg1 because those volumes are contained by a different SVM.
You cannot assign a storage object to a policy group if its containing object or its child objects belong to a policy group. The following table lists the restrictions.
|If you assign the...||Then you cannot assign...|
|SVM to a policy group||Any storage objects contained by the SVM to a policy group|
|Volume to a policy group||The volume's containing SVM or any child LUNs or files to a policy group|
|LUN to a policy group||The LUN's containing volume or SVM to a policy group|
|File to a policy group||The file's containing volume or SVM to a policy group|
In the following illustration, the SVM vs3 is assigned to policy group pg2. You cannot assign volumes vol4 or vol5 to a policy group because an object in the storage hierarchy (SVM vs3) is assigned to a policy group.
You can assign FlexVol volumes to policy groups. Infinite Volumes are not supported with Storage QoS.
The following FlexVol volume variations are not supported with Storage QoS: