Specifications

NetApp Deduplication for FAS and V-Series Deployment and Implementation Guide

The checksum type you can use with deduplication on a V-Series system is restricted. Only block checksum

type (BCS) is supported with deduplication on a V-Series system. Zoned checksums are not supported, and

a performance degradation will exist on random workloads with zoned checksums (ZCS). Refer to the Data

ONTAP Data Protection Online Backup and Recovery Guide for information about NearStore configuration.

For additional information regarding V-Series systems, refer to TR-3461, Best Practices Guide for V-Series.

4.8 DEDUPLICATION AND SNAPMIRROR REPLICATION

Although there are substantial benefits to be achieved with deduplication alone, a complete storage solution

typically involves the need to additionally mirror the data to another location for disaster recovery purposes.

Replication of the deduplicated volume is supported by using SnapMirror in two ways—volume SnapMirror

and –qtree SnapMirror, as discussed in the next two subsections. Keep in mind that deduplication is

supported only on NetApp storage systems that are running the NearStore option. So any flexible volume

shown in the following figures with deduplication running, even if it’s a SnapMirror ―primary,‖ is on a

NearStore option licensed system.

NetApp recommends not using deduplication with sync SnapMirror. Although technically it will work, the

integration and scheduling of deduplication with sync SnapMirror are complicated to implement in the type of

rigorous real-world scenarios that demand synchronous replication.

For a complete discussion of SnapMirror, refer to TR-3446, SnapMirror Async Best Practices Guide.

REPLICATING WITH VOLUME SNAPMIRROR

A deduplicated volume can be replicated to a secondary storage system (destination) by using volume

SnapMirror, as shown in Figure 3.

Figure 3) Volume SnapMirror replication of a deduplicated volume for disaster recovery.

To run deduplication with volume SnapMirror:

Deduplication must be licensed at the primary location (source). However, the NearStore option must

be licensed on both the source and destination (or an R200 must be used in one or both locations).

Starting with Data ONTAP 7.3.1, the NearStore license is no longer required on the destination system,

but installation of the deduplication license on the destination system is still recommended as part of the

best practices.

Deduplication does not need to be licensed at the destination. However, if the primary site is down and

the secondary location becomes the new primary, deduplication needs to be licensed for continued

deduplication to occur. Therefore the best practice is to have deduplication licensed at both locations.

In a volume SnapMirror relationship, the destination storage system should use an identical or later

release of Data ONTAP.