QuestionQ33

VerifiedData ONTAP 8.0 7-Mode Fundamentals

When deduplication runs on SnapVault destinations, which 3 statements are true?

Choose three
Explanation

Because SnapVault's qtree/volume-based transfer engine is not fully dedup-aware end-to-end, the primary system still sends previously deduplicated blocks in expanded form, so the destination must independently deduplicate the data it receives regardless of the source's own deduplication state. Deduplication savings are not visible until the Snapshot copy created by the baseline SnapVault transfer (which locks the shared blocks) ages out and those blocks are freed. To capture the savings sooner, NetApp's deduplication process for SnapVault destinations deletes the Snapshot copy created immediately by the transfer, performs the deduplication scan against the active file system, and then recreates that Snapshot copy so the space savings persist under the retained backup copy.

Community Discussion

No comments yet. Be the first to start the discussion!