<?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: P2V Snap Drive in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/P2V-Snap-Drive/m-p/139977#M9248</link>
    <description>&lt;P&gt;Ok, in this scenario create a seperate VMDK for the drive to be managed by snapdrive, and then setup snapdrive VMDK support following these instructions -&amp;nbsp;&lt;A href="https://library.netapp.com/ecmdocs/ECMP1217281/html/GUID-39AD1BFF-86EF-4F64-9853-4CE3AA1AED63.html" target="_blank"&gt;https://library.netapp.com/ecmdocs/ECMP1217281/html/GUID-39AD1BFF-86EF-4F64-9853-4CE3AA1AED63.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 02 May 2018 05:06:50 GMT</pubDate>
    <dc:creator>AlexDawson</dc:creator>
    <dc:date>2018-05-02T05:06:50Z</dc:date>
    <item>
      <title>P2V Snap Drive</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/P2V-Snap-Drive/m-p/139756#M9239</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are looking to P2V some of our physical estate into VMware that are currently connected using snapdrive luns.&amp;nbsp;Is this approach&amp;nbsp;supported or do we have to robocopy the data to the virtual server once the P2V of the OS is complete?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:47:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/P2V-Snap-Drive/m-p/139756#M9239</guid>
      <dc:creator>PENGUINONTAP9</dc:creator>
      <dc:date>2025-06-04T13:47:43Z</dc:date>
    </item>
    <item>
      <title>Re: P2V Snap Drive</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/P2V-Snap-Drive/m-p/139852#M9244</link>
      <description>&lt;P&gt;Hi there, is your plan to disconnect the LUN from the physical server and reconnect it to the virtual one? That should work fine and is quite simple for iSCSI.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For FC LUNs, you would need to look into RDM or VMDK snapdrive connectivity, but that is possible.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 06:11:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/P2V-Snap-Drive/m-p/139852#M9244</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2018-04-26T06:11:09Z</dc:date>
    </item>
    <item>
      <title>Re: P2V Snap Drive</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/P2V-Snap-Drive/m-p/139969#M9247</link>
      <description>&lt;P&gt;The plan is to move the data from iscsi luns to vmdk. We are migrating the data from non supported storage&lt;/P&gt;</description>
      <pubDate>Tue, 01 May 2018 10:40:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/P2V-Snap-Drive/m-p/139969#M9247</guid>
      <dc:creator>PENGUINONTAP9</dc:creator>
      <dc:date>2018-05-01T10:40:31Z</dc:date>
    </item>
    <item>
      <title>Re: P2V Snap Drive</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/P2V-Snap-Drive/m-p/139977#M9248</link>
      <description>&lt;P&gt;Ok, in this scenario create a seperate VMDK for the drive to be managed by snapdrive, and then setup snapdrive VMDK support following these instructions -&amp;nbsp;&lt;A href="https://library.netapp.com/ecmdocs/ECMP1217281/html/GUID-39AD1BFF-86EF-4F64-9853-4CE3AA1AED63.html" target="_blank"&gt;https://library.netapp.com/ecmdocs/ECMP1217281/html/GUID-39AD1BFF-86EF-4F64-9853-4CE3AA1AED63.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2018 05:06:50 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/P2V-Snap-Drive/m-p/139977#M9248</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2018-05-02T05:06:50Z</dc:date>
    </item>
  </channel>
</rss>

