Specifications

NetApp Deduplication for FAS and V-Series Deployment and Implementation Guide
27
Keep the following points in mind:
Deduplication is licensed on both the source and the destination.
Deduplication is enabled, run, and managed independently on the source and the destination.
Deduplication doesn’t yield any network bandwidth savings because qtree SnapMirror works at the
logical layer, and it sends undeduplicated data over the network.
Storage savings at the destination are not achieved automatically when qtree SnapMirror updates
(unlike volume SnapMirror), because the data that is sent over the network to the destination is not
deduplicated. This data must be deduplicated again on the destination after qtree SnapMirror has
transferred the data from the source.
The deduplication schedule is not integrated with the qtree SnapMirror update on either the source or
the destination; it must be configured independently.
Storage savings are achieved on both the source and the destination.
4.9 DEDUPLICATION AND SNAPVAULT
The behavior of deduplication with SnapVault is similar to the behavior of deduplication with qtree
SnapMirror, except for the following points. (For information about other aspects of running deduplication
with SnapMirror, see section ―Replicating with SnapMirror.‖)
The deduplication schedule is tied to the SnapVault schedule on the destination system. The
deduplication schedule on the source is not tied to the SnapVault update schedule, and it can be
configured independently on a volume, just like qtree SnapMirror.
Every SnapVault update (baseline or incremental) kicks off the deduplication process on the destination
after the archival Snapshot is created.
The archival Snapshot copy is replaced with a new one 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.)
The deduplication schedule on the destination cannot be configured manually, and the sis start
command is not allowed either. However, the sis start -s command can be run manually on the
destination.
The SnapVault update is not tied to the deduplication operation; that is, a subsequent incremental
update is allowed to run while the deduplication process on the destination volume from the previous
backup is still in progress. In this case, the deduplication process continues to run, but the archival
Snapshot copy does not get replaced after deduplication has finished running.
When using SnapVault, the maximum volume sizes for deduplication for the primary and secondary are
independent of one another. Volumes on each of the systems will need to abide by their respective
maximum volume size limits.
Protection Manager 3.7 and SnapVault integration with deduplication do not work optimally. This is
because deduplication replaces Snapshot copies. As a result, Protection Manager has to wait for
deduplication to finish before renaming Snapshot copies. During the time that Protection Manager waits,
it does not allow clients to list the Snapshot copies or restore from them. This adversely affects the
recovery point objective.
For additional information regarding SnapVault, refer to TR-3487, SnapVault Design and Implementation
Guide.
For additional information regarding Protection Manager, refer to TR-3710, Protection Manager Best
Practice Guide.
4.10 DEDUPLICATION AND SNAPVAULT FOR NETBACKUP
Deduplication is not supported with SnapVault for NetBackup. This applies to both structured (database) and
unstructured (file) data types. The following notes are provided as related information:
Deduplication in a configuration not based on SnapVault for NetBackup (for example, NetBackup
shared or flexible disk option) remains supported.