2011-09-28 07:29 PM - last edited on 2014-09-25 03:45 PM by alissa
I've set up a test lab for a vfiler migration as I need to do one in a few weeks time, but not having much success. Everytime I run vfiler migrate start vfilertest@ontapsim-01 I'm getting a connection refused error.
The simulators have been set up with the following configuration: (everything is images as I can't ssh directly into my test environment, using vsphere client to access)
When I run the vfiler migrate start command:
Any idea what Undefines error: 0 means?
Ping is working between both filers, I have also set up a snapmirror relationship between them to verify connectivity. I have set it up so that identical ipspace and volumes exists on both filers. Is there anything else I need to do?
Solved! SEE THE SOLUTION
2011-09-28 11:52 PM
By default, vfiler migrate uses rsh. With your syntax, you need to run "options rsh.enable on" on each node then it will work... but even better. "secureadmin setup ssl" then "secureadmin enable ssl"... then on your vfiler migrate start command add the parameter "-c secure" and it will use ssl.
Also...make sure you create the volumes of the same name on the target but don't initiate the mirrors...vfiler migrate will initiate.
2011-09-29 12:09 AM
Great! If you are going to the NetApp Insight Conference, we will be teaching advanced MultiStore which will cover vfiler migrate and other advanced features (DR, Data Motion, etc.).
2014-05-02 02:39 PM
Guys, i have do do real migration of vfiler, from your comments above, i will be using online or offline migration steps.
Do i need to create each volume on the destination system ( aggrigate) before conducting vfiler migrate cmd ? this is not very clear anywhere ? i would need to match the sizes as well ?
I am really getting stressed out over vfiler migration as i have over 25 volumes to migrate on one vfiler, nowhere in the process it says i need to create or will the process create the volumes ?
2014-05-02 02:42 PM
2014-05-05 02:38 PM
Also if you use the CLI, then make sure to vol options volname fs_size_fixed off on each target volume after migrate complete... PM handles this as part of the automation.
I would create a test vFiler to migrate then have the process worked out for either method you use, CLI, PM offline, PM online.