#Migrate SVM ONTAP 9.10.1P13

1 messages · Page 1 of 1 (latest)

lapis prism
#

Hi All, Im looking for some guidenace on how to migrate a SVM from cluster 1 to cluster 2, The cluster 1 already has a SVM-DR relationship to cluster 3 which is cluster 2s SVM-DR location. Would it be as simple as Setup a new SVM-DR to cluster 2 and flip it and then setup a new SVM DR?

regal ether
#

The thing with Snapmirror SVM (the new name that I personally do not like!) is that you are allowed multiple destinations. Only one of them is allowed identity-preserve set to true. So if you’re currently using it, you may need to adjust it to set to false for the time being, redo the snapmirror to cluster 2 then maybe find a way to resync cluster 2 to cluster 3?

I think you may be able to use svm migrate also. I have not personally used that yet. The restrictions always got in the way (the source could never be updated to a supported version).

lapis prism
#

I dont think SVM migrate will be an option as its moving from a C190 to a AFF700

regal ether
#

That’s aff to aff. Might be possible

#

Remember the c190 is not really a c series it is an aff will be supported by using 9.10.1 and higher

pulsar river
#

svm migrate does not support SVM-DR (Source Volumes as far as i know), i think the idea with a new fan-out relationship to cluster2 and flipping identity preserve=true (if used) should work. Whats not mentioned yet: what workloads should be relocated? File, Block or both?

lapis prism
#

All file Frechna, We cant keep the IPs as they are in another DC

pulsar river
#

in that case i would deal with SVM-DR Fanout

lapis prism
#

Or what about remove the current SVM-DR and setup a new SVM DR to the new prod side? SVM-DR from old prod to new prod and then setup a new SVM-DR to the new DR site?

pulsar river
#

yeah for sure, that will work - even with identity preserve true and discard network config

lapis prism
#

Will it work with the SVM-DR to a normal SVM type or will it need to be a DP dst?