<?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 Storage Different between Nimble and Vcenter in HPE Nimble Storage Solution Specialists</title>
    <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/storage-different-between-nimble-and-vcenter/m-p/7079840#M263</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a problem with the space declared between our Nimble and our Vcenter.&lt;/P&gt;&lt;P&gt;To explain I will take an example :&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have one LUN of 2To on Vcenter, VM on it use 1.75To at the moment so we have an alert. On the Nimble, we have 600Go used for this 2To.&lt;/P&gt;&lt;P&gt;If you multiply this example by the number of our LUN (~15 LUN), we lost much storage....&lt;/P&gt;&lt;P&gt;We have an idea but we don't know if that can work : If we resize the LUN for 1To on the Nimble, we will have 600Go/1To used. Contrariwise, I think that can cause a bug if we do the analyse of the storage...&lt;/P&gt;&lt;P&gt;Someone can help ?&lt;/P&gt;&lt;P&gt;Thank you !&lt;/P&gt;</description>
    <pubDate>Thu, 20 Feb 2020 10:58:48 GMT</pubDate>
    <dc:creator>Antonin_H</dc:creator>
    <dc:date>2020-02-20T10:58:48Z</dc:date>
    <item>
      <title>Storage Different between Nimble and Vcenter</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/storage-different-between-nimble-and-vcenter/m-p/7079840#M263</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a problem with the space declared between our Nimble and our Vcenter.&lt;/P&gt;&lt;P&gt;To explain I will take an example :&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have one LUN of 2To on Vcenter, VM on it use 1.75To at the moment so we have an alert. On the Nimble, we have 600Go used for this 2To.&lt;/P&gt;&lt;P&gt;If you multiply this example by the number of our LUN (~15 LUN), we lost much storage....&lt;/P&gt;&lt;P&gt;We have an idea but we don't know if that can work : If we resize the LUN for 1To on the Nimble, we will have 600Go/1To used. Contrariwise, I think that can cause a bug if we do the analyse of the storage...&lt;/P&gt;&lt;P&gt;Someone can help ?&lt;/P&gt;&lt;P&gt;Thank you !&lt;/P&gt;</description>
      <pubDate>Thu, 20 Feb 2020 10:58:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/storage-different-between-nimble-and-vcenter/m-p/7079840#M263</guid>
      <dc:creator>Antonin_H</dc:creator>
      <dc:date>2020-02-20T10:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Storage Different between Nimble and Vcenter</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/storage-different-between-nimble-and-vcenter/m-p/7081214#M272</link>
      <description>&lt;P&gt;Hi Antonin_H&lt;/P&gt;&lt;P&gt;I would kindly request you to get in touch with the Tech Support with the serial number to know what exactly is happening on the array.&lt;/P&gt;&lt;P&gt;To be more precise,&amp;nbsp; Depending on the array model that you should be either running compression, or running compression and dedupe. What happens is that the file system (vmfs - Vmware) in this instance know how much space it is using on the datastore.&amp;nbsp;&amp;nbsp; What the file system is not aware of is how the blocks are being handled on the array side.&amp;nbsp; Meaning when we compress the blocks or dedupe the blocks the space saving for that is reflected on the space used on the array.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Mahesh202&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 10:11:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/storage-different-between-nimble-and-vcenter/m-p/7081214#M272</guid>
      <dc:creator>Mahesh202</dc:creator>
      <dc:date>2020-03-03T10:11:03Z</dc:date>
    </item>
  </channel>
</rss>

