Skip to main content
NetApp Knowledge Base

Why is the change not immediately reflected on destination volume for SM-S

  1. Last updated
  2. Save as PDF
Views:
58
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirror Synchronous (SM-S)

Answer

  • It is an expected behavior.
  • This situation occurs as an SM-S destination volume is redirected to the latest exported Snapshot copy, which is updated only once every six hours by default.
  • However, if wish to access the changed data immediately at the destination for test/verification purposes, manually initiate the SnapMirror update.
  • How often an SM-S relationship updates the exported Snapshot copy is controlled by the SnapMirror policy's -common-snapshot-schedule parameter.
  • Modify the -common-snapshotschedule parameter to a minimum of 30 minutes and a maximum of 24 hours.

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.