When running deduplication on SnapVault destinations, which statement is true?

When running deduplication on SnapVault destinations, which statement is true?

• A. Deduplication internally synchronizes with the SnapVault schedule on the destination.
• B. The source SnapVault data is deduplicated inline on the target before it is written to disk.
• C. The source (primary) system sends duplicated data even if the source data is deduplicated.
• D. Deduplication savings are available after the baseline snapshot rolls off and the blocks are freed.

Answer: (A)

Deduplication for SnapVault destinations happens on the destination system and is driven by the destination’s own SnapVault transfer schedule. When new data arrives from a SnapVault transfer, the destination runs dedup in coordination with that schedule, reusing existing blocks where possible. This means dedup isn’t performed on the source during transfer, and you don’t have to wait for a baseline to roll off to see savings—the dedup process is tied to the destination’s backup cycles.

Deduplication for SnapVault destinations happens on the destination system and is driven by the destination’s own SnapVault transfer schedule. When new data arrives from a SnapVault transfer, the destination runs dedup in coordination with that schedule, reusing existing blocks where possible. This means dedup isn’t performed on the source during transfer, and you don’t have to wait for a baseline to roll off to see savings—the dedup process is tied to the destination’s backup cycles.