<?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 - vmfs backups</title>
    <link>http://communities.vmware.com/community/vmtn/vi/esx3.5?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Tue, 04 Dec 2007 19:48:19 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2007-12-04T19:48:19Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: vmfs backups</title>
      <link>http://communities.vmware.com/message/810795?tstart=0#810795</link>
      <description>Thanks, wila. But in thread &lt;a class="jive-link-message" href="http://communities.vmware.com/message/810769#810769"&gt;http://communities.vmware.com/message/810769&lt;/a&gt; troberts (a VMware TSE) wrote:&lt;br /&gt;
&lt;blockquote&gt;Just using cp to copy an vmdk file to a non-VMFS filesystem will &lt;b&gt;corrupt&lt;/b&gt; the vmdk because the blosk sizes are different.&lt;/blockquote&gt;
(Emphasis mine.) This seems to contradict what you wrote above.</description>
      <pubDate>Tue, 04 Dec 2007 19:47:00 GMT</pubDate>
      <author>franl</author>
      <guid>http://communities.vmware.com/message/810795?tstart=0#810795</guid>
      <dc:date>2007-12-04T19:47:00Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: vmfs backups</title>
      <link>http://communities.vmware.com/message/810197?tstart=0#810197</link>
      <description>You can use the cp command to get your data out of the VMFS and it will work - as you say - provided that the destination filesystem is capable of storing these large files. &lt;br /&gt;
For best compatibility however, it is recommended to use the vmkfstools command to export your disks to a "thin" format of your disks so that they never cross the 2Gb boundary.&lt;br /&gt;
&lt;br /&gt;
Then for importing the disks back into your vmfs storage, you can again use cp, however this has downsides as:&lt;br /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;there will be a larger number of SCSI locks which can cause problems with your other VMs&lt;/li&gt;
&lt;li&gt;the destination VM disk can be fragmented as cp doesn't allocate the complete file before starting the copy&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
So in conclusion, the standard unix copy commands work with the VMFS filesystem, but they are not the optimal way of using your resources. In that case use the vmkfstools command.&lt;br /&gt;
Here's a simple example:&lt;br /&gt;
&lt;br /&gt;
backup:&lt;br /&gt;
vmkfstools -i /vmfs/volumes/storage1/test/test.vmdk -d 2gbsparse /home/wila/backup/test.vmdk&lt;br /&gt;
&lt;br /&gt;
restore:&lt;br /&gt;
vmkfstools -i /home/wila/backup/test.vmdk /vmfs/volumes/storage1/test/test.vmdk&lt;br /&gt;
&lt;br /&gt;
Message was edited by: wila&lt;br /&gt;
Added example</description>
      <pubDate>Tue, 04 Dec 2007 08:06:41 GMT</pubDate>
      <author>wila</author>
      <guid>http://communities.vmware.com/message/810197?tstart=0#810197</guid>
      <dc:date>2007-12-04T08:06:41Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: vmfs backups</title>
      <link>http://communities.vmware.com/message/809498?tstart=0#809498</link>
      <description>The Virtual Machine Backup Guide for ESX Server 3.0.1 says: "You can use ftp, scp, and cp commands for copying files to and from a VMFS volume as long as the host file system supports these large files."&lt;br /&gt;
&lt;br /&gt;
But I could swear that I've read in these forums that one should not use such commands to copy virtual machines from a VMFS volume, because there is a risk of corrupting the virtual disk files.&lt;br /&gt;
&lt;br /&gt;
Which is it: Are these commands safe for backing up virtual machines or not?</description>
      <pubDate>Mon, 03 Dec 2007 16:20:21 GMT</pubDate>
      <author>franl</author>
      <guid>http://communities.vmware.com/message/809498?tstart=0#809498</guid>
      <dc:date>2007-12-03T16:20:21Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: vmfs backups</title>
      <link>http://communities.vmware.com/message/809429?tstart=0#809429</link>
      <description>Hi,&lt;br /&gt;
&lt;br /&gt;
You don't need to back those up, for rebuilding the VMs the only required files are the .vmdk and vmx files. Without the vmx file you'd probably survive as well.&lt;br /&gt;
In the case of a host failure, the advice is to rebuilt from scratch. It's not as bad as it sounds, if you have a slightly complicated setup then you are encouraged to look at building a kickstart file for rebuilding your hosts.</description>
      <pubDate>Mon, 03 Dec 2007 15:23:18 GMT</pubDate>
      <author>wila</author>
      <guid>http://communities.vmware.com/message/809429?tstart=0#809429</guid>
      <dc:date>2007-12-03T15:23:18Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: vmfs backups</title>
      <link>http://communities.vmware.com/message/809427?tstart=0#809427</link>
      <description>Just really worry about the VM's.  If you had to rebuild from scratch you would create another datastore and then restore the VM's register and your set&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Steve Beaver&lt;br /&gt;
VMTN Forum Moderator&lt;br /&gt;
&lt;br /&gt;
**Virtualization is a journey, not a project.**</description>
      <pubDate>Mon, 03 Dec 2007 15:21:24 GMT</pubDate>
      <author>sbeaver</author>
      <guid>http://communities.vmware.com/message/809427?tstart=0#809427</guid>
      <dc:date>2007-12-03T15:21:24Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>vmfs backups</title>
      <link>http://communities.vmware.com/message/809416?tstart=0#809416</link>
      <description>Hello&lt;br /&gt;
I'm comletely new in ESX 3.0.2 architecture, so please forgive me maybe stupid question but i bothering about loosing my data. My question is about backups of VMFS content. I 'm currently doing virtual machines backups using vcbMounter command - and this is very good tool for saving particular virtual machine, but what about the rest of vmfs filesystem structures ?. I mean, what about /vmfs/devices content ? If I lost completely whole /vmfs filesystem, information about datastores structures and all those vml.xxxxxx files would be lost too ? How can I backup this files which i suppose represents datastores. Or maybe I'm wrong and there's no need to backup them ?  &lt;br /&gt;
&lt;br /&gt;
Regards&lt;br /&gt;
Tomek</description>
      <pubDate>Mon, 03 Dec 2007 15:12:04 GMT</pubDate>
      <author>tomekz</author>
      <guid>http://communities.vmware.com/message/809416?tstart=0#809416</guid>
      <dc:date>2007-12-03T15:12:04Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
  </channel>
</rss>

