#ONTAP SVM migration

1 messages · Page 1 of 1 (latest)

wise urchin
#

I need to relocate an SVM used by Trident and was wondering about SVM data mobility/SVM-DR for migration.
Is this as straight forward as it is with regular NAS volumes or does Trident use for example the volume UUID's to keep track of things?

For an SVM with over 100 volumes, how would you have migrated the Trident data?

wise urchin
#

I tried it out and SVM-DR (with identity) worked as far as I can tell, with one caveat; "vserver aggr-list" needs to be populated and then "tridentctl update backend" needs to be run.

shut plover
#

Hello, I have a question on the same argument, do the >= 9.10.1 vserver migrate feature can be used to migrate astra trident volumes non disruptively?

wise urchin
#

I believe so, but it is very limited. I couldn't use it because there were too many volumes.

steel wind
#

yeah, that's correct: you have to fill vserver aggr-list, then you can move volumes with vol move in the backend.... afterwards you have to update the trident backend and change vserver aggr-list to only include the new aggregate... (this assumes you move the data within the same cluster)

Moving the LIF is fully transparent