Volume Usage Limits

Volume usage limits determine how much of a volume can be consumed before an alert is sent to the administrator. When the usage limit is reached, the performance policy associated with the volume determines the next action (for example, whether to make the volume read-only or take the volume offline). An alert is also sent.

You can configure warning levels (a volume usage warning level and a snapshot usage warning level) below the usage limits so you get an alert before the limit is actually reached.

In most cases, you should set the quota to 100% (no quota). Some applications do not tolerate changes to volume sizes. Quotas were developed to address this issue. Using quotas lets you set a limit but leave room in case more space is needed.

For example, if you have an application that you do not want to fill all the space on the volume before more space is available for expansion, set a quota for the volume.You now have a safety factor, and when the quota is met, you can reset the quota, giving more space to the application.You can then plan for further expansion if necessary.

If the volume is approaching the quota limit, an event is logged. If enforcement is enabled, the administrator can access the system log to determine what follow-up actions to take, such as preventing the user from accessing more disk space or allocating additional disk space to the user.