<?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 Promote new volume for SVM root. Non-disruptive? in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Promote-new-volume-for-SVM-root-Non-disruptive/m-p/140641#M31095</link>
    <description>&lt;P&gt;I'm in the process of replacing an existing 4-node cluster with 4 new nodes and disks. The SVM root volume load-sharing, for some reason, shows the actual mounted volume for root as one of the destination volumes, not the source. So I have root, root_m2, root_m3, root_m4. root is the source/primary, but looking at the namespace, root_m4 is the volume actually mounted. Rather than mess with all that, I figured I could just create a brand new root_vol and promote it, then re-setup the load-sharing mirrors after the old hardware is pulled out of the cluster. So my question is, is the promotion of a new SVM root volume disruptive at all? Can I do this any time or should I do it after hours or schedule true downtime?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Running 9.1P11 with a FAS6250, FAS3220 and FAS9000 with an AFF-300A waiting to join once I remove the 6250 and 3220. Thanks in advance!&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 13:39:51 GMT</pubDate>
    <dc:creator>iancase</dc:creator>
    <dc:date>2025-06-04T13:39:51Z</dc:date>
    <item>
      <title>Promote new volume for SVM root. Non-disruptive?</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Promote-new-volume-for-SVM-root-Non-disruptive/m-p/140641#M31095</link>
      <description>&lt;P&gt;I'm in the process of replacing an existing 4-node cluster with 4 new nodes and disks. The SVM root volume load-sharing, for some reason, shows the actual mounted volume for root as one of the destination volumes, not the source. So I have root, root_m2, root_m3, root_m4. root is the source/primary, but looking at the namespace, root_m4 is the volume actually mounted. Rather than mess with all that, I figured I could just create a brand new root_vol and promote it, then re-setup the load-sharing mirrors after the old hardware is pulled out of the cluster. So my question is, is the promotion of a new SVM root volume disruptive at all? Can I do this any time or should I do it after hours or schedule true downtime?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Running 9.1P11 with a FAS6250, FAS3220 and FAS9000 with an AFF-300A waiting to join once I remove the 6250 and 3220. Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:39:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Promote-new-volume-for-SVM-root-Non-disruptive/m-p/140641#M31095</guid>
      <dc:creator>iancase</dc:creator>
      <dc:date>2025-06-04T13:39:51Z</dc:date>
    </item>
  </channel>
</rss>

