<?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: 24-hour downtime with Replication in Array Setup and Networking</title>
    <link>https://community.hpe.com/t5/array-setup-and-networking/24-hour-downtime-with-replication/m-p/7034465#M2311</link>
    <description>&lt;P&gt;Please make sure your snapshot retention is configured more than a day (24 hours) at least , to allow maintaining the "Common snapshot" between arrays.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Simply pause the replication, once the destination array backs online, resume replication as common snapshot is preserved hence only changed block delta transfer and no entire reseed will be required.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;One to add is you can also login to InfoSight to define a maintenance windows to suppress automatic case creation due to the absence of the array...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Feb 2019 17:12:12 GMT</pubDate>
    <dc:creator>Thomas_Lam_HK</dc:creator>
    <dc:date>2019-02-12T17:12:12Z</dc:date>
    <item>
      <title>24-hour downtime with Replication</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/24-hour-downtime-with-replication/m-p/7034330#M2310</link>
      <description>&lt;P&gt;I've got a 24-hour power downtime coming up at one Data Center. Is there anything I should do beforehand to pause/stop replication between the Nimble there and the one at our primary DC? Anything to worry about when the outage is over? I realize that the snapshots will be waiting to send on the one that's still alive, just don't want it to spend the next month trying to play catch-up on replication.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Feb 2019 20:06:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/24-hour-downtime-with-replication/m-p/7034330#M2310</guid>
      <dc:creator>Fstevens</dc:creator>
      <dc:date>2019-02-11T20:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: 24-hour downtime with Replication</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/24-hour-downtime-with-replication/m-p/7034465#M2311</link>
      <description>&lt;P&gt;Please make sure your snapshot retention is configured more than a day (24 hours) at least , to allow maintaining the "Common snapshot" between arrays.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Simply pause the replication, once the destination array backs online, resume replication as common snapshot is preserved hence only changed block delta transfer and no entire reseed will be required.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;One to add is you can also login to InfoSight to define a maintenance windows to suppress automatic case creation due to the absence of the array...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2019 17:12:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/24-hour-downtime-with-replication/m-p/7034465#M2311</guid>
      <dc:creator>Thomas_Lam_HK</dc:creator>
      <dc:date>2019-02-12T17:12:12Z</dc:date>
    </item>
  </channel>
</rss>

