<?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: LUN configuration best practice in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/LUN-configuration-best-practice/m-p/126096#M27199</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please refer best practices guide:&amp;nbsp;&lt;A href="http://www.netapp.com/us/media/tr-3702.pdf" target="_blank"&gt;http://www.netapp.com/us/media/tr-3702.pdf&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Dec 2016 06:19:12 GMT</pubDate>
    <dc:creator>Sahana</dc:creator>
    <dc:date>2016-12-09T06:19:12Z</dc:date>
    <item>
      <title>LUN configuration best practice</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/LUN-configuration-best-practice/m-p/126075#M27196</link>
      <description>&lt;P&gt;What is the best practice for configuring LUNS for Hyper-V?&amp;nbsp; Should it be one LUN per volume?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are running Ontap 8.1.1 and all of the VMs are generation 1 VHDX.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 18:06:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/LUN-configuration-best-practice/m-p/126075#M27196</guid>
      <dc:creator>AllianceITSupport</dc:creator>
      <dc:date>2025-06-04T18:06:46Z</dc:date>
    </item>
    <item>
      <title>Re: LUN configuration best practice</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/LUN-configuration-best-practice/m-p/126096#M27199</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please refer best practices guide:&amp;nbsp;&lt;A href="http://www.netapp.com/us/media/tr-3702.pdf" target="_blank"&gt;http://www.netapp.com/us/media/tr-3702.pdf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Dec 2016 06:19:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/LUN-configuration-best-practice/m-p/126096#M27199</guid>
      <dc:creator>Sahana</dc:creator>
      <dc:date>2016-12-09T06:19:12Z</dc:date>
    </item>
    <item>
      <title>Re: LUN configuration best practice</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/LUN-configuration-best-practice/m-p/126118#M27207</link>
      <description>&lt;P&gt;I have worked LUN configuration for Hyper-V. In general, there are many points need to follow to do the best service. But now i can say you can do go ahead for the single volume with single LUN for hyper-V because the lun&amp;nbsp;you want to assign to the hyper-v host machine would be a bigger size where many VMs will be run.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1)If VMs critical for the production then volume must be a guaranteed(Thick) volume so that no need to monitor everytime of the thin volume space.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2)IPOS need to calculate before the creating the LUN from the aggregate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3)One volume one LUN will help if migration required in the future.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks, Many more points are there to keep in mind for assign the LUN to the hyper-v&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 10 Dec 2016 21:19:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/LUN-configuration-best-practice/m-p/126118#M27207</guid>
      <dc:creator>TOPHAN</dc:creator>
      <dc:date>2016-12-10T21:19:56Z</dc:date>
    </item>
  </channel>
</rss>

