<?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 Backup a running VM using rsync in Operating System - VMware</title>
    <link>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573430#M600</link>
    <description>hi&lt;BR /&gt;&lt;BR /&gt;Has someone tried to backup a running VM from ESX 3.5 using rsync?&lt;BR /&gt;</description>
    <pubDate>Thu, 28 Jan 2010 16:06:01 GMT</pubDate>
    <dc:creator>'chris'</dc:creator>
    <dc:date>2010-01-28T16:06:01Z</dc:date>
    <item>
      <title>Backup a running VM using rsync</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573430#M600</link>
      <description>hi&lt;BR /&gt;&lt;BR /&gt;Has someone tried to backup a running VM from ESX 3.5 using rsync?&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Jan 2010 16:06:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573430#M600</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2010-01-28T16:06:01Z</dc:date>
    </item>
    <item>
      <title>Re: Backup a running VM using rsync</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573431#M601</link>
      <description>I just did a quick test with an linux VM running on ESXi4 from NFS storage. The copy booted without any problems. Interesting, very interesting.</description>
      <pubDate>Thu, 28 Jan 2010 20:15:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573431#M601</guid>
      <dc:creator>wobbe</dc:creator>
      <dc:date>2010-01-28T20:15:28Z</dc:date>
    </item>
    <item>
      <title>Re: Backup a running VM using rsync</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573432#M602</link>
      <description>@wobbe&lt;BR /&gt;&lt;BR /&gt;How did you copied, have you done using rsync?</description>
      <pubDate>Thu, 28 Jan 2010 20:28:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573432#M602</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2010-01-28T20:28:31Z</dc:date>
    </item>
    <item>
      <title>Re: Backup a running VM using rsync</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573433#M603</link>
      <description>Yep. I did.&lt;BR /&gt;&lt;BR /&gt;rsync -r /mnt/lv0/linux/ /mnt/lv0/copy/&lt;BR /&gt;&lt;BR /&gt;This was on the NSF storage server using rsync 2.6.8. (CentOS 5.4)&lt;BR /&gt;The running VM was also CentOS.</description>
      <pubDate>Thu, 28 Jan 2010 20:50:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573433#M603</guid>
      <dc:creator>wobbe</dc:creator>
      <dc:date>2010-01-28T20:50:40Z</dc:date>
    </item>
    <item>
      <title>Re: Backup a running VM using rsync</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573434#M604</link>
      <description>Have you really backup a running VM?&lt;BR /&gt;&lt;BR /&gt;I've tried to backup with rsync directly from ESX 3.5 to an other linux machine and I'm getting these problems:&lt;BR /&gt;&lt;BR /&gt;#  rsync -r ssh SRV12  root@192.168.1.11:/var&lt;BR /&gt;Password:&lt;BR /&gt;rsync: link_stat "/vmfs/volumes/49172c57-524d3fc3-6cfc-001e4f1285d0/ssh" failed: No such file or directory (2)&lt;BR /&gt;rsync: send_files failed to open "/vmfs/volumes/49172c57-524d3fc3-6cfc-001e4f1285d0/SRV12/SRV12-000001-delta.vmdk": Device or resource busy (16)&lt;BR /&gt;rsync: send_files failed to open "/vmfs/volumes/49172c57-524d3fc3-6cfc-001e4f1285d0/SRV12/SRV12-350c5ca2.vswp": Device or resource busy (16)&lt;BR /&gt;</description>
      <pubDate>Thu, 04 Feb 2010 13:50:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573434#M604</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2010-02-04T13:50:51Z</dc:date>
    </item>
    <item>
      <title>Re: Backup a running VM using rsync</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573435#M605</link>
      <description>Chris, he has run rsync inside the VM. Whether that gave a (crash-)consistent result I doubt.&lt;BR /&gt;&lt;BR /&gt;Your command has failed because the files which make up a VM are intentionally locked by the virtualization layer. Even if they were not locked, you would not get a reliable result if the VM makes changes to the life file system.&lt;BR /&gt;&lt;BR /&gt;The work-around is to create a 'snaphot' of the VM. The virtualization layer will create new delta/REDO files into which it stores all data that is written - this means that the original file is not changed so you can create a 'crash-consistent' copy. Well, and of course it now unlocks the files so you can read from them.&lt;BR /&gt;&lt;BR /&gt;After the backup is complete, delete the snapshots and all writes collected in the delta/REDO files will be merged to the original disk. And the files will be locked again ;-)</description>
      <pubDate>Thu, 04 Feb 2010 15:13:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573435#M605</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2010-02-04T15:13:28Z</dc:date>
    </item>
    <item>
      <title>Re: Backup a running VM using rsync</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573436#M606</link>
      <description>Can I do it a snapshot of a running VM using rsnapshot from &lt;A href="http://rsnapshot.org/" target="_blank"&gt;http://rsnapshot.org/&lt;/A&gt; ?</description>
      <pubDate>Thu, 04 Feb 2010 16:02:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573436#M606</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2010-02-04T16:02:18Z</dc:date>
    </item>
    <item>
      <title>Re: Backup a running VM using rsync</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573437#M607</link>
      <description>It is my understanding that rsnapshot's idea is to create a full backup of file systems and then make incremental backups which look like other full backups due to using hard links for files already copied.&lt;BR /&gt;I think today's buzzword is 'de-duplication' :-)&lt;BR /&gt;&lt;BR /&gt;The main data of a VM is encapsulated in one or more large files. You cannot really do 'incremental backups' - well, with ESX4 and changed block tracking it is possible, but that is just a framework, no complete application.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Chris, can we step back a moment and have a better look at your configuration (what OS and data is in the VM) and requirements for backups? Maybe there is a 'better' way to do backups than running rsync - the ESX service console is not a generic Linux environment for all kinds of applications.</description>
      <pubDate>Thu, 04 Feb 2010 16:22:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/backup-a-running-vm-using-rsync/m-p/4573437#M607</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2010-02-04T16:22:12Z</dc:date>
    </item>
  </channel>
</rss>

