#Migration With Data Mobilty and SVM-DR

1 messages · Page 1 of 1 (latest)

random summit
#

Hi folks,
We need to migrate a NAS SVM which is a source of SVM-DR relationship. We just need to migrate the source SVM. The destination cluster won’t be tech refreshed. As far as we know vserver migrate is not supported with SVM-DR. Our idea is the following:

  • Release and the delete the SVM-DR relationship.
  • Perform svm-migration of the source SVM to the new source cluster.
  • Recreate and resync the SVM-DR from the new source cluster to the same destination.

We have doubts if it’s possible to resync the relationship once migrated cause the source cluster will be different or we will have to recopy all the data once the SVM is migrated.

Any experience on this? Thanks!!

full tapir
#

As far as i understand svm migrate is a edge case of SVM-DR

#

in the sense it is automated for moving resources as SVM-DR , Network lifs and personality and volumes and after that remove the source entities

#

check pages 20-28

#

to be honest i would use SVM-DR instead of SVM migrate since i can controll better the cut-over time

#

and have more controll over the operation

strong dragon
#

There is an option with mobility: -auto-cutover false
That will allow a manual cutover when you are ready

random summit
#

Thanks for your comments. The idea is to use vserver migrate with manual cutover and cleaning. In case we use SVM-DR to migrate we would have the same problem with the current SVM-DR cause as far as I know fan out SVM-DR is not supported.

gray gorge
#

Documentation generally always states that only one SVMDR with identity-preserve:true is allowed. This is true in most cases.
However there is a provision for migration use-cases. If the second SVMDR / fan-out SVMDR is for migration (and will be temporary), both SVMDR fan-out can be identity-preserve:true.

#

You need to be on 9.4+ and in an elevated privilege for the commands to work properly to create the fan-out identity-preserve SVMDR. Aside from that, it is vital to ensure you test such a migration plan before implementing in production so you have all the steps down.

narrow sonnet
#

Hi, when using the manual cutover is this a disruptive process? Would clients lose access to the data. Saw a mention that I could take up 120seconds to cutover.