Storage efficiency behavior with volume move and SnapMirror operations
Suggest changes
PDFs
The behavior of storage efficiency can be affected by other storage operations that are active or started at the same time. You should be aware of the impact of these operations on storage efficiency.
There are several situations where storage efficiency on a volume can be affected by other operations including volume moves, SnapMirror relationships, FabricPool volumes, and temperature-sensitive storage efficiency (TSSE).
FabricPool
The all tiering policy is commonly used on data protection volumes to immediately mark data as cold and tier it as soon as possible. There is no waiting for a minimum number of days to pass before the data is made cold and tiered.
Because the all tiering policy tiers data as soon as possible, storage efficiencies that rely on background processes, like 32K efficient adaptive compression (TSSE), do not have enough time to be applied. Inline storage efficiencies like 8K compression are applied as normal.
The following table describes the behavior of a source volume and destination volume when you perform one of these operations.
Source volume efficiency |
Destination volume default behavior |
Default behavior after manually enabling TSSE (after SnapMirror break) |
||||
|---|---|---|---|---|---|---|
Storage efficiency type |
New writes |
Cold data compression |
Storage efficiency type |
New writes |
Cold data compression |
|
No storage efficiency (likely FAS) |
File compression |
File compression is attempted inline on newly written data |
No cold data compression, data remains as it is |
TSSE with cold data scan algorithm as ZSTD |
8k inline compression is attempted in TSSE format |
File compressed data: N/A
|
No storage efficiency (likely FAS) |
File compression on C-Series platforms using ONTAP 9.11.1P10 or ONTAP 9.12.1P3 |
No TSSE-enabled cold data compression |
File compressed data: N/A |
TSSE with cold data scan algorithm as ZSTD |
8K inline compression |
File compressed data: N/A
|
No storage efficiency (likely FAS) |
TSSE on C-Series platforms using ONTAP 9.12.1P4 and later or ONTAP 9.13.1 and later |
8K inline compression is attempted in TSSE format |
File compressed data: N/A
|
TSSE with cold data scan algorithm as ZSTD |
8K inline compression is attempted in TSSE format |
File compressed data: N/A
|
File compression group |
Same as source |
File compression is attempted inline on newly written data |
No cold data compression, data remains as it is |
TSSE with cold data scan algorithm as ZSTD |
8k inline compression is attempted in TSSE format |
File compressed data: Not compressed
|
TSSE cold data scan |
TSSE using the same compression algorithm as source volume (LZOPro→LZOPro and ZSTD→ZSTD) |
8K inline compression attempted in TSSE format |
32K compression attempted with LzoPro after threshold days based coldness is met on both existing data and newly written data. |
TSSE is enabled. NOTE: LZOPro cold data scan algorithm can be changed to ZSTD. |
8K inline compression is attempted in TSSE format |
32K compression is attempted after threshold days coldness is met on both existing data and newly written data. |