<?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: HP VSA with hyper-v 2012 in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/hp-vsa-with-hyper-v-2012/m-p/6305799#M7746</link>
    <description>&lt;P&gt;yes and no...&amp;nbsp; you can do a MS cluster with HA on two nodes.&amp;nbsp; That requires node+disk majority.&amp;nbsp; As for VSAs running a HA san on the same two servers, you will run into a problem for true HA w/ quorum.&amp;nbsp; You CAN impliment a virtual FOM which would then require manual intervention to regain quorum if the "wrong" node on the san were to fail.&amp;nbsp; The better solution is to have a 3rd node w/ a FOM to run to maintain quorum and ensure there is no need for human interaction to maintain quorum.&amp;nbsp; The FOM is a very light weight VM, so you can find some cheap POS old server to run in a closet and run the FOM on that, or run it on your desktop computer if its win8 and you always leave it on anyway.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Short answer:&amp;nbsp; for Microsoft, 2 nodes is enought, for VSA, two storage nodes are enought, but you need a 3rd FOM node running as well on cheap hardware to really count as HA.&lt;/P&gt;</description>
    <pubDate>Mon, 16 Dec 2013 05:46:57 GMT</pubDate>
    <dc:creator>oikjn</dc:creator>
    <dc:date>2013-12-16T05:46:57Z</dc:date>
    <item>
      <title>HP VSA with hyper-v 2012</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/hp-vsa-with-hyper-v-2012/m-p/6304743#M7741</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;is it possible to have high-availibility with only 2 hyper-v hosts?&lt;/P&gt;&lt;P&gt;Installing windows server 2012 on two servers and on top (as vm) the VSA and configuring the fail-over cluster in windows.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does it work? Because there is no quorum?!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does automatic VM restart works?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;</description>
      <pubDate>Sat, 14 Dec 2013 17:17:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/hp-vsa-with-hyper-v-2012/m-p/6304743#M7741</guid>
      <dc:creator>loop22</dc:creator>
      <dc:date>2013-12-14T17:17:46Z</dc:date>
    </item>
    <item>
      <title>Re: HP VSA with hyper-v 2012</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/hp-vsa-with-hyper-v-2012/m-p/6305799#M7746</link>
      <description>&lt;P&gt;yes and no...&amp;nbsp; you can do a MS cluster with HA on two nodes.&amp;nbsp; That requires node+disk majority.&amp;nbsp; As for VSAs running a HA san on the same two servers, you will run into a problem for true HA w/ quorum.&amp;nbsp; You CAN impliment a virtual FOM which would then require manual intervention to regain quorum if the "wrong" node on the san were to fail.&amp;nbsp; The better solution is to have a 3rd node w/ a FOM to run to maintain quorum and ensure there is no need for human interaction to maintain quorum.&amp;nbsp; The FOM is a very light weight VM, so you can find some cheap POS old server to run in a closet and run the FOM on that, or run it on your desktop computer if its win8 and you always leave it on anyway.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Short answer:&amp;nbsp; for Microsoft, 2 nodes is enought, for VSA, two storage nodes are enought, but you need a 3rd FOM node running as well on cheap hardware to really count as HA.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2013 05:46:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/hp-vsa-with-hyper-v-2012/m-p/6305799#M7746</guid>
      <dc:creator>oikjn</dc:creator>
      <dc:date>2013-12-16T05:46:57Z</dc:date>
    </item>
  </channel>
</rss>

