<?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 Advice on creating vol and LUNs in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Advice-on-creating-vol-and-LUNs/m-p/18223#M1622</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with that...The best practice is to not mix nas and san data in the same volume...even though it does work it is best to keep separate.&amp;nbsp; They can still share the same aggregate for more spindle I/O.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Oct 2011 21:08:19 GMT</pubDate>
    <dc:creator>scottgelb</dc:creator>
    <dc:date>2011-10-12T21:08:19Z</dc:date>
    <item>
      <title>Advice on creating vol and LUNs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Advice-on-creating-vol-and-LUNs/m-p/18218#M1621</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am looking on some advice on how to design the storage structure when creating vols, luns and cifs.&amp;nbsp; When we recieved our netapp a couple of months ago a tech from the vedor set everything up and gave us a quick rundown on how to manage it.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;His recommendation was that for every LUN or CIFS that needed to be created it was a good practice to create each one its own volume.&amp;nbsp; So far i have been following that method but i wanted to poll the community pro's on what they thought about doing it this way.&amp;nbsp; I really dont see any harm in it but Im new to the game and wanted to make sure im following the proper methods when it comes to administering the storage. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:43:49 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Advice-on-creating-vol-and-LUNs/m-p/18218#M1621</guid>
      <dc:creator>stanleyj42</dc:creator>
      <dc:date>2025-06-05T06:43:49Z</dc:date>
    </item>
    <item>
      <title>Advice on creating vol and LUNs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Advice-on-creating-vol-and-LUNs/m-p/18223#M1622</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with that...The best practice is to not mix nas and san data in the same volume...even though it does work it is best to keep separate.&amp;nbsp; They can still share the same aggregate for more spindle I/O.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2011 21:08:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Advice-on-creating-vol-and-LUNs/m-p/18223#M1622</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2011-10-12T21:08:19Z</dc:date>
    </item>
    <item>
      <title>Advice on creating vol and LUNs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Advice-on-creating-vol-and-LUNs/m-p/18229#M1623</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I second that, mixing SAN &amp;amp; NAS data in the same volume can lead to a number of issues so rule of thumb: keep them separate&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2011 21:25:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Advice-on-creating-vol-and-LUNs/m-p/18229#M1623</guid>
      <dc:creator>andrc</dc:creator>
      <dc:date>2011-10-12T21:25:59Z</dc:date>
    </item>
  </channel>
</rss>

