<?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: Problem with Windows Server 2016 Failover Cluster Hyper-V and Cluster Shared volume in Operating System - Microsoft</title>
    <link>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/7025366#M13154</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;We faced similar issue, have you solved this problem?&lt;/P&gt;</description>
    <pubDate>Thu, 15 Nov 2018 11:13:07 GMT</pubDate>
    <dc:creator>dronez</dc:creator>
    <dc:date>2018-11-15T11:13:07Z</dc:date>
    <item>
      <title>Problem with Windows Server 2016 Failover Cluster Hyper-V and Cluster Shared volume</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/6991035#M12995</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I'm having problems with a Failover Cluster Hyper-V in Windows Server 2016, loosing connectivity to specific LUN's that are exported to the Cluster I mean one of my cluster shared volume .&lt;/P&gt;&lt;P&gt;So, i have a multiple BL660c Gen8 servers running on the same cluster, and everytime one of the node lost connectivity to the CSV (LUN).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="111.PNG" style="width: 851px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/100328iC69B89B4B073CEF7/image-size/large?v=v2&amp;amp;px=2000" role="button" title="111.PNG" alt="111.PNG" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="112.PNG" style="width: 848px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/100329iB97752715E02C5C6/image-size/large?v=v2&amp;amp;px=2000" role="button" title="112.PNG" alt="112.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone had this kind of issues and can help me?&lt;/P&gt;&lt;P&gt;&amp;nbsp;Best Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 11 Dec 2017 08:27:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/6991035#M12995</guid>
      <dc:creator>amelloul</dc:creator>
      <dc:date>2017-12-11T08:27:11Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with Windows Server 2016 Failover Cluster Hyper-V and Cluster Shared volume</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/6994694#M13009</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Please&amp;nbsp; double check you Blade`s&amp;nbsp; OS&amp;nbsp; Multy-path settings - MPIO&amp;nbsp; role tool&amp;nbsp; ?&lt;/P&gt;&lt;P&gt;Also check&amp;nbsp; at HW&amp;nbsp; level any&amp;nbsp; amber or red light.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind regards Nik&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jan 2018 10:49:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/6994694#M13009</guid>
      <dc:creator>Nikolay Savov</dc:creator>
      <dc:date>2018-01-24T10:49:00Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with Windows Server 2016 Failover Cluster Hyper-V and Cluster Shared volume</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/6994777#M13010</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;thank you for the reply.&lt;/P&gt;&lt;P&gt;In fact the configuration in MPIO tool is good, because we have cheked with Microsoft Support, but the problem is still running.&lt;/P&gt;&lt;P&gt;we also observed that this issue occur when we start the backup operations&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2018 07:53:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/6994777#M13010</guid>
      <dc:creator>amelloul</dc:creator>
      <dc:date>2018-01-25T07:53:40Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with Windows Server 2016 Failover Cluster Hyper-V and Cluster Shared volume</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/6994850#M13011</link>
      <description>What backup software you are using?&lt;BR /&gt;Is there only one backup software?&lt;BR /&gt;Check you San SW status&lt;BR /&gt;Is it fail on all Blades hosting the CSV store in the cluster?&lt;BR /&gt;&lt;BR /&gt;That should not be happening at all 😎</description>
      <pubDate>Thu, 25 Jan 2018 19:51:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/6994850#M13011</guid>
      <dc:creator>Nikolay Savov</dc:creator>
      <dc:date>2018-01-25T19:51:09Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with Windows Server 2016 Failover Cluster Hyper-V and Cluster Shared volume</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/7025366#M13154</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;We faced similar issue, have you solved this problem?&lt;/P&gt;</description>
      <pubDate>Thu, 15 Nov 2018 11:13:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/problem-with-windows-server-2016-failover-cluster-hyper-v-and/m-p/7025366#M13154</guid>
      <dc:creator>dronez</dc:creator>
      <dc:date>2018-11-15T11:13:07Z</dc:date>
    </item>
  </channel>
</rss>

