Which action will cause a currently in-sync SnapMirror relationship to fall out of sync?

Which action will cause a currently in-sync SnapMirror relationship to fall out of sync?

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

Answer: (D)

SnapMirror keeps the relationship in sync by both ends agreeing on how data is replicated, including the specific relationship definitions stored on each storage system. The destination uses its own snapmirror.conf to determine what to pull, from where, and under what rules. If you modify the snapmirror.conf for that relationship on the destination, you’re changing the destination’s understanding of the relationship. That misalignment can cause the destination to pull from the wrong source, apply updates differently, or reject updates, so the destination no longer matches the source. The in-sync state depends on that agreement being consistent, so altering the destination’s configuration directly disrupts it. In contrast, running an update from the source simply sends newer data along the existing relationship, which maintains or restores synchronization. Releasing the relationship or altering the source’s configuration doesn’t create the same direct misalignment at the destination—the destination’s copy of the relationship and its expectations remain intact or are handled differently—so those actions don’t cause the same immediate out-of-sync condition.

SnapMirror keeps the relationship in sync by both ends agreeing on how data is replicated, including the specific relationship definitions stored on each storage system. The destination uses its own snapmirror.conf to determine what to pull, from where, and under what rules. If you modify the snapmirror.conf for that relationship on the destination, you’re changing the destination’s understanding of the relationship. That misalignment can cause the destination to pull from the wrong source, apply updates differently, or reject updates, so the destination no longer matches the source. The in-sync state depends on that agreement being consistent, so altering the destination’s configuration directly disrupts it.

In contrast, running an update from the source simply sends newer data along the existing relationship, which maintains or restores synchronization. Releasing the relationship or altering the source’s configuration doesn’t create the same direct misalignment at the destination—the destination’s copy of the relationship and its expectations remain intact or are handled differently—so those actions don’t cause the same immediate out-of-sync condition.