Correctly Releasing Snapmirror Relationships
Posted by Joe Thompson on June 7, 2011
Over the last couple of weeks I’ve been tidying up a NetApp backup configuration and have repeatedly hit the same issue when removing snapmirror relationships.
Each time it’s taken me a long time to find the solution, but for ease of my memory next time round, here it is reproduced from the NOW site in full:
A snapmirror relationship has been deleted from FilerView or the snapmirror.conf file, but the relationship still appears under “snapmirror status”.
Snapmirror release fails with “no releasable destinations.”
Take the following steps to correctly delete a snapmirror relationship:
- Quiesce and break the snapmirror.
- Run “snapmirror status -l” to find what the base snapshot is:
destfiler> snapmirror status -l test_dst
Snapmirror is on.
Mirror Timestamp: Wed Jun 17 15:18:02 EDT 2009
Base Snapshot: srcfiler(0101168974)_test_dst.5 <— this is the baseline snapshot
Current Transfer Type: Scheduled
Current Transfer Error: None
Last Transfer Type: Scheduled
Last Transfer Size: 76 KB
Last Transfer Duration: 00:00:04
Last Transfer From: srcfiler:test_src
- Delete the baseline snapshot from the source filer’s volume:
srcfiler> snap delete test_src srcfiler(0101168974)_test_dst.5
Run “snapmirror release source_vol destfiler:dest_vol” on the source. This will delete the baseline snapshot on the source volume as well.
- Delete the schedule from snapmirror.conf on the destination filer, or delete the schedule from FilerView under Snapmirror -> Manage.After a minute or two, run snapmirror status. The relationship should no longer be present.
destfiler> snapmirror status test_dst
Snapmirror is on.
Occasionally, a stale, orphaned entry remains in snapmirror status on the source filer:
Progress: 0 KB
Mirror Timestamp: -
Base Snapshot: -
Current Transfer Type: -
Current Transfer Error: -
Last Transfer Type: -
Last Transfer Size: -
Last Transfer Duration: -
Last Transfer From: -
On the destination filer, the volume has been deleted and the relationship does not show up.
The solution is to issue the snapmirror release command from the source filer. This command will result in the following output:
sourcefilername destfilername:destvol: No release-able destination found that matches those parameters. Use ‘snapmirror destinations’ to see a list of release-able destinations.
However, the orphaned snapmirror relationship will be removed.