NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform.
You will still be able to view content, but posting and replying will be temporarily disabled.
To learn more, please review the information in this blog post.

Microsoft Virtualization Discussions

invoke-ncsnapmirrorupdate or resync for svm-dr

JGPSHNTAP
5,143 Views

I'm just curious if i'm missing something.

 

destination volume is required in both those cmdlets.

 

Well with svm-dr the command on the CLI is

 

snapmirror resync vservername: or snapmirror update vservername:

 

if you try to run 

 

invoke-ncsnapmirrorupdate it will fail b/c there is no destination volume, or if you try a volume you will get it's a member of a constituent.  

 

I know this must be something simple, Anyone?

 

 

2 REPLIES 2

SysWintel
4,394 Views

We are experiencing the same issue using the powershell commands invoke-ncsnapmirrorupdate

 

 

The CLI command below works fine just specifying the destination-vserver

 

snapmirror update -destination-vserver $DestVServer

 

 

 

 

The powershell command does not accept the DestinationvServer on its own

Invoke-NcSnapmirrorUpdate -DestinationVserver $DestVServer

 

When providing the DestinationVolume,The error "Invoke-NcSnapmirrorUpdate : Relationship with destination " $DestVServer:$DestVolume" is not a valid relationship for this operation because it is a constituent relationship of a vserver SnapMirror relationship." is diaplayed

 

Invoke-NcSnapmirrorUpdate -Controller $DestController -DestinationVserver $DestVServer -DestinationVolume $DestVolume

 

JGPSHNTAP - Did you find a workaround for this or get any response?

 

JGPSHNTAP
4,335 Views

Yes you have to build the variable with dr svr.  So somethiing like this. $destinationvserver:

 

 And i think we used destinationpath.    I will have to look later

Public