<?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: Seeding replication in Array Setup and Networking</title>
    <link>https://community.hpe.com/t5/array-setup-and-networking/seeding-replication/m-p/7004629#M2199</link>
    <description>&lt;P&gt;sounds intresting, I will need to do that as well in the near future, I wonder if you can seed with a younger smaller snapshot then that would incrementally build, while applying a QoS policy that limit bandwidth consumption.&lt;/P&gt;</description>
    <pubDate>Thu, 03 May 2018 23:16:35 GMT</pubDate>
    <dc:creator>twisted_tech</dc:creator>
    <dc:date>2018-05-03T23:16:35Z</dc:date>
    <item>
      <title>Seeding replication</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/seeding-replication/m-p/7004587#M2198</link>
      <description>&lt;P&gt;I have a volume at one site that is 3TB. Rather than replicate the volume and max the WAN link I plan to take a copy of the data and ship it to our 2nd site and want to use the data copy as a seed for the replication.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However I can't see a way of&amp;nbsp;setting the seeded volume as the destination for replication.&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 14:27:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/seeding-replication/m-p/7004587#M2198</guid>
      <dc:creator>TobyJ</dc:creator>
      <dc:date>2018-05-03T14:27:02Z</dc:date>
    </item>
    <item>
      <title>Re: Seeding replication</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/seeding-replication/m-p/7004629#M2199</link>
      <description>&lt;P&gt;sounds intresting, I will need to do that as well in the near future, I wonder if you can seed with a younger smaller snapshot then that would incrementally build, while applying a QoS policy that limit bandwidth consumption.&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 23:16:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/seeding-replication/m-p/7004629#M2199</guid>
      <dc:creator>twisted_tech</dc:creator>
      <dc:date>2018-05-03T23:16:35Z</dc:date>
    </item>
    <item>
      <title>Re: Seeding replication</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/seeding-replication/m-p/7005113#M2200</link>
      <description>&lt;P&gt;I found the doc below which helpfuly says contact support so I've logged a ticket&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://infosight.hpe.com/InfoSight/media/cms/active/pubs_GUI_Administration_Guide_NOS_4x.whz/zev1501525218651.html" target="_blank"&gt;https://infosight.hpe.com/InfoSight/media/cms/active/pubs_GUI_Administration_Guide_NOS_4x.whz/zev1501525218651.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 May 2018 10:04:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/seeding-replication/m-p/7005113#M2200</guid>
      <dc:creator>TobyJ</dc:creator>
      <dc:date>2018-05-08T10:04:19Z</dc:date>
    </item>
  </channel>
</rss>

