The snapvault update command, or its modern equivalent snapmirror update for SnapVault (XDP) relationships, is used to initiate a manual data transfer from the source (primary) system to the destination (secondary) system. This process is a "pull" operation, meaning the command must be executed from the CLI of the destination cluster or SVM. The secondary system contacts the primary system to pull the incremental changes captured in new Snapshot copies. Therefore, the command to perform the update is only available on the secondary system.

Stating the answer is "False" would imply that the snapvault update command could be executed from the primary system. This is incorrect. The primary system does not "push" updates to the secondary in a standard SnapVault relationship; it only responds to "pull" requests initiated by the secondary.

1. NetApp ONTAP 9 Command Reference: In the manual page for the snapmirror update command (which manages SnapVault relationships)

the description explicitly states its operational context: "You run this command from the destination cluster or SVM to start an update from a source volume to a destination volume."

Source: NetApp ONTAP 9 Commands

snapmirror update manual page.

2. NetApp ONTAP 9 Data Protection Guide: When describing the manual update process for SnapMirror relationships (which includes SnapVault)

the procedure confirms the location where the command is run.

Source: NetApp ONTAP 9.7 Data Protection Guide

Page 53

"Manually update a SnapMirror relationship". The guide states

"You can use the snapmirror update command from the destination CLI to update a data protection relationship."

3. NetApp Technical Report (TR-4015): This best practices guide reinforces the operational model of SnapVault/SnapMirror updates.

Source: NetApp TR-4015

"SnapMirror Configuration and Best Practices Guide for ONTAP 9"

Section 5.1 "Manual Updates". The document specifies

"A manual update is initiated from the destination cluster using the snapmirror update command."