Solved: Storage Migration using NMC - Page 2

JLundfelt · ‎2012-04-23

Hey Everyone,

Have a quick question regarding using the NetApp Management Console. What is the most efficient way to migrate volumes between aggregates / controllers? Is it to

A) Create target volumes, and setup snapmirror relationships, restrict the source volume(s), complete the mirror(s), and change the CIFS / NFS export path(s)

B) Create target volumes, restrict the source volume(s), use ndmpcopy and change the CIFS / NFS export path(s)

C) Use NMC / Migration Manager to define datasets, and select resource pools to dynamically provision the targets, and CIFS / NFS export path(s)

Thanks in advance!

-Jon

arunchak · ‎2012-04-24

Hi,

SSM checks the eligibility criteria, which if fails it remains grayed out. For migration there shouldn't be any shars, exports or LUN maps associated with it..

Also please notice that we recommend to use this solution only on secondary volumes and not on primary volumes. Though it works for primary volumes, its not a foolproof mechanism as you need to manually export/map NFS/LUN.

>>Have to remove NMC dataset

You need not delete the dataset, you can break the relationship from ONTAP or induce a disaster on source which will make the secondary volume writable.

>>

2) NMC Secondary Space Management Wizard

Pro: Allows for one click volume migration

Con: Intra-controller only. Requires Source volume to be inaccessible during migration. Requires CIFS / NFS exports to be recreated

This is the reason we recommend it only for migrating secondary volume for which there won't be any exports.

Thanks,

Arun

View solution in original post

Storage Migration using NMC

Sign-up for Software Release Notifications!

Join us on Discord