Which action will cause a currently in-sync SnapMirror relationship to fall out of sync if performed on the destination?

Which action will cause a currently in-sync SnapMirror relationship to fall out of sync if performed on the destination?

• A. Running snapmirror update on the destination system
• B. Running snapmirror release on the destination system
• C. Modifying the /etc/snapmirror.conf file for the relationship on the source system
• D. Modifying the /etc/snapmirror.conf file for the relationship on the destination system

Answer: (D)

SnapMirror stays in sync by following the relationship as defined on both systems, and the destination uses its own copy of the relationship configuration to know what to mirror from where. Editing the destination’s snapmirror.conf changes the rules that govern what the destination should accept from the source. That alteration can make the destination diverge from the source’s current state, so the relationship can go out of sync. Running an update on the destination simply applies missing changes under the existing rules, so it doesn’t cause a loss of synchronization. Releasing the relationship on the destination would terminate the relationship entirely, which is a different outcome than simply being out of sync. Modifying the source’s configuration could affect future mirroring, but the immediate cause of the destination falling out of sync is changing its own snapmirror.conf.

SnapMirror stays in sync by following the relationship as defined on both systems, and the destination uses its own copy of the relationship configuration to know what to mirror from where. Editing the destination’s snapmirror.conf changes the rules that govern what the destination should accept from the source. That alteration can make the destination diverge from the source’s current state, so the relationship can go out of sync.

Running an update on the destination simply applies missing changes under the existing rules, so it doesn’t cause a loss of synchronization. Releasing the relationship on the destination would terminate the relationship entirely, which is a different outcome than simply being out of sync. Modifying the source’s configuration could affect future mirroring, but the immediate cause of the destination falling out of sync is changing its own snapmirror.conf.