Overview of SAN volume provisioning
Suggest changes
PDFs
ONTAP provides several basic options for SAN volume provisioning. Each option uses a different method for managing the volume space and space requirements for the ONTAP block sharing technologies. You should understand how each provisioning option works so you can choose the best option for your environment.
|
Placing SAN LUNs and NAS shares on the same FlexVol volume is not recommended. You should instead provision separate FlexVol volumes for your SAN LUNs and your NAS shares. This simplifies management and the replication deployments. It also parallels the way FlexVol volumes are supported in Active IQ Unified Manager (formerly OnCommand Unified Manager). |
Thin provisioning for volumes
When a thinly provisioned volume is created, ONTAP does not reserve any extra space when the volume is created. As data is written to the volume, the volume requests the storage it needs from the aggregate to accommodate the write operation. Using thin-provisioned volumes enables you to overcommit your aggregate, which introduces the possibility of the volume not being able to secure the space it needs when the aggregate runs out of free space.
You create a thin-provisioned FlexVol volume by setting its -space-guarantee option to none.
Thick provisioning for volumes
When a thick-provisioned volume is created, ONTAP sets aside enough storage from the aggregate to ensure that any block in the volume can be written to at any time. When you configure a volume to use thick provisioning, you can employ any of the ONTAP storage efficiency capabilities, such as compression and deduplication, to offset the larger upfront storage requirements.
You create a thick-provisioned FlexVol volume by setting its -space-slo (service level objective) option to thick.
Semi-thick provisioning for volumes
When a volume using semi-thick provisioning is created, ONTAP sets aside storage space from the aggregate to account for the volume size. If the volume is running out of free space because blocks are in use by block-sharing technologies, ONTAP makes an effort to delete protection data objects (Snapshot copies and FlexClone files and LUNs) to free up the space they are holding. As long as ONTAP can delete the protection data objects fast enough to keep pace with the space required for overwrites, the write operations continue to succeed. This is called a “best effort” write guarantee.
|
You cannot employ storage efficiency technologies such as deduplication, compression, and compaction on a volume that is using semi-thick provisioning. |
You create a semi-thick-provisioned FlexVol volume by setting its -space-slo (service level objective) option to semi-thick.
Use with space-reserved files and LUNs
A space-reserved file or LUN is one for which storage is allocated when it is created. Historically, NetApp has used the term “thin-provisioned LUN” to mean a LUN for which space reservation is disabled (a non-space-reserved LUN).
|
|
Non-space-reserved files are not generally referred to as “thin-provisioned files.” |
The following table summarizes the major differences in how the three volume provisioning options can be used with space-reserved files and LUNs:
| Volume provisioning | LUN/file space reservation | Overwrites | Protection data2 | Storage efficiency3 |
|---|---|---|---|---|
Thick |
Supported |
Guaranteed1 |
Guaranteed |
Supported |
Thin |
No effect |
None |
Guaranteed |
Supported |
Semi-thick |
Supported |
Best effort1 |
Best effort |
Not supported |
Notes
-
The ability to guarantee overwrites or provide a best-effort overwrite assurance requires that space reservation is enabled on the LUN or file.
-
Protection data includes Snapshot copies, and FlexClone files and LUNs marked for automatic deletion (backup clones).
-
Storage efficiency includes deduplication, compression, any FlexClone files and LUNs not marked for automatic deletion (active clones), and FlexClone subfiles (used for Copy Offload).
Support for SCSI thin-provisioned LUNs
ONTAP supports T10 SCSI thin-provisioned LUNs as well as NetApp thin-provisioned LUNs. T10 SCSI thin provisioning enables host applications to support SCSI features including LUN space reclamation and LUN space monitoring capabilities for blocks environments. T10 SCSI thin provisioning must be supported by your SCSI host software.
You use the ONTAP space-allocation setting to enable/disable support for the T10 thin provisioning on a LUN. You use the ONTAP space-allocation enable setting to enable T10 SCSI thin provisioning on a LUN.
The [-space-allocation {enabled|disabled}] command in the ONTAP Command Reference Manual has more information to enable/disable support for the T10 thin provisioning and to enable T10 SCSI thin provisioning on a LUN.