#svm mobility cifs server migration

1 messages · Page 1 of 1 (latest)

fierce nexus
#

Hi folks, had to dig abit to find this:

Will SVM data mobility migrate the SVM configuration information for Active Directory and
Lightweight Directory Access Protocol (LDAP) authentication?
Answer: Yes, migration of Active Directory and LDAP authentication configuration is transferred to the
destination cluster as part of the migration.

Just so that i'm understanding this correctly; this does mean that I will not need to rejoin the SVM to the domain at the destination cluster?
But users will just need to refresh their connections? (assuming the migration works with no issues)

edgy hedge
#

Correct. And technically, users shouldn't even need to refresh anything, as the IP address will stay the same

prisma timber
#

is that like svm-dr with identity preserve = true?

dull whale
#

more than that. ISVM mobility will literally relocate the entire SVM to another cluster and then "clean up" (or delete) the svm from the source.

The few times I have used it, nobody noticed.

fierce nexus
#

I ran some tests between two sites... both on a cifs domain connected svm and an nfs enabled svm.

Both volumes were snapmirror sources with a destination at a third site.

During the migration, I had a Windows share open in one window and a continuous dd write running on the NFS volume. It didn’t miss a beat... it felt just like a regular LIF migration within the same cluster. The snapmirror protection follows the volumes.

The only (minor) issue I ran into was having to recreate a few custom cron schedules on the destination cluster, which caused a migration failure, but resumed fine once created.
The -check-only flag doesn’t seem to check for that and I’m not entirely sure why it’s necessary.

Other than that, everything worked flawlessly so far