<?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: Destroy an aggregate and add its disks to another aggregate in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Destroy-an-aggregate-and-add-its-disks-to-another-aggregate/m-p/98876#M20081</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the plan should&amp;nbsp;work&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;reallocation is recommended. With 20 disks added though, WAFL&amp;nbsp;should be able to&amp;nbsp;deal with optimizing the layout fairly quickly&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A few things to consider:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;- make sure you have enough space in aggr4 to accommodate&amp;nbsp;the volumes from aggr3&lt;/P&gt;&lt;P&gt;&amp;nbsp;- make sure&amp;nbsp;that the root volume is not in&amp;nbsp;aggr3&lt;/P&gt;&lt;P&gt;&amp;nbsp;-&amp;nbsp;performance-wise, make sure that the destination node can cope with the new workload (CPU, memory,..)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;BTW, have you considered moving (and keeping) aggr3 to the other node using ARL (Aggregate Relocate)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jan 2015 22:55:01 GMT</pubDate>
    <dc:creator>JSHACHER11</dc:creator>
    <dc:date>2015-01-05T22:55:01Z</dc:date>
    <item>
      <title>Destroy an aggregate and add its disks to another aggregate</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Destroy-an-aggregate-and-add-its-disks-to-another-aggregate/m-p/98874#M20080</link>
      <description>&lt;P&gt;My environment is Ontap cluster 8.2.1P1, cDot Mode, FAS3220.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently I have an aggregate called aggr3 with 18 disks and only one raid group for this aggregate.&lt;/P&gt;&lt;P&gt;I have another aggregate called aggr4 and it has two raid group with 22 disks.&lt;/P&gt;&lt;P&gt;All the disk are the same type and model - SAS, 900GB, 10k&lt;/P&gt;&lt;P&gt;However, aggr3 disks are owned by controller 2 and the aggr4 disks are owned by controller 1.&lt;/P&gt;&lt;P&gt;I want to destroy the aggr3 and add 18 disks + 2 spare disks to aggr4 for the third raid group.&lt;/P&gt;&lt;P&gt;The third raid group on aggr4 has only 20 disk.&lt;/P&gt;&lt;P&gt;Therefore,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Raid group 1 on aggr4 - has 22 disks&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Raid group 2 on aggr4 - has 22 disks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Raid group 3 on aggr4 - has 20 disks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Here is my steps and procedure.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1.Move all the VOL from aggr3 to aggr4 and&amp;nbsp;&lt;/SPAN&gt;make sure no VOL and LUN on aggr3.&lt;/P&gt;&lt;P&gt;2.offline the aggr3 and then&amp;nbsp;Destroy aggr3.&lt;/P&gt;&lt;P&gt;3.zeroed disks that were from aggr3.&lt;/P&gt;&lt;P&gt;4.reassign disks to controller1 to prepare for aggr4.&lt;/P&gt;&lt;P&gt;5.After assign the disks, add those 20 disks to aggr4 for third raid group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are those steps and procedure good enough?&lt;/P&gt;&lt;P&gt;Do I need to run the&amp;nbsp;reallocate?&lt;/P&gt;&lt;P&gt;Is there any documentaton for me to follow for what I plan to do?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:20:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Destroy-an-aggregate-and-add-its-disks-to-another-aggregate/m-p/98874#M20080</guid>
      <dc:creator>JohnChen</dc:creator>
      <dc:date>2025-06-05T05:20:27Z</dc:date>
    </item>
    <item>
      <title>Re: Destroy an aggregate and add its disks to another aggregate</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Destroy-an-aggregate-and-add-its-disks-to-another-aggregate/m-p/98876#M20081</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the plan should&amp;nbsp;work&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;reallocation is recommended. With 20 disks added though, WAFL&amp;nbsp;should be able to&amp;nbsp;deal with optimizing the layout fairly quickly&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A few things to consider:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;- make sure you have enough space in aggr4 to accommodate&amp;nbsp;the volumes from aggr3&lt;/P&gt;&lt;P&gt;&amp;nbsp;- make sure&amp;nbsp;that the root volume is not in&amp;nbsp;aggr3&lt;/P&gt;&lt;P&gt;&amp;nbsp;-&amp;nbsp;performance-wise, make sure that the destination node can cope with the new workload (CPU, memory,..)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;BTW, have you considered moving (and keeping) aggr3 to the other node using ARL (Aggregate Relocate)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jan 2015 22:55:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Destroy-an-aggregate-and-add-its-disks-to-another-aggregate/m-p/98876#M20081</guid>
      <dc:creator>JSHACHER11</dc:creator>
      <dc:date>2015-01-05T22:55:01Z</dc:date>
    </item>
  </channel>
</rss>

