SnapMirror relationship converted from sync to async later fails reverse resync
Applies to
- ONTAP 9
- SnapMirror relationships converted from SnapMirror Synchronous (SM-S) or SnapMirror ActiveSync (SM-as) to Asynchronous XDP
Issue
- A SnapMirror relationship was previously configured as SnapMirror Synchronous (SM-S) or SnapMirror ActiveSync (SM-as)
- The synchronous relationship was later converted to asynchronous SnapMirror
- When a reverse or flip resync is later attempted, snapmirror resync fails with:
Failed to create snapshot "snapmirror.<UUID>_<ID>.<timestamp>" on destination volume "<vserver>:<volume>". (Volume is in a SnapMirror Automated FailOver relationship and is fenced for protocol access)
Additional related errors may include:
Cannot reverse the direction of this SnapMirror relationship because its source endpoint is involvedSnapMirror relationships remain unhealthy and do not resync; DR protection cannot be restored
Relevant log output:
WAFL_FENCE_VOLUMEandwafl_init_sync_repl_vol_datamessages in sktrace logs during reverse resync- SnapMirror show output indicates
Healthy: falseandUnhealthyReason: Transfer failed. - Persistent fencing flags may be present on affected volumes
