The type of space management you should use depends on many factors, including your tolerance for out-of-space errors, whether you plan to overcommit your aggregates, and your rate of data overwrite.
The following table can help you determine which space management capabilities best suit your requirements.
| If... | Then use... | Typical usage | Notes |
|---|---|---|---|
| You want management simplicity |
FlexVol volumes with a space guarantee of volume OR Traditional volumes |
NAS file systems | This is the easiest option to administer. As long as you have sufficient free space in the volume, writes to any file in this volume will always succeed. |
|
Writes to certain files must always succeed
You want to overcommit your aggregate |
FlexVol volumes with a space guarantee of file
OR Traditional volume AND space reservation enabled for files that require writes to succeed |
LUNS Databases |
This option enables you to guarantee writes to specific files. |
|
You need even more effective storage usage than file space
reservation provides
You actively monitor available space on your volume and can take corrective action when needed Snapshot copies are short-lived Your rate of data overwrite is relatively predictable and low |
FlexVol volumes with a space guarantee of volume
OR Traditional volume AND Space reservation on for files that require writes to succeed AND Fractional reserve < 100% |
LUNs (with active space monitoring)
Databases (with active space monitoring) |
With fractional reserve <100%, it is possible to use up all available space, even with space reservations on. Before enabling this option, be sure either that you can accept failed writes or that you have correctly calculated and anticipated storage and Snapshot copy usage. |
|
You want to overcommit your aggregate
You actively monitor available space on your aggregate and can take corrective action when needed |
FlexVol volumes with a space guarantee of none |
Storage providers who need to provide storage that they know
will not immediately be used
Storage providers who need to allow available space to be dynamically shared between volumes |
With an overcommitted aggregate, writes can fail due to insufficient space. |