Qtree SnapMirror with deduplication

Qtree SnapMirror does not automatically initiate a deduplication operation at the completion of every individual qtree SnapMirror transfers. You can set up a deduplication schedule independent of your qtree SnapMirror transfer schedule.

When using qtree SnapMirror with deduplication, remember the following:

You need to enable both deduplication and SnapMirror licenses.
Deduplication can be enabled on the source system, the destination system, or both systems.
Even with deduplication enabled on the source system duplicate blocks are sent to the destination system.
Therefore, there are no network bandwidth savings.
You should set up the deduplication and SnapMirror schedules so that the SnapMirror transfers start after the deduplication operation completes. Otherwise the deduplicated blocks remain locked in the SnapMirror base Snapshot copy.
Note: There is one base Snapshot copy per qtree SnapMirror relationship.
The deduplication schedule is not tied to a qtree SnapMirror update and can be configured just like the deduplication schedule for any volume.