<?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: Snapmirror to multiple peers in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Snapmirror-to-multiple-peers/m-p/94695#M19490</link>
    <description>There is limit on number of concurrent replication streams, you may have hit it.</description>
    <pubDate>Tue, 28 Oct 2014 04:22:24 GMT</pubDate>
    <dc:creator>aborzenkov</dc:creator>
    <dc:date>2014-10-28T04:22:24Z</dc:date>
    <item>
      <title>Snapmirror to multiple peers</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Snapmirror-to-multiple-peers/m-p/94615#M19485</link>
      <description>I have started initializing some volumes to a new cluster peer at a different branch office and noticed since doing so the existing snapmirror peer relationship is failing. The schedule is currently set for the same time of day (4am). Are the processes from one peer locking the other out?</description>
      <pubDate>Thu, 05 Jun 2025 05:26:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Snapmirror-to-multiple-peers/m-p/94615#M19485</guid>
      <dc:creator>AtlJeepGuy</dc:creator>
      <dc:date>2025-06-05T05:26:22Z</dc:date>
    </item>
    <item>
      <title>Re: Snapmirror to multiple peers</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Snapmirror-to-multiple-peers/m-p/94695#M19490</link>
      <description>There is limit on number of concurrent replication streams, you may have hit it.</description>
      <pubDate>Tue, 28 Oct 2014 04:22:24 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Snapmirror-to-multiple-peers/m-p/94695#M19490</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2014-10-28T04:22:24Z</dc:date>
    </item>
  </channel>
</rss>

