<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Snapshot Issue with VMware Data Recovery</title>
	<atom:link href="http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:13:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Yannick</title>
		<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/comment-page-1/#comment-51337</link>
		<dc:creator>Yannick</dc:creator>
		<pubDate>Thu, 11 Aug 2011 09:41:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1427#comment-51337</guid>
		<description>Hello, 

I have the same problem but only with a virtual machine which has two disk on two diffent datastores.

If I use your method it is definitively good ? Or should I do this for exemple each week ?

Thx.</description>
		<content:encoded><![CDATA[<p>Hello, </p>
<p>I have the same problem but only with a virtual machine which has two disk on two diffent datastores.</p>
<p>If I use your method it is definitively good ? Or should I do this for exemple each week ?</p>
<p>Thx.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel</title>
		<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/comment-page-1/#comment-51290</link>
		<dc:creator>Joel</dc:creator>
		<pubDate>Fri, 05 Aug 2011 19:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1427#comment-51290</guid>
		<description>This appears to still be an issue with vdr 1.2.1.  Making the above changes to ddb.deleteable and create/remove snap process cleared the issue for me.  Thx.</description>
		<content:encoded><![CDATA[<p>This appears to still be an issue with vdr 1.2.1.  Making the above changes to ddb.deleteable and create/remove snap process cleared the issue for me.  Thx.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maarten van Dijk</title>
		<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/comment-page-1/#comment-49546</link>
		<dc:creator>Maarten van Dijk</dc:creator>
		<pubDate>Wed, 24 Nov 2010 08:45:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1427#comment-49546</guid>
		<description>I ran ito this problem as well.
I used VDR over a long time but never noticed this behaviour till my VDR solution crashed. Over a long time I expierenced problems creating decent backups. The first few months after implementing I it ran without any problem but than without any reason it started to produce failed backups. I tried different things to get i working again but succeeded always in a temporarly working solution. I removed the existing job and created a new job to a different destination. Since I did this I was never be able to get it running decent again.
I think to remove the product completly and setting up a different solution for my backup. Does anybody recommend something?</description>
		<content:encoded><![CDATA[<p>I ran ito this problem as well.<br />
I used VDR over a long time but never noticed this behaviour till my VDR solution crashed. Over a long time I expierenced problems creating decent backups. The first few months after implementing I it ran without any problem but than without any reason it started to produce failed backups. I tried different things to get i working again but succeeded always in a temporarly working solution. I removed the existing job and created a new job to a different destination. Since I did this I was never be able to get it running decent again.<br />
I think to remove the product completly and setting up a different solution for my backup. Does anybody recommend something?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ken</title>
		<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/comment-page-1/#comment-49067</link>
		<dc:creator>ken</dc:creator>
		<pubDate>Wed, 01 Sep 2010 20:25:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1427#comment-49067</guid>
		<description>Hi Scott, we met at VMUG a few weeks ago at the EMC booth and talked about VCDX cert...  I have good luck with VDR to date, however, I just updated vCenter to 4.1 and rebuilt vCenter on w2008 64bit, and also configured VUM on the same server, hey - its a lab!  and now VDR can&#039;t seem to read the snapshot during the backup process, it fails everytime.. I&#039;ve tried a variety of things to resolve this issue, moved vCenter VM to new datastore with more space since the one it was on was showing usage warnings.. rebooted, looked at logs, can&#039;t see anything at all the would indicate why VDR can&#039;t mount \ read the snapshot to perform the backup... all other VMs are backing up fine..  my thought is that it just isn&#039;t ready for vSphere 4.1 64bit vcenter \ VUM... has anyone else experienced this or know what this is about?</description>
		<content:encoded><![CDATA[<p>Hi Scott, we met at VMUG a few weeks ago at the EMC booth and talked about VCDX cert&#8230;  I have good luck with VDR to date, however, I just updated vCenter to 4.1 and rebuilt vCenter on w2008 64bit, and also configured VUM on the same server, hey &#8211; its a lab!  and now VDR can&#8217;t seem to read the snapshot during the backup process, it fails everytime.. I&#8217;ve tried a variety of things to resolve this issue, moved vCenter VM to new datastore with more space since the one it was on was showing usage warnings.. rebooted, looked at logs, can&#8217;t see anything at all the would indicate why VDR can&#8217;t mount \ read the snapshot to perform the backup&#8230; all other VMs are backing up fine..  my thought is that it just isn&#8217;t ready for vSphere 4.1 64bit vcenter \ VUM&#8230; has anyone else experienced this or know what this is about?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Glücker</title>
		<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/comment-page-1/#comment-48766</link>
		<dc:creator>Stefan Glücker</dc:creator>
		<pubDate>Thu, 01 Jul 2010 12:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1427#comment-48766</guid>
		<description>I actually have the same problem with BackupExec 2010 and using the VMware Agent - which uses the vstorage API&#039;s ... No vcbmounter -U there anymore, which mostly helped in enviroments with VCB ... so I will try you&#039;re suggestions.</description>
		<content:encoded><![CDATA[<p>I actually have the same problem with BackupExec 2010 and using the VMware Agent &#8211; which uses the vstorage API&#8217;s &#8230; No vcbmounter -U there anymore, which mostly helped in enviroments with VCB &#8230; so I will try you&#8217;re suggestions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hcalik</title>
		<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/comment-page-1/#comment-47832</link>
		<dc:creator>hcalik</dc:creator>
		<pubDate>Wed, 07 Apr 2010 19:26:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1427#comment-47832</guid>
		<description>I have the same problem.  vmdsk disk is full i have disabled vdr.</description>
		<content:encoded><![CDATA[<p>I have the same problem.  vmdsk disk is full i have disabled vdr.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/comment-page-1/#comment-47431</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Fri, 05 Feb 2010 13:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1427#comment-47431</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by scott_lowe: As posted by @esloof and others, an issue has been uncovered with VMware Data Recovery. More details here http://tr.im/qafs...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by scott_lowe: As posted by @esloof and others, an issue has been uncovered with VMware Data Recovery. More details here <a href="http://tr.im/qafs.." rel="nofollow">http://tr.im/qafs..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans de Jongh</title>
		<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/comment-page-1/#comment-45106</link>
		<dc:creator>Hans de Jongh</dc:creator>
		<pubDate>Sat, 11 Jul 2009 08:21:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1427#comment-45106</guid>
		<description>I had the same problem, but that was before this post.. The only way i saw a solutions was to clone the disks of 30 VM`s....

ATM i have exactly the same problem.... i`ll try your solution</description>
		<content:encoded><![CDATA[<p>I had the same problem, but that was before this post.. The only way i saw a solutions was to clone the disks of 30 VM`s&#8230;.</p>
<p>ATM i have exactly the same problem&#8230;. i`ll try your solution</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware Info</title>
		<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/comment-page-1/#comment-45088</link>
		<dc:creator>VMware Info</dc:creator>
		<pubDate>Wed, 08 Jul 2009 14:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1427#comment-45088</guid>
		<description>&lt;strong&gt;Quick Tips for Troubleshooting vDR (VMware Data Recovery)...&lt;/strong&gt;

After working a couple of weeks with vDR, John Simon sent me over some of his favorite quick commands for troubleshooting and working with the appliance driven backup product.  Seems as though he ran into the snapshot issue blogged about on Scott?s Bl...</description>
		<content:encoded><![CDATA[<p><strong>Quick Tips for Troubleshooting vDR (VMware Data Recovery)&#8230;</strong></p>
<p>After working a couple of weeks with vDR, John Simon sent me over some of his favorite quick commands for troubleshooting and working with the appliance driven backup product.  Seems as though he ran into the snapshot issue blogged about on Scott?s Bl&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Siebert</title>
		<link>http://blog.scottlowe.org/2009/06/29/snapshot-issue-with-vmware-data-recovery/comment-page-1/#comment-45022</link>
		<dc:creator>Eric Siebert</dc:creator>
		<pubDate>Wed, 01 Jul 2009 17:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1427#comment-45022</guid>
		<description>I&#039;ve been testing VDR and have not seen this, in my testing the snapshot is removed properly and I have verified this using WinSCP. It may be under certain situations or with specific settings that this is happening.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been testing VDR and have not seen this, in my testing the snapshot is removed properly and I have verified this using WinSCP. It may be under certain situations or with specific settings that this is happening.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

