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

Question

Options

• ARunning snapmirroe update on the source storage system.
• BRunning snapmirror release on the source storage system.
• CModifying the /etc/snapmirror.conf file for the relationship on the source storage system
• DModifying the /etc/snapmirror.conf file for the relationship on the destination storage system.

• A
  8% (4)
• B
  2% (1)
• C
  12% (6)
• D
  78% (39)

Explanation

https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_snapmirror.1.html https://library.netapp.com/ecmdocs/ECMP1196979/html/man5/na_snapmirror.conf.5.html snapmirror update [ -S source ] [ -k kilobytes ] [ -s src_snap ] [ -c create_dest_snap ] [ -w ] For asynchronous mirrors, an update is immediately started from the source to the destination to update the mirror with the contents of the source. For synchronous mirrors, a snapshot is created on the source volume which becomes visible to clients of the destination volume. The snapmirror update command must be issued on the destination filer. snapmirror release source { filer:volume | filer:qtree } Tell SnapMirror that a certain direct mirror is no longer going to request updates. If a certain destination is no longer going to request updates, you must tell SnapMirror so that it will no longer retain a snapshot for that destination. This command will remove snapshots that are no longer needed for replication to that destination, and can be used to clean up SnapMirror- created snapshots after snapmirror break is issued on the destination The source argument is the source volume or qtree that the destination is to be released from. The destination argument should be either the destination filer and destination volume name or the destination filer and destination qtree path. You can use a line from the output of the snapmirror destinations command as the set of arguments to this command. The /etc/snapmirror.conf file exists on the node containing the mirror used for SnapMirror.

No community discussion yet for this question.