The transition to NetApp MS Azure AD B2C is complete. If you missed the pre-registration, you will be invited to reigister at next log in.
Please note that access to your NetApp data may take up to 1 hour.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

ONTAP Discussions

SVM DR Assistance

TABER_BRANDEN

Hello. I am Trying to convert some existing snapmirror DP relationships to a SVM DR relationship per the article here: 
http://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-dpg%2FGUID-898A828D-B69E-4951-98AD-C8BF7D6DB7BA.html

When I run the command: snapmirror resync -destination-path *destination_SVM* it comes back with this error. I'm not sure how to get past it. Any advice?
Error: command failed: Could not determine whether msid needs to be preserved or not. Reason: Root volumes do not match.

 

Thanks in advance.

1 ACCEPTED SOLUTION

robinpeter

Since the MSID is different, you can use the options "-identity-preserve false" while create the SVM snapmirror relationship

 

or

 

Preserve the DR-volumes MSID

 

ClusterDR::> set diag
ClusterDR::*> debug vserverdr restamp-msid -vserver svmdr83 -preserve-msid true

 

here is the lil more detailed steps.

https://kb.netapp.com/support/s/article/ka31A0000000jXPQAY/how-to-preserve-nfs-file-handles-and-volume-msids-with-svm-dr-vserver-disaster-recovery?lan...

 

 

View solution in original post

6 REPLIES 6

robinpeter

In case if you haven't match the volume name on source and destination.

 

  1. Ensure that the names of the source volume and destination volume (including the root volume) are the same
  2. View the names of the source volume and destination volume by using the snapmirror show command.
  3. If the names are not the same, rename the destination DP volume to match the name of its source volume by using the volume rename command.

TABER_BRANDEN

Thanks for the suggestion. I have made sure all volumes except the root volume are mirrored and also that the name of the root volume is the same on both.

These steps from the article above worked for some other SVM's but I keep getting this msid error on others.

robinpeter

Can you please post the output of following commands.

 

ClusterPROD::> volume show -vserver svmprod01 -fields msid

ClusterDR::> volume show -vserver svmdr01 -fields msid

ClusterDR::> snapmirror show -fields msid-preserve

And what's your ontap version ? 

TABER_BRANDEN

DR::> vol show -vserver DRSVM -fields msid
vserver volume msid
------------ ------------- ----------
DRSVM volume1 2147485366
DRSVM volume2 2147485367
DRSVM volume3 2147485368
DRSVM volume4 2147485369
DRSVM SOURCESVM_root 2147484681
5 entries were displayed.

 

SOURCE::> vol show -vserver SOURCESVM -fields msid
vserver volume msid
--------- ------------- ----------
SOURCESVM volume1 2147484675
SOURCESVM volume2 2147484676
SOURCESVM volume3 2147484677
SOURCESVM volume4 2147484678
SOURCESVM SOURCESVM_root 2147484673
5 entries were displayed.

 

DR::*> snapmirror show -destination-path DRSVM: -fields msid-preserve
source-path destination-path msid-preserve
----------- ---------------- -------------
SOURCESVM: DRSVM: false

robinpeter

Since the MSID is different, you can use the options "-identity-preserve false" while create the SVM snapmirror relationship

 

or

 

Preserve the DR-volumes MSID

 

ClusterDR::> set diag
ClusterDR::*> debug vserverdr restamp-msid -vserver svmdr83 -preserve-msid true

 

here is the lil more detailed steps.

https://kb.netapp.com/support/s/article/ka31A0000000jXPQAY/how-to-preserve-nfs-file-handles-and-volume-msids-with-svm-dr-vserver-disaster-recovery?lan...

 

 

View solution in original post

TABER_BRANDEN

Thanks this article helped accomplish what I needed to do.

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public