<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>VMware Data Recovery Archives - ESX Virtualization</title>
	<atom:link href="https://www.vladan.fr/tag/vmware-data-recovery/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vladan.fr/tag/vmware-data-recovery/</link>
	<description>VMware ESXi, vSphere, VMware Backup, Hyper-V... how-to, videos....</description>
	<lastBuildDate>Sat, 26 Apr 2025 16:14:10 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>How-to enable verbose logging in VDR &#8211; VMware Data Recovery</title>
		<link>https://www.vladan.fr/enabling-verbose-logging-in-vdr-vmware-data-recovery/</link>
					<comments>https://www.vladan.fr/enabling-verbose-logging-in-vdr-vmware-data-recovery/#comments</comments>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Fri, 07 Jan 2011 18:05:17 +0000</pubDate>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[VDR verbose logging]]></category>
		<category><![CDATA[VMware Data Recovery]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=8820</guid>

					<description><![CDATA[<p>A quick post about how to enable verbose logging in VDR. Update: VDR has been replaced in vSphere 5.1 by VDP (vSphere Data Protection). The product is based on EMC’s Avamar code and present an interesting upgrade for existing customers which are upgrading from vSphere 4.x where vSphere Data Protection (VDP) was bundled. But to transition [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/enabling-verbose-logging-in-vdr-vmware-data-recovery/">How-to enable verbose logging in VDR &#8211; VMware Data Recovery</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.vladan.fr/enabling-verbose-logging-in-vdr-vmware-data-recovery/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>If you&#8217;re trying to use Windows CIFS with VDR</title>
		<link>https://www.vladan.fr/if-youre-trying-to-use-windows-cifs-with-vdr/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Tue, 28 Dec 2010 07:40:59 +0000</pubDate>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[VDR]]></category>
		<category><![CDATA[Vmware Backup solution]]></category>
		<category><![CDATA[VMware Data Recovery]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=8770</guid>

					<description><![CDATA[<p>Error when trying to use CIFS share as a destination for backup. If you're trying to setup Windows CIFS as a destination deduplication store for your VMware VDR (VMware Data Recovery) appliance, you might run into an error. It's an error which you can see at the console of the VDR appliance: Status code returned [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/if-youre-trying-to-use-windows-cifs-with-vdr/">If you&#8217;re trying to use Windows CIFS with VDR</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>How to fix damaged restore points in VDR</title>
		<link>https://www.vladan.fr/how-to-fix-damaged-restore-points-in-vdr/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Thu, 02 Dec 2010 09:18:17 +0000</pubDate>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[destination datastore locked in VDR]]></category>
		<category><![CDATA[Fixing damaged restore points]]></category>
		<category><![CDATA[VDR destination datastores locked]]></category>
		<category><![CDATA[VMware Data Recovery]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=8486</guid>

					<description><![CDATA[<p>VDR &#8211; VMware Data Recovery, fixing damaged restore poins. VDR is a part of vSphere Essentials PLUS and above versions (except standard) and it's a virtual appliance which helps you to protect your Virtual Machines running under VMware vSphere 4.x by using deduplication and CBT. It's a simple backup solution with no e-mail reporting (yet), [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/how-to-fix-damaged-restore-points-in-vdr/">How to fix damaged restore points in VDR</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Using VMware Data Recovery without vCenter?</title>
		<link>https://www.vladan.fr/using-vmware-data-recovery-without-vcenter/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Sat, 13 Nov 2010 14:20:37 +0000</pubDate>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[Best practices VDR]]></category>
		<category><![CDATA[VDR]]></category>
		<category><![CDATA[VMware Data Recovery]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=8223</guid>

					<description><![CDATA[<p>Using VDR without vCenter, in which situations? I wonder why would someone would want to use VMware Data Recovery (VDR) without vCenter. Yes there might be a case for that. In case you're running vCenter as a Virtual Machine (which is good practice) and this VM is being protected by High Availability (HA). Then if [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/using-vmware-data-recovery-without-vcenter/">Using VMware Data Recovery without vCenter?</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>VDR appliance not mounting automatically the backup destination after reboot</title>
		<link>https://www.vladan.fr/vdr-appliance-not-mounting-automatically-the-backup-destination-after-reboot/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Thu, 28 Oct 2010 10:19:47 +0000</pubDate>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[deduplication store not mounted automatically]]></category>
		<category><![CDATA[not mounting automatically after reboot]]></category>
		<category><![CDATA[VMware Data Recovery]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=8027</guid>

					<description><![CDATA[<p>VDR not mounting automatically a deduplication store. I was having issues with not mounting automatically the backup destination after rebooting the VDR appliance since some time now. This was happening in my environment since I upgraded to the VDR 1.2. This is something that I was aware of and I usually mount the destination deduplication [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/vdr-appliance-not-mounting-automatically-the-backup-destination-after-reboot/">VDR appliance not mounting automatically the backup destination after reboot</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>VDR – how to get a log bundle before you call the support</title>
		<link>https://www.vladan.fr/vdr-how-to-get-a-log-bundle-before-you-call-the-support/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Tue, 26 Oct 2010 06:52:25 +0000</pubDate>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[VDR]]></category>
		<category><![CDATA[Vmware Backup solution]]></category>
		<category><![CDATA[VMware Data Recovery]]></category>
		<category><![CDATA[vSphere Essentials Plus]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=7987</guid>

					<description><![CDATA[<p>VDR &#8211; VMware Data Recovery While listening this year's VMworld Session on VDR &#8211; VMware Data Recovery  &#8211; while on many of the information I already knew and was aware of, because I install and use VDR quite often. There was an information about how to collect the diagnostic logs, in case anything gets wrong. [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/vdr-how-to-get-a-log-bundle-before-you-call-the-support/">VDR – how to get a log bundle before you call the support</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Integrity check with details in VDR 1.2</title>
		<link>https://www.vladan.fr/integrity-check-with-details-in-vdr-1-2/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Thu, 24 Jun 2010 12:08:45 +0000</pubDate>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[Deduplication store for VDR]]></category>
		<category><![CDATA[VDR 1.2]]></category>
		<category><![CDATA[VDR backup appliance]]></category>
		<category><![CDATA[VMware Data Recovery]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=6476</guid>

					<description><![CDATA[<p>Detailed Informations about Integrity scan. This is a quick follow up post after explaining how to initiate a manual integrity check in VMware Data Recovery &#8211; backup solution provided with vSphere Essentials Plus package. In my last article I showed you that sometimes you have to initiate the manual integrity check to correct an error [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/integrity-check-with-details-in-vdr-1-2/">Integrity check with details in VDR 1.2</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>How-to update VDR to 1.2</title>
		<link>https://www.vladan.fr/how-to-update-vdr-to-1-2/</link>
					<comments>https://www.vladan.fr/how-to-update-vdr-to-1-2/#comments</comments>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Mon, 14 Jun 2010 09:46:30 +0000</pubDate>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[VDR]]></category>
		<category><![CDATA[VMware Backup with VDR]]></category>
		<category><![CDATA[VMware Data Recovery]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=6391</guid>

					<description><![CDATA[<p>How to update VDR without loosing all restore points and configuration. With the update of VDR &#8211; VMware Data recovery the question is how to proceed to an update to the latest version without loosing the configuration settings, backup jobs and the deduplication stores. In my lab I tested the step by step solution provided [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/how-to-update-vdr-to-1-2/">How-to update VDR to 1.2</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.vladan.fr/how-to-update-vdr-to-1-2/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Do you want to see a little magic?</title>
		<link>https://www.vladan.fr/do-you-want-to-see-a-little-magic/</link>
					<comments>https://www.vladan.fr/do-you-want-to-see-a-little-magic/#comments</comments>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Fri, 22 Jan 2010 07:33:21 +0000</pubDate>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[Backup vSphere]]></category>
		<category><![CDATA[VDR]]></category>
		<category><![CDATA[VMware Data Recovery]]></category>
		<category><![CDATA[vSphere Essential Plus]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=4766</guid>

					<description><![CDATA[<p>VDR &#8211; VMware Data Recovery &#8211; Verbose Logs where to find that? I was just reading the VDR Admin guide once more. In details and I found some information that I have overlooked the last time I was reading the pdf guide. Usually when you want to see VDR logs you go and connect to [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/do-you-want-to-see-a-little-magic/">Do you want to see a little magic?</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.vladan.fr/do-you-want-to-see-a-little-magic/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>VDR backup fail error</title>
		<link>https://www.vladan.fr/vdr-backup-fail-error/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Tue, 12 Jan 2010 07:53:12 +0000</pubDate>
				<category><![CDATA[Backup]]></category>
		<category><![CDATA[VDR]]></category>
		<category><![CDATA[VDR Error]]></category>
		<category><![CDATA[VDR error -1020]]></category>
		<category><![CDATA[VMware Data Recovery]]></category>
		<category><![CDATA[VMware VDR]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=4511</guid>

					<description><![CDATA[<p>VMware Data Recovery error &#8211; Trouble writing files, error -1020 (Sharing violation) Sometimes you came out in a trouble when your VDR backup does report an error. Trouble writing files, error -1020 (Sharing violation) And when you manually trigger the backup it fails with the following error: The destination is not available for a backup [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/vdr-backup-fail-error/">VDR backup fail error</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
