<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Storage vMotion in ESX 3.5 with multiple disks in multiple Datastores in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Storage-vMotion-in-ESX-3-5-with-multiple-disks-in-multiple-Datastores/m-p/71053#M6752</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Well, probably to late answer to be any good to you in your project, but I'll share my experience anyway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume you are talking about moving the VMDKs while the VM is running? We noticed the same behaviour when using the Storage vMotion plugin (&lt;A href="http://code.google.com/p/akutz/downloads/list" target="_blank"&gt;http://code.google.com/p/akutz/downloads/list&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, we found a workaround. If you in the plugin first move (drag-and-drop) the whole VM to the new datastore then MOVE BACK (drag-and-drop) the VMDK that should stay where it is and not be moved, it worked for us. Seems to be a bug/feature in the plugin.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;/Ulrik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Nov 2009 23:12:15 GMT</pubDate>
    <dc:creator>ulrik_ivers</dc:creator>
    <dc:date>2009-11-17T23:12:15Z</dc:date>
    <item>
      <title>Storage vMotion in ESX 3.5 with multiple disks in multiple Datastores</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Storage-vMotion-in-ESX-3-5-with-multiple-disks-in-multiple-Datastores/m-p/71048#M6751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a customer with 2 disks (VMDK files) in 2 different Datastores (VMFS,FC SAN).&lt;/P&gt;&lt;P&gt;The second disk is for the page file (to shring the volume, improve DeDupe and minimize Snapshot size)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The problem is we need to run Storage vMotion to migrate some of the workload to a new aggregate, but the Storage vMotion tools / plugins we found all migrate the 2 disks ot the same Datastore.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know / have experience with a tool that will allow me to map each VMDK to a different datastore in the destination ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate any input..&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Eran B&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:22:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Storage-vMotion-in-ESX-3-5-with-multiple-disks-in-multiple-Datastores/m-p/71048#M6751</guid>
      <dc:creator>eranb</dc:creator>
      <dc:date>2025-06-05T07:22:37Z</dc:date>
    </item>
    <item>
      <title>Re: Storage vMotion in ESX 3.5 with multiple disks in multiple Datastores</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Storage-vMotion-in-ESX-3-5-with-multiple-disks-in-multiple-Datastores/m-p/71053#M6752</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Well, probably to late answer to be any good to you in your project, but I'll share my experience anyway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume you are talking about moving the VMDKs while the VM is running? We noticed the same behaviour when using the Storage vMotion plugin (&lt;A href="http://code.google.com/p/akutz/downloads/list" target="_blank"&gt;http://code.google.com/p/akutz/downloads/list&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, we found a workaround. If you in the plugin first move (drag-and-drop) the whole VM to the new datastore then MOVE BACK (drag-and-drop) the VMDK that should stay where it is and not be moved, it worked for us. Seems to be a bug/feature in the plugin.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;/Ulrik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Nov 2009 23:12:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Storage-vMotion-in-ESX-3-5-with-multiple-disks-in-multiple-Datastores/m-p/71053#M6752</guid>
      <dc:creator>ulrik_ivers</dc:creator>
      <dc:date>2009-11-17T23:12:15Z</dc:date>
    </item>
  </channel>
</rss>

