V-Series front-ends other vendor storage. a vFiler is a 7-mode concept of a separate FAS (logical container) and a Vserver is a similar container but for Clustered ONTAP (cluster-mode). There are many differences between the two (vFiler runs on one node in a 7-mode ha pair, but a Vserver runs on all nodes in clustered ontap) but both are very similar in concept where they segment multi-tenant access but for different modes of ONTAP.
So depending on the mode of ONTAP you are running you could run a vFiler(s) (optional in 7-mode) or a Vserver(s) (required to serve data in clustered ONTAP).
vServer (cluster-mode only): Vservers can be thought of as a secure virtual storage system. It is made up of the volumes, which can be joined in a name space hierarchy, for NAS workload or the volumes could be individual sub-containers of LUNs, for a SAN workload. Vservers can be easily modified as well, scaling to several petabytes as needed.
Differences between vfiler and vservers:
Vservers in Cluster-Mode supersede vFiler capabilities by providing a single namespace, using resources from many nodes within the cluster, support for any Cluster-Mode data protocol, and includes fully-delegated role-based access control.
But we have the facility to move the volumes around which are attached to vservers that helps too for that local cluster but we can do the snapmirror of volumes and root to remote site - this works like vfiler migrate but is completely manual process not click'n' go.
Recreating all the cifs shares, exports, igroups and lun mappings… maybe a nice WFA project to create the features of vFiler migrate for Vservers…
It does come up where customers want to move a volume from on Vserver to another like vFilers but can’t…but good point they can snapmirror (as long as the volume language is the same for all volumes in the Vserver … another interesting requirement).