<?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 / minimalize downtime in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437715#M9758</link>
    <description>&lt;P&gt;Thank you&lt;/P&gt;</description>
    <pubDate>Fri, 26 Aug 2022 17:15:30 GMT</pubDate>
    <dc:creator>TimJMcCuen</dc:creator>
    <dc:date>2022-08-26T17:15:30Z</dc:date>
    <item>
      <title>snapmirror / minimalize downtime</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437519#M9747</link>
      <description>&lt;P&gt;I am looking to snap mirror volumes form an older 4 node to&amp;nbsp; a new 4 node cluster.&amp;nbsp; I plan to snapmirror volumes from one cluster to the other.&amp;nbsp; &amp;nbsp; I would also like to limit downtime for my NFS hosts.&amp;nbsp; &amp;nbsp; &amp;nbsp;Once the data has been snapmirrored to the new cluster can reassign the data lif IPs from the old cluster to the cluster.&amp;nbsp; The new cluster will be on the same VLAN and subnet as the old cluster.&amp;nbsp; &amp;nbsp; I realize at some point my hosts will probably drop the NFS connection to the NetApp storage as we transistion from old to new.&amp;nbsp; &amp;nbsp; I want to minimalize downtime and not have the hosts remount the storage (data LIF) if possible.&lt;/P&gt;&lt;P&gt;Can this be done?&amp;nbsp; Any tips of tricks please pass my way.&amp;nbsp; &amp;nbsp;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:57:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437519#M9747</guid>
      <dc:creator>TimJMcCuen</dc:creator>
      <dc:date>2025-06-04T09:57:54Z</dc:date>
    </item>
    <item>
      <title>Re: snapmirror / minimalize downtime</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437565#M9748</link>
      <description>&lt;P&gt;Are you able to add the new nodes to the existing cluster and then use vol move?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Decide whether to upgrade by moving volumes or storage&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.netapp.com/us-en/ontap-systems-upgrade/upgrade/upgrade-decide-to-use-this-guide.html" target="_blank" rel="noopener"&gt;https://docs.netapp.com/us-en/ontap-systems-upgrade/upgrade/upgrade-decide-to-use-this-guide.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Aug 2022 05:14:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437565#M9748</guid>
      <dc:creator>NetApp_SR</dc:creator>
      <dc:date>2022-08-23T05:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: snapmirror / minimalize downtime</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437705#M9756</link>
      <description>&lt;P&gt;Thank you for the response.&amp;nbsp; &amp;nbsp;We don't want to add the new nodes to the existing cluster for warranty reasons.&amp;nbsp; &amp;nbsp; We still plan to keep the old cluster cluster around til the warranty expires in a couple years.&amp;nbsp; &amp;nbsp;We would like to move just a couple of volumes form the old cluster to the new with minimal disruption.&amp;nbsp; &amp;nbsp;Is snapmirror the only real way to do that?&amp;nbsp; &amp;nbsp;Can the Data LIFs IPs be transferred to the new cluster ?&amp;nbsp; Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2022 15:22:23 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437705#M9756</guid>
      <dc:creator>TimJMcCuen</dc:creator>
      <dc:date>2022-08-26T15:22:23Z</dc:date>
    </item>
    <item>
      <title>Re: snapmirror / minimalize downtime</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437707#M9757</link>
      <description>&lt;P&gt;Snapmirror is ever reliable and provides data-consistent migration. In this situation, I think there will be some downtime during final cut-off (snapmirror-breaking-making dest vol read/write &lt;STRONG&gt;etc&lt;/STRONG&gt;). However, NFS clients &lt;STRONG&gt;need not remount&lt;/STRONG&gt;, as long as the SAME IP addresses are transferred to the New Cluster independently after the Migration.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2022 16:04:36 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437707#M9757</guid>
      <dc:creator>Ontapforrum</dc:creator>
      <dc:date>2022-08-26T16:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: snapmirror / minimalize downtime</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437715#M9758</link>
      <description>&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2022 17:15:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/snapmirror-minimalize-downtime/m-p/437715#M9758</guid>
      <dc:creator>TimJMcCuen</dc:creator>
      <dc:date>2022-08-26T17:15:30Z</dc:date>
    </item>
  </channel>
</rss>

