<?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: Volume containing LUN best practices in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Volume-containing-LUN-best-practices/m-p/443772#M42111</link>
    <description>&lt;P&gt;Basic guidelines:&lt;BR /&gt;Each LUN in a separate volume&lt;BR /&gt;Space Guarantee:None&lt;BR /&gt;Autogrow:Enabled (If snapshots are enabled, it depends what is it (LUN) used for -SQL/EXCH/ORCL/Databases etc, if snapshots are managed by ONTAP. If the host application manages 'data-recovery', at the host-side, and netapp snaps aren't needed, then disable snapshots)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please Note: If a space-reserved LUN is created in a none-guaranteed volume, the LUN behaves the same as a non-space-reserved LUN, so basically it has no effect. Hence, it makes sense to disable space-reservation and keep volume &amp;amp; LUN THIN (unless you are asked to make it (vol/lun) thick b'cos of the requirements from your organization).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Following Kbs worth reading:&lt;BR /&gt;&lt;A href="https://kb.netapp.com/onprem/ontap/os/FAQ%3A_Over_Provisioning_aka_Thin_Provisioning_in_ONTAP" target="_blank"&gt;https://kb.netapp.com/onprem/ontap/os/FAQ%3A_Over_Provisioning_aka_Thin_Provisioning_in_ONTAP&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://kb.netapp.com/onprem/ontap/os/LUN_has_been_brought_offline_with_space-allocation_disabled" target="_blank"&gt;https://kb.netapp.com/onprem/ontap/os/LUN_has_been_brought_offline_with_space-allocation_disabled&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://docs.netapp.com/us-en/ontap/san-admin/automatic-host-side-space-management-concept.html" target="_blank"&gt;https://docs.netapp.com/us-en/ontap/san-admin/automatic-host-side-space-management-concept.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Apr 2023 19:27:26 GMT</pubDate>
    <dc:creator>Ontapforrum</dc:creator>
    <dc:date>2023-04-26T19:27:26Z</dc:date>
    <item>
      <title>Volume containing LUN best practices</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Volume-containing-LUN-best-practices/m-p/443745#M42102</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;I have a question about the properties to assign to a volume in an AFF array that serves a LUN via FC.&lt;BR /&gt;Basically the question is whether in this scenario enabling autogrow makes sense if what you are serving is a LUN and if space reservation for snapshots should be enabled or not.&lt;/P&gt;&lt;P&gt;On the other hand, snapshot autodelete, I imagine that it would be recommended to enable it.&lt;/P&gt;&lt;P&gt;Thank you so much&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:49:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Volume-containing-LUN-best-practices/m-p/443745#M42102</guid>
      <dc:creator>Kiko</dc:creator>
      <dc:date>2025-06-04T09:49:54Z</dc:date>
    </item>
    <item>
      <title>Re: Volume containing LUN best practices</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Volume-containing-LUN-best-practices/m-p/443772#M42111</link>
      <description>&lt;P&gt;Basic guidelines:&lt;BR /&gt;Each LUN in a separate volume&lt;BR /&gt;Space Guarantee:None&lt;BR /&gt;Autogrow:Enabled (If snapshots are enabled, it depends what is it (LUN) used for -SQL/EXCH/ORCL/Databases etc, if snapshots are managed by ONTAP. If the host application manages 'data-recovery', at the host-side, and netapp snaps aren't needed, then disable snapshots)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please Note: If a space-reserved LUN is created in a none-guaranteed volume, the LUN behaves the same as a non-space-reserved LUN, so basically it has no effect. Hence, it makes sense to disable space-reservation and keep volume &amp;amp; LUN THIN (unless you are asked to make it (vol/lun) thick b'cos of the requirements from your organization).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Following Kbs worth reading:&lt;BR /&gt;&lt;A href="https://kb.netapp.com/onprem/ontap/os/FAQ%3A_Over_Provisioning_aka_Thin_Provisioning_in_ONTAP" target="_blank"&gt;https://kb.netapp.com/onprem/ontap/os/FAQ%3A_Over_Provisioning_aka_Thin_Provisioning_in_ONTAP&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://kb.netapp.com/onprem/ontap/os/LUN_has_been_brought_offline_with_space-allocation_disabled" target="_blank"&gt;https://kb.netapp.com/onprem/ontap/os/LUN_has_been_brought_offline_with_space-allocation_disabled&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://docs.netapp.com/us-en/ontap/san-admin/automatic-host-side-space-management-concept.html" target="_blank"&gt;https://docs.netapp.com/us-en/ontap/san-admin/automatic-host-side-space-management-concept.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 19:27:26 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Volume-containing-LUN-best-practices/m-p/443772#M42111</guid>
      <dc:creator>Ontapforrum</dc:creator>
      <dc:date>2023-04-26T19:27:26Z</dc:date>
    </item>
  </channel>
</rss>

