#SVM Migration

1 messages · Page 1 of 1 (latest)

jovial viper
#

Hello all, I had a few questions about SVM Migration. I have reviewed this link as my source but sometimes documentation is not always up-to-date https://docs.netapp.com/us-en/ontap/svm-migrate/?utm_source=chatgpt.com#supported-and-unsupported-features. Are Flex Group volumes still not supported as part of the migration?

The key function I want to make sure of below is will it move ALL export policies and rules for NFS volumes?

SVM Migration moves the entire SVM configuration and data, including:

Volumes
LIFs (CIFS, NFS, iSCSI, etc.)
CIFS server configuration (AD join, shares, share ACLs)
NFS configuration
Export policies and all export rules
Name services (DNS, LDAP, NIS configs)
Local users/groups
Snapshot policies
QoS policies

twilit kraken
#

@jovial viper currently FlexGroup volumes are not supported. Please contact your account team and have them open a FEPVR on your behalf. This will help product managment prioritize this feature. I know its a very popular ask but it cant hurt to have one more. It will help bump the priority!

Thank you!

jovial viper
#

@twilit kraken But everything else that will migrated looks to be correct, especially the NFS related items?

serene anvil
#

and the other bummer with FlexGroups...does not support "volume rehost".
I was thinking I could re-host the FG outside the SVM, use snapmirror on it (which is supported) and then re-host on the destination. Unfortanately, that is not a work around.

#

Oh...also pretty sure (unless something has changed) it only works for NAS. If there are any LUNs/iSCSI/etc, the SVM migrate will fail

#

Just checked. FC SAN and iSCSI SAN are not supported

#

If you need it, there is a hack. a brief downtime.
Basically, and I did this with a customer a few weeks ago...first migrate the iSCSI out of the SVM (so no SAN protocols left) and then SVM-migrate the rest.
I can give the details if you want them

twilit kraken
#

@jovial viper yes all NFS related items will be migrated. You can use vserver migrate start –check-only true to confirm. @pine sorrel can you please confirm?

serene anvil
#

The check only is great. It will find things that won’t go. Like luns, enabled block protocols, flexgroups, etc.

Find the issues, correct the issues and check again.

Then after it runs, I usually expect it to transfer everything and eventually fail on service-policies/firewall-policies.

Silly. ONTAP stopped using them long ago. Service-policies fully replace them. Yet svm-migrate will see and fail if there is something amiss with them

jovial viper
#

Perfect, thanks folks, appreciate the feedback!

jovial viper
#

Last question, I promise. When running the migration with "-auto-cutover false" the migrate tool will simply maintain a continous sync of data between the volumes (cluster) until you actually cutover, correct?

main wharf
#

Yes, it will hold pending a manual cutover trigger