<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NFS Datastore in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NFS-Datastore/m-p/11500#M1158</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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).&amp;nbsp; It works near the same as vFiler0 and each vFiler can have its own IPSpace separate from vfiler0 (separate routing table if needed).&amp;nbsp; It can also be helpful when you upgrade to a new controller and new disks with data motion to move between controllers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Dec 2011 17:12:25 GMT</pubDate>
    <dc:creator>scottgelb</dc:creator>
    <dc:date>2011-12-13T17:12:25Z</dc:date>
    <item>
      <title>NFS Datastore</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NFS-Datastore/m-p/11495#M1155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there any reason why one would use a vFiler for an NFS datastore for ESX?&amp;nbsp; I'm running two dual-head FAS3140's in a replicated environment.&amp;nbsp; 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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:39:39 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NFS-Datastore/m-p/11495#M1155</guid>
      <dc:creator>DANTHEMAN</dc:creator>
      <dc:date>2025-06-05T06:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: NFS Datastore</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NFS-Datastore/m-p/11500#M1158</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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).&amp;nbsp; It works near the same as vFiler0 and each vFiler can have its own IPSpace separate from vfiler0 (separate routing table if needed).&amp;nbsp; It can also be helpful when you upgrade to a new controller and new disks with data motion to move between controllers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Dec 2011 17:12:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NFS-Datastore/m-p/11500#M1158</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2011-12-13T17:12:25Z</dc:date>
    </item>
  </channel>
</rss>

