2014-05-13 06:46 AM
Just wonder if i could pick the communities brains and gather some thoughts on how to proceed with some work i need to do.
We have a couple of v3240's and they have been previously configured. On the primary unit there is a series of volumes split between the 2 controllers shared by CIFS and each volume is Snap Mirrored to the secondary unit. So its a pretty simple set up but it has come to light that we need to re-configure these and use vFilers as a company standard has been set that says so. This is where i am a bit stuck as i've never touched Multistore & vFilers before and i don't have a simulator available to try this on as it wont run on my home pc
I just wonder what people with more experience than me might do here? Can you enable Multistore, create a vFiler unit and then attach previously configured volumes to it? From various posts and forums i've read i guess you can but everything i read talks about adding a new volume to a vFiler unit, not an existing volumes. Or is enabling Multistore as an after thought a bad thing to do and it would be advisable to basically start from scratch again?
Any thoughts, tips, ideas would be gratefully received.
2014-05-13 07:47 AM
Vfilers are the easiest thing and people should be using them.
You should look at creating a vfiler and then setup a dr-vfiler for DR.
You will need downtime and swing everything to a vfiler and either use CNAME or move the DNS records to them
2014-05-13 09:32 AM
One of the Insight labs I taught a few years back covers how to migrate to a vFiler... you can assign existing volumes to vFilers without a data migration, however there are reconfiguration requirements, for example, joining the domain with the same netbios name, creating the cifs shares, nfs exports, igroups and lun maps (if iscsi is used, if fcp you have to keep that in vfiler0). See below.. an outline of what needs to be done but not command line examples. We normally would have about a 4-8 hour PS engagement to do this for our customers depending on the complexity of what is being re-created in the vFiler.
It is possible to migrate an existing physical controller to a vFiler unit. There are many considerations to plan for moving a physical controller into a vFiler. There will be downtime to migrate to a vFiler, but if you plan (and pre-write commands or scripts) for all the considerations below, the downtime can be short. In many cases you may take vfiler0 and create more than one vFiler, and that can be extrapolated from the list below.
There are a lot of small things to migrate from vfiler0 into the vFiler and these considerations also apply when migrating from one physical controller to another physical controller. Below is a checklist of topics without ONTAP commands (anyone doing this work should know the commands or where to find them). A pre-written plan to execute on-site is the key to success when migrating to a vFiler from a physical controller.
2014-05-15 06:33 AM
Thanks for that Scott. That gives me a good idea on what i need to do. If i could get the NetApp simulator to work on my laptop i might be able to have a practice at this work before trying it on a live system.