<?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: Hyper-V over SMB implementations in Microsoft Virtualization Discussions</title>
    <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Hyper-V-over-SMB-implementations/m-p/443703#M6732</link>
    <description>&lt;P&gt;&lt;SPAN&gt;VMCX files (smilar to VMC files) are used by Windows Explorer to provide information about the VM in the Explorer window.&amp;nbsp; I don't see why it would need protecting, it sits in the \virtual machines directory under each user, so not user file that would have a session open to it.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Apr 2023 13:50:55 GMT</pubDate>
    <dc:creator>johneasty</dc:creator>
    <dc:date>2023-04-25T13:50:55Z</dc:date>
    <item>
      <title>Hyper-V over SMB implementations</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Hyper-V-over-SMB-implementations/m-p/443696#M6729</link>
      <description>&lt;P&gt;Hi Everyone We have hyper-v workload hosted on NetApp CIFS.&lt;/P&gt;&lt;P&gt;The datastore share was configured with continuous availability.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We analyzed the open files from NetApp cli and found that only vhdx files are protected with continuous availability.&lt;/P&gt;&lt;P&gt;There are some files which are showing as not protected with VMCX and VMRS extensions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this the correct state?　Shouldn't all files be CA protected?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:49:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Hyper-V-over-SMB-implementations/m-p/443696#M6729</guid>
      <dc:creator>NetApP_3260</dc:creator>
      <dc:date>2025-06-04T09:49:54Z</dc:date>
    </item>
    <item>
      <title>Re: Hyper-V over SMB implementations</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Hyper-V-over-SMB-implementations/m-p/443698#M6731</link>
      <description>&lt;P&gt;I've also noticed that, and it appears to be the correct behavior. In essence, the Windows SMB client has not requested persistent file handles on those files.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It makes sense, those are the only files that need to sustain IO across a storage failover event.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 13:19:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Hyper-V-over-SMB-implementations/m-p/443698#M6731</guid>
      <dc:creator>ChanceBingen</dc:creator>
      <dc:date>2023-04-25T13:19:46Z</dc:date>
    </item>
    <item>
      <title>Re: Hyper-V over SMB implementations</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Hyper-V-over-SMB-implementations/m-p/443703#M6732</link>
      <description>&lt;P&gt;&lt;SPAN&gt;VMCX files (smilar to VMC files) are used by Windows Explorer to provide information about the VM in the Explorer window.&amp;nbsp; I don't see why it would need protecting, it sits in the \virtual machines directory under each user, so not user file that would have a session open to it.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 13:50:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Hyper-V-over-SMB-implementations/m-p/443703#M6732</guid>
      <dc:creator>johneasty</dc:creator>
      <dc:date>2023-04-25T13:50:55Z</dc:date>
    </item>
  </channel>
</rss>

