On Fri, 17 Jun 2011, Lawrence K. Chen, P.Eng. wrote: > One of the neat things about the zfs appliance, is the nfs migration > feature....we make the old share on netapp read-only, point all the > clients to the zfs appliance a creates a cache of the metadata and > starts copying the data over in the background (or on demand if a client > requests something that hasn't been copied over yet). At least that's > the theory....storage admin is grumbling that NetApp uses > /vol/<filesystem> on the exports and ZFS appliance is using > /export/<filesystem> and wants the ZFS appliance to do /vol before > trying the NFS migration in production. Guess I don't understand why > the name of the export is so important.
Well, the path of the share is defined both on the server and the client, so if you change the name of the share (like the location/path), the clients have to be changed. However, you should be using aliases in the shares instead of full paths anyway. I know the NetApp supports it -- ZFS probably does as well. So, /vol/<filesystem> becomes /filesystem. Of course, if you're actually changing NFS servers, you still need to change the client, but only once. Once it's done, you can change the path of the share on the same server and not have to make any modifications to the client, so it's a good idea anyway. -Adam _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
