How do platforms supporting QAT or zlib compression impact SnapMirror and volume move?
Applies to
- AFF and ASA A-Series platforms supporting QuickAssist Technology (QAT) and zlib compression
- A1K, A90, A70, A50, A30, A20
- SnapMirror
- Volume move (
vol move
)
Answer
Source | Destination | SnapMirror behavior | Volume move behavior |
|
|
All data compression savings are maintained |
All data compression savings are maintained |
|
|
zlib compression savings are reformatted to destination platform native compression savings (TSSE supported) |
zlib compression savings are reformatted to the destination platform native compression savings |
|
|
zlib compression savings are reformatted to destination platform native compression savings |
N/A |
|
|
All compression savings are written as zlib compression savings | All compression savings reformatted to zlib compression savings |
- Note: There is no need to explicitly enable compression on a SnapMirror destination. Doing so can result in SnapMirror not maintaining storage efficiency savings over the network
- Check a volume's compression algorithm by using the command:
::> volume efficiency show -fields state,compression-algorithm
Ensure that storage efficiency is enabled before concluding that any given compression algorithm is being used
Reformatting
- Reformatting QAT (zlib) compressed data to a non-QAT platform's native compression incurs additional overhead. This may result in a marginal performance impact to replication for both SnapMirror and volume move
- Due to the highly efficient QAT / zlib compression alogorithm, significant differences between source and destination volume sizes can result when replicating to or from a non-QAT platform
Additional Information
Parent topic: SnapMirror storage efficiency configurations and behavior