#Migrating to new HW with FlexClones

1 messages · Page 1 of 1 (latest)

manic spear
#

I'd like some suggestions on the best way to approach this case:
I need to replace an AFF A300 2-node system with a new AFF C30 system. The challenge is that there are a lot of FlexClones on the volumes of the two SVMs on the A300 that need to be migrated as well.
There is plenty of space on the C30, so I'm not worried about losing some efficiency during the migration. Downtime of several hours is acceptable if needed.

Any suggestions?

sleek ether
#

If you are looking to migrate everything on each SVM, SVM migrate is an easy way to go. LIFs, vols, everything in the SVM is migrated in one go.

manic spear
#

Thanks for the reply. SVM migrate would be the easiest, I agree. Do you know if SVM migrate will migrate all flexclones as well?

sleek ether
#

Yes it should.

fathom nest
cursive pilot
#

SVM MIGRATE only works with NAS. I do not think it transfers any block-based storage (FCP/NVME/iSCSI)

harsh badge
#

It is supported for the ASA->ASAr2 migrations though, so I wouldn't be surprised if there's an FPVR to get SAN support for SVM migrate

hybrid latch
#

Will you extend the existing cluster with the new C30s, or will there be two separate clusters? I have a question. Do you write to the clone or not? If you don't write to the clones, you can mark the snapshot that was used for the clone, unmount the clone, perform the vol move or snapmirror, and recreate the clone based on the snapshot of the old clone. This only works if you don't change the clone. If there are changes, you need to copy the changes.

manic spear
#

Thanks for all the replies.

This System only uses NFS, so SVM migrate would be an option, but as OG1 wrote, SVM migrate is sadly not supported with FlexClones.

Yes, the clones are used actively (R/W) and can't be deleted.
Initially, I hoped to set up the C30 as a new cluster, but I guess I could convert the A300 to a switched cluster, add the C30s migrate that way.

I guess my best way to migrate the volumes / clones in the same cluster would be to first split all clone, then move the parent volumes as well as the clones using "vol move" according to: https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_do_I_move_a_volume_with_attached_FlexClones

The easiest way would probably be to use ARL, but AFF A to AFF C is sadly also not supported.