Lag, caused by SnapMirror failures: replication transfer failed to complete
Applies to
- SnapMirror
- Data ONTAP 7 Mode
Issue
- Lag is observed for SnapMirror relationships
- From the logs, the relationships are failing.
Destination sm-log:
dst Wed Mar 3 00:07:01 UTC source-node:source_vol destination-node:destination_vol Request (Retry)
dst Wed Mar 3 00:07:08 UTC source-node:source_vol destination-node:destination_vol Start
dst Wed Mar 3 00:07:43 UTC source-node:source_vol destination-node:destination_vol Abort (replication transfer failed to complete)
Source sm-log:
src Wed Mar 3 00:07:02 UTC source-node:source_vol destination-node:destination_vol Request (10.216.28.15)
src Wed Mar 3 00:07:30 UTC source-node:source_vol destination-node:destination_vol Start
src Wed Mar 3 00:07:33 UTC source-node:source_vol destination-node:destination_vol Abort (Transfer failed)
- Note: Locked snapshot on the destination can also cause failure with similar errors. To confirm, check EMS log:
Thu Aug 21 21:13:02 CEST [NAME4: snapmirror.dst.snapDelErr:error]: Snapshot ****4(0142226993)_vol_Mon_Logs.29 in destination volume vol_Mon_Logs is in use, cannot delete.
If found, use "SnapMirror updates fail with error: replication transfer failed to complete" to resolve the issue.