<?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: Change root volume nondisruptively? in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Change-root-volume-nondisruptively/m-p/78016#M5520</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you can. Exactly as you describe - mark new volume as root and issue “cf takeover”.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 20 May 2012 10:41:53 GMT</pubDate>
    <dc:creator>aborzenkov</dc:creator>
    <dc:date>2012-05-20T10:41:53Z</dc:date>
    <item>
      <title>Change root volume nondisruptively?</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Change-root-volume-nondisruptively/m-p/78011#M5519</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Curious if I can change the root volume on both heads of a FAS3140 cluster nondisruptively.&amp;nbsp; I've recently done the root volume change on a brand new pair of 3210s (before they were clustered and before any other data lived on the heads), so I'm familiar with the process, but...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How is this different for a cluster?&amp;nbsp; Can I mark a new volume with 'vol options xxxx root' on one head, then issue 'cf takeover' from the other head and change the root vol on the fly?&amp;nbsp; I guess I'm really just wondering when the process happens - would the new volume become root when the head2 takes over for head1....or does the new root vol become live when 'cf giveback' commences.&amp;nbsp; Or is this even possible to consider in a clustered scenario without downtime.&amp;nbsp; Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:26:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Change-root-volume-nondisruptively/m-p/78011#M5519</guid>
      <dc:creator>gpnetsupport</dc:creator>
      <dc:date>2025-06-05T06:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: Change root volume nondisruptively?</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Change-root-volume-nondisruptively/m-p/78016#M5520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you can. Exactly as you describe - mark new volume as root and issue “cf takeover”.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 May 2012 10:41:53 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Change-root-volume-nondisruptively/m-p/78016#M5520</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2012-05-20T10:41:53Z</dc:date>
    </item>
    <item>
      <title>Re: Change root volume nondisruptively?</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Change-root-volume-nondisruptively/m-p/78024#M5521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks very much - marked as answer.&amp;nbsp; I've got a few weeks to go before I can attempt.&amp;nbsp; I love netapp technology, but it seems like I'm always throwing data around to regain/reprovision space.&amp;nbsp; Never enough shelves &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.netapp.com/5.0.1/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;.&amp;nbsp; Looking forward to a jump from 7.3.2 to 8.0.3 in the next couple weeks!&amp;nbsp; Thanks again for a quick response.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 May 2012 10:47:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Change-root-volume-nondisruptively/m-p/78024#M5521</guid>
      <dc:creator>gpnetsupport</dc:creator>
      <dc:date>2012-05-20T10:47:04Z</dc:date>
    </item>
  </channel>
</rss>

