<?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: SAN Snapshot usage in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/san-snapshot-usage/m-p/6492138#M8374</link>
    <description>&lt;P&gt;unfortunately that is how it is. &amp;nbsp;Keep it thin provisioned.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why do you want to make it thick? &amp;nbsp;Just leave it thin and if you are paranoid, just make sure that you don't overprovision your LUNs.&lt;/P&gt;</description>
    <pubDate>Thu, 29 May 2014 13:11:05 GMT</pubDate>
    <dc:creator>oikjn</dc:creator>
    <dc:date>2014-05-29T13:11:05Z</dc:date>
    <item>
      <title>SAN Snapshot usage</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/san-snapshot-usage/m-p/6491998#M8373</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yesterday I converted a 2TB mirrored (3.4TB utilised) thinly provisioned volume to a fully provisioned volume which consumed 4TB. The volume contains part of the clustered Hyper-V virtual machines.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However when DPM runs and creates an application snapshot it consumes a further 3.4TB of storage until the snapshot is finshed with and deleted, the snapshot is listed as being Thin in CMC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I switch it back to Thin provisioning the snapshots only take up a few gigabytes of space.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is with DPM 2012 R2 and the SAN is running on version 10.5.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know a way around this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2014 11:44:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/san-snapshot-usage/m-p/6491998#M8373</guid>
      <dc:creator>BGS-IT</dc:creator>
      <dc:date>2014-05-29T11:44:51Z</dc:date>
    </item>
    <item>
      <title>Re: SAN Snapshot usage</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/san-snapshot-usage/m-p/6492138#M8374</link>
      <description>&lt;P&gt;unfortunately that is how it is. &amp;nbsp;Keep it thin provisioned.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why do you want to make it thick? &amp;nbsp;Just leave it thin and if you are paranoid, just make sure that you don't overprovision your LUNs.&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2014 13:11:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/san-snapshot-usage/m-p/6492138#M8374</guid>
      <dc:creator>oikjn</dc:creator>
      <dc:date>2014-05-29T13:11:05Z</dc:date>
    </item>
    <item>
      <title>Re: SAN Snapshot usage</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/san-snapshot-usage/m-p/6492412#M8375</link>
      <description>&lt;P&gt;Thanks for that.&lt;BR /&gt;&lt;BR /&gt;Is this a v10.5 issue or does it affect all HP SANs?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We wanted to make it Full provisioned because we've run out of space in the past due to snapshots not being removed automatically after backups&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2014 15:21:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/san-snapshot-usage/m-p/6492412#M8375</guid>
      <dc:creator>BGS-IT</dc:creator>
      <dc:date>2014-05-29T15:21:12Z</dc:date>
    </item>
    <item>
      <title>Re: SAN Snapshot usage</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/san-snapshot-usage/m-p/6492602#M8376</link>
      <description>&lt;P&gt;it applies for all versions that I've dealt with (at least since v8.5)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I do is I create an "emergency space" LUN that isn't actually filled with any data, but is thick provisioned. &amp;nbsp;That way, if I"m not paying attention and the san actually fills with space and stops serving IO, I can quickly delete that LUN, get back enough space to get the SAN functioning again and then deal with freeing up space for real or purchasing extra space. &amp;nbsp;In my case, I keep a 50GB LUN for this ammount, but you might want to keep more/less depending on what your data usage rate is and how quickly you think you can respond to get more storage or delete unneeded space to free things up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On of the major problems with the SAN as it is now is that there is no space reclaimation for thin volumes other than deleting the LUN once its expanded. &amp;nbsp;There is a rhumor that will change in an upcomming release, but I'm not holding my breath given their history of updates.&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2014 17:01:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/san-snapshot-usage/m-p/6492602#M8376</guid>
      <dc:creator>oikjn</dc:creator>
      <dc:date>2014-05-29T17:01:22Z</dc:date>
    </item>
  </channel>
</rss>

