<?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 2 Arbiters for Simplivity stretched cluster in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/2-arbiters-for-simplivity-stretched-cluster/m-p/7223680#M4946</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We require to deploy a streched cluster (2 nodes per site).&lt;/P&gt;&lt;P&gt;Can we deploy 1x arbiter per site (1x Production, 1x DR site) instead of deploying 1 single arbier on a third site?&lt;/P&gt;&lt;P&gt;Much apprecietd&lt;/P&gt;</description>
    <pubDate>Tue, 03 Sep 2024 12:12:01 GMT</pubDate>
    <dc:creator>Sim123</dc:creator>
    <dc:date>2024-09-03T12:12:01Z</dc:date>
    <item>
      <title>2 Arbiters for Simplivity stretched cluster</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/2-arbiters-for-simplivity-stretched-cluster/m-p/7223680#M4946</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We require to deploy a streched cluster (2 nodes per site).&lt;/P&gt;&lt;P&gt;Can we deploy 1x arbiter per site (1x Production, 1x DR site) instead of deploying 1 single arbier on a third site?&lt;/P&gt;&lt;P&gt;Much apprecietd&lt;/P&gt;</description>
      <pubDate>Tue, 03 Sep 2024 12:12:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/2-arbiters-for-simplivity-stretched-cluster/m-p/7223680#M4946</guid>
      <dc:creator>Sim123</dc:creator>
      <dc:date>2024-09-03T12:12:01Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Arbiters for Simplivity stretched cluster</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/2-arbiters-for-simplivity-stretched-cluster/m-p/7223935#M4950</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2336645"&gt;@Sim123&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;According to the guidelines mentioned in the HPE SimpliVity administration guide, an arbiter should be placed on a third physical site.&lt;BR /&gt;This is because, if both production and DR site experience simultaneous failures, the cluster might become unavailable. To minimize the risk of a single event affecting both the sites, its often recommended to place it in a seperate location.&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Sanika.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;FONT size="2"&gt;If you feel this was helpful, please click the &lt;STRONG&gt;KUDOS&lt;/STRONG&gt; thumb below. Also consider marking this as an "&lt;STRONG&gt;Accepted Solution"&lt;/STRONG&gt;, if the post has helped to solve your issue.&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2024 08:20:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/2-arbiters-for-simplivity-stretched-cluster/m-p/7223935#M4950</guid>
      <dc:creator>Sanika</dc:creator>
      <dc:date>2024-08-28T08:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Arbiters for Simplivity stretched cluster</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/2-arbiters-for-simplivity-stretched-cluster/m-p/7223996#M4955</link>
      <description>&lt;P dir="auto" style="margin: 0;"&gt;Hello &lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2336645"&gt;@Sim123&lt;/a&gt;,&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;In a stretch cluster, the SimpliVity nodes may be in different locations (for example, different buildings), but they are still part of the same cluster and have zones configured. In this case, you can't have 2 arbiters configured since you can only assign one arbiter per cluster.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;If what you want to do is have two separate clusters (Production + DR site) then you could have an arbiter on each cluster arbitrating its opposite cluster. So DR arbitrates Production and vice versa.&amp;nbsp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;Best practice though is to have the SimpliVity arbiter outside the SimpliVity storage as mention on previous reply.&amp;nbsp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;Let me know if you have any questions.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2024 15:37:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/2-arbiters-for-simplivity-stretched-cluster/m-p/7223996#M4955</guid>
      <dc:creator>gustenar</dc:creator>
      <dc:date>2024-08-28T15:37:10Z</dc:date>
    </item>
    <item>
      <title>Query: 2 Arbiters for Simplivity stretched cluster</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/2-arbiters-for-simplivity-stretched-cluster/m-p/7224200#M4960</link>
      <description>&lt;P style="margin: 0;"&gt;Hello,&lt;/P&gt;
&lt;P style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;Let us know if you were able to resolve the issue.&lt;/P&gt;
&lt;P style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.&lt;/P&gt;
&lt;P style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;Please click on "Thumbs Up/Kudo" icon to give a "Kudo".&lt;/P&gt;
&lt;P style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;Thank you for being a HPE valuable community member.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Aug 2024 12:08:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/2-arbiters-for-simplivity-stretched-cluster/m-p/7224200#M4960</guid>
      <dc:creator>support_s</dc:creator>
      <dc:date>2024-08-30T12:08:43Z</dc:date>
    </item>
  </channel>
</rss>

