<?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 : All Content - Backup &amp; Recovery</title>
    <link>http://communities.vmware.com/community/vmtn/vsphere/datarecovery-vcb</link>
    <description>All Content in Backup &amp; Recovery</description>
    <language>en</language>
    <pubDate>Mon, 23 Nov 2009 05:24:43 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-11-23T05:24:43Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>cmd.exe copy speed limitation -&amp;gt; Powershell</title>
      <link>http://communities.vmware.com/message/1423534</link>
      <description>It does not depend by your shell, but from your VCB transport method.&lt;br /&gt;
Are you using NDB mode? Can you set to SAN mode (and give to VCB proxy the LUN visibility)?&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <pubDate>Mon, 23 Nov 2009 05:24:43 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1423534</guid>
      <dc:date>2009-11-23T05:24:43Z</dc:date>
      <clearspace:dateToText>6 hours, 19 minutes ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Unable to backup Virtual Machine from VDR</title>
      <link>http://communities.vmware.com/message/1423530</link>
      <description>Just power off the VM from the vSphere Client.&lt;br /&gt;
Seems that there is a process or a driver that lock the guest shutdown procedure.&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <pubDate>Mon, 23 Nov 2009 05:12:06 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1423530</guid>
      <dc:date>2009-11-23T05:12:06Z</dc:date>
      <clearspace:dateToText>6 hours, 32 minutes ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Trouble deploying vDR appliance 1.1</title>
      <link>http://communities.vmware.com/message/1423502</link>
      <description>&lt;br /&gt;
SUSSED!!!&lt;br /&gt;
&lt;p /&gt;
 I have solved my problem. I am able to deploy the ovf but only if i am in the Hosts and Clusters view. If i try from the VM and templates view it errors.  Is this how appliances should be deployed (from the hosts and cluster view) or should i be able to deploy from the VM and templates view?&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Mon, 23 Nov 2009 03:47:45 GMT</pubDate>
      <author>MarkIveli</author>
      <guid>http://communities.vmware.com/message/1423502</guid>
      <dc:date>2009-11-23T03:47:45Z</dc:date>
      <clearspace:dateToText>7 hours, 56 minutes ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>What's the latest on VDR 1.1????</title>
      <link>http://communities.vmware.com/message/1423396</link>
      <description>As mentioned above, huge improvement in Integrity Check performance. A check on my 200GB dedupe store took 4hrs not 1-2 days (and this is on a very modest iSCSI setup - Starwind Free, Single 1TB drive, Vista Workstation). General responsiveness seems better too.&lt;br /&gt;
&lt;br /&gt;
Has a couple of issues, nothing to get annoyed about so far but, importantly, I have not tested restore performance yet.&lt;br /&gt;
&lt;br /&gt;
Overall this "feels" like a good release and what VDR should have been from the start but until consistent performance over a significant period of time is proven I can't honestly say.&lt;br /&gt;
&lt;br /&gt;
I, like many others were let down by the real world performance of this product when it was released, so I won't believe it till I see it.&lt;br /&gt;
&lt;br /&gt;
I am encouraged by this release though and am glad there is an effort being made by Azmir and his team to make it a workable solution. The way this software "should" operate is potentially brilliant for someone like me who wants to "set and forget".&lt;br /&gt;
&lt;br /&gt;
Watch this space...</description>
      <pubDate>Sun, 22 Nov 2009 22:45:52 GMT</pubDate>
      <author>Kiemo</author>
      <guid>http://communities.vmware.com/message/1423396</guid>
      <dc:date>2009-11-22T22:45:52Z</dc:date>
      <clearspace:dateToText>12 hours, 58 minutes ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Can VMware Data Recovery be installed and used on free ESXi 4.0?</title>
      <link>http://communities.vmware.com/message/1423391</link>
      <description>No you can not VDR can only be used on the paid versions.  for backing up guests with the free version there is only traditional InGuest Agent based backup available&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points&lt;br /&gt;
&lt;br /&gt;
Tom Howarth VCP / vExpert&lt;br /&gt;
VMware Communities User Moderator&lt;br /&gt;
Blog: &lt;a class="jive-link-external" href="http://www.planetvm.net/"&gt;www.planetvm.net&lt;/a&gt;&lt;br /&gt;
Contributing author on "&lt;a class="jive-link-external" href="http://www.amazon.co.uk/VMware-VSphere-Virtual-Infrastructure-Security/dp/0137158009/ref=sr_1_1?ie=UTF8&amp;#38;s=books&amp;#38;qid=1256146240&amp;#38;sr=1-1"&gt;VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment&lt;/a&gt;&amp;rdquo;.</description>
      <pubDate>Sun, 22 Nov 2009 22:18:33 GMT</pubDate>
      <author>tom howarth</author>
      <guid>http://communities.vmware.com/message/1423391</guid>
      <dc:date>2009-11-22T22:18:33Z</dc:date>
      <clearspace:dateToText>13 hours, 25 minutes ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>VCB 1.5 not deleting</title>
      <link>http://communities.vmware.com/message/1423366</link>
      <description>Hi,&lt;br /&gt;
&lt;br /&gt;
I use VCB 1.5 with Backupexec 12.5 for Full-VM. It works great, the only problem I have it does not delete the mounted files on the proxy after the backup is done. The snapshot gets deleted. I support another side with almost identical setup and there it works. &lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
Edy</description>
      <pubDate>Sun, 22 Nov 2009 21:32:55 GMT</pubDate>
      <author>fafa24</author>
      <guid>http://communities.vmware.com/message/1423366</guid>
      <dc:date>2009-11-22T21:32:55Z</dc:date>
      <clearspace:dateToText>14 hours, 11 minutes ago</clearspace:dateToText>
    </item>
    <item>
      <title>Clone to Template Fails - No room on datastore</title>
      <link>http://communities.vmware.com/message/1423309</link>
      <description>When you assign a RAW-Device, a file with the same size as the RAW-Device will be created in the directory of your VM, which needs no real size on the disk but to create this Dummy-file the format of your VMFS-Datastore must be with 8 MB Block size, when you add such a big LUN with more than 1 TB. So I think you had to create a Datastore with such a big Block Size to save the Dummy-File on it. Hope this is true...&lt;br /&gt;
Paul</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vsphere_essentials</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">clone</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">template</category>
      <pubDate>Sun, 22 Nov 2009 20:16:14 GMT</pubDate>
      <author>Paul1</author>
      <guid>http://communities.vmware.com/message/1423309</guid>
      <dc:date>2009-11-22T20:16:14Z</dc:date>
      <clearspace:dateToText>15 hours, 28 minutes ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>VCB Snapshot issue only with Server 2008 R2</title>
      <link>http://communities.vmware.com/message/1423252</link>
      <description>This is a pure impertinence. Release notes of esx4u1 say "W2008R2 support". I tell you something VMware, if I can´t backup my w2008r2 exchange and sql servers i can´t use the whole product!!!! I checked the eventlogs, no vss operations at all. No file system harmonizing, no clean exchange state, backup is ergo totally useless. Like a hardware SAN-Snapshot. This has to be addressed!! It is absolutely unbelievable how you have the heart to bring such a beta piece to sunlight.&lt;br /&gt;
&lt;br /&gt;
Joerg</description>
      <pubDate>Sun, 22 Nov 2009 18:33:09 GMT</pubDate>
      <author>joergriether</author>
      <guid>http://communities.vmware.com/message/1423252</guid>
      <dc:date>2009-11-22T18:33:09Z</dc:date>
      <clearspace:dateToText>17 hours, 9 minutes ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>No VMware VSS on 2k8 R2?</title>
      <link>http://communities.vmware.com/message/1423251</link>
      <description>I agree. Many many things with w2008r2 are NOT suppoted at all with esx4, not even esx4u1. Just to mention this one here (VSS) and also graphics. VSS is a real bad one. Many admins count on vss awareness when using vcb with their exchange and sql servers.&lt;br /&gt;
&lt;br /&gt;
Joerg</description>
      <pubDate>Sun, 22 Nov 2009 18:21:25 GMT</pubDate>
      <author>joergriether</author>
      <guid>http://communities.vmware.com/message/1423251</guid>
      <dc:date>2009-11-22T18:21:25Z</dc:date>
      <clearspace:dateToText>17 hours, 23 minutes ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Data Recovery: restore while source VM is gone</title>
      <link>http://communities.vmware.com/message/1423152</link>
      <description>In the restore tab of VDR you must see all the restore point... also for deleted VM.&lt;br /&gt;
But remember retention policies... you can loose your restore point after their expire.&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <pubDate>Sun, 22 Nov 2009 07:29:48 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1423152</guid>
      <dc:date>2009-11-22T07:29:48Z</dc:date>
      <clearspace:dateToText>1 day, 4 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VCB &amp;#38; Symantec Exchange 2007 Agent</title>
      <link>http://communities.vmware.com/message/1423120</link>
      <description>The Symantec VI Agent is what enabled you to do the Image level backups of the Virtual Machines.  Without that agent, you are not able to get copies of the vmdk files backed up.&lt;br /&gt;
&lt;br /&gt;
Think of it like the physical world.  If you purchase symantec backupexec system recovery or Acronis...you are gonig to get snapshots of your server (including all files at that point in time...but anything like Exchange will not have its logs truncated and will be crash consistant backups.&lt;br /&gt;
&lt;br /&gt;
You need to have an application level backup solution to get valid and consistent Exchange, SQL, Oracle, Active Directory (basically database type products) backups.</description>
      <pubDate>Sun, 22 Nov 2009 05:52:30 GMT</pubDate>
      <author>Rumple</author>
      <guid>http://communities.vmware.com/message/1423120</guid>
      <dc:date>2009-11-22T05:52:30Z</dc:date>
      <clearspace:dateToText>1 day, 5 hours ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>VDR with vsphere , Failed to create snapshot for XXX, Fehler -3941 ( Erstellen des Snapshots fehlgeschlagen)</title>
      <link>http://communities.vmware.com/message/1422802</link>
      <description>Hello buddy,&lt;br /&gt;
&lt;br /&gt;
I also have the same issue, hope u can suggest me someting,&lt;br /&gt;
&lt;br /&gt;
•is FT enabled? No&lt;br /&gt;
&lt;br /&gt;
•does it have 3rd party multi-path? No&lt;br /&gt;
&lt;br /&gt;
•does it have a RDM in physical compatibility mode? No &lt;br /&gt;
&lt;br /&gt;
•did you import this vm from a vmware server or workstation installation?No&lt;br /&gt;
&lt;br /&gt;
My Virtual machine is Windows Xp Professional with HDD of 30 GB  with vmware toosl installed, Hardware version 7, im trying to the destination of network share which have free space of 72 Gb.</description>
      <pubDate>Sat, 21 Nov 2009 13:20:04 GMT</pubDate>
      <author>Ace007</author>
      <guid>http://communities.vmware.com/message/1422802</guid>
      <dc:date>2009-11-21T13:20:04Z</dc:date>
      <clearspace:dateToText>1 day, 22 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Snapshots left on VMFS after VDR backup failed - how to merge/delete?</title>
      <link>http://communities.vmware.com/message/1422766</link>
      <description>Create a new snapshot and then choose delete all.&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <pubDate>Sat, 21 Nov 2009 10:13:31 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1422766</guid>
      <dc:date>2009-11-21T10:13:31Z</dc:date>
      <clearspace:dateToText>2 days, 1 hour ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Which Backup Tool (on a budget) ?</title>
      <link>http://communities.vmware.com/message/1422587</link>
      <description>&lt;br /&gt;
No worries Gostev,&lt;br /&gt;
&lt;br /&gt;
I'll be patiently wait for that :-o)&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
at the moment I also trialling VDR v 1.1 but it doesn't have much in terms of difference and functionality apart from bug fixes only. &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Fri, 20 Nov 2009 22:34:24 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1422587</guid>
      <dc:date>2009-11-20T22:34:24Z</dc:date>
      <clearspace:dateToText>2 days, 13 hours ago</clearspace:dateToText>
      <clearspace:replyCount>19</clearspace:replyCount>
    </item>
    <item>
      <title>CIFS errors - CIFS dedupe stores ready for production environment?</title>
      <link>http://communities.vmware.com/message/1422496</link>
      <description>It depends is the best that I can offer with CIFS.  We absolutely recommend against CIFS (documented in the Admin Guide)&lt;br /&gt;
&lt;br /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;On a server that has another role such as CIFS shares on a vCenter Server.&lt;/li&gt;
&lt;li&gt;Connected to a virtual machine.&lt;/li&gt;
&lt;li&gt;Shared to multiple services or servers.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Obviously, performance is ultimately dependent on the speed on that physical fileserver, the number of disks/ spindles that make up the CIFS share and the network connection between VDR and the fileserver.  So, your mileage may vary with CIFS.&lt;br /&gt;
&lt;br /&gt;
Because of this, running the VDR destination disk as a vmdk is highly recommended since you will most likely will be running it on HCL compliant storage - performance, sharing/locks and stability is better.&lt;br /&gt;
&lt;br /&gt;
Good luck!</description>
      <pubDate>Fri, 20 Nov 2009 20:15:46 GMT</pubDate>
      <author>azmir</author>
      <guid>http://communities.vmware.com/message/1422496</guid>
      <dc:date>2009-11-20T20:15:46Z</dc:date>
      <clearspace:dateToText>2 days, 15 hours ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>VDR 1.1 and Server 2008 R2 - cannot quiesce virtual machine</title>
      <link>http://communities.vmware.com/message/1422455</link>
      <description>Here's where I saw it!&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://blogs.vmware.com/uptime/2009/11/vmware-data-recovery-11-and-file-level-restore.html"&gt;http://blogs.vmware.com/uptime/2009/11/vmware-data-recovery-11-and-file-level-restore.html&lt;/a&gt;</description>
      <pubDate>Fri, 20 Nov 2009 19:51:21 GMT</pubDate>
      <author>Kiemo</author>
      <guid>http://communities.vmware.com/message/1422455</guid>
      <dc:date>2009-11-20T19:51:21Z</dc:date>
      <clearspace:dateToText>2 days, 15 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Can't connect to Data Recovery Appliance</title>
      <link>http://communities.vmware.com/message/1422445</link>
      <description>confirmed new release of VDR ver 1.1 fixes authentucation issue when you have a guest VM's with more than 16 IP Addresses</description>
      <pubDate>Fri, 20 Nov 2009 19:46:24 GMT</pubDate>
      <author>vkelly</author>
      <guid>http://communities.vmware.com/message/1422445</guid>
      <dc:date>2009-11-20T19:46:24Z</dc:date>
      <clearspace:dateToText>2 days, 15 hours ago</clearspace:dateToText>
      <clearspace:replyCount>89</clearspace:replyCount>
    </item>
    <item>
      <title>Although Early: How is new VDR 1.1 going?</title>
      <link>http://communities.vmware.com/message/1422463</link>
      <description>&lt;br /&gt;
I see.. Thanks for the info.&lt;br /&gt;
&lt;p /&gt;
 But i have to complain that the VDR does not check this before it starts a backup, everything will look fine untill 99% of the backup, stupid logic to not check this when adding it as a destination and then give a error/warning.</description>
      <pubDate>Fri, 20 Nov 2009 19:25:31 GMT</pubDate>
      <author>mastrboy</author>
      <guid>http://communities.vmware.com/message/1422463</guid>
      <dc:date>2009-11-20T19:25:31Z</dc:date>
      <clearspace:dateToText>2 days, 16 hours ago</clearspace:dateToText>
      <clearspace:replyCount>11</clearspace:replyCount>
    </item>
    <item>
      <title>vdrfilerestore and vm with multiple drives</title>
      <link>http://communities.vmware.com/message/1422433</link>
      <description>thanks again, this is good stuff.</description>
      <pubDate>Fri, 20 Nov 2009 19:01:21 GMT</pubDate>
      <author>duhaas</author>
      <guid>http://communities.vmware.com/message/1422433</guid>
      <dc:date>2009-11-20T19:01:21Z</dc:date>
      <clearspace:dateToText>2 days, 16 hours ago</clearspace:dateToText>
      <clearspace:replyCount>11</clearspace:replyCount>
    </item>
    <item>
      <title>Slow vStorage API, Service Console Backup Performance in ESX4</title>
      <link>http://communities.vmware.com/message/1422144</link>
      <description>Orion, try using VEEAM in the Virtual Appliance mode to work around this issue.&lt;br /&gt;
&lt;br /&gt;
Also, if you really have to do network backups, check out the speed of incremental backup by running the job more than once - it will be at least 10 times faster than first job run. With VEEAM, only first backup is full, but subsequent backups are forever-incremental (although you still get full backup as an output because VEEAM uses synthetic backup). For those incremental passes, you will also see 120MB/s and faster speed (in other words, comparable with VCB).</description>
      <pubDate>Fri, 20 Nov 2009 14:33:29 GMT</pubDate>
      <author>Gostev</author>
      <guid>http://communities.vmware.com/message/1422144</guid>
      <dc:date>2009-11-20T14:33:29Z</dc:date>
      <clearspace:dateToText>2 days, 21 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Anyone else having these VDR issues?</title>
      <link>http://communities.vmware.com/message/1422100</link>
      <description>Good information.  Thanks.</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vdr</category>
      <pubDate>Fri, 20 Nov 2009 13:53:31 GMT</pubDate>
      <author>chrisaug</author>
      <guid>http://communities.vmware.com/message/1422100</guid>
      <dc:date>2009-11-20T13:53:31Z</dc:date>
      <clearspace:dateToText>2 days, 21 hours ago</clearspace:dateToText>
      <clearspace:replyCount>123</clearspace:replyCount>
    </item>
    <item>
      <title>How to recover VMDK from Backup Exec 12.5 VMWARE agent</title>
      <link>http://communities.vmware.com/message/1422005</link>
      <description>&lt;br /&gt;
Yes, it would failed as the SID is different and unique.&lt;br /&gt;
&lt;br /&gt;
Have you tried to recover the first / initial AD server using BESR 2010 as the whole complete set first and then you can start to recover the rest of the server ?&lt;br /&gt;
&lt;br /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Fri, 20 Nov 2009 11:36:27 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1422005</guid>
      <dc:date>2009-11-20T11:36:27Z</dc:date>
      <clearspace:dateToText>3 days, 8 minutes ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Potential VDR+CIFS Workaround</title>
      <link>http://communities.vmware.com/message/1422029</link>
      <description>In vdr 1.1 i'm experience a problem with connection CIFS shares with domain credential auth..&lt;br /&gt;
&lt;br /&gt;
With local credentials all - OK.</description>
      <pubDate>Fri, 20 Nov 2009 11:16:45 GMT</pubDate>
      <author>Bers</author>
      <guid>http://communities.vmware.com/message/1422029</guid>
      <dc:date>2009-11-20T11:16:45Z</dc:date>
      <clearspace:dateToText>3 days, 27 minutes ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>Failed to create snapshot for XXXX, error -3902 ( file access error)</title>
      <link>http://communities.vmware.com/message/1421858</link>
      <description>I will try it too.....</description>
      <pubDate>Fri, 20 Nov 2009 06:08:39 GMT</pubDate>
      <author>tomtux</author>
      <guid>http://communities.vmware.com/message/1421858</guid>
      <dc:date>2009-11-20T06:08:39Z</dc:date>
      <clearspace:dateToText>3 days, 5 hours ago</clearspace:dateToText>
      <clearspace:replyCount>15</clearspace:replyCount>
    </item>
    <item>
      <title>File Level Restore "unmounting disk" issue</title>
      <link>http://communities.vmware.com/message/1421850</link>
      <description>&lt;br /&gt;
We just released VDR 1.1 - and it comes with the fully supported File Level Restore Client for Windows VMs.  It will support 64-bit guest OS and addresses the limitations that we had in the experimental version.  You can download it here&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA=="&gt;http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA==&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Check out my post in the forum for more information about the VDR 1.1 release.</description>
      <pubDate>Fri, 20 Nov 2009 05:07:51 GMT</pubDate>
      <author>azmir</author>
      <guid>http://communities.vmware.com/message/1421850</guid>
      <dc:date>2009-11-20T05:07:51Z</dc:date>
      <clearspace:dateToText>3 days, 6 hours ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Next version of VDR??</title>
      <link>http://communities.vmware.com/message/1421848</link>
      <description>&lt;br /&gt;
VDR 1.1 was released today.  It can be downloaded here&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA=="&gt;http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA==&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Look in the forum for more information about this release.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Fri, 20 Nov 2009 05:01:32 GMT</pubDate>
      <author>azmir</author>
      <guid>http://communities.vmware.com/message/1421848</guid>
      <dc:date>2009-11-20T05:01:32Z</dc:date>
      <clearspace:dateToText>3 days, 6 hours ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>VDR schedule reboots</title>
      <link>http://communities.vmware.com/message/1421847</link>
      <description>&lt;br /&gt;
VDR 1.1 is available now&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA=="&gt;http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA==&lt;/a&gt;</description>
      <pubDate>Fri, 20 Nov 2009 04:56:19 GMT</pubDate>
      <author>azmir</author>
      <guid>http://communities.vmware.com/message/1421847</guid>
      <dc:date>2009-11-20T04:56:19Z</dc:date>
      <clearspace:dateToText>3 days, 6 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Selecting VM for VDR Backup strangeness?</title>
      <link>http://communities.vmware.com/message/1421830</link>
      <description>&lt;br /&gt;
I believe this is fixed in VDR 1.1 - available here&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA=="&gt;http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA==&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Release notes cover upgrade procedure&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/support/vdr/doc/vdr_110_releasenotes.html"&gt;http://www.vmware.com/support/vdr/doc/vdr_110_releasenotes.html&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Fri, 20 Nov 2009 04:48:51 GMT</pubDate>
      <author>azmir</author>
      <guid>http://communities.vmware.com/message/1421830</guid>
      <dc:date>2009-11-20T04:48:51Z</dc:date>
      <clearspace:dateToText>3 days, 6 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>VDR 1.0.2 - error message during recatalog error -2241 destination index invalid/damaged</title>
      <link>http://communities.vmware.com/message/1421822</link>
      <description>VDR 1.1 is available for download and highly recommend downloading this release - more information here&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/thread/243436?tstart=0"&gt;http://communities.vmware.com/thread/243436?tstart=0&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Also, some additional suggestions post VDR 1.1 upgrade&lt;br /&gt;
&lt;br /&gt;
Check the backup appliance for the store.lck folder, which is found in &lt;br /&gt;
&lt;br /&gt;
/VMwareDataRecovery/BackupStore/store.lck. &lt;br /&gt;
&lt;br /&gt;
If this folder exists and you are certain there are no other instances of Data Recovery using this deduplication store, delete the store.lck folder and its contents.  &lt;br /&gt;
&lt;br /&gt;
Once upgraded to VDR 1.1, delete the &amp;lt;destination&amp;gt;/VMwareDataRecovery/BackupStore.cat and &amp;lt;destination&amp;gt;/VMwareDataRecovery/BackupStore.cat.bak files and start a manual integrity check. This will cause the VDR engine to rebuild the catalog.</description>
      <pubDate>Fri, 20 Nov 2009 04:31:51 GMT</pubDate>
      <author>azmir</author>
      <guid>http://communities.vmware.com/message/1421822</guid>
      <dc:date>2009-11-20T04:31:51Z</dc:date>
      <clearspace:dateToText>3 days, 7 hours ago</clearspace:dateToText>
      <clearspace:replyCount>11</clearspace:replyCount>
    </item>
    <item>
      <title>Data Recovery backup job fails with error  -3902</title>
      <link>http://communities.vmware.com/message/1421818</link>
      <description>Note that VDR 1.1 is now available.  This releaseeliminates reoccurring error -3902 after vCenter Server connection has been restored, so we highly recommend customers upgrading to this release.  See my post in the forum for more information about this release.&lt;br /&gt;
&lt;br /&gt;
Thanks.</description>
      <pubDate>Fri, 20 Nov 2009 04:24:43 GMT</pubDate>
      <author>azmir</author>
      <guid>http://communities.vmware.com/message/1421818</guid>
      <dc:date>2009-11-20T04:24:43Z</dc:date>
      <clearspace:dateToText>3 days, 7 hours ago</clearspace:dateToText>
      <clearspace:replyCount>26</clearspace:replyCount>
    </item>
    <item>
      <title>VMware Data Recovery 1.1 is available now!</title>
      <link>http://communities.vmware.com/message/1421817</link>
      <description>I am happy to announce the availability of VMware Data Recovery (VDR) version 1.1.  We highly recommend every VDR customer to upgrade to this release.  Note that VDR 1.1 is supported on both vSphere 4.0 and vSphere 4.0 Update 1.&lt;br /&gt;
&lt;br /&gt;
A)	What's new in VDR 1.1:&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
•	GUI File Level Restore (FLR) client for Windows virtual machines – this is the fully supported version of the FLR client to allow granular restore of individual files.    This new functionality complements the full virtual machine restore capability that has been available since VDR 1.0.&lt;br /&gt;
&lt;br /&gt;
•	Support for backing up Windows 2008 R2 and Windows 7 virtual machines (requires upgrading to vSphere 4.0 Update 1 for VMware Tools support)&lt;br /&gt;
&lt;br /&gt;
•	Datarecovery.ini support – this file allows customization of the VDR parameters such as how frequent integrity check and reclaim operations run, maximum concurrent backups allowed and disabling any file level restore operations.  &lt;br /&gt;
&lt;br /&gt;
•	The VDR appliance is now a HW7 virtual machine, runs 64-bit CentOS 5.2 as the guest OS and has updated VMware Tools.  &lt;br /&gt;
&lt;br /&gt;
•	OpsLocks is disabled by default when connecting to CIFS shares as a backup destination.  In certain instances, disabling OpLocks improves stability of storing and retrieving data from CIFS destinations.&lt;br /&gt;
&lt;br /&gt;
•	Ability to add network shares using fully qualified domain name or IP address.&lt;br /&gt;
&lt;br /&gt;
•	Enhanced documentation set – the VDR Admin Guide now provides more detailed information on using, understanding and troubleshooting VDR.&lt;br /&gt;
&lt;br /&gt;
B)	Top issues resolved in VDR 1.1&lt;br /&gt;
&lt;br /&gt;
•	Improved integrity check performance – while the performance improvement is very data dependent (size of dedupe store and number of restore points), everyone should see an improvement in integrity check performance compared to VDR 1.0.x.&lt;br /&gt;
&lt;br /&gt;
•	Elimination of spurious damaged restore points and side effects (such as locked dedupe stores until damaged restore points are manually deleted).&lt;br /&gt;
&lt;br /&gt;
•	Elimination of reoccurring error -3902 after vCenter Server connection has been restored.&lt;br /&gt;
&lt;br /&gt;
•	Various vSphere Client to VDR appliance client connection problems including when there is a VM in inventory with too many IP addresses assigned.&lt;br /&gt;
&lt;br /&gt;
C)	Some things to keep in mind when upgrading to VDR 1.1&lt;br /&gt;
&lt;br /&gt;
•	Before shutting down the VDR 1.0.x instance, check the backup appliance for the store.lck folder, which is found in &lt;br /&gt;
&lt;br /&gt;
/VMwareDataRecovery/BackupStore/store.lck. &lt;br /&gt;
&lt;br /&gt;
If this folder exists and you are certain there are no other instances of Data Recovery using this deduplication store, delete the store.lck folder.  This will eliminate any issues post VDR 1.1 upgrade issues around  “Trouble writing files, error -1020 (Sharing violation)” and “Could not restore the Data Recovery appliance configuration” errors.  &lt;br /&gt;
&lt;br /&gt;
•	Follow the steps outlined in the release notes around the 1.0.x to 1.1 upgrade steps, especially if you want to retain existing restore points.&lt;br /&gt;
&lt;br /&gt;
VDR 1.1 documentation (Release Notes and Admin Guide) can be found here:&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/support/pubs/vdr_pubs.html"&gt;http://www.vmware.com/support/pubs/vdr_pubs.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
VDR 1.1 binaries can be found here&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA=="&gt;http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA==&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Thanks!</description>
      <pubDate>Fri, 20 Nov 2009 04:21:10 GMT</pubDate>
      <author>azmir</author>
      <guid>http://communities.vmware.com/message/1421817</guid>
      <dc:date>2009-11-20T04:21:10Z</dc:date>
      <clearspace:dateToText>3 days, 7 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>Open Files, databases</title>
      <link>http://communities.vmware.com/message/1421724</link>
      <description>&lt;br /&gt;
Hi Morpheous,&lt;br /&gt;
&lt;p /&gt;
Does this means if theVM is Windows Vm with VMWare tools installed, those vss-aware application can be backed up without having agent specific installed on each VM ? &lt;br /&gt;
&lt;p /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Fri, 20 Nov 2009 00:43:02 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1421724</guid>
      <dc:date>2009-11-20T00:43:02Z</dc:date>
      <clearspace:dateToText>3 days, 11 hours ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Backup Exec 12.5 Backup Strategy</title>
      <link>http://communities.vmware.com/message/1421712</link>
      <description>&lt;br /&gt;
Hi Tyson,&lt;br /&gt;
&lt;p /&gt;
If I were you I'd get the Agent for each of the Server apps (eg. Exchange, SQL Server and Domain Controller) yes it does sounds very expensive solution but when disaster strikes, you can begrateful that all of the data is transactionally consistent (not crash consistentas in VM hard power off).&lt;br /&gt;
&lt;p /&gt;
Exchange, SQL Server and Domain Controllers are the servers that you don't want to lose it so you can treat it as if they were a physical servers, the rest can go as normal assuming you install the VCB v1.5 properly.&lt;br /&gt;
&lt;p /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Fri, 20 Nov 2009 00:13:29 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1421712</guid>
      <dc:date>2009-11-20T00:13:29Z</dc:date>
      <clearspace:dateToText>3 days, 11 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VCB Batch Logging/History/Mail or VDR Mail Notification</title>
      <link>http://communities.vmware.com/message/1421694</link>
      <description>&lt;br /&gt;
Yes Please, that'd be great to know.&lt;br /&gt;
&lt;br /&gt;
Cheers&lt;br /&gt;
&lt;br /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Fri, 20 Nov 2009 00:06:10 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1421694</guid>
      <dc:date>2009-11-20T00:06:10Z</dc:date>
      <clearspace:dateToText>3 days, 11 hours ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>How to compare VMDKs filesystem</title>
      <link>http://communities.vmware.com/message/1421594</link>
      <description>Create a minimal windows install specifically for maintenance and jobs like this. You can leave it off or suspended. Keep a collection of tools available for testing etc. It becomes easy to temporarily attach VMDKs to recover files, test, compare, etc. With your two disks mounted you have hundreds of simple Windows tools for directory compare.</description>
      <pubDate>Thu, 19 Nov 2009 21:31:30 GMT</pubDate>
      <author>DSTAVERT</author>
      <guid>http://communities.vmware.com/message/1421594</guid>
      <dc:date>2009-11-19T21:31:30Z</dc:date>
      <clearspace:dateToText>3 days, 14 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>vcbmounter.exe speed</title>
      <link>http://communities.vmware.com/message/1421190</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
I have written a script with the Perl CLI SDK to backup some VMs from our ESX servers. From within the script I'm using vcbmounter.exe with this commandline:&lt;br /&gt;
&lt;p /&gt;
{quote} "c:\path\vcbmounter.exe -h vspherehost -u user -p password -a name:vmname -r w:\path\to\backup -t fullvm -F 0 -M 1 -m nbd"{/quote}&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Now a 28Gb VM takes 80mins to backup, which seems a bit long for me. Converter only needs 28mins for it.&lt;br /&gt;
&lt;p /&gt;
Can I somehow speed vcbmounter up? Do I use wrong/bad parameters?&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Lars&lt;br /&gt;
&lt;p /&gt;
(and what are the correct tags for code/quotes? There's no buttons in this editor...)</description>
      <pubDate>Thu, 19 Nov 2009 15:32:09 GMT</pubDate>
      <author>LarsOeschey</author>
      <guid>http://communities.vmware.com/message/1421190</guid>
      <dc:date>2009-11-19T15:32:09Z</dc:date>
      <clearspace:dateToText>3 days, 20 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>VMDKs not getting saved by VCBackup for V7 VMs</title>
      <link>http://communities.vmware.com/message/1421010</link>
      <description>&lt;br /&gt;
Hi there,&lt;br /&gt;
&lt;p /&gt;
we did an upgrade from VI3 to vSphere4 a couple of weeks ago.&lt;br /&gt;
This week I created some new vms which now are version 7 vms.&lt;br /&gt;
Those vms are running great and haven't got any problems.&lt;br /&gt;
&lt;p /&gt;
One drawback is, that we're no longer able to creat VCBackups from those V7 machines, because the VMDKs won't get saved.&lt;br /&gt;
The only files getting backed up are .log, .vmx, .vram and .da.&lt;br /&gt;
&lt;p /&gt;
Here is what VCbackup logs: &lt;br /&gt;
&lt;p /&gt;
&lt;i&gt;&lt;strike&gt;2009-11-19 11:12:33.978 'App' 684 info&lt;/strike&gt; Current working directory: D:\Jobs\VCBBackup&lt;/i&gt;&lt;br /&gt;
&lt;i&gt;&lt;strike&gt;2009-11-19 11:12:33.978 'BaseLibs' 684 info&lt;/strike&gt; HOSTINFO: Seeing Intel CPU, numCoresPerCPU 4 numThreadsPerCore 1.&lt;/i&gt;&lt;br /&gt;
&lt;i&gt;&lt;strike&gt;2009-11-19 11:12:33.978 'BaseLibs' 684 info&lt;/strike&gt; HOSTINFO: This machine has 1 physical CPUS, 4 total cores, and 4 logical CPUs.&lt;/i&gt;&lt;br /&gt;
&lt;i&gt;&lt;strike&gt;2009-11-19 11:12:34.447 'BaseLibs' 684 info&lt;/strike&gt; Using system libcrypto, version 90709F&lt;/i&gt;&lt;br /&gt;
&lt;i&gt;Copying "&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=_CX_Oracle_02"&gt;_CX_Oracle_02&lt;/a&gt; BERVM09A16/BERVM09A16.vmx":&lt;/i&gt;&lt;br /&gt;
+        0%=====================50%=====================100%+&lt;br /&gt;
+        **************************************************+&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;Copying "&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=_CX_Oracle_02"&gt;_CX_Oracle_02&lt;/a&gt; BERVM09A16/BERVM09A16.nvram":&lt;/i&gt;&lt;br /&gt;
+        0%=====================50%=====================100%+&lt;br /&gt;
+        **************************************************+&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;Copying "&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=_CX_Oracle_02"&gt;_CX_Oracle_02&lt;/a&gt; BERVM09A16//vmware-7.log":&lt;/i&gt;&lt;br /&gt;
+        0%=====================50%=====================100%+&lt;br /&gt;
+        **************************************************+&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;Copying "&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=_CX_Oracle_02"&gt;_CX_Oracle_02&lt;/a&gt; BERVM09A16//vmware-2.log":&lt;/i&gt;&lt;br /&gt;
+        0%=====================50%=====================100%+&lt;br /&gt;
+        **************************************************+&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;Copying "&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=_CX_Oracle_02"&gt;_CX_Oracle_02&lt;/a&gt; BERVM09A16//vmware-3.log":&lt;/i&gt;&lt;br /&gt;
+        0%=====================50%=====================100%+&lt;br /&gt;
+        **************************************************+&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;Copying "&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=_CX_Oracle_02"&gt;_CX_Oracle_02&lt;/a&gt; BERVM09A16//vmware-4.log":&lt;/i&gt;&lt;br /&gt;
+        0%=====================50%=====================100%+&lt;br /&gt;
+        **************************************************+&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;Copying "&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=_CX_Oracle_02"&gt;_CX_Oracle_02&lt;/a&gt; BERVM09A16//vmware-5.log":&lt;/i&gt;&lt;br /&gt;
+        0%=====================50%=====================100%+&lt;br /&gt;
+        **************************************************+&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;Copying "&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=_CX_Oracle_02"&gt;_CX_Oracle_02&lt;/a&gt; BERVM09A16//vmware-6.log":&lt;/i&gt;&lt;br /&gt;
+        0%=====================50%=====================100%+&lt;br /&gt;
+        **************************************************+&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;Copying "&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=_CX_Oracle_02"&gt;_CX_Oracle_02&lt;/a&gt; BERVM09A16//vmware.log":&lt;/i&gt;&lt;br /&gt;
+        0%=====================50%=====================100%+&lt;br /&gt;
+        **************************************************+&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
We are using this command to initiate the backup:&lt;br /&gt;
&lt;p /&gt;
&lt;i&gt;vcbmounter.exe -h vcenter.ourcompany.local -u backup -p ultrasecurepassword -a name:%1 -r "E:\VCBBACKUP\TODAY\%DATE%_%1" -t fullvm -L 2 &amp;gt; D:\Jobs\VCBBackup\VCBLog\%date%\%1.txt&lt;/i&gt; &lt;br /&gt;
&lt;p /&gt;
Older VMs are getting backed up without any problems.&lt;br /&gt;
Have you got any suggestions?&lt;br /&gt;
&lt;p /&gt;
Regards,&lt;br /&gt;
John&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcbackup</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vmdk</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backup</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">esx4</category>
      <pubDate>Thu, 19 Nov 2009 10:46:28 GMT</pubDate>
      <author>PACEDE</author>
      <guid>http://communities.vmware.com/message/1421010</guid>
      <dc:date>2009-11-19T10:46:28Z</dc:date>
      <clearspace:dateToText>4 days, 58 minutes ago</clearspace:dateToText>
    </item>
    <item>
      <title>Vsphere VCB</title>
      <link>http://communities.vmware.com/message/1420971</link>
      <description>No big difference between VCB for 3.5 and 4.0&lt;br /&gt;
&lt;br /&gt;
You can setup VCB Proxy in VM for IP storage only if SAN mode is used. NBD is fully supported for all storage types, but it would load service console / vmkernel interfaces instead of direct access to SAN.&lt;br /&gt;
&lt;br&gt;---&lt;br /&gt;
MCSA, MCTS, VCP, VMware vExpert '2009&lt;br /&gt;
&lt;a class="jive-link-external" href="http://blog.vadmin.ru"&gt;http://blog.vadmin.ru&lt;/a&gt;</description>
      <pubDate>Thu, 19 Nov 2009 10:00:28 GMT</pubDate>
      <author>Anton V Zhbankov</author>
      <guid>http://communities.vmware.com/message/1420971</guid>
      <dc:date>2009-11-19T10:00:28Z</dc:date>
      <clearspace:dateToText>4 days, 1 hour ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>vDR not seeing new cluster</title>
      <link>http://communities.vmware.com/message/1420744</link>
      <description>I created a new cluster (2 hosts) under the same datacenter as my other cluster (6 hosts) but for some reason the vDR does not see the new cluster as it doesn't even show up on the list to choose from.  I've already tried rebooting the vDR appliance and the vCenter VM.  Anyone else experienced this?</description>
      <pubDate>Thu, 19 Nov 2009 00:14:45 GMT</pubDate>
      <author>fgl</author>
      <guid>http://communities.vmware.com/message/1420744</guid>
      <dc:date>2009-11-19T00:14:45Z</dc:date>
      <clearspace:dateToText>4 days, 11 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>VCB error</title>
      <link>http://communities.vmware.com/message/1420396</link>
      <description>hello we are using a script in the crontab that is backing up the virt. machine to a nfs volume&lt;br /&gt;
for a long time a works very fine since last weekend different esx hosts (3.5 update 4) shows &lt;br /&gt;
an error that the vmx-file contains unknow   virtualhw.version = "4"&lt;br /&gt;
&lt;br /&gt;
17:45:08: (BACKUP) FEHLER - unbekannte vHW(=) bei /vmfs/volumes/4aa7bfbd-4298d3e2-accc-001cc4467212/WNPQT001/WNPQT001.vmx&lt;br /&gt;
&lt;br /&gt;
example of vmx file that is not working &lt;br /&gt;
&lt;br /&gt;
#!/usr/bin/vmware&lt;br /&gt;
config.version = "8"&lt;br /&gt;
displayName = "WNPQT001"&lt;br /&gt;
sched.cpu.shares = "normal"&lt;br /&gt;
memSize = "3600"&lt;br /&gt;
sched.mem.shares = "normal"&lt;br /&gt;
guestOS = "winnetstandard"&lt;br /&gt;
scsi0.present = "true"&lt;br /&gt;
scsi0.virtualDev = "lsilogic"&lt;br /&gt;
scsi0:0.present = "true"&lt;br /&gt;
scsi0:0.name = "WNPQT001.vmdk"&lt;br /&gt;
ethernet0.present = "true"&lt;br /&gt;
ethernet0.virtualDev = "vmxnet"&lt;br /&gt;
ethernet0.connectionType = "monitor_dev"&lt;br /&gt;
ide0:0.present = "true"&lt;br /&gt;
ide0:0.deviceType = "atapi-cdrom"&lt;br /&gt;
ide0:0.fileName = "auto detect"&lt;br /&gt;
ide0:0.startConnected = "FALSE"&lt;br /&gt;
powertype.reset = "default"&lt;br /&gt;
powertype.poweroff = "default"&lt;br /&gt;
powertype.poweron = "default"&lt;br /&gt;
draw = "gdi"&lt;br /&gt;
ethernet0.generatedaddress = "00:50:56:8e:28:f7"&lt;br /&gt;
uuid.bios = "50 21 00 2d 1e 35 a4 5e-0a d5 91 f9 32 cf 0b 78"&lt;br /&gt;
checkpoint.cptconfigname = "WNPQT001.vmss"&lt;br /&gt;
floppy0.startconnected = "false"&lt;br /&gt;
priority.ungrabbed = "normal"&lt;br /&gt;
uuid.location = "56 4d e8 5c f6 62 ac a3-4e b2 56 c5 ea 25 e7 d2"&lt;br /&gt;
suspend.directory = "."&lt;br /&gt;
ethernet0.addresstype = "vpx"&lt;br /&gt;
ethernet0.networkname = "VLAN_736"&lt;br /&gt;
priority.grabbed = "normal"&lt;br /&gt;
usb.present = "false"&lt;br /&gt;
floppy0.filename = "/dev/fd0"&lt;br /&gt;
virtualhw.version = "4"&lt;br /&gt;
powertype.suspend = "default"&lt;br /&gt;
isolation.tools.dnd.disable = "true"&lt;br /&gt;
tools.syncTime = "FALSE"&lt;br /&gt;
&lt;br /&gt;
scsi0:1.present = "true"&lt;br /&gt;
scsi0:1.name = "WNPQT001_1.vmdk"&lt;br /&gt;
scsi0:1.deviceType = "scsi-hardDisk"&lt;br /&gt;
&lt;br /&gt;
numvcpus = "2"&lt;br /&gt;
&lt;br /&gt;
scsi0:0.deviceType = "scsi-hardDisk"&lt;br /&gt;
ide0:0.autodetect = "true"&lt;br /&gt;
extendedConfigFile = "WNPQT001.vmxf"&lt;br /&gt;
virtualHW.productCompatibility = "hosted"&lt;br /&gt;
tools.upgrade.policy = "manual"&lt;br /&gt;
&lt;br /&gt;
scsi0:0.redo = ""&lt;br /&gt;
scsi0:1.redo = ""&lt;br /&gt;
scsi0:0.mode = "persistent"&lt;br /&gt;
scsi0:1.mode = "persistent"&lt;br /&gt;
nvram = "WNPQT001.nvram"&lt;br /&gt;
sched.cpu.units = "mhz"&lt;br /&gt;
scsi0:0.fileName = "WNPQT001.vmdk"&lt;br /&gt;
scsi0:1.fileName = "WNPQT001_1.vmdk"&lt;br /&gt;
&lt;br /&gt;
guestOSAltName = "Microsoft Windows Server 2003, Standard Edition (32-Bit)"&lt;br /&gt;
sched.cpu.affinity = "all"&lt;br /&gt;
toolScripts.afterPowerOn = "true"&lt;br /&gt;
toolScripts.afterResume = "true"&lt;br /&gt;
toolScripts.beforeSuspend = "true"&lt;br /&gt;
toolScripts.beforePowerOff = "true"&lt;br /&gt;
&lt;br /&gt;
annotation = "Logon Portal Evaluierung"&lt;br /&gt;
migrate.hostlog = "./WNPQT001.vmss.hlog"&lt;br /&gt;
sched.cpu.min = "0"&lt;br /&gt;
sched.mem.minsize = "0"&lt;br /&gt;
sched.mem.max = "3600"&lt;br /&gt;
sched.swap.derivedName = "/vmfs/volumes/4aa7bfbd-4298d3e2-accc-001cc4467212/WNPQ                  T001/WNPQT001.vmss.vswp"&lt;br /&gt;
hostCPUID.0 = "0000000168747541444d416369746e65"&lt;br /&gt;
guestCPUID.0 = "0000000168747541444d416369746e65"&lt;br /&gt;
userCPUID.0 = "0000000168747541444d416369746e65"&lt;br /&gt;
hostCPUID.1 = "00020f120002080000000001178bfbff"&lt;br /&gt;
guestCPUID.1 = "00020f120000080000000001078bbbff"&lt;br /&gt;
userCPUID.1 = "00020f120002080000000001078bbbff"&lt;br /&gt;
hostCPUID.80000001 = "00020f1200000e4600000002e3d3fbff"&lt;br /&gt;
guestCPUID.80000001 = "00020f1200000e4600000000e3d3fbff"&lt;br /&gt;
userCPUID.80000001 = "00020f1200000e4600000000e3d3fbff"&lt;br /&gt;
evcCompatibilityMode = "FALSE"</description>
      <pubDate>Wed, 18 Nov 2009 17:32:59 GMT</pubDate>
      <author>mach03</author>
      <guid>http://communities.vmware.com/message/1420396</guid>
      <dc:date>2009-11-18T17:32:59Z</dc:date>
      <clearspace:dateToText>4 days, 18 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>vicfg-cfgbackup restore fails, "invalidbundle"</title>
      <link>http://communities.vmware.com/message/1420181</link>
      <description>&lt;br /&gt;
Good, glad to hear that Dan.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Wed, 18 Nov 2009 14:34:20 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1420181</guid>
      <dc:date>2009-11-18T14:34:20Z</dc:date>
      <clearspace:dateToText>4 days, 21 hours ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>VDR - clear logs</title>
      <link>http://communities.vmware.com/message/1419966</link>
      <description>Yes, under Configuration -- Log -- Clear log&lt;br /&gt;
But as i can see now, this only clears the log - not the events.&lt;br /&gt;
&lt;br /&gt;
Paul</description>
      <pubDate>Wed, 18 Nov 2009 09:56:58 GMT</pubDate>
      <author>Paul1</author>
      <guid>http://communities.vmware.com/message/1419966</guid>
      <dc:date>2009-11-18T09:56:58Z</dc:date>
      <clearspace:dateToText>5 days, 1 hour ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Veeam Backup Vs PHD esXpress</title>
      <link>http://communities.vmware.com/message/1419618</link>
      <description>A number of messages that were irrelevant to the discussion were deleted.  This thread remains locked.&lt;br /&gt;
&lt;br /&gt;
I ask people to abide by the &lt;a class="jive-link-external" href="http://www.vmware.com/communities/content/community_terms/"&gt;VMware Communities Terms of Use&lt;/a&gt; and please keep the conversation civil.&lt;br /&gt;
&lt;br /&gt;
Regards, Robert&lt;br&gt;&lt;br&gt;Robert Dell'Immagine, Director of VMware Communities</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">veeam</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">phd_esxpress</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backup</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backups</category>
      <pubDate>Tue, 17 Nov 2009 22:34:07 GMT</pubDate>
      <author>RDellimmagine</author>
      <guid>http://communities.vmware.com/message/1419618</guid>
      <dc:date>2009-11-17T22:34:07Z</dc:date>
      <clearspace:dateToText>5 days, 13 hours ago</clearspace:dateToText>
      <clearspace:replyCount>32</clearspace:replyCount>
    </item>
    <item>
      <title>VMware Data Recovery could not add the specified network share.Please ensure your network credentials are valid</title>
      <link>http://communities.vmware.com/message/1419276</link>
      <description>Thanks jguide, that did the job!</description>
      <pubDate>Tue, 17 Nov 2009 17:16:59 GMT</pubDate>
      <author>fixit</author>
      <guid>http://communities.vmware.com/message/1419276</guid>
      <dc:date>2009-11-17T17:16:59Z</dc:date>
      <clearspace:dateToText>5 days, 18 hours ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>VDR 1.2 major issue.  Anyone see this one?</title>
      <link>http://communities.vmware.com/message/1418972</link>
      <description>I figured out the problem on this one.&lt;br /&gt;
I didn't have enough space in the data store that the backup was running in to attach the drive.&lt;br /&gt;
I can't say VMWare support was any help here, didn't hear from anyone until the following morning.&lt;br /&gt;
Looks like Gold support is now 8 hours wait time.</description>
      <pubDate>Tue, 17 Nov 2009 12:53:45 GMT</pubDate>
      <author>jguide</author>
      <guid>http://communities.vmware.com/message/1418972</guid>
      <dc:date>2009-11-17T12:53:45Z</dc:date>
      <clearspace:dateToText>5 days, 22 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Mysql service problem with VCB</title>
      <link>http://communities.vmware.com/message/1418999</link>
      <description>OK. So, using the example on pg 6:&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
{code}&lt;/p&gt;&lt;/p&gt;
&lt;p&gt;&lt;p&gt;IF &amp;ldquo;%1%&amp;rdquo; == &amp;ldquo;freeze&amp;rdquo; goto doFreeze  &lt;br/&gt;&lt;br/&gt;
goto postThaw  &lt;br/&gt;&lt;br/&gt;&lt;/p&gt;&lt;/p&gt;
&lt;p&gt;&lt;p&gt;:postThaw  &lt;br/&gt;&lt;br/&gt;
IF &amp;ldquo;%1%&amp;rdquo; == &amp;ldquo;thaw goto doThaw  &lt;br/&gt;&lt;br/&gt;
goto fail &lt;br/&gt;&lt;br/&gt;&lt;/p&gt;&lt;/p&gt;
&lt;p&gt;&lt;p&gt;:doFreeze  &lt;br/&gt;&lt;br/&gt;
net stop mysql  &lt;br/&gt;&lt;br/&gt;
goto EOF &lt;br/&gt;&lt;br/&gt;&lt;/p&gt;&lt;/p&gt;
&lt;p&gt;&lt;p&gt;:doThaw  &lt;br/&gt;&lt;br/&gt;
net start mysql  &lt;br/&gt;&lt;br/&gt;
goto EOF &lt;br/&gt;&lt;br/&gt;&lt;/p&gt;&lt;/p&gt;
&lt;p&gt;&lt;p&gt;:fail &lt;br/&gt;&lt;br/&gt;
echo &amp;ldquo;$ERRORLEVEL% &amp;gt;&amp;gt; vcbError.txt &lt;br/&gt;&lt;br/&gt;&lt;/p&gt;&lt;/p&gt;
&lt;p&gt;&lt;p&gt;:EOF &lt;br/&gt;&lt;br/&gt;
&lt;br/&gt;&lt;br/&gt;
{code}&lt;br/&gt;
&lt;br /&gt;
This would go on the VM under  "%ProgramFiles%\VMware\VMware Tools\backupScripts.d". You can call it vcb.bat or vcb.cmd. The VCB snapshot process will call the batch file automagically. You will need to have VMware Tools installed as indicated in the doc in order for this to work. If you have doubts, test it before putting it in production. I would recommend that you test backing up AND restoring the VM. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Dave Convery, VCDX&lt;br /&gt;
VMware vExpert 2009&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.dailyhypervisor.com/"&gt;http://www.dailyhypervisor.com&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/dconvery"&gt;http://twitter.com/dconvery&lt;/a&gt;&lt;br /&gt;
&lt;img src="http://communities.vmware.com/servlet/JiveServlet/download/38-20623/vExpert_logo_100x57.jpg" alt="http://communities.vmware.com/servlet/JiveServlet/download/38-20623/vExpert_logo_100x57.jpg" class="jive-image"  /&gt;&lt;br /&gt;
Careful. We don't want to learn from this.&lt;br /&gt;
Bill Watterson, "Calvin and Hobbes"</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">mysql</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">service</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">problem</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcb</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">script</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">snapshot</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vms</category>
      <pubDate>Tue, 17 Nov 2009 12:36:55 GMT</pubDate>
      <author>dconvery</author>
      <guid>http://communities.vmware.com/message/1418999</guid>
      <dc:date>2009-11-17T12:36:55Z</dc:date>
      <clearspace:dateToText>5 days, 23 hours ago</clearspace:dateToText>
      <clearspace:replyCount>12</clearspace:replyCount>
    </item>
    <item>
      <title>VMware Data Recovery step-by-step for newbie's</title>
      <link>http://communities.vmware.com/message/1418616</link>
      <description>&lt;p /&gt;
&lt;br /&gt;
Yes, that is very true, since I use that Veeam product, I'm no longer in anger with VDR &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt;&lt;br /&gt;
&lt;p /&gt;
Cheers.&lt;br /&gt;
&lt;p /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">data_recovery</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vdr</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vsphere4</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vsphere</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">recovery</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcenter</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">esx4</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vmware</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">data</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">recovere</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backup</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcb</category>
      <pubDate>Mon, 16 Nov 2009 23:15:43 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1418616</guid>
      <dc:date>2009-11-16T23:15:43Z</dc:date>
      <clearspace:dateToText>6 days, 12 hours ago</clearspace:dateToText>
      <clearspace:replyCount>11</clearspace:replyCount>
    </item>
    <item>
      <title>restoring an vm to a different host</title>
      <link>http://communities.vmware.com/message/1417981</link>
      <description>&lt;b&gt;Here is my backuptools.conf configuration:&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
#URL for the VC SDK instance to connect to. The format is&lt;br /&gt;
&lt;br /&gt;
#&amp;lt;hostname&amp;gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=%3Aport"&gt;:port&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
VCHOST=localhost&lt;br /&gt;
&lt;br /&gt;
#The certficate thumbprint for the host. This needs to be set only if SSL&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
#certificate verification needs to be enabled. The thumbprint can be obtainedby using &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
#"openssl s_client -connect &amp;lt;host&amp;gt;:443" to get the certificate and&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#"openssl x509 -noout -in &amp;lt;certificate&amp;gt; -fingerprint -sha1".&lt;br /&gt;
&lt;br /&gt;
#HOST_THUMBPRINT=&lt;br /&gt;
&lt;br /&gt;
#Username to use for VC SDK authentication&lt;br /&gt;
&lt;br /&gt;
USERNAME=root&lt;br /&gt;
&lt;br /&gt;
#Password to user for VC SDK authentication WARNING: It is recommended that you don't specify the&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#password in the configuration file.&lt;br /&gt;
&lt;br /&gt;
PASSWORD=xxxxxxxxxxxx&lt;br /&gt;
&lt;br /&gt;
#Since VMware tools report IP addresses only for running VMs,&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#we cache a mapping of IP addresses to virtual machine UUIDs&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
#in this file. This enables a powered off VM to be backed up&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#using its DNS name or IP address as an identifier even when it&lt;br /&gt;
&lt;br /&gt;
#is powered off. (However, the first backup must be taken when&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#the VM is powered on, or a cache entry must be created by invoking&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
#vcbVmName when the VM is powered on.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
VMNAMECACHE=/var/cache/vmName.cache&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#Temporary directory (required for legacy VM restoration and for restoring using scp.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
TEMPDIR=/tmp&lt;br /&gt;
&lt;br /&gt;
#Optional datastore catalog file.&lt;br /&gt;
#By default, all VCB utilities assume that datastore names refer to&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#VMFS volume labels and are therefore accessible under "/vmfs/volumes".&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#If this is not the case for any of your file systems containing virtual&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#machines (because you are using a non-standard NAS mount, for example),&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#you can use a datastore catalog to do the translation. Entries in this&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#catalog must adhere to the following standard:&lt;br /&gt;
&lt;br /&gt;
#"= "&amp;lt;mountpoint&amp;gt;&lt;br /&gt;
#Example: NAS share labelled "esxnas42" mounted on "/mnt/nas/42":&lt;br /&gt;
 #&lt;br /&gt;
&lt;a class="jive-link-anchor" href="#:port"&gt;:port&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
#&lt;br /&gt;
&lt;a class="jive-link-anchor" href="#esxnas42"&gt;esxnas42&lt;/a&gt;= /mnt/nas/42&lt;br /&gt;
#DATASTORE=/etc/vmware/datastore.cat&lt;br /&gt;
&lt;br /&gt;
#Default settings for importing legacy VMs that have been backed up&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#with "vmsnap.pl" on ESX 2.5.x.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#Datastore path and directory under which the VM is going to be&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#restored. You can use %VMNAME% to indicate the legacy VM's name&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#in the path&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#DSPATH="&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=vol0"&gt;vol0&lt;/a&gt; %VMNAME%"&lt;br /&gt;
&lt;br /&gt;
#The host the virtual machine is going to be associated with.&lt;br /&gt;
#The default setting associates the VM with the host the restore&lt;br /&gt;
#is being run on.&lt;br /&gt;
&lt;br /&gt;
VMHOST='hostname'&lt;br /&gt;
#Resource pool the VM is part of. You can use %VMHOST% to specify the&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#host name the VM is going to be associated with.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
#You can use the "resourcepools" command of "vcbUtil" to get a list of&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#all known resource pools on the VC/ESX server.&lt;br /&gt;
&lt;br /&gt;
#RESOURCEPOOL="/ha-folder-root/ha-datacenter/ha-folder-host/192.168.253.205/Resources"&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#VC folder in which the virtual machine is going to be placed in.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#User permissions are associated with folders.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#You can use the "vmfolders" command of "vcbUtil" to get a list of&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#all folders that can hold virtual machines.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
#FOLDERPATH="/ha-folder-root/ha-datacenter/ha-folder-vm"&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
&lt;b&gt;I don't know where else to configure...&lt;/b&gt;</description>
      <pubDate>Mon, 16 Nov 2009 12:07:14 GMT</pubDate>
      <author>CMCC</author>
      <guid>http://communities.vmware.com/message/1417981</guid>
      <dc:date>2009-11-16T12:07:14Z</dc:date>
      <clearspace:dateToText>6 days, 23 hours ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>file level restore for linux systems for VMWare Data Recovery</title>
      <link>http://communities.vmware.com/message/1417838</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
I was trying to dig up some information about the file level restore feature for VMware data recovery, specially for linux  systems.&lt;br /&gt;
&lt;p /&gt;
For example, is it limited to specific linux systems, specific linux filesystems being used within the guest. &lt;br /&gt;
&lt;p /&gt;
 For example, can it backup Novell  NSS filesystems on linux.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
I checked the documentation, but I can't seem to find any info in there about it.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Kind regards,&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Hen</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">linux</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">nss</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">file</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">level</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">data</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">recovery</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">novell</category>
      <pubDate>Mon, 16 Nov 2009 08:03:10 GMT</pubDate>
      <author>seniornwb</author>
      <guid>http://communities.vmware.com/message/1417838</guid>
      <dc:date>2009-11-16T08:03:10Z</dc:date>
      <clearspace:dateToText>1 week, 3 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>ComVault Simpana 8 with VCB</title>
      <link>http://communities.vmware.com/message/1417721</link>
      <description>&lt;br /&gt;
Hi All,&lt;br /&gt;
&lt;p /&gt;
Any findings on this subject?&lt;br /&gt;
&lt;p /&gt;
I too am looking to upgrade to vSphere 4 and would prefer to keep the existing scripted method for VCB backups when upgrading to CV8 also.&lt;br /&gt;
&lt;p /&gt;
Just curious about the VCB 1.5U1 reliance for the proxy box, whichin my case is ALSO the CV server.&lt;br /&gt;
&lt;p /&gt;
Cheers,&lt;br /&gt;
&lt;p /&gt;
Garreth. &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcb</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backup</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">comvault</category>
      <pubDate>Mon, 16 Nov 2009 02:16:29 GMT</pubDate>
      <author>Garrethh</author>
      <guid>http://communities.vmware.com/message/1417721</guid>
      <dc:date>2009-11-16T02:16:29Z</dc:date>
      <clearspace:dateToText>1 week, 9 hours ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>VDR and Firewall ports?</title>
      <link>http://communities.vmware.com/message/1417550</link>
      <description>You need to open TCP port 902 from VDR appliance to ESX servers.</description>
      <pubDate>Sun, 15 Nov 2009 11:53:36 GMT</pubDate>
      <author>shlomo.rivkin</author>
      <guid>http://communities.vmware.com/message/1417550</guid>
      <dc:date>2009-11-15T11:53:36Z</dc:date>
      <clearspace:dateToText>1 week, 23 hours ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>vcbmounter failed to mount the vm</title>
      <link>http://communities.vmware.com/message/1417545</link>
      <description>&lt;br /&gt;
Also please ensure that F: is not a mapped network drive.&lt;br /&gt;
&lt;p /&gt;
 Thanks&lt;br /&gt;
&lt;p /&gt;
Rahul</description>
      <pubDate>Sun, 15 Nov 2009 10:21:07 GMT</pubDate>
      <author>rahqa</author>
      <guid>http://communities.vmware.com/message/1417545</guid>
      <dc:date>2009-11-15T10:21:07Z</dc:date>
      <clearspace:dateToText>1 week, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Vshpere 4.0 Data Recovery Issue(Failed to create snapshot for VM1, error -3941 ( create snapshot failed)</title>
      <link>http://communities.vmware.com/message/1417539</link>
      <description>&lt;br /&gt;
Jacky,&lt;br /&gt;
&lt;br /&gt;
That's ok, at least i can share what I've learnt and went through, this is also one of the most common error in using VDR v1.02.&lt;br /&gt;
&lt;p /&gt;
please share it here if you know any other trick for the resolution.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Cheers.&lt;br /&gt;
&lt;p /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Sun, 15 Nov 2009 08:53:01 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1417539</guid>
      <dc:date>2009-11-15T08:53:01Z</dc:date>
      <clearspace:dateToText>1 week, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>VMX only backup - supported agents (e.g. TSM)</title>
      <link>http://communities.vmware.com/message/1417495</link>
      <description>Note the all backup solutions for virtual environment will backup also the vmx file. So do not worry.&lt;br /&gt;
For example you can use VCB or VDR (two VMware solutions).&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backup</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">tsm</category>
      <pubDate>Sun, 15 Nov 2009 06:22:58 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1417495</guid>
      <dc:date>2009-11-15T06:22:58Z</dc:date>
      <clearspace:dateToText>1 week, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>bring to compliance</title>
      <link>http://communities.vmware.com/message/1417238</link>
      <description>&lt;br /&gt;
I agree - the VDR admin guide is not close to complete.  It does not include the word 'compliance' anywhere in it, let alone how to use it.&lt;br /&gt;
&lt;p /&gt;
A search of the "knowledgebase" yields no results for compliance either. &lt;br /&gt;
&lt;p /&gt;
Try the evaluator's guide, it fils in some of the gaps, though it still leaves a lot to be desired: &lt;br /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/files/pdf/data-recovery-evaluators-guide.pdf"&gt;http://www.vmware.com/files/pdf/data-recovery-evaluators-guide.pdf&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Sat, 14 Nov 2009 14:23:42 GMT</pubDate>
      <author>swany7</author>
      <guid>http://communities.vmware.com/message/1417238</guid>
      <dc:date>2009-11-14T14:23:42Z</dc:date>
      <clearspace:dateToText>1 week, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Issue backup up Windows 2003 VM's</title>
      <link>http://communities.vmware.com/message/1417179</link>
      <description>Hi Eire,&lt;br /&gt;
&lt;br /&gt;
What is the actual Error message ? is that Error 156 failed to mount VM ? or failed to quiesce or even failed to hold up VM ?&lt;br /&gt;
&lt;p /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Sat, 14 Nov 2009 10:49:04 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1417179</guid>
      <dc:date>2009-11-14T10:49:04Z</dc:date>
      <clearspace:dateToText>1 week, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Disaster Recovery solutions (and ideas?) for VMWare vSphere4?</title>
      <link>http://communities.vmware.com/message/1417121</link>
      <description>I have  Falconstor coming next week to discuss replication with me. Trying to avoid buying FC/IP routers because of the cost of those things plus they really dont do much for the price.. The guy said IBM, HP, I think dell and someone else is OEMing there product now.&lt;br /&gt;
&lt;br /&gt;
Also going to be taking a look at hitachi's new storage. I have heard allot of good things about there new AMS line. Finally someone moving into the less expensive SAS storage with same performance, wonder what took so long. Also interested in the dense sata shelves they are offering.&lt;br /&gt;
&lt;br /&gt;
Sorry about the troubles you have had with your SVC, I have always had good luck with SVC. I worked with a shop had SVC in front of 8300's talk about fast storage. I know the last time I did replication with SVC we didnt have any issues. I also had a HUGE pipe to replicate over, OC3. &lt;br /&gt;
&lt;br /&gt;
My next pipe is a 1.5 gig pipe so I dont think I am going to have any trouble.&lt;br /&gt;
&lt;br /&gt;
Let me know how your falconstor turns out if you go that route.</description>
      <pubDate>Sat, 14 Nov 2009 04:45:40 GMT</pubDate>
      <author>Runamuck</author>
      <guid>http://communities.vmware.com/message/1417121</guid>
      <dc:date>2009-11-14T04:45:40Z</dc:date>
      <clearspace:dateToText>1 week, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>SMVI or NetBackup</title>
      <link>http://communities.vmware.com/message/1414738</link>
      <description>I do have a secondary filer at a DR site, and SMVI's ability to initiate snapmirror replication is very appealing to me.  I think my plan is to use SMVI for snapshots locally and replicating to our DR site, along with an occasional ndmp backup of a snapshot to tape.&lt;br /&gt;
&lt;br /&gt;
Thanks!</description>
      <pubDate>Wed, 11 Nov 2009 19:57:21 GMT</pubDate>
      <author>CharlesSchlesinger</author>
      <guid>http://communities.vmware.com/message/1414738</guid>
      <dc:date>2009-11-11T19:57:21Z</dc:date>
      <clearspace:dateToText>1 week, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Backup report script required</title>
      <link>http://communities.vmware.com/message/1414482</link>
      <description>What you want is a little complicated to do on a single command line &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;&lt;br /&gt;
Try to use VESI:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://blog.thevesi.org/2009/07/08/vizioncore-vranger-pro-40-and-powershell/"&gt;http://blog.thevesi.org/2009/07/08/vizioncore-vranger-pro-40-and-powershell/&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vmware</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backup</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backups</category>
      <pubDate>Wed, 11 Nov 2009 15:19:34 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1414482</guid>
      <dc:date>2009-11-11T15:19:34Z</dc:date>
      <clearspace:dateToText>1 week, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Issue backing up VM</title>
      <link>http://communities.vmware.com/message/1414194</link>
      <description>&lt;p /&gt;
&lt;br /&gt;
Hi All,&lt;br /&gt;
&lt;p /&gt;
Has anyone try logon to SSH console and then issue this command:&lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;services.sh restart&lt;/b&gt;&lt;br /&gt;
&lt;p /&gt;
That's what I usually do since I'm using ESXi 4 &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backups</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcbmounter</category>
      <pubDate>Wed, 11 Nov 2009 10:00:23 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1414194</guid>
      <dc:date>2009-11-11T10:00:23Z</dc:date>
      <clearspace:dateToText>1 week, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>backup software compatability guide</title>
      <link>http://communities.vmware.com/message/1414144</link>
      <description>&lt;div class="jive-quote"&gt;where is the backup software compatability guide?&lt;/div&gt;
Good question, but I haven't find.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;i heard of some backup software support vStorage API now, so when we do VCB backup, we never need holding tank now, this will reduce the backup time. but i want to know which backup software vendor support this functionality.&lt;/div&gt;
Probably all new version of backup product will support this feature.&lt;br /&gt;
&lt;br /&gt;
At this timeVeeam Backup 4 use it:&lt;br /&gt;
&lt;div class="jive-quote"&gt;NEW Veeam Backup &amp;#38; Replication 4.0 offers a major breakthrough in full and incremental backup speeds. Using technological advancements within VMware vSphere 4 and the VMware vStorage APIs for data protection&lt;/div&gt;
&lt;br /&gt;
Andre</description>
      <pubDate>Wed, 11 Nov 2009 08:40:41 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1414144</guid>
      <dc:date>2009-11-11T08:40:41Z</dc:date>
      <clearspace:dateToText>1 week, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VCB on a linux host.</title>
      <link>http://communities.vmware.com/message/1414074</link>
      <description>As written before VCB framework works only on Windows.&lt;br /&gt;
&lt;br /&gt;
You can use other solution, like VDR.&lt;br /&gt;
Or use vcbMount from your ESX.&lt;br /&gt;
&lt;br /&gt;
See also: &lt;a href="http://communities.vmware.com/docs/DOC-10780" class="jive-link-wiki"&gt;Backup solutions for VMware ESXi&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <pubDate>Wed, 11 Nov 2009 06:31:20 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1414074</guid>
      <dc:date>2009-11-11T06:31:20Z</dc:date>
      <clearspace:dateToText>1 week, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Backup solutions for VMware ESXi</title>
      <link>http://communities.vmware.com/docs/DOC-10780</link>
      <description>&lt;h2&gt;Free solutions &lt;/h2&gt;
&lt;br /&gt;
&lt;b&gt;ghettoVCB&lt;/b&gt; &lt;br /&gt;
&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-8760"&gt;ghettoVCB.sh - Free alternative for backing up VM's for ESX(i) 3.5 and 4.0+&lt;/a&gt; &lt;br /&gt;
&lt;a href="http://communities.vmware.com/docs/DOC-9843" class="jive-link-wiki"&gt;ghettoVCBg2 - Free alternative for backing up VMs in ESX(i) 3.5 and 4.x (no SSH console required!)&lt;/a&gt; &lt;br /&gt;
This script performs backups of virtual machines residing on ESX(i) 3.5/4.0+ servers using methodology similar to VMware's VCB tool. &lt;br /&gt;
It's created and well maintained by &lt;a href="http://communities.vmware.com/people/lamw" class="jive-link-profile"&gt;lamw&lt;/a&gt; &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Other script based solutions&lt;/b&gt; &lt;br /&gt;
&lt;a href="http://communities.vmware.com/docs/DOC-8881" class="jive-link-wiki"&gt;Another ESXi backup script&lt;/a&gt; &lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/blogs/gabrielmaciel/2008/12/08/free-vm-backup-alternative-for-esx-35-and-esxi"&gt;http://communities.vmware.com/blogs/gabrielmaciel/2008/12/08/free-vm-backup-alternative-for-esx-35-and-esxi&lt;/a&gt; &lt;br /&gt;
&lt;a href="http://communities.vmware.com/message/1031280#1031280" class="jive-link-message"&gt;Re: Free ESXi Backup Solution for Windows&lt;/a&gt; &lt;br /&gt;
&lt;a href="http://communities.vmware.com/thread/225865" class="jive-link-thread"&gt;Any new backup VM Solutions - ESX 3.5&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;VMware Converter Standalone&lt;/b&gt; &lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/products/converter/"&gt;http://www.vmware.com/products/converter/&lt;/a&gt; &lt;br /&gt;
Is not designed as a backup solution, but could be used also for this purpose. &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;File copy solutions&lt;/b&gt; &lt;br /&gt;
For a powered off VM is possible to simple copy all the files in the VM folder. &lt;br /&gt;
To use also with a powered on VM you need to do create a VMware snapshot to unlock the *-flat.vmdk files &lt;br /&gt;
To make this copy several tools could be used: &lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Datastore browser (directly from VIC or vSphere Client) &lt;/li&gt;
&lt;li&gt;SCP / Veeam fastSCP (need to enable SSH access: &lt;a class="jive-link-external" href="http://www.yellow-bricks.com/2008/08/10/howto-esxi-and-ssh/"&gt;http://www.yellow-bricks.com/2008/08/10/howto-esxi-and-ssh/&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;hr /&gt;
&lt;h2&gt;VMware solutions (need license) &lt;/h2&gt;
&lt;br /&gt;
&lt;b&gt;VMware Consolidated Backup (VCB)&lt;/b&gt; &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;VMware Data Recovery (VDR)&lt;/b&gt; &lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/products/vcenter-data-recovery/"&gt;http://www.vmware.com/products/vcenter-data-recovery/&lt;/a&gt;&lt;hr /&gt;
&lt;h2&gt;Other commercial solutions&lt;/h2&gt;
&lt;br /&gt;
&lt;b&gt;Veeam Backup &amp;#38; Replication&lt;/b&gt; &lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.veeam.com/vmware-esx-backup.html"&gt;http://www.veeam.com/vmware-esx-backup.html&lt;/a&gt; &lt;br /&gt;
&lt;a class="jive-link-external" href="http://veeam.com/vmware-esx-server/backup/documents/Veeam_Backup_User_Guide_3.0.pdf"&gt;http://veeam.com/vmware-esx-server/backup/documents/Veeam_Backup_User_Guide_3.0.pdf&lt;/a&gt; &lt;br /&gt;
Veeam Backup &amp;#38; Replication is the first enterprise-ready solution that combines backup and replication in a single product for fast recovery of your VMware ESX servers. Backup is easy, but recovery can be hard – and that’s when the clock is ticking loudest. But with Veeam Backup &amp;#38; Replication, fast recovery is easier than you ever thought possible. &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Vizioncore vRanger Pro 3.3&lt;/b&gt; &lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vizioncore.com/products/vRangerPro/vRanger3x.php"&gt;http://www.vizioncore.com/products/vRangerPro/vRanger3x.php&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vizioncore.com/products/vRangerPro/documents/vRangerProUserManual_Eng.pdf"&gt;http://www.vizioncore.com/products/vRangerPro/documents/vRangerProUserManual_Eng.pdf&lt;/a&gt;&lt;br /&gt;
Vizioncre vRanger Pro 3.3 is the ideal solution for customers wanting the same reliability of vRanger Pro 4.0 DPP but require features that are not yet supported in the 4.0 version. Supports VMware 3.X, 4.0 (vSphere) and ESXi.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Trilead VM Explorer&lt;/b&gt; &lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.trilead.com/"&gt;http://www.trilead.com/&lt;/a&gt; &lt;br /&gt;
Trilead VM Explorer is a management tool that eases management, backup and disaster recovery tasks in your VMware ESX environment. Backups can be stored to ESX, Windows, Linux and FreeBSD based storage platforms or directly to a SAN. VM Explorer has only to be licenced once for your infrastructure, you don't have to pay any fees per ESX Server, CPU, or anything similar.&lt;hr /&gt;
&lt;h2&gt;Commercial solutions that may support ESXi in the future releases&lt;/h2&gt;
&lt;br /&gt;
&lt;b&gt;esXpress&lt;/b&gt; &lt;br /&gt;
&lt;a class="jive-link-external" href="http://phdvirtual.com/products/esxpress-virtual-backup"&gt;http://phdvirtual.com/products/esxpress-virtual-backup&lt;/a&gt; &lt;br /&gt;
esXpress radically alters the notion of how to protect data in virtual infrastructures in one simple way: we use the virtual infrastructure to backup and restore itself!&lt;br /&gt;
esXpress v3.6 is Compatible with VMware ESX v3, v3.5 and vSphere4.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Vizioncore vRanger Pro 4.0&lt;/b&gt; &lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vizioncore.com/products/vRangerPro/"&gt;http://www.vizioncore.com/products/vRangerPro/&lt;/a&gt; &lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vizioncore.com/products/vRangerPro/documents/vRangerPro-DPP-FAQ.pdf"&gt;http://www.vizioncore.com/products/vRangerPro/documents/vRangerPro-DPP-FAQ.pdf&lt;/a&gt; &lt;br /&gt;
vRanger Pro Data Protection Platform (DPP) is the market-leading backup, recovery and backup management solution for virtual environments. The 4.0 release is the next generation of vRanger Pro which features a completely redesigned architecture, including plug-n-play modularity and a service-based architecture. VMware ESX3.x and VMware ESX 4.x upon initial release. Future releases include support for: VMware ESXi 3.x, VMware ESX &amp;#38; ESXi 3.x VCB, VMware ESXi 4.x, VMware ESX &amp;#38; ESXi 4.x VCB.&lt;br /&gt;
&lt;br /&gt;
&lt;hr /&gt;
&lt;h2&gt;The free ESXi "problem" &lt;/h2&gt;
With the free version of ESXi then you cannot actually use a third party tool to perform any backups. This is against your EULA. If it is the paid version of ESXi go for it.&lt;br /&gt;
So be sure which you are using to be sure you do not violate the EULA.&lt;br /&gt;
&lt;br /&gt;
As for other mechanisms, you can snapshot the VM and then copy the data via the vSphere Client/VIC as well. There is also VMware Converter. These tools do not violate the EULA.&lt;br /&gt;
&lt;br /&gt;
See also: &lt;a class="jive-link-external" href="http://www.virtualizationpractice.com/blog/?p=274"&gt;http://www.virtualizationpractice.com/blog/?p=274&lt;/a&gt; - VMware Forcing Third Parties to NOT Sell Products for Free ESXi&lt;br /&gt;
&lt;br /&gt;
&lt;hr /&gt;
&lt;h2&gt;Storage based solutions &lt;/h2&gt;
&lt;br /&gt;
If you have a stora NFS base, then file copy could be simple...&lt;br /&gt;
For other shared storage you can use storage snapshots.&lt;br /&gt;
&lt;br /&gt;
&lt;hr /&gt;
&lt;h2&gt;Backup ESXi configuration &lt;/h2&gt;
&lt;br /&gt;
You can use the RCLI to make a backup configuration of your ESXi host using &lt;br /&gt;
esxcfg-cfgbackup &lt;br /&gt;
You can find more information for the RCLI documentation here: &lt;a class="jive-link-external" href="http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_rcli.pdf"&gt;http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_rcli.pdf&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
There are also other ways to do a backup of ESXi configuration, see:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.r71.nl/index.php/kb/technical/212-vmware-esxi-configuration-backup"&gt;http://www.r71.nl/index.php/kb/technical/212-vmware-esxi-configuration-backup&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://support.dell.com/support/edocs/software/eslvmwre/DG/ESXi_3_5_U4/HTML/app_c.htm"&gt;http://support.dell.com/support/edocs/software/eslvmwre/DG/ESXi_3_5_U4/HTML/app_c.htm&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backup</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">esxi4</category>
      <pubDate>Wed, 16 Sep 2009 05:44:17 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/docs/DOC-10780</guid>
      <dc:date>2009-09-16T05:44:17Z</dc:date>
      <clearspace:dateToText>1 week, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Restoring vm in ESXi 4.0</title>
      <link>http://communities.vmware.com/message/1413104</link>
      <description>thank you all for replys. I made transfer to another esxi host vm's powered off via copying all vm's files.</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">esxi4</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">recovery</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">restore</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">esxi-backup.pl</category>
      <pubDate>Tue, 10 Nov 2009 09:10:48 GMT</pubDate>
      <author>raimundasjan</author>
      <guid>http://communities.vmware.com/message/1413104</guid>
      <dc:date>2009-11-10T09:10:48Z</dc:date>
      <clearspace:dateToText>1 week, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Datacentre Failure</title>
      <link>http://communities.vmware.com/message/1413005</link>
      <description>Thx Andru.</description>
      <pubDate>Tue, 10 Nov 2009 05:54:47 GMT</pubDate>
      <author>singhpdeep0007</author>
      <guid>http://communities.vmware.com/message/1413005</guid>
      <dc:date>2009-11-10T05:54:47Z</dc:date>
      <clearspace:dateToText>1 week, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>VDR will not complete a backup of a VM stuck at xx%</title>
      <link>http://communities.vmware.com/message/1412984</link>
      <description>I tried your tips but all 5 VM's reported a closed bracket on active tasks&lt;br /&gt;
&lt;br /&gt;
&lt;strike&gt;root@hpc01b14 /&lt;/strike&gt;# vim-cmd vmsvc/get.tasklist 96&lt;br /&gt;
(ManagedObjectReference) [ ]&lt;br /&gt;
&lt;br /&gt;
So I assumed the pending task must be on the VDR server so I rebooted it (I can't reboot my VM's a they are in production and I have to wait for a maintenace window)&lt;br /&gt;
When the VDR rebooted it did remove snapshots from 3 out of the 5 VM's &lt;br /&gt;
&lt;br /&gt;
For the remaining 2 VM's it is no longer showing them as active backup tasks but it still has the drives mounted and there are still Snapshots on the 2 VM's&lt;br /&gt;
&lt;br /&gt;
I was thinking of shutting down the VDR and just removing the snapshots manually and unmounting the drives from the VDR.  Anyone have experiance/thoughts with that?&lt;br /&gt;
&lt;br /&gt;
I do have a SR open with VMware.  If there is an official resolution I will post it</description>
      <pubDate>Tue, 10 Nov 2009 03:56:24 GMT</pubDate>
      <author>abbasi</author>
      <guid>http://communities.vmware.com/message/1412984</guid>
      <dc:date>2009-11-10T03:56:24Z</dc:date>
      <clearspace:dateToText>1 week, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>VDR Damaged Restore Points</title>
      <link>http://communities.vmware.com/message/1412792</link>
      <description>"Aha! Clearly, VDR has become self aware, and obviously gets jealous when you get to leave and it doesn't."&lt;br /&gt;
&lt;br /&gt;
For right now... I'm okay with that...  If it would just return when I do.</description>
      <pubDate>Mon, 09 Nov 2009 21:24:15 GMT</pubDate>
      <author>GT_Jacket</author>
      <guid>http://communities.vmware.com/message/1412792</guid>
      <dc:date>2009-11-09T21:24:15Z</dc:date>
      <clearspace:dateToText>1 week, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>usage of QueryChangedDiskAreas</title>
      <link>http://communities.vmware.com/message/1412333</link>
      <description>Hi All,&lt;br /&gt;
&lt;br /&gt;
I need some info regarding QueryChangedDiskAreas API introduced with vSphere. Can this API be used to get used blocks related to a disk.&lt;br /&gt;
&lt;br /&gt;
say, i have a VM with one disk. for this VM, i enabled changeTracking. now that i created a snapshot for it. this created a changeId. Now, i call QueryChangedDiskAreas API with changeId set to '*'. It is returning me DiskChangeInfo structure with only one entry, pointing to my entire VM length. &lt;br /&gt;
&lt;br /&gt;
another scenario, i have a VM enabled with changeTracking. this VM has got few snapshots. Now that am trying to retrieve only used blocks for this VM. How can this be done??&lt;br /&gt;
&lt;br /&gt;
Please let me know your comments.&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
-Raghu.</description>
      <pubDate>Mon, 09 Nov 2009 13:33:01 GMT</pubDate>
      <author>dayra01</author>
      <guid>http://communities.vmware.com/message/1412333</guid>
      <dc:date>2009-11-09T13:33:01Z</dc:date>
      <clearspace:dateToText>1 week, 6 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Backup of data store and VMs on Netapp</title>
      <link>http://communities.vmware.com/message/1412329</link>
      <description>I am having some difficulty backing up our VMs that are stored on a Netapp filer. I was wondering if anyone using a netapp filer with VMs on a FC lun could tell me how they are performing backups? I am intesrested in some commments on my following 3 issues from anyone with some experience with these products.&lt;br /&gt;
&lt;br /&gt;
I have the following products purchased:&lt;br /&gt;
Snap Manager for VI&lt;br /&gt;
FlexClone&lt;br /&gt;
Netbackup NDMP license&lt;br /&gt;
&lt;br /&gt;
ISSUE 1&lt;br /&gt;
The difficulty that i see is that the NDMP backup produces a backup which consistes of 2 large files. These two large files are my 2 ESX datastores. The 2 datastores are located on 1 FlexVol containing 2 FC Luns. I cannot recover any individual files or VMs. I think that this pretty much makes the NDMP backup of 2 FC Luns containing ESX data stores useless (unless i want to recover the whole datastore). Therefore I think that i will have to use VCB backups to backup the individual VMs and keep them for long term backup (we purchased NDMP license and no VCB).&lt;br /&gt;
&lt;br /&gt;
ISSUE 2&lt;br /&gt;
We have Snap Manager for VI configured and working successfuly to take snapshots of the VMs located on the 2 data stores. If i want to backup a snapshot I would usually enter the name of the snapshot in the file list sucah as /vol/vol2/.snapshot/hourly.1  Snap Manager for VI uses its own naming convention for snapshots which is a long and unique name. Therefore if i want to backup a snapshot created by SMVI I have to enter the name of the snapshot  which changes daily into the backup software file list. This is not practical on a daily basis for automated backups. Backups of these SMVI snapshots are required for consistent backups.&lt;br /&gt;
&lt;br /&gt;
ISSUE 3&lt;br /&gt;
FlexClone has been recommended to aid with backups so that a Volume can be mounted and then used for backup. Simple in theory for non-FC luns but in this case the FC luns contain VMFS datastores so the backup cannot take place until the FlexClone is presented and mounted to the ESX server. A flat file backup of the Datastore using Linux client may be possible at this stage. To perfrom VCB backups at this stage the VMs would have to be added to the ESX inventory and brough online. A lot of manual work here and not ideal on a daily basis.</description>
      <pubDate>Mon, 09 Nov 2009 13:14:52 GMT</pubDate>
      <author>mark_a_k</author>
      <guid>http://communities.vmware.com/message/1412329</guid>
      <dc:date>2009-11-09T13:14:52Z</dc:date>
      <clearspace:dateToText>1 week, 6 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>VDR Snapshots fail with VMware tools VSS support installed</title>
      <link>http://communities.vmware.com/message/1411966</link>
      <description>&lt;br /&gt;
Hey Mightyman&lt;br /&gt;
&lt;p /&gt;
 Thanks for your response.  I am testing with a 2008r2 server and a 2003 server.  The 2008r2 server displays the snapshot error and the 2003 box times out.  Manual snapshots work without an issue.&lt;br /&gt;
&lt;p /&gt;
At this point, after reading pretty much every post that is even slightly relevant (several from you), if decided to drop VDR until there is official 2008r2 support.  Hopefully by then lots of the other bugs that are being complained about will be resolved.</description>
      <pubDate>Mon, 09 Nov 2009 00:45:07 GMT</pubDate>
      <author>ydnA</author>
      <guid>http://communities.vmware.com/message/1411966</guid>
      <dc:date>2009-11-09T00:45:07Z</dc:date>
      <clearspace:dateToText>2 weeks, 10 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Cron Issues again with GhettoVCB.sh script</title>
      <link>http://communities.vmware.com/message/1411774</link>
      <description>&lt;br /&gt;
Good Evening Everyone,&lt;br /&gt;
&lt;p /&gt;
     Actually the issue has been resolved. Cron does work as I had a spelling mistype in my GhettoVCB.sh script. Also, I downloaded the latest GhettoVCB script. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
Steve</description>
      <pubDate>Sun, 08 Nov 2009 04:45:39 GMT</pubDate>
      <author>Stevester</author>
      <guid>http://communities.vmware.com/message/1411774</guid>
      <dc:date>2009-11-08T04:45:39Z</dc:date>
      <clearspace:dateToText>2 weeks, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Backing up a single ESXi v4 Server</title>
      <link>http://communities.vmware.com/message/1411526</link>
      <description>&lt;br /&gt;
Thanks Dave and Andre,&lt;br /&gt;
&lt;p /&gt;
This first customer originally purchased ESXi for $500. It is licensed but ESXi became free only weeks later. They have now upgraded to ESXi v4 with a new license. I guess that is the free version. I purchased an HP for another customer with ESXi on a USB device. I've since upgraded them to ESXi v4, which may also technically be a "free" version. I'm really looking for a plan here to use for 6-8 regular customers. I think the customers would choke over $1000 for essentials but I could actually use that for 3 customers since they are such good customers that they are connected to my system thru a VPN and are centrally administered from my site. They have been customers for 15-25 years, starting with mini-computers so it isn't like they are going away anytime soon.&lt;br /&gt;
&lt;p /&gt;
Seagate Backup Exec looks messy with VMWare. They are clearly targeting HUGE customers for their product and it has become massive overkill for most of mine. The VMWare agent is $3000 MSRP, although it is on-sale right now for $1669. One customer would need upgrades totalling $3000- for a media server (old server with tape drive), VMWare agent, Exchange Agent, SQL Agent. They still wouldn't be backing up Active Directory, but the forest is backed up at my location weekly.&lt;br /&gt;
&lt;p /&gt;
At this point the customers are using the backup included with Server 2003, which is the basic product version that eventually became Seagate Backup Exec. It is less than they should have but is free. I have exported each machine and written them to DVDs so I could create the virtual machines on a new VMWare server fairly easily. Perhaps I should just wait awhile until somebody gets a package well done for VMWare.</description>
      <pubDate>Sat, 07 Nov 2009 15:04:41 GMT</pubDate>
      <author>GregBradley</author>
      <guid>http://communities.vmware.com/message/1411526</guid>
      <dc:date>2009-11-07T15:04:41Z</dc:date>
      <clearspace:dateToText>2 weeks, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Failed to create snapshot for &amp;lt;VM-Name&amp;gt;, Error -1 (Unknown) on VDR v1.0.2</title>
      <link>http://communities.vmware.com/message/1411558</link>
      <description>&lt;br /&gt;
I found several posts on here that indicate you should reinstall VMWare Tools on the 2008 servers doing a custom install without the VSS driver (and without the SVGA driver, but that's unrelated to VDR). Some people say that works.&lt;br /&gt;
&lt;p /&gt;
 It definitely changed the error I was receiving....but hasn't resolved my issue yet. YMMV. Worth a try, right? If you try it, please post the results.&lt;br /&gt;
&lt;p /&gt;
Thanks,&lt;br /&gt;
&lt;p /&gt;
Bruce Lautenschlager&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vdr</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">failed</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">to</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">create</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">snapshot</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">for</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">&amp;lt;vm-name&amp;gt;</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">error</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">-1</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">(unknown)</category>
      <pubDate>Sat, 07 Nov 2009 14:20:01 GMT</pubDate>
      <author>blautens</author>
      <guid>http://communities.vmware.com/message/1411558</guid>
      <dc:date>2009-11-07T14:20:01Z</dc:date>
      <clearspace:dateToText>2 weeks, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>VDR and High I/O SQL Server</title>
      <link>http://communities.vmware.com/message/1411466</link>
      <description>Update.&lt;br /&gt;
&lt;br /&gt;
Apparently VDR for some reason is recognizing the Persistent disks.  I do not know how or why that would be possible, but I am going to find out with a restore rehearsal once this is done, and see what the problem is.</description>
      <pubDate>Sat, 07 Nov 2009 04:50:49 GMT</pubDate>
      <author>jjahns</author>
      <guid>http://communities.vmware.com/message/1411466</guid>
      <dc:date>2009-11-07T04:50:49Z</dc:date>
      <clearspace:dateToText>2 weeks, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>vData Recovery deleted the vmdk files that I didn't "tick" to backup</title>
      <link>http://communities.vmware.com/message/1411046</link>
      <description>That looks to be the correct KB article for our scenario, specifically this was relevant to us..&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;A non-independent disk resides on another datastore that is formatted to a larger block size as the disk is larger than 256GB&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
...the disks that got wiped out were all 500GB on seperate datstores.  &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/shocked.gif" alt=":0" /&gt;&lt;br /&gt;
&lt;p /&gt;
Just had a thought, it still only partly explains it, because the 5th disk in this VM was kept intact (the disk named the same as the C: drive).</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backups</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">data_recovery</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">failed</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">deleted</category>
      <pubDate>Fri, 06 Nov 2009 16:30:48 GMT</pubDate>
      <author>sportsystems</author>
      <guid>http://communities.vmware.com/message/1411046</guid>
      <dc:date>2009-11-06T16:30:48Z</dc:date>
      <clearspace:dateToText>2 weeks, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>fullvm and file  server:storage1</title>
      <link>http://communities.vmware.com/message/1410938</link>
      <description>&lt;br /&gt;
All right, thank you.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Att&lt;br /&gt;
&lt;p /&gt;
Marcos da Rosa</description>
      <pubDate>Fri, 06 Nov 2009 15:33:50 GMT</pubDate>
      <author>marcosdarosa</author>
      <guid>http://communities.vmware.com/message/1410938</guid>
      <dc:date>2009-11-06T15:33:50Z</dc:date>
      <clearspace:dateToText>2 weeks, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Trouble reading from destination volume, error -2241 ( Destination index invalid/damaged)</title>
      <link>http://communities.vmware.com/message/1410719</link>
      <description>Just wanted to say this I found this post very useful. Had a problem with my SAN over night and couldn't pull any backups from my dedupe store untill I had deleted the lock file as described above.&lt;br /&gt;
&lt;br /&gt;
Life saver!</description>
      <pubDate>Fri, 06 Nov 2009 11:40:17 GMT</pubDate>
      <author>Kiemo</author>
      <guid>http://communities.vmware.com/message/1410719</guid>
      <dc:date>2009-11-06T11:40:17Z</dc:date>
      <clearspace:dateToText>2 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>VDR evaluation - backups fail due to licensing issue</title>
      <link>http://communities.vmware.com/message/1410532</link>
      <description>&lt;br /&gt;
Thanks for the suggestions. We had in fact had added another host to the vCenter Server to manage - the host was running a licensed copy of Esxi. Changeing this host's licensing to Evaluation Mode resolved the issue.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
--&lt;br /&gt;
&lt;p /&gt;
riaan</description>
      <pubDate>Fri, 06 Nov 2009 05:51:43 GMT</pubDate>
      <author>riaanb</author>
      <guid>http://communities.vmware.com/message/1410532</guid>
      <dc:date>2009-11-06T05:51:43Z</dc:date>
      <clearspace:dateToText>2 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>VDR - Multiple VMDKs with the Same Name</title>
      <link>http://communities.vmware.com/message/1408700</link>
      <description>Does anyone have any insight ?   I can't be the only one that still gets this wih 1.0.2 even though it says its fixed.</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vdr</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vmdk</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backup</category>
      <pubDate>Wed, 04 Nov 2009 16:25:36 GMT</pubDate>
      <author>ben13</author>
      <guid>http://communities.vmware.com/message/1408700</guid>
      <dc:date>2009-11-04T16:25:36Z</dc:date>
      <clearspace:dateToText>2 weeks, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VDR job starts at wrong time</title>
      <link>http://communities.vmware.com/message/1408420</link>
      <description>&lt;br /&gt;
Have you ever used the "Bring to compliance" button? With using this option, the backup window will be ignored until all the VM's are backuped. (in compliance).&lt;br /&gt;
&lt;p /&gt;
But I can remeber, the same behavior in my environment. The selected times were inverted. Backups's stop at the beginning of the backup time frame. I than used 24 hours timeframe for backups, because the backup itself dosn't make a very high load with Version 7 HW, so it was no problem backuping up during the day. When you start the job at night for the first time, it will be backuing up at night for the following days.</description>
      <pubDate>Wed, 04 Nov 2009 13:08:54 GMT</pubDate>
      <author>Paul1</author>
      <guid>http://communities.vmware.com/message/1408420</guid>
      <dc:date>2009-11-04T13:08:54Z</dc:date>
      <clearspace:dateToText>2 weeks, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>vcbmounter error : X is not a writeable directory</title>
      <link>http://communities.vmware.com/message/1407150</link>
      <description>Junction points cannot be created on mapped drives. Hence you cant backup.</description>
      <pubDate>Tue, 03 Nov 2009 12:54:31 GMT</pubDate>
      <author>Lakshmi Gayatri</author>
      <guid>http://communities.vmware.com/message/1407150</guid>
      <dc:date>2009-11-03T12:54:31Z</dc:date>
      <clearspace:dateToText>2 weeks, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Networker Virtual Edition Client</title>
      <link>http://communities.vmware.com/message/1406584</link>
      <description>As far as I know there is still no support</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">networker</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">legato</category>
      <pubDate>Mon, 02 Nov 2009 21:17:28 GMT</pubDate>
      <author>AllBlack</author>
      <guid>http://communities.vmware.com/message/1406584</guid>
      <dc:date>2009-11-02T21:17:28Z</dc:date>
      <clearspace:dateToText>2 weeks, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>VMware Consolidation Backup</title>
      <link>http://communities.vmware.com/message/1405975</link>
      <description>VCB proxy can work on 2003 and 2008 Server, and also on x86 and x64 architecture.&lt;br /&gt;
But be sure that also the backup program (if you use some other software) is compatible.&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <pubDate>Mon, 02 Nov 2009 12:53:53 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1405975</guid>
      <dc:date>2009-11-02T12:53:53Z</dc:date>
      <clearspace:dateToText>2 weeks, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>VCB for Linux?</title>
      <link>http://communities.vmware.com/message/1405488</link>
      <description>The vcbMount command exist also on each ESX.&lt;br /&gt;
So you can implement some script also there.&lt;br /&gt;
But I do not think that you can move those script to another Linux system.&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <pubDate>Sun, 01 Nov 2009 16:39:23 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1405488</guid>
      <dc:date>2009-11-01T16:39:23Z</dc:date>
      <clearspace:dateToText>3 weeks, 19 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VCB Won't Work To New vSphere Host</title>
      <link>http://communities.vmware.com/message/1405408</link>
      <description>&lt;br /&gt;
Problem fixed.  The host name / certificate were not correct.  I renamed the host and generated a new certificate.  Here are the steps:&lt;br /&gt;
&lt;p /&gt;
In VI client, configuration, DNS and Routing, properties, change hostname.  Next, reboot server.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Run these commands and input the information when prompted: &lt;br /&gt;
&lt;p /&gt;
&lt;strike&gt;root@usvs1 ssl&lt;/strike&gt;# openssl req -nodes -new -x509 -keyout rui.key -out rui.crt -days 3650 -config /etc/pki/tls/openssl.cnf&lt;br /&gt;
Generating a 1024 bit RSA private key&lt;br /&gt;
.++++++&lt;br /&gt;
.......++++++&lt;br /&gt;
writing new private key to 'rui.key'&lt;br /&gt;
&lt;hr /&gt;
You are about to be asked to enter information that will be incorporated&lt;br /&gt;
into your certificate request.&lt;br /&gt;
What you are about to enter is what is called a Distinguished Name or a DN.&lt;br /&gt;
There are quite a few fields but you can leave some blank&lt;br /&gt;
For some fields there will be a default value,&lt;br /&gt;
If you enter '.', the field will be left blank.&lt;br /&gt;
&lt;hr /&gt;
Country Name (2 letter code) &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=GB"&gt;GB&lt;/a&gt;:US&lt;br /&gt;
State or Province Name (full name) &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=Berkshire"&gt;Berkshire&lt;/a&gt;:California&lt;br /&gt;
Locality Name (eg, city) &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=Newbury"&gt;Newbury&lt;/a&gt;:Palo Alto&lt;br /&gt;
Organization Name (eg, company) &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=My+Company+Ltd"&gt;My Company Ltd&lt;/a&gt;:VMware, Inc.&lt;br /&gt;
Organizational Unit Name (eg, section) []:VMware ESX Server Certificate&lt;br /&gt;
Common Name (eg, your name or your server's hostname) []:usvs1.localdomain&lt;br /&gt;
Email Address []:ssl-certificates@vmware.com&lt;br /&gt;
&lt;strike&gt;root@usvs1 ssl&lt;/strike&gt;# service mgmt-vmware restart&lt;br /&gt;
Stopping VMware ESX Management services:&lt;br /&gt;
   VMware ESX Host Agent Watchdog                          &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=++OK++"&gt;  OK  &lt;/a&gt;&lt;br /&gt;
   VMware ESX Host Agent                                   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=++OK++"&gt;  OK  &lt;/a&gt;&lt;br /&gt;
Starting VMware ESX Management services:&lt;br /&gt;
   VMware ESX Host Agent (background)                      &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=++OK++"&gt;  OK  &lt;/a&gt;&lt;br /&gt;
   Availability report startup (background)                &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=++OK++"&gt;  OK  &lt;/a&gt;&lt;br /&gt;
&lt;strike&gt;root@usvs1 ssl&lt;/strike&gt;#&lt;br /&gt;
&lt;p /&gt;
Replace "usvs1.localdomain" with your hostname:&lt;br /&gt;
&lt;br /&gt;
&lt;strike&gt;root@usvs1 ssl&lt;/strike&gt;# hostname&lt;br /&gt;
usvs1.localdomain</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcb</category>
      <pubDate>Sun, 01 Nov 2009 08:40:58 GMT</pubDate>
      <author>rhill</author>
      <guid>http://communities.vmware.com/message/1405408</guid>
      <dc:date>2009-11-01T08:40:58Z</dc:date>
      <clearspace:dateToText>3 weeks, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>ESXi 4.0 upgrade broke my backup solution, fix or alternate plan for small business?</title>
      <link>http://communities.vmware.com/message/1404818</link>
      <description>You mentioned not wanting to mess with scripts but there is a very well developed solution that combined with your intended iomega NAS device and external USB would make an excellent DR solution. Have a look at &lt;a class="jive-link-external" href="http://communities.vmware.com/docs/DOC-8760"&gt;http://communities.vmware.com/docs/DOC-8760&lt;/a&gt;. It is truly set and forget. A new version is eminent and will add a great deal of flexibility.</description>
      <pubDate>Sat, 31 Oct 2009 00:27:49 GMT</pubDate>
      <author>DSTAVERT</author>
      <guid>http://communities.vmware.com/message/1404818</guid>
      <dc:date>2009-10-31T00:27:49Z</dc:date>
      <clearspace:dateToText>3 weeks, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>17</clearspace:replyCount>
    </item>
    <item>
      <title>VDR Schedule</title>
      <link>http://communities.vmware.com/message/1404374</link>
      <description>&lt;br /&gt;
Did you get this fixed?&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
We have the same issue in our environment.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Manual backups work fine, however the schedule backups do not run.  We see in the logs that the integrity check runs fine, however, there is no attempt to run the actual backup.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Any ideas?</description>
      <pubDate>Fri, 30 Oct 2009 16:01:55 GMT</pubDate>
      <author>pacmantravis</author>
      <guid>http://communities.vmware.com/message/1404374</guid>
      <dc:date>2009-10-30T16:01:55Z</dc:date>
      <clearspace:dateToText>3 weeks, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Vmware data recovery vs vmware consolidated backup</title>
      <link>http://communities.vmware.com/message/1404324</link>
      <description>So here's some preliminary results on this.&lt;br /&gt;
&lt;br /&gt;
Using CIFS to backup to a windows share, you technically do not even need VCB to backup the deduplicated data off to tape.  The speed, on our environment, did not change that much using CIFS, but all environments are different.  &lt;br /&gt;
&lt;br /&gt;
I for one like this method of backup for the VMs.  Its integrated with vCenter.  Meaning my boss only goes to 1 interface to test the viability of a backup by performing a "restore rehearsal."&lt;br /&gt;
&lt;br /&gt;
I do not like the fact that there are a few limitations on this method of backup.  I believe that this is on purpose, and VMware will possibly intend to package this as a separate and expensive add-on for vSphere.  Granted I could be wrong, but that is my opinion on the matter.  Either way, this is something that, once they work out most of the kinks and provide file-level restore capabilities that are built-in to vCenter, will probably put most methods of backing up virtual machines to shame.  The concept and methods are there.&lt;br /&gt;
&lt;br /&gt;
Overall, happy with this.  Have not had any major issues so far.</description>
      <pubDate>Fri, 30 Oct 2009 15:33:53 GMT</pubDate>
      <author>jjahns</author>
      <guid>http://communities.vmware.com/message/1404324</guid>
      <dc:date>2009-10-30T15:33:53Z</dc:date>
      <clearspace:dateToText>3 weeks, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>11</clearspace:replyCount>
    </item>
    <item>
      <title>restore via Vibe</title>
      <link>http://communities.vmware.com/message/1404243</link>
      <description>&lt;br /&gt;
Review the other article from NetworkAdminKB.com on how to install and configure NetApp Vibe for use with VMWare ESX server.&lt;br /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://networkadminkb.com/kb/Knowledge%20Base/SAN/Installing%20and%20Configuring%20NetApp%20VIBE.aspx"&gt;http://networkadminkb.com/kb/Knowledge%20Base/SAN/Installing%20and%20Configuring%20NetApp%20VIBE.aspx&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
In that article the configuration file is explained.  Add the following line to the configuration file to specify SSH.Bat as the SSHCMD to run&lt;br /&gt;
&lt;p /&gt;
sshcmd=D:\Folder\ssh.bat&lt;br /&gt;
&lt;p /&gt;
Vibe is from Netapp, not VMWare.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Fri, 30 Oct 2009 14:33:48 GMT</pubDate>
      <author>LEslinger</author>
      <guid>http://communities.vmware.com/message/1404243</guid>
      <dc:date>2009-10-30T14:33:48Z</dc:date>
      <clearspace:dateToText>3 weeks, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Tape Backup Integration with VMware Data Recovery (VDR) - How to guide</title>
      <link>http://communities.vmware.com/message/1404079</link>
      <description>Great, thank you for the response sir !&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Fri, 30 Oct 2009 11:57:09 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1404079</guid>
      <dc:date>2009-10-30T11:57:09Z</dc:date>
      <clearspace:dateToText>3 weeks, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>VDR /RDM</title>
      <link>http://communities.vmware.com/message/1404077</link>
      <description>&lt;br /&gt;
Great, glad to hear that Cesario.&lt;br /&gt;
&lt;br /&gt;
Don't forget to mark it as answer to help people know which one is the solution &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/wink.gif" alt=";-)" /&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Cheers.&lt;br /&gt;
&lt;br /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Fri, 30 Oct 2009 11:56:20 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1404077</guid>
      <dc:date>2009-10-30T11:56:20Z</dc:date>
      <clearspace:dateToText>3 weeks, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>GhettoVCB.sh on ESX4 for backup VM: sintax error</title>
      <link>http://communities.vmware.com/message/1404001</link>
      <description>hi to all.&lt;br /&gt;
&lt;br /&gt;
after upgrade from esx3.5 to esx4, my old backup script (vmbk.pl) is unsupported.&lt;br /&gt;
&lt;br /&gt;
now i want test and use a new script, ghettoVCB.sh, for backup of my VM.&lt;br /&gt;
&lt;br /&gt;
with a old version of ghetto (Date: 11/01/2008), the script is working fine, but with last version (with new feature COMPRESSION) the script return a sintax error:&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;b&gt;&lt;strike&gt;root@esx03 ~&lt;/strike&gt;# ./ghettoVCB-completo.sh vmbcklist&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 5:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 8:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 15:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 18:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 20:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 21:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 26:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 29:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 34:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 37:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 42:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 44:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 47:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 50:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 53:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 56:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 59:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 61:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 63:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;: command not foundo.sh: line 65:&lt;/b&gt; &lt;br /&gt;
&lt;b&gt;'/ghettoVCB-completo.sh: line 66: syntax error near unexpected token `{&lt;/b&gt;&lt;br /&gt;
&lt;b&gt;'/ghettoVCB-completo.sh: line 66: `printUsage() {&lt;/b&gt;&lt;br /&gt;
&lt;b&gt;&lt;strike&gt;root@esx03 ~&lt;/strike&gt;#&lt;/b&gt; &lt;br /&gt;
&lt;p /&gt;
at line 66  the code is this:&lt;br /&gt;
&lt;p /&gt;
66  printUsage() {&lt;br /&gt;
67         SCRIPT_PATH=$(basename $0)&lt;br /&gt;
68         echo -e "\nUsage: ${SCRIPT_PATH} &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=VM_FILE_INPUT"&gt;VM_FILE_INPUT&lt;/a&gt;\n"&lt;br /&gt;
69         exit&lt;br /&gt;
70  } &lt;br /&gt;
&lt;p /&gt;
 can you help me??&lt;br /&gt;
&lt;p /&gt;
very thanks &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Fri, 30 Oct 2009 10:47:42 GMT</pubDate>
      <author>mardux</author>
      <guid>http://communities.vmware.com/message/1404001</guid>
      <dc:date>2009-10-30T10:47:42Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Snapshots &amp;#38; Backups</title>
      <link>http://communities.vmware.com/message/1403898</link>
      <description>I suppose there is no such limitations. VDR can backup any VM and maximum size for both VMDK and RDM disks is 2TB.&lt;br /&gt;
&lt;br /&gt;
But I strongly do not recommend VDR to backup such VMs. Backup system disk / partition only with VDR and backup data with traditional backup solutions.&lt;br /&gt;
&lt;br&gt;---&lt;br /&gt;
MCSA, MCTS, VCP, VMware vExpert '2009&lt;br /&gt;
&lt;a class="jive-link-external" href="http://blog.vadmin.ru"&gt;http://blog.vadmin.ru&lt;/a&gt;</description>
      <pubDate>Fri, 30 Oct 2009 08:33:46 GMT</pubDate>
      <author>Anton V Zhbankov</author>
      <guid>http://communities.vmware.com/message/1403898</guid>
      <dc:date>2009-10-30T08:33:46Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Snapshot question while trying to using VDR 1.02</title>
      <link>http://communities.vmware.com/message/1403724</link>
      <description>I'm getting the same error on some of my VMs using VCB and NetBackup. Any one know how to fix or work around this?</description>
      <pubDate>Fri, 30 Oct 2009 01:45:49 GMT</pubDate>
      <author>SonyaGJordan</author>
      <guid>http://communities.vmware.com/message/1403724</guid>
      <dc:date>2009-10-30T01:45:49Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>How to use vStorage API ?</title>
      <link>http://communities.vmware.com/message/1403730</link>
      <description>&lt;p /&gt;
Yes, that's what i was thinking before :-|&lt;br /&gt;
&lt;br /&gt;
Otherwise your Ghetto script will supports vStorage :-O&lt;br /&gt;
&lt;p /&gt;
Cheers.&lt;br /&gt;
&lt;br /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vstorage</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcb</category>
      <pubDate>Fri, 30 Oct 2009 01:32:27 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1403730</guid>
      <dc:date>2009-10-30T01:32:27Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>cannot backup powered off VM's with VDR</title>
      <link>http://communities.vmware.com/message/1403665</link>
      <description>&lt;p /&gt;
Hi ehinkle,&lt;br /&gt;
&lt;br /&gt;
May I know what VM is that ?&lt;br /&gt;
&lt;p /&gt;
I also got thesame problem with Windows Server2003-8 x64 bit too but i've found the solution by following the steps bellow:&lt;br /&gt;
&lt;p /&gt;
This is what VMWare suggest: &lt;a class="jive-link-external" href="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;#38;docType=kc&amp;#38;externalId=1009073&amp;#38;sliceId=1&amp;#38;docTypeID=DT_KB_1_1&amp;#38;dialogID=38752513&amp;#38;stateId=0%200%2038754922"&gt;http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;#38;docType=kc&amp;#38;externalId=1009073&amp;#38;sliceId=1&amp;#38;docTypeID=DT_KB_1_1&amp;#38;dialogID=38752513&amp;#38;stateId=0%200%2038754922&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
But I'm not following it ;-| since I feel uncomfortable in removing the VSS snapshot provider support in VMWare tools: &lt;br /&gt;
&lt;p /&gt;
&lt;ol&gt;
&lt;li&gt;Backup the following regkey: *&lt;u&gt;HKLM\Software\Microsoft\EventSystem&lt;/u&gt; *&lt;/li&gt;
&lt;li&gt;Erase the regkey _&lt;b&gt;HKLM\Software\Microsoft\EventSystem{26c409cc-ae86-11d1-b616-00805fc79216}&lt;/b&gt; _an below&lt;/li&gt;
&lt;li&gt;Reboot.&lt;/li&gt;
&lt;li&gt;Verify that things are working by running&lt;/li&gt;
&lt;/ol&gt;
&lt;blockquote&gt;&lt;b&gt;vssadmin list writers&lt;/b&gt; &lt;br clear="all" /&gt;			 *	vssadmin list providers.*&lt;/blockquote&gt;
and then in the services.msc list of services snap ins, make sure the following services are Started Automatically:COM+ System Application&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;Distributed Transaction Coordinator&lt;/li&gt;
&lt;li&gt;Volume Shadow Copy&lt;/li&gt;
&lt;li&gt;VMware Physical Disk Helper Service&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
Automatically but not started:&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;Microsoft Software Shadow Copy Provider&lt;/li&gt;
&lt;li&gt;VMware Snapshot Provider&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
now the backup is all working great &lt;img src="http://communities.vmware.com/images/emoticons/happy.gif" alt="http://communities.vmware.com/images/emoticons/happy.gif" class="jive-image"  /&gt;&lt;br /&gt;
&lt;br /&gt;
This is the solution that i tried around myself without uninstalling the VSS Provider support in VMWare tools&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Fri, 30 Oct 2009 00:06:23 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1403665</guid>
      <dc:date>2009-10-30T00:06:23Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.</title>
      <link>http://communities.vmware.com/message/1403593</link>
      <description>To All,&lt;br /&gt;
&lt;br /&gt;
The&lt;br /&gt;
following tricks working without uninstalling the VMWare tools support&lt;br /&gt;
for VSS. Please be advised that I've tried this method on all of my failed to backup of &lt;b&gt;&lt;u&gt;Windows Server 2008/2003 x64&lt;/u&gt;&lt;/b&gt; VMs&lt;br /&gt;
&lt;br /&gt;
The reason why I'm doing this again is that I feel uncomfortable in removing the VSS snapshot provider support in VMWare tools:&lt;br /&gt;
&lt;br /&gt;
1. Backup the following regkey: _*HKLM\Software\Microsoft\EventSystem* _&lt;br /&gt;
2. Erase the regkey &lt;u&gt;&lt;b&gt;HKLM\Software\Microsoft\EventSystem{26c409cc-ae86-11d1-b616-00805fc79216}&lt;/b&gt;&lt;/u&gt; an below &lt;br /&gt;
3. Reboot. &lt;br /&gt;
4. Verify that things are working by running&lt;br /&gt;
&lt;br /&gt;
vssadmin list writers&lt;br /&gt;
vssadmin list providers. &lt;br /&gt;
&lt;p /&gt;
and then in the services.msc list of services snap ins, make sure the following services are Started Automatically:&lt;br /&gt;
&lt;br /&gt;
1. COM+ System Application&lt;br /&gt;
2. Distributed Transaction Coordinator&lt;br /&gt;
3. Volume Shadow Copy&lt;br /&gt;
4. VMware Physical Disk Helper Service&lt;br /&gt;
&lt;p /&gt;
Automatically but not started:&lt;br /&gt;
&lt;br /&gt;
1. Microsoft Software Shadow Copy Provider&lt;br /&gt;
2. VMware Snapshot Provider &lt;br /&gt;
&lt;br /&gt;
now the backup is all working great &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt;&lt;br /&gt;
&lt;br /&gt;
This is the solution that i tried around myself without uninstalling the VSS Provider support in VMWare tools.&lt;br /&gt;
&lt;br /&gt;
See the following KB URL:    &lt;b&gt;_&lt;a class="jive-link-external" href="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;#38;docType=kc&amp;#38;externalId=1009073&amp;#38;sliceId=1&amp;#38;docTypeID=DT_KB_1_1&amp;#38;dialogID=38752513&amp;#38;stateId=0%200%2038754922_"&gt;http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;#38;docType=kc&amp;#38;externalId=1009073&amp;#38;sliceId=1&amp;#38;docTypeID=DT_KB_1_1&amp;#38;dialogID=38752513&amp;#38;stateId=0%200%2038754922_&lt;/a&gt;&lt;/b&gt;&lt;br /&gt;
&lt;p /&gt;
Hope this can be a helpful post for all of you.&lt;br /&gt;
&lt;p /&gt;
Kind Regards,&lt;br /&gt;
AWT</description>
      <pubDate>Thu, 29 Oct 2009 22:30:09 GMT</pubDate>
      <author>AlbertWT</author>
      <guid>http://communities.vmware.com/message/1403593</guid>
      <dc:date>2009-10-29T22:30:09Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>vcenter vcb role and search virtual machine</title>
      <link>http://communities.vmware.com/message/1403229</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
 that was the reason, the permission was defined at wrong place - at the cluster level. I forgot it. When I redefined it to datacenter, enumeration  started working.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks, David</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcenter</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcb</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcbvmname</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcbmounter</category>
      <pubDate>Thu, 29 Oct 2009 18:06:32 GMT</pubDate>
      <author>dsumsky</author>
      <guid>http://communities.vmware.com/message/1403229</guid>
      <dc:date>2009-10-29T18:06:32Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>vSphere includes VMware Data Recovery...correct?</title>
      <link>http://communities.vmware.com/message/1403007</link>
      <description>&lt;br /&gt;
Thank you!&lt;br /&gt;
&lt;p /&gt;
 SB</description>
      <pubDate>Thu, 29 Oct 2009 15:34:34 GMT</pubDate>
      <author>SlickBag</author>
      <guid>http://communities.vmware.com/message/1403007</guid>
      <dc:date>2009-10-29T15:34:34Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>File &amp;lt;unspecified filename&amp;gt; is larger than the maximum size supported by datastore &amp;lt;unspecified datastore&amp;gt;</title>
      <link>http://communities.vmware.com/message/1402631</link>
      <description>&lt;br /&gt;
Thanks, dstavert.&lt;br /&gt;
&lt;p /&gt;
The information is very useful, and offers a work around of sorts. Only problem I see with this is that it locks you in with regards to Storage vMotions? If you move the VM using SvMotion to different LUNs (say from LUN 1 and 3, to LUN 6 and 8). The config file would probably still point the working dir and the swap dir to LUN 1 and 3? Which means, if you want to remove LUN 1 and 3 for a storage redesign, you have to take down the VM in question to reconfigure the VMX. &lt;br /&gt;
&lt;p /&gt;
So adding these parameters to the VMX basically makes Storage vMotions unusable for the VMs (If I understand how the config parameters work). I presume that Storage vMotion does not update the working dir and move the swap files during a Storage vMotion.&lt;br /&gt;
&lt;p /&gt;
 We have 3 storage systems attached to our SAN with a total raw capacity of approx. 130TB, and changing the LUN design (adding/removing) is vital to us. We also completely changed out our Dell EMC Clariions with new ones, all without downtime. The only reason we managed to achieve this was because of Storage vMotions. Because of this, I cannot do a configuration change that locks us in to the LUNs the VMs are running on now. Especially for these VMs, which are basically some of the most important ones.</description>
      <category domain="http://communities.vmware.com/tags?communityID=3066">snapshot</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">backup</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vsphere</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">esx4</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vcb</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">vsphere4</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">snapshots</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">fail</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">block</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">size</category>
      <category domain="http://communities.vmware.com/tags?communityID=3066">maximum</category>
      <pubDate>Thu, 29 Oct 2009 10:32:59 GMT</pubDate>
      <author>glemmestad</author>
      <guid>http://communities.vmware.com/message/1402631</guid>
      <dc:date>2009-10-29T10:32:59Z</dc:date>
      <clearspace:dateToText>3 weeks, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
  </channel>
</rss>

