<?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 Replication – An Overview in Array Performance and Data Protection</title>
    <link>https://community.hpe.com/t5/array-performance-and-data/replication-an-overview/m-p/6986846#M1098</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial;"&gt;For added protection and disaster recovery data stored on a Nimble Storage array (source) can be efficiently replicated to another CS-Series array (target). Similar in concept to Nimble Storage snapshots, after the initial seeding only the changed data is replicated &lt;SPAN style="font-family: Arial;"&gt;compressed&lt;/SPAN&gt; to the other array. &lt;/SPAN&gt;&lt;SPAN style="font-family: Arial;"&gt;That second array can be different configuration from the one used in production. This makes disaster recovery affordable. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;To recover, the snapshots on the target system can be cloned and made active. They can either be used on the secondary system (target) or be replicated back to the primary system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a link to a KB article on replication seeding: &lt;A _jive_internal="true" href="https://community.hpe.com/docs/DOC-1046"&gt;https://community.nimblestorage.com/docs/DOC-1046&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Jan 2013 04:30:45 GMT</pubDate>
    <dc:creator>nimble-admin47</dc:creator>
    <dc:date>2013-01-30T04:30:45Z</dc:date>
    <item>
      <title>Replication – An Overview</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/replication-an-overview/m-p/6986846#M1098</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial;"&gt;For added protection and disaster recovery data stored on a Nimble Storage array (source) can be efficiently replicated to another CS-Series array (target). Similar in concept to Nimble Storage snapshots, after the initial seeding only the changed data is replicated &lt;SPAN style="font-family: Arial;"&gt;compressed&lt;/SPAN&gt; to the other array. &lt;/SPAN&gt;&lt;SPAN style="font-family: Arial;"&gt;That second array can be different configuration from the one used in production. This makes disaster recovery affordable. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;To recover, the snapshots on the target system can be cloned and made active. They can either be used on the secondary system (target) or be replicated back to the primary system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a link to a KB article on replication seeding: &lt;A _jive_internal="true" href="https://community.hpe.com/docs/DOC-1046"&gt;https://community.nimblestorage.com/docs/DOC-1046&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2013 04:30:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/replication-an-overview/m-p/6986846#M1098</guid>
      <dc:creator>nimble-admin47</dc:creator>
      <dc:date>2013-01-30T04:30:45Z</dc:date>
    </item>
  </channel>
</rss>

