The transition to NetApp MS Azure AD B2C is complete. If you missed the pre-registration, you will be invited to register at next log in.Please note that access to your NetApp data may take up to 1 hour.To learn more, read the FAQ and watch the video.Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.
Is there any reason why one would use a vFiler for an NFS datastore for ESX? I'm running two dual-head FAS3140's in a replicated environment. I'm assuming that without a vFiler I'd be stuck with the IP configuration of vfiler0 but I'm looking for any upside/downside when making the decision.
Flexibility to move the vFiler without VMware knowing... some even create a vFiler per datastore (can be overkill but any way you could group it for mobility with data motion). It works near the same as vFiler0 and each vFiler can have its own IPSpace separate from vfiler0 (separate routing table if needed). It can also be helpful when you upgrade to a new controller and new disks with data motion to move between controllers.