<?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 VSC 6 VM Optimization - Online Migration failed in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-6-VM-Optimization-Online-Migration-failed/m-p/104832#M8184</link>
    <description>&lt;P&gt;noHi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i experience some issues with the new NetApp VSC 6 and VM Optimation &amp;amp; Migration.&lt;/P&gt;&lt;P&gt;my Environment:&lt;/P&gt;&lt;P&gt;- server 2012 R2 / vcenter 6 / vmfs 5&lt;/P&gt;&lt;P&gt;- netapp vsc 6&lt;/P&gt;&lt;P&gt;- all vm data stores created by vsc 5&lt;/P&gt;&lt;P&gt;starting&amp;nbsp;lun scan its working fine. vsc 6 shows me all misaligned vms&lt;/P&gt;&lt;P&gt;now select a misaligned VM and try to migrate to existing data store - result : there are no suitable datastore available´. . .&amp;nbsp; i cant believed&lt;/P&gt;&lt;P&gt;trying to run migration by using "new datastore" . vsc 6 creates a new datastore and migrate the vm to the new datastore.&lt;/P&gt;&lt;P&gt;run a re-scan to all datastores to be sure vsc 6 has recognized the new datastore.&lt;/P&gt;&lt;P&gt;now trying to migrate the next vm and get the same error when&amp;nbsp;choose to existing datastore, but normally vsc 6 should display the self (previous) created datastore.&lt;/P&gt;&lt;P&gt;same Issue seems to be for offline Migration . . . no suitable datastore available.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;has anyone tried to work with the vsc 6 VM Optimation Tool ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks for any feedback !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Mario&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 04:20:26 GMT</pubDate>
    <dc:creator>haven2008</dc:creator>
    <dc:date>2025-06-05T04:20:26Z</dc:date>
    <item>
      <title>VSC 6 VM Optimization - Online Migration failed</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-6-VM-Optimization-Online-Migration-failed/m-p/104832#M8184</link>
      <description>&lt;P&gt;noHi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i experience some issues with the new NetApp VSC 6 and VM Optimation &amp;amp; Migration.&lt;/P&gt;&lt;P&gt;my Environment:&lt;/P&gt;&lt;P&gt;- server 2012 R2 / vcenter 6 / vmfs 5&lt;/P&gt;&lt;P&gt;- netapp vsc 6&lt;/P&gt;&lt;P&gt;- all vm data stores created by vsc 5&lt;/P&gt;&lt;P&gt;starting&amp;nbsp;lun scan its working fine. vsc 6 shows me all misaligned vms&lt;/P&gt;&lt;P&gt;now select a misaligned VM and try to migrate to existing data store - result : there are no suitable datastore available´. . .&amp;nbsp; i cant believed&lt;/P&gt;&lt;P&gt;trying to run migration by using "new datastore" . vsc 6 creates a new datastore and migrate the vm to the new datastore.&lt;/P&gt;&lt;P&gt;run a re-scan to all datastores to be sure vsc 6 has recognized the new datastore.&lt;/P&gt;&lt;P&gt;now trying to migrate the next vm and get the same error when&amp;nbsp;choose to existing datastore, but normally vsc 6 should display the self (previous) created datastore.&lt;/P&gt;&lt;P&gt;same Issue seems to be for offline Migration . . . no suitable datastore available.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;has anyone tried to work with the vsc 6 VM Optimation Tool ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks for any feedback !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Mario&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 04:20:26 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-6-VM-Optimization-Online-Migration-failed/m-p/104832#M8184</guid>
      <dc:creator>haven2008</dc:creator>
      <dc:date>2025-06-05T04:20:26Z</dc:date>
    </item>
  </channel>
</rss>

