<?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 Replicating a replica volume in HPE Nimble Storage Solution Specialists</title>
    <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/replicating-a-replica-volume/m-p/7009272#M52</link>
    <description>&lt;P&gt;So here is the scenario.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have four arrays, we have replications going on between the different&amp;nbsp;DCs. We just&amp;nbsp;set up our&amp;nbsp;fourth array which&amp;nbsp;we will be moving to a DC in Oklahoma City. This array will be used to house our replication form the other three arrays.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to see if I can seed the fourth array without breaking replication from&amp;nbsp;the other arrays.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way I can replicate the replica volume to the fourth array without&amp;nbsp;putting the volume collection&amp;nbsp;online or removing the replica volume from the downstream volume collection?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Right now we are like this&lt;/P&gt;&lt;P&gt;DCA --&amp;gt; DCB replication. Pretty basic.&lt;/P&gt;&lt;P&gt;I want to try DCA --&amp;gt; DCB --&amp;gt; DCB --&amp;gt; DCC&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 19 Jun 2018 13:22:39 GMT</pubDate>
    <dc:creator>dillonkkelly</dc:creator>
    <dc:date>2018-06-19T13:22:39Z</dc:date>
    <item>
      <title>Replicating a replica volume</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/replicating-a-replica-volume/m-p/7009272#M52</link>
      <description>&lt;P&gt;So here is the scenario.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have four arrays, we have replications going on between the different&amp;nbsp;DCs. We just&amp;nbsp;set up our&amp;nbsp;fourth array which&amp;nbsp;we will be moving to a DC in Oklahoma City. This array will be used to house our replication form the other three arrays.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to see if I can seed the fourth array without breaking replication from&amp;nbsp;the other arrays.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way I can replicate the replica volume to the fourth array without&amp;nbsp;putting the volume collection&amp;nbsp;online or removing the replica volume from the downstream volume collection?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Right now we are like this&lt;/P&gt;&lt;P&gt;DCA --&amp;gt; DCB replication. Pretty basic.&lt;/P&gt;&lt;P&gt;I want to try DCA --&amp;gt; DCB --&amp;gt; DCB --&amp;gt; DCC&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2018 13:22:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/replicating-a-replica-volume/m-p/7009272#M52</guid>
      <dc:creator>dillonkkelly</dc:creator>
      <dc:date>2018-06-19T13:22:39Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating a replica volume</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/replicating-a-replica-volume/m-p/7012687#M69</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;Unfortunately, Nimble doesn't support cascading replication today (ie a volume A-&amp;gt;B-&amp;gt;C).&lt;/P&gt;&lt;P&gt;The only thing you could do would be to clone a replicated snapshot on B, and then set it to replicate to C - however that will be a 100% re-sync of the data across the replication link.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Jul 2018 09:27:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/replicating-a-replica-volume/m-p/7012687#M69</guid>
      <dc:creator>Nick_Dyer</dc:creator>
      <dc:date>2018-07-23T09:27:40Z</dc:date>
    </item>
  </channel>
</rss>

