Is it normal that ResyncTransfer starts with SM-S Initialization completion?
Applies to
- ONTAP 9
- SnapMirror Synchronous (SM-S)
Answer
Yes, it is an expected behavior.
Additional Information
Sample of ASUP -> SNAPMIRROR-AUDIT-LOG-TXT.GZ:
Wed Jan 31 16:55:25 JST 2024 Initialize[Jan 31 16:02:41]:a25fa83d-c006-11ee-bd03-xxxxxxxxx Operation-Uuid=b8e66c16-c006-11ee-bd03-xxxxxxxxx Group=none Operation-Cookie=0 action=End source=src-svm:src-vol destination=dst-svm:dest-vol status=Success bytes_transferred=107064321094 network_compression_ratio=1.0:1 transfer_desc=Logical Transfer with Storage Efficiency - Optimized Directory Mode Note=Autoresync operation is queued.
Wed Jan 31 16:55:25 JST 2024 ResyncTransfer[Jan 31 16:55:25]:a25fa83d-c006-11ee-bd03-xxxxxxxxx Operation-Uuid=aac76742-f705-4c30-8e42-xxxxxxxxx Group=none Operation-Cookie=0 action=Start source=src-svm:src-vol destination=dst-svm:dest-vol
Wed Jan 31 16:55:27 JST 2024 ResyncTransfer[Jan 31 16:55:25]:a25fa83d-c006-11ee-bd03-xxxxxxxxx Operation-Uuid=aac76742-f705-4c30-8e42-xxxxxxxxx Group=none Operation-Cookie=0 action=Info Latest Snapshot copy snapmirrorPreXferAFS.c7ab5714-997b-11ee-9bf6-d039ea9d8299_2148474803.2024-01-31_165525 on the destination dst-svm:dest-vol is not the base Snapshot copy. Attempting a local-rollback-based SnapMirror resync to correct this issue.