Storing
Thin Image pair and snapshot data in a
Dynamic Provisioning pool
You can create Thin Image (TI) pairs and store snapshot data in a Dynamic Provisioning pool.
The following figure shows a
Dynamic Provisioning pool that contains
Thin Image pair and snapshot data. When you use
Dynamic Provisioning and
Thin Image in one pool created from one parity group, the total capacity used by
Dynamic Provisioning and
Thin Image is required.
Dynamic Tiering and
active flash pools cannot be used for
Thin Image pairs.
When you create Thin Image pairs in a Dynamic Provisioning pool, you can use the Suspend TI pairs when the depletion threshold is exceeded option to prevent Thin Image pair operations from affecting the DP-VOLs in the pool. When this option is enabled and the depletion threshold for the pool is exceeded, Thin Image pair operations are suspended, so the depletion threshold of the pool functions as the upper limit capacity for the Thin Image pairs.
- When the depletion threshold is not exceeded:
- Thin Image pairs can be created.
- Thin Image pairs can be split.
- When the depletion threshold is exceeded and the Suspend
TI Pairs option is not enabled:
- Thin Image pairs cannot be created.
- Thin Image pairs can be split.
- When the depletion threshold is exceeded and the Suspend
TI Pairs option is enabled:
- SIM code 62Exxx is output.
- Thin Image pairs cannot be created.
- Thin Image pairs cannot be split.
For a Dynamic Provisioning pool that contains Thin Image pairs and snapshot data, the capacity of snapshot data is included in the used capacity of the pool.
If you are concerned about operations when Dynamic Provisioning and Thin Image share a pool, it is recommended that you use separate pools for Dynamic Provisioning and Thin Image.