<?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: LS Mirror in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128563#M23081</link>
    <description>&lt;P&gt;Good point..I prefer using DP mirrors (there is a KB on doing that instead).. then you don't have to update the mirror after any change for users to see the namespace change.&amp;nbsp; The difference if you recover vsroot (never have had to do that) then you need to break the mirror and make-vsroot the volume instead of the single snapmirror promote command for LS mirrors.&amp;nbsp; If you have a snapmirror license, I prefer this method... also I just heard from support that the new best practice is we only need 2 vsroot mirrors regardless of number of nodes in the cluster, so a 12 node cluster doesn't need 12 mirrors per SVM anymore.&lt;/P&gt;</description>
    <pubDate>Wed, 01 Mar 2017 14:05:46 GMT</pubDate>
    <dc:creator>scottgelb</dc:creator>
    <dc:date>2017-03-01T14:05:46Z</dc:date>
    <item>
      <title>LS Mirror</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128457#M23066</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am planning to configure LS mirrors for root volumes of Vservers. We have a huge environment with SVMs hosting SAN-FC and NAS-NFS&amp;amp;CIFS.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let me know if there will be any impact while configuring LS mirrors on production system. Do we need downtime if yes how much and what would be the Impact.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Its&amp;nbsp;FAS8060 /&amp;nbsp;8.3.2P6 = 4 node cluster&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in Advance &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 15:24:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128457#M23066</guid>
      <dc:creator>ShivaR</dc:creator>
      <dc:date>2025-06-04T15:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: LS Mirror</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128528#M23073</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Setting up LS mirrors does not need downtime. Please refer&amp;nbsp;&lt;A href="https://library.netapp.com/ecm/ecm_get_file/ECMP1653502" target="_blank"&gt;https://library.netapp.com/ecm/ecm_get_file/ECMP1653502&lt;/A&gt; for more information.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2017 04:07:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128528#M23073</guid>
      <dc:creator>Sahana</dc:creator>
      <dc:date>2017-02-28T04:07:51Z</dc:date>
    </item>
    <item>
      <title>Re: LS Mirror</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128534#M23074</link>
      <description>&lt;P&gt;Something to consider is that changed export rules will not propogate until the LS mirror syncs - this means that there could be some delay in using new datastores or new hosts.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But in general - you do want the LS mirrors in place, in case of cluster partition you will still have some data service occuring.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2017 06:33:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128534#M23074</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2017-02-28T06:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: LS Mirror</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128563#M23081</link>
      <description>&lt;P&gt;Good point..I prefer using DP mirrors (there is a KB on doing that instead).. then you don't have to update the mirror after any change for users to see the namespace change.&amp;nbsp; The difference if you recover vsroot (never have had to do that) then you need to break the mirror and make-vsroot the volume instead of the single snapmirror promote command for LS mirrors.&amp;nbsp; If you have a snapmirror license, I prefer this method... also I just heard from support that the new best practice is we only need 2 vsroot mirrors regardless of number of nodes in the cluster, so a 12 node cluster doesn't need 12 mirrors per SVM anymore.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Mar 2017 14:05:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128563#M23081</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2017-03-01T14:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: LS Mirror</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128564#M23082</link>
      <description>&lt;P&gt;here is the kb article to restore vsroot from a DP mirror.&amp;nbsp; &lt;A href="https://library.netapp.com/ecmdocs/ECMP1196906/html/GUID-3A6C32A1-EBE5-4F5C-A3EA-837BF6246A83.html&amp;nbsp;" target="_blank"&gt;https://library.netapp.com/ecmdocs/ECMP1196906/html/GUID-3A6C32A1-EBE5-4F5C-A3EA-837BF6246A83.html&amp;nbsp;&lt;/A&gt; a reference in case you need official support...&lt;/P&gt;</description>
      <pubDate>Wed, 01 Mar 2017 14:08:53 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/LS-Mirror/m-p/128564#M23082</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2017-03-01T14:08:53Z</dc:date>
    </item>
  </channel>
</rss>

