The behavior of deduplication with SnapVault is similar to the
behavior of deduplication with qtree SnapMirror, except for the
following points.
- Starting from Data ONTAP 7.3, deduplication is also supported on the SnapVault
destination volume.
- The deduplication schedule is tied to the SnapVault schedule on the destination system. The deduplication schedule on the source system is not tied to the SnapVault update schedule, and it can be configured independently on a volume, as in qtree SnapMirror.
- Every SnapVault update (baseline or incremental) starts a deduplication process on the destination system after the archival Snapshot is taken.
- A new Snapshot copy replaces the archival Snapshot copy
after deduplication has finished running on the destination. (The name of this new Snapshot copy is the same as that of the archival copy, but the creation time of this copy is changed).
- You cannot manually configure the deduplication schedule on the
destination system or run the
sis start command. However, you can run the sis start -s command on the destination system.
- The SnapVault update is not tied to the deduplication operation; that is, a subsequent incremental update is allowed to continue while the deduplication operation
on the destination volume from the previous backup is still in progress. In this case, the deduplication operation
continues, however the archival Snapshot copy does not get replaced after the deduplication operation
is complete.
Note: You can run a maximum of eight concurrent
deduplication operations on your
storage system. This number includes the
deduplication operations linked to
SnapVault volumes and those that are not linked to
SnapVault volumes.
Note: Protection Manager and deduplication is not a supported configuration.
