#Migrate SVM ONTAP 9.10.1P13
1 messages · Page 1 of 1 (latest)
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).
I dont think SVM migrate will be an option as its moving from a C190 to a AFF700
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
This gives a pretty good idea of requirements
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?
All file Frechna, We cant keep the IPs as they are in another DC
in that case i would deal with SVM-DR Fanout
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?
yeah for sure, that will work - even with identity preserve true and discard network config
Will it work with the SVM-DR to a normal SVM type or will it need to be a DP dst?