topic Re: Using Remove-NaSnapmirror, no release-able destinations in Microsoft Virtualization Discussions

Using Remove-NaSnapmirror, no release-able destinations

panayigreg — Thu, 05 Jun 2025 07:06:21 GMT

Has anyone managed to get the remove-nasnapmirror cmdlet to work? According to the help:

This convenience cmdlet completely deletes a SnapMirror relationship. After a series of sanity checks, this cmdlet
releases the mirror on the source, breaks the mirror on the destination, deletes any snapshots on the destination,
and deletes any sync or async SnapMirror schedule entries on the destination.

When I run it against a test snapmirror relationship I get "SnapMirror error: No release-able destination found that matches those parameters." but I'm not sure why.

Thanks

Re: Using Remove-NaSnapmirror, no release-able destinations

cknight — Mon, 01 Nov 2010 18:12:23 GMT

To completely remove a SnapMirror relationship, several steps are needed.

Release the SnapMirror on the source controller
Break the SnapMirror on the destination controller
Delete the destination snapshot
Delete async schedule, if any
Delete sync schedule, if any

These may all be accomplished via the Toolkit as follows:

Invoke-NaSnapmirrorRelease (source controller)
Invoke-NaSnapmirrorBreak (destination controller)
Remove-NaSnapshot (using BaseSnapshot field from Get-NaSnapmirror (destination controller))
Remove-NaSnapmirrorSchedule (destination controller)
Remove-NaSnapmirrorSyncSchedule (destination controller)

It sounds as if the first step isn't working in Remove-NaSnapmirror, so I suggest trying the steps individually to confirm.

Re: Using Remove-NaSnapmirror, no release-able destinations

panayigreg — Wed, 03 Nov 2010 10:13:46 GMT

Thanks - I was runing this whilst connected to the detsination filer hence that error, however I have now get another error of " destination is not in a snapmirrored state", I'm using the following while connected to the source controller

$filer2=connect-nacontroller -name filer2

remove-nasnapmirror -destination filer1:vol1 -source filer2:vol2 -sourcecontroller $filer2

if i connect to the destination and run get-nasnapmirror vol1 the volume is shown as being in a snapmirrored state.

Re: Using Remove-NaSnapmirror, no release-able destinations

cknight — Wed, 03 Nov 2010 16:35:17 GMT

You are correct to send Remove-NaSnapmirror to the destination controller. However, this code you posted has a bug that isn't immediately obvious:

$filer2=connect-nacontroller -name filer2

remove-nasnapmirror -destination filer1:vol1 -source filer2:vol2 -sourcecontroller $filer2

In this snippet, I think you are trying to send Remove-NaSnapmirror to the destination controller. However, the preceding line contains Connect-NaController, which will set the value of $global:CurrentNaController to filer2. This will cause Remove-NaSnapmirror to be sent to filer2.

There are various ways to fix this, the simplest being to use the -Transient switch:

$filer2 = Connect-NaController -Name filer2 -Transient

Remove-NaSnapmirror -Destination filer1:vol1 -Source filer2:vol2 -SourceController $filer2

Re: Using Remove-NaSnapmirror, no release-able destinations

panayigreg — Wed, 03 Nov 2010 16:57:24 GMT

Thanks - that's now worked.