<?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 Always useful to set up thin provisionning ? in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Always-useful-to-set-up-thin-provisionning/m-p/90697#M7884</link>
    <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;Existential question, is it always useful to set up thin provisionning (especially when no dedicated SAN admin is in the place) ?&lt;/P&gt;&lt;P&gt;We have a simple server and SAN infra relying on :&lt;/P&gt;&lt;P&gt;2 ESXi 5.1U2 hosts (managed by a vCenter with Enterprise licenses)&lt;/P&gt;&lt;P&gt;1 FAS-2040 hosting SATA disks with a shelf hosting SAS disks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They are interconnected each other directly with FC cards.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the FAS-2040 each controller is managing an aggregate (Active/Active configuration).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Controller A is managing SATA drives and presents 1 big thick LUN to VMware (stored in a thick dedicated volume)&lt;/P&gt;&lt;P&gt;Controller B is managing SAS drives and presents 1 big thick LUN to VMware (stored in a thick dedicated volume)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So only 1 volume per aggregate (+ the system one of course).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In that setup is there any reason why Thin provisioning shoul be activated ? Or is it a situation where working with full Thick is OK (especially knowing that it's not possible to add disks) ?&lt;/P&gt;&lt;P&gt;Because in that configuration, the only place where I would see thin provisioning useful is in VMware when creating the VMDKs ?!&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:27:55 GMT</pubDate>
    <dc:creator>ateliersbusch</dc:creator>
    <dc:date>2025-06-05T05:27:55Z</dc:date>
    <item>
      <title>Always useful to set up thin provisionning ?</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Always-useful-to-set-up-thin-provisionning/m-p/90697#M7884</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;Existential question, is it always useful to set up thin provisionning (especially when no dedicated SAN admin is in the place) ?&lt;/P&gt;&lt;P&gt;We have a simple server and SAN infra relying on :&lt;/P&gt;&lt;P&gt;2 ESXi 5.1U2 hosts (managed by a vCenter with Enterprise licenses)&lt;/P&gt;&lt;P&gt;1 FAS-2040 hosting SATA disks with a shelf hosting SAS disks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They are interconnected each other directly with FC cards.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the FAS-2040 each controller is managing an aggregate (Active/Active configuration).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Controller A is managing SATA drives and presents 1 big thick LUN to VMware (stored in a thick dedicated volume)&lt;/P&gt;&lt;P&gt;Controller B is managing SAS drives and presents 1 big thick LUN to VMware (stored in a thick dedicated volume)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So only 1 volume per aggregate (+ the system one of course).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In that setup is there any reason why Thin provisioning shoul be activated ? Or is it a situation where working with full Thick is OK (especially knowing that it's not possible to add disks) ?&lt;/P&gt;&lt;P&gt;Because in that configuration, the only place where I would see thin provisioning useful is in VMware when creating the VMDKs ?!&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:27:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Always-useful-to-set-up-thin-provisionning/m-p/90697#M7884</guid>
      <dc:creator>ateliersbusch</dc:creator>
      <dc:date>2025-06-05T05:27:55Z</dc:date>
    </item>
  </channel>
</rss>

