<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Virtual files and their purposes</title>
    <link>http://communities.vmware.com/community/vmtn/vi/esxi3.5?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Wed, 29 Oct 2008 19:21:28 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-10-29T19:21:28Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Virtual files and their purposes</title>
      <link>http://communities.vmware.com/message/1087046?tstart=0#1087046</link>
      <description>Snapshots are a good way to do backup and they're great it you want to rollback from a change / patch / etc.   My concern was over the size the of snapshot - i.e. 270 GB snapshot file on your 800 GB vmdk.  At some point you'll want to commit the snapshot and if something screws up there seems to have been a lot of data that will have changed.  Plus the snapshot will take a very long time to commit back to the main vmdk.&lt;br /&gt;
&lt;br /&gt;
The vmsn file by the way is a snapshot of the memory of the VM when you took the snapshot.  If you were to revert back to the snapshot then the VM would load up the memory file and the VM would start exactly as it was when you took the snapshot.</description>
      <pubDate>Wed, 29 Oct 2008 19:21:28 GMT</pubDate>
      <author>Dave.Mishchenko</author>
      <guid>http://communities.vmware.com/message/1087046?tstart=0#1087046</guid>
      <dc:date>2008-10-29T19:21:28Z</dc:date>
      <clearspace:dateToText>1 year, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Virtual files and their purposes</title>
      <link>http://communities.vmware.com/message/1087019?tstart=0#1087019</link>
      <description>&lt;br /&gt;
Hi Dave,&lt;br /&gt;
&lt;p /&gt;
Thanks for the quick response.  I was using the snapshot as a roll back in case I mussed something up, or installed something which proved not good.  If you don't want to run snapshots much, I take it the purpose is not for backup.  What's the reccomended archive and backup method?&lt;br /&gt;
&lt;p /&gt;
Regards,&lt;br /&gt;
&lt;p /&gt;
John</description>
      <pubDate>Wed, 29 Oct 2008 18:43:16 GMT</pubDate>
      <author>jmueske</author>
      <guid>http://communities.vmware.com/message/1087019?tstart=0#1087019</guid>
      <dc:date>2008-10-29T18:43:16Z</dc:date>
      <clearspace:dateToText>1 year, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Virtual files and their purposes</title>
      <link>http://communities.vmware.com/message/1087006?tstart=0#1087006</link>
      <description>The vswp file is the memory swap file for the VM.   The file is created when you power on a VM and is equal to the memory of the VM minus any memory reservation that you have set.  ESXi will use this file should it need to swap contents of the VMs memory to disk should the ESXi host run low on physical memory.  The other vmdk files are snap shots and in general you don't want to run them for a long time or let them grow that large.</description>
      <pubDate>Wed, 29 Oct 2008 18:24:16 GMT</pubDate>
      <author>Dave.Mishchenko</author>
      <guid>http://communities.vmware.com/message/1087006?tstart=0#1087006</guid>
      <dc:date>2008-10-29T18:24:16Z</dc:date>
      <clearspace:dateToText>1 year, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Virtual files and their purposes</title>
      <link>http://communities.vmware.com/message/1086882?tstart=0#1086882</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
I've configured a Windows server with a 40GB local drive and 800GB data drive (virtual disk files with the *.vmdk extension).  I can see these files in the datastore browser, see attached.  However I also have some large files taking up space which are weird sizes.  I suspect they have to do with the snapshot I've taken, can someone confirm this?  The suspicious files are circled.&lt;br /&gt;
&lt;p /&gt;
Regards,&lt;br /&gt;
&lt;p /&gt;
John</description>
      <pubDate>Wed, 29 Oct 2008 16:34:25 GMT</pubDate>
      <author>jmueske</author>
      <guid>http://communities.vmware.com/message/1086882?tstart=0#1086882</guid>
      <dc:date>2008-10-29T16:34:25Z</dc:date>
      <clearspace:dateToText>1 year, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
  </channel>
</rss>

