<?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 quiesce * in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/snapmirror-quiesce/m-p/130265#M28365</link>
    <description>&lt;P&gt;The safest approach is to just follow the procedure outlined in your upgrade advisor report:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(a) Determine the destination path for each SnapMirror relationship using the command:&lt;BR /&gt;snapmirror show&lt;BR /&gt;(b) For each destination volume, enter the following command to allow existing SnapMirror transfers to finish.&lt;BR /&gt;snapmirror quiesce -destination-path destination&lt;BR /&gt;If there are no active transfers for the SnapMirror relationship, this command sets its status to Quiesced . If the relationship has active transfers, the status is set to Quiescing until thetransfer is completed, and then the status becomes Quiesced&lt;BR /&gt;(c) Verify that all SnapMirror relationships are quiesced:&lt;BR /&gt;snapmirror show -status !Quiesced&lt;BR /&gt;This command displays any SnapMirror relationships that are not quiesced.&lt;BR /&gt;(d) If any SnapMirror relationships are currently transferring, do one of the following options:&lt;BR /&gt;(i) Wait for the transfers to complete before performing the Data ONTAP upgrade.&lt;BR /&gt;(ii) Stop the transfers by entering the following command:&lt;BR /&gt;snapmirror abort -destination-path destination -h&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have dedupes running, I'd issue a:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;volume efficiency show -vserver * -op-status Active&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And then just issue a stop command on any active processes. &amp;nbsp;Deduplication is opportunistic and will chew through CPU and such which isn't necessarily a good thing during an NDU.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(BTW - the previous comment about going to 9.1P2 is spot on - lots of good stuff in 9+)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 19 Apr 2017 12:53:37 GMT</pubDate>
    <dc:creator>colsen</dc:creator>
    <dc:date>2017-04-19T12:53:37Z</dc:date>
    <item>
      <title>snapmirror quiesce *</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/snapmirror-quiesce/m-p/130235#M28358</link>
      <description>&lt;P&gt;hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am preparing for an upgrade of CDOT from 8.3.2 to 8.3.2P9. I want to quiesce all SM relationships. Is it simply by running&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;snapmirror quiesce *&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and then&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;snapmirror resume *&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What did you guys do in this scenario?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't understand why NetApp did not make this easier in CDOT, compared to 7-mode&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How about deduplication what is your experience?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 15:11:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/snapmirror-quiesce/m-p/130235#M28358</guid>
      <dc:creator>duanebachi1</dc:creator>
      <dc:date>2025-06-04T15:11:11Z</dc:date>
    </item>
    <item>
      <title>Re: snapmirror quiesce *</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/snapmirror-quiesce/m-p/130261#M28364</link>
      <description>&lt;P&gt;Before considering going to 8.3.2P1, I would highly suggest reviewing 9.1p1. &amp;nbsp;Lots of more features.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2017 12:26:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/snapmirror-quiesce/m-p/130261#M28364</guid>
      <dc:creator>JGPSHNTAP</dc:creator>
      <dc:date>2017-04-19T12:26:22Z</dc:date>
    </item>
    <item>
      <title>Re: snapmirror quiesce *</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/snapmirror-quiesce/m-p/130265#M28365</link>
      <description>&lt;P&gt;The safest approach is to just follow the procedure outlined in your upgrade advisor report:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(a) Determine the destination path for each SnapMirror relationship using the command:&lt;BR /&gt;snapmirror show&lt;BR /&gt;(b) For each destination volume, enter the following command to allow existing SnapMirror transfers to finish.&lt;BR /&gt;snapmirror quiesce -destination-path destination&lt;BR /&gt;If there are no active transfers for the SnapMirror relationship, this command sets its status to Quiesced . If the relationship has active transfers, the status is set to Quiescing until thetransfer is completed, and then the status becomes Quiesced&lt;BR /&gt;(c) Verify that all SnapMirror relationships are quiesced:&lt;BR /&gt;snapmirror show -status !Quiesced&lt;BR /&gt;This command displays any SnapMirror relationships that are not quiesced.&lt;BR /&gt;(d) If any SnapMirror relationships are currently transferring, do one of the following options:&lt;BR /&gt;(i) Wait for the transfers to complete before performing the Data ONTAP upgrade.&lt;BR /&gt;(ii) Stop the transfers by entering the following command:&lt;BR /&gt;snapmirror abort -destination-path destination -h&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have dedupes running, I'd issue a:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;volume efficiency show -vserver * -op-status Active&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And then just issue a stop command on any active processes. &amp;nbsp;Deduplication is opportunistic and will chew through CPU and such which isn't necessarily a good thing during an NDU.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(BTW - the previous comment about going to 9.1P2 is spot on - lots of good stuff in 9+)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2017 12:53:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/snapmirror-quiesce/m-p/130265#M28365</guid>
      <dc:creator>colsen</dc:creator>
      <dc:date>2017-04-19T12:53:37Z</dc:date>
    </item>
  </channel>
</rss>

