The key requirement is that the vFiler owns ALL volumes in the aggregate that will be reassigned. If there is a volume from any other vFiler in that aggregate, it will fail.

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Kawakubo, Ken
Sent: Monday, February 06, 2012 11:25 AM
To: toasters@teaparty.net
Subject: anybody has experience using snapmover?

Dear list,

We have an active-active cluster with vfilers. One vfiler in node-1 is having performance issues. Since node-1’s CPU usage is much higher than node-2. I would like to migrate the vfiler from node-1 to node-2.

I found a feature called snapmover in vfiler manual. I found that the command "vfiler migrate -m nocopy" migrates a vfiler from node-1 to node-2 without actually copying data. This command merely changes the software disk ownership of disks that make up the vfiler and is non-disruptive. Furthermore, snapmover is now a non-license feature. Sounds too good to be true?

I want to know if there is any gotcha using snapmover. Does anybody have experiences using "vfiler migrate -m nocopy" command?

Our cluster is NetApp V3170.

Regards,

Ken Kawakubo