<?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: Surviving 1 node failure in stretched cluster in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/surviving-1-node-failure-in-stretched-cluster/m-p/7048030#M563</link>
    <description>&lt;P&gt;No.Simplivity maintains 2 copies only&amp;nbsp; of the data.&lt;/P&gt;&lt;P&gt;A stretched cluster forces the copies to be maintained in distint failure domians.&lt;/P&gt;&lt;P&gt;IE we can survive a catastorphic failure of Zone A or&amp;nbsp; Zone B&lt;/P&gt;&lt;P&gt;What you are describing if I am correct is a catasrophic failure of a zone combinded with an additional failing node and how to prevent this causing dataloss/unavailability.&lt;/P&gt;&lt;P&gt;There is no way to add a third copy&amp;nbsp; of the data on either Zone.&lt;/P&gt;&lt;P&gt;A remote backup to another site would be the only way to ensure availability.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 28 May 2019 14:11:20 GMT</pubDate>
    <dc:creator>DaveOb</dc:creator>
    <dc:date>2019-05-28T14:11:20Z</dc:date>
    <item>
      <title>Surviving 1 node failure in stretched cluster</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/surviving-1-node-failure-in-stretched-cluster/m-p/7048019#M562</link>
      <description>&lt;P&gt;Hello, is it possible for some VM that are not anymore protected by HA (storage HA lost sync) to be HA compliant once again even with a node failure.&lt;/P&gt;&lt;P&gt;I mean stretched cluster of 4 nodes (1 &amp;amp; 2 in zone A, 3 &amp;amp; 4 in zone B)&lt;/P&gt;&lt;P&gt;&amp;nbsp;Node 3&amp;nbsp;have failed in zone B&lt;/P&gt;&lt;P&gt;VM that were "paired" on the node 3 with one of the node in zone A are ot anymore protected by HA.&lt;/P&gt;&lt;P&gt;If for exemple VM "File" have Primary data on Node&amp;nbsp;1 and Secondary data on node 3. If Node 1 fails also I will face "DU" for the VM "File". Do I have the possibility to "re dispatch" the data on the node 3 for that VM to the node 4 that is still available ? If yes how can I do it ?&lt;/P&gt;&lt;P&gt;Hope to be clear, thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 May 2019 12:18:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/surviving-1-node-failure-in-stretched-cluster/m-p/7048019#M562</guid>
      <dc:creator>J-Philippe</dc:creator>
      <dc:date>2019-05-28T12:18:35Z</dc:date>
    </item>
    <item>
      <title>Re: Surviving 1 node failure in stretched cluster</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/surviving-1-node-failure-in-stretched-cluster/m-p/7048030#M563</link>
      <description>&lt;P&gt;No.Simplivity maintains 2 copies only&amp;nbsp; of the data.&lt;/P&gt;&lt;P&gt;A stretched cluster forces the copies to be maintained in distint failure domians.&lt;/P&gt;&lt;P&gt;IE we can survive a catastorphic failure of Zone A or&amp;nbsp; Zone B&lt;/P&gt;&lt;P&gt;What you are describing if I am correct is a catasrophic failure of a zone combinded with an additional failing node and how to prevent this causing dataloss/unavailability.&lt;/P&gt;&lt;P&gt;There is no way to add a third copy&amp;nbsp; of the data on either Zone.&lt;/P&gt;&lt;P&gt;A remote backup to another site would be the only way to ensure availability.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 May 2019 14:11:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/surviving-1-node-failure-in-stretched-cluster/m-p/7048030#M563</guid>
      <dc:creator>DaveOb</dc:creator>
      <dc:date>2019-05-28T14:11:20Z</dc:date>
    </item>
  </channel>
</rss>

