<?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: replica MSA 2060 in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7213894#M17366</link>
    <description>&lt;P dir="auto" style="margin: 0;"&gt;Hi,&amp;nbsp; MSA 2060 FC controllers would have 4 FC host ports per controller and one management ethernet port. For replication to work the controller FC host ports on the 2 MSAs should be able to communicate with each other and transfer data. The management ethernet port wont handle the replication data traffic.&amp;nbsp; &amp;nbsp;From SMU guide(Page 45):&amp;nbsp; &lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=a00128580en_us&amp;amp;docLocale=en_US" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=a00128580en_us&amp;amp;docLocale=en_US&lt;/A&gt; To replicate a volume, you must first create a peer connection or use an existing one, and create a replication set. A peer connection establishes bi-directional communication between a local and remote system, both of which must have FC or iSCSI ports, a virtual pool, and an Advanced Data Services license. The system establishes a peer connection by&lt;BR /&gt;connecting a host port on the local system with a user-specified host port on the remote system, then exchanging information and setting up a long-term communication path in-band. Because the communication path establishes a peer connection between the two systems, replications can occur in either direction.&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 16 Sep 2024 09:20:18 GMT</pubDate>
    <dc:creator>ArunKKR</dc:creator>
    <dc:date>2024-09-16T09:20:18Z</dc:date>
    <item>
      <title>replica MSA 2060</title>
      <link>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7213558#M17361</link>
      <description>&lt;P&gt;I have two MS 2060 FC, I need to replicate volumes between these computers, each computer is in two different geographical locations, I do not have point-to-point FC, it is necessary that they be seen by FC or it can be replicated by IP through the administration positions that are to 1G, which will REQUIRE to be carried out, they will have a document that explains it and a diagram to present to the managers since I have found something clear, Greetings and THANK YOU very much.&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2024 08:21:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7213558#M17361</guid>
      <dc:creator>jdiaz220481</dc:creator>
      <dc:date>2024-05-06T08:21:41Z</dc:date>
    </item>
    <item>
      <title>Re: replica MSA 2060</title>
      <link>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7213894#M17366</link>
      <description>&lt;P dir="auto" style="margin: 0;"&gt;Hi,&amp;nbsp; MSA 2060 FC controllers would have 4 FC host ports per controller and one management ethernet port. For replication to work the controller FC host ports on the 2 MSAs should be able to communicate with each other and transfer data. The management ethernet port wont handle the replication data traffic.&amp;nbsp; &amp;nbsp;From SMU guide(Page 45):&amp;nbsp; &lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=a00128580en_us&amp;amp;docLocale=en_US" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=a00128580en_us&amp;amp;docLocale=en_US&lt;/A&gt; To replicate a volume, you must first create a peer connection or use an existing one, and create a replication set. A peer connection establishes bi-directional communication between a local and remote system, both of which must have FC or iSCSI ports, a virtual pool, and an Advanced Data Services license. The system establishes a peer connection by&lt;BR /&gt;connecting a host port on the local system with a user-specified host port on the remote system, then exchanging information and setting up a long-term communication path in-band. Because the communication path establishes a peer connection between the two systems, replications can occur in either direction.&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Sep 2024 09:20:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7213894#M17366</guid>
      <dc:creator>ArunKKR</dc:creator>
      <dc:date>2024-09-16T09:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: replica MSA 2060</title>
      <link>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7214012#M17367</link>
      <description>&lt;P dir="auto" style="margin: 0;"&gt;Hi , We wanted to follow up and check if the information shared addressed the query. Request you to please respond with a Yes/No. You may also click on "Accept as a solution" button if the issue is resolved. &lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2024 07:17:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7214012#M17367</guid>
      <dc:creator>ArunKKR</dc:creator>
      <dc:date>2024-05-03T07:17:48Z</dc:date>
    </item>
    <item>
      <title>Re: replica MSA 2060</title>
      <link>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7227513#M17815</link>
      <description>&lt;P&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1921163"&gt;@ArunKKR&lt;/a&gt;&amp;nbsp;the funny part is after a new firmware upgrade&amp;nbsp;IN210P001 2024-04-26T21:18:51Z Active OK&lt;BR /&gt;my volume replication schedule is not working, manually I am clicking the start replication button every time which is. very annoying for me.&lt;/P&gt;
&lt;P&gt;looking for solutions and investigating issues.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 14:41:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7227513#M17815</guid>
      <dc:creator>samratcis</dc:creator>
      <dc:date>2024-10-21T14:41:59Z</dc:date>
    </item>
    <item>
      <title>Re: replica MSA 2060</title>
      <link>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7227605#M17818</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2093787"&gt;@samratcis&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;I have shared few steps through a private message.&lt;/P&gt;
&lt;P&gt;Please try those steps.&lt;/P&gt;
&lt;P&gt;I would suggest to log an HPE support case to get the logs reviewed if those steps fails to resolve the issue.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 16:06:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/replica-msa-2060/m-p/7227605#M17818</guid>
      <dc:creator>ArunKKR</dc:creator>
      <dc:date>2024-10-21T16:06:48Z</dc:date>
    </item>
  </channel>
</rss>

