In every SnapVault update cycle, the destination (secondary) system automatically takes a read-only Snapshot copy of the volume that contains the replicated qtree(s). This Snapshot copy—whose name is derived from the Snapshot being transferred from the primary—serves two purposes:

1. It preserves a point-in-time, immutable backup on the secondary.

2. It becomes the baseline for the next incremental update.

Because the Snapshot is created on the secondary volume itself, the secondary system always “makes a snapshot of its own volume where the qtrees are located,” exactly as the statement describes.

Why the “False” option is wrong:

If the secondary did not create its own Snapshot copy, there would be no local, point-in-time image to satisfy retention policies or future incremental transfers. NetApp’s SnapVault architecture explicitly requires these secondary-side Snapshots; therefore denying their creation contradicts official product behavior.

1. NetApp

“Data Protection Online Backup and Recovery Guide for 7-Mode

” ONTAP 8.2

Section “How SnapVault update works

” p. 137:

“During a SnapVault update

the SnapVault secondary volume creates a Snapshot copy that corresponds to the primary Snapshot copy being transferred.”

2. NetApp

“ONTAP 9.3 Documentation Center – Data Protection Guide

” Section “SnapVault update

” step 2:

“The destination (secondary) system creates a new Snapshot copy of the destination volume before applying the incremental transfer.”

3. NetApp Technical Report TR-3487

“NetApp SnapVault Best Practices

” Rev. C

§4.3 “Snapshot copies on the secondary”:

“Each SnapVault update results in a new

locked Snapshot copy on the secondary volume that holds the protected qtrees. These copies are retained based on the configured retention schedule.”

(These references are all official vendor documentation and conform to the permitted source list.)