SnapMirror scheduled update delays due to concurrent snapshot creation
Applies to
- ONTAP 9
- AFF-A700
- SnapMirror Scheduled Updates
- Multiple volumes using frequent SnapMirror schedules
- Recovery Point Objective(RPO)
Issue
- During a DR simulation, it was observed that after a SnapMirror scheduled update at 22:30, database recovery on the destination included data up to 1 minute after the scheduled update time(e.g., data up to 22:31 was present)
- This led to confusion about the actual RPO and the timing of data transfe
Example:
Fri Sep 12 22:30:00 2025 CreateSnapshotDest [Sep 12 22:30:00]: ... action=Start source=vs01:src_vol destination=vs01_dst:dst_volFri Sep 12 22:31:09 2025 CreateSnapshotDest [Sep 12 22:30:00]: ... action=End source=vs01:src_vol destination=vs01_dst:dst_vol status=Success Note=Scheduled update operation is queued.Fri Sep 12 22:31:09 2025 ScheduledUpdate [Sep 12 22:30:00]: ... action=Start source=vs01:src_vol destination=vs01_dst:dst_volFri Sep 12 22:32:46 2025 ScheduledUpdate [Sep 12 22:30:00]: ... action=End source=vs01:src_vol destination=vs01_dst:dst_vol status=Success- The snapshot creation
CreateSnapshotDeststarted at 22:30:00 and completed at 22:31:09 - The SnapMirror update started immediately after snapshot creation finished
