Skip to main content
NetApp Knowledge Base

Leftover SnapMirror snapshot could not be deleted after a failed SnapMirror initialization

Views:
5,500
Visibility:
Public
Votes:
1
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

ONTAP 9

Issue

  • If SnapMirror initialization fails, SnapMirror relationship cannot be set up on source. A SnapMirror snapshot is left behind and cannot be deleted:

cm3220a-cn::> snapmirror release -source-path sv3220:sv_src10 -destination-path nfs3220:sv_dst10

Error: command failed: Source information for relationship with destination "nfs3220:sv_dst10" not found. (entry doesn't exist)

  • The SnapMirror initialization snapshot is left behind and cannot be deleted:

cm3220a-cn::> snapshot delete -vserver sv3220 -volume sv_src10 -snapshot *

Error: command failed on vserver "sv3220" volume "sv_src10" snapshot

'snapmirror.61ba83c0-badb-11e3-bd1a-123478563412_2147484781.2014-06-29_205633':

  • This snapshot copy is currently used as a reference snapshot copy by one or more SnapMirror relationships. Deleting the snapshot copy can cause future SnapMirror operations to fail:

Warning: Do you want to continue running this command? {y|n}: y

cm3220a-cn::> snapshot show -volume sv_src10
---Blocks---
Vserver Volume Snapshot State Size Total% Used%
-------- ------- ------------------------------- -------- -------- ------ -----
sv3220 sv_src10
snapmirror.61ba83c0-badb-11e3-bd1a-123478563412_2147484781.2014-06-29_205633
valid 80KB 0% 32%

This article describes the procedure to be followed to delete the leftover SnapMirror snapshot and return the volume back to a clean state.

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support