topic Re: SVM DR Assistance in ONTAP Discussions

SVM DR Assistance

TABER_BRANDEN — Wed, 04 Jun 2025 15:14:52 GMT

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.

Re: SVM DR Assistance

robinpeter — Mon, 03 Apr 2017 19:41:29 GMT

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

Ensure that the names of the source volume and destination volume (including the root volume) are the same
View the names of the source volume and destination volume by using the snapmirror show command.
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.

Re: SVM DR Assistance

TABER_BRANDEN — Mon, 03 Apr 2017 20:21:42 GMT

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.

Re: SVM DR Assistance

robinpeter — Mon, 03 Apr 2017 20:33:43 GMT

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 ?

Re: SVM DR Assistance

TABER_BRANDEN — Mon, 03 Apr 2017 20:53:22 GMT

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

Re: SVM DR Assistance

robinpeter — Mon, 03 Apr 2017 21:18:31 GMT

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

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?language=en_US

Re: SVM DR Assistance

TABER_BRANDEN — Fri, 07 Apr 2017 15:06:10 GMT

Thanks this article helped accomplish what I needed to do.