<?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 Vsnap? in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536429#M16014</link>
    <description>Hi,&lt;BR /&gt;I have a EVA3000 disk-array with Business-Copy license.&lt;BR /&gt;I read that EVA supports three types of clones:&lt;BR /&gt;- traditional snapshots, using same space of original Vdisk&lt;BR /&gt;- Vsnap or virtually capacity-free snapshot&lt;BR /&gt;- snapclone&lt;BR /&gt;I'm interested in Vsnap but I wasn't able to find this option in CommandView; I see only options for traditional snapshot.&lt;BR /&gt;How can I create a Vsnap?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
    <pubDate>Tue, 03 May 2005 04:35:21 GMT</pubDate>
    <dc:creator>Domenico Viggiani</dc:creator>
    <dc:date>2005-05-03T04:35:21Z</dc:date>
    <item>
      <title>Vsnap?</title>
      <link>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536429#M16014</link>
      <description>Hi,&lt;BR /&gt;I have a EVA3000 disk-array with Business-Copy license.&lt;BR /&gt;I read that EVA supports three types of clones:&lt;BR /&gt;- traditional snapshots, using same space of original Vdisk&lt;BR /&gt;- Vsnap or virtually capacity-free snapshot&lt;BR /&gt;- snapclone&lt;BR /&gt;I'm interested in Vsnap but I wasn't able to find this option in CommandView; I see only options for traditional snapshot.&lt;BR /&gt;How can I create a Vsnap?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 03 May 2005 04:35:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536429#M16014</guid>
      <dc:creator>Domenico Viggiani</dc:creator>
      <dc:date>2005-05-03T04:35:21Z</dc:date>
    </item>
    <item>
      <title>Re: Vsnap?</title>
      <link>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536430#M16015</link>
      <description>Domenico,&lt;BR /&gt;I'm not sure which version of CV-EVA you have, but I have attached a picture from V3.3 where a 'Vsnap' is selected.</description>
      <pubDate>Tue, 03 May 2005 04:51:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536430#M16015</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-05-03T04:51:17Z</dc:date>
    </item>
    <item>
      <title>Re: Vsnap?</title>
      <link>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536431#M16016</link>
      <description>OK, thank you.&lt;BR /&gt;But related help says:&lt;BR /&gt;"Allocate on demand â   Reserves the space a Vdisk requires on the physical disk, but only as data is stored in it."&lt;BR /&gt;Thus this is not a virtually capacity-free snapshot as marketing adverti</description>
      <pubDate>Tue, 03 May 2005 04:56:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536431#M16016</guid>
      <dc:creator>Domenico Viggiani</dc:creator>
      <dc:date>2005-05-03T04:56:45Z</dc:date>
    </item>
    <item>
      <title>Re: Vsnap?</title>
      <link>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536432#M16017</link>
      <description>I cannot follow your argument...&lt;BR /&gt;&lt;BR /&gt;The original data *must* be stored somewhere for the snapshot to retain its point-in-time view when the data of the original virtual disk is changed.&lt;BR /&gt;How did you think a "virtually capacity-free" snapshot worked?</description>
      <pubDate>Tue, 03 May 2005 05:02:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536432#M16017</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-05-03T05:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: Vsnap?</title>
      <link>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536433#M16018</link>
      <description>I thought that point-in-time snapshot was made by pointers to original data, with no use of space. Only next changes needed to be saved somewhere, incrementally filling space.&lt;BR /&gt;</description>
      <pubDate>Tue, 03 May 2005 05:37:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536433#M16018</guid>
      <dc:creator>Domenico Viggiani</dc:creator>
      <dc:date>2005-05-03T05:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: Vsnap?</title>
      <link>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536434#M16019</link>
      <description>And that is exactly how the "Vsnap" or "virtually capacity-free" snapshot works, except that it is called "Demand-allocated" in CV-EVA.</description>
      <pubDate>Tue, 03 May 2005 05:56:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536434#M16019</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-05-03T05:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: Vsnap?</title>
      <link>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536435#M16020</link>
      <description>Well, now it works as I intended; just after creation:&lt;BR /&gt; - Capacity Used: 0 GB &lt;BR /&gt; - Initial Allocation: 0 GB &lt;BR /&gt;After some disk activity:&lt;BR /&gt; - Capacity Used: 2 GB &lt;BR /&gt; - Initial Allocation: 0 GB &lt;BR /&gt;&lt;BR /&gt;Perpaphs, before I made some mistake.&lt;BR /&gt;&lt;BR /&gt;Thank you for clarification&lt;BR /&gt;</description>
      <pubDate>Tue, 03 May 2005 07:03:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/vsnap/m-p/3536435#M16020</guid>
      <dc:creator>Domenico Viggiani</dc:creator>
      <dc:date>2005-05-03T07:03:20Z</dc:date>
    </item>
  </channel>
</rss>

