Skip to main content

Storage efficiency behavior with volume move and SnapMirror operations

Contributors netapp-lenida netapp-dbagwell dmp-netapp

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. This includes when you perform a volume move or SnapMirror operation and what happens when you perform a SnapMirror break and manually enable temperature-sensitive storage efficiency (TSSE) depends on the type of efficiency on the source volume.

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
Uncompressed data: 32K compression attempted after threshold days met
Newly written data: 32K compression attempted after threshold days met

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
Uncompressed data: 32K compression attempted after threshold days met
Newly written data: 32K compression attempted after threshold days met

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
Uncompressed data: 32K compression attempted after threshold days met
Newly written data: 32K compression attempted after threshold days met

TSSE with cold data scan algorithm as ZSTD

8K inline compression is attempted in TSSE format

File compressed data: N/A
Uncompressed data: 32K compression attempted after threshold days met
Newly written data: 32K compression attempted after threshold days met

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
Uncompressed data: 32K compression is attempted after threshold days met
Newly written data: 32K compression is attempted after threshold days met

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.