topic ONTAP Select 9.x best practice for aggregate creation in ONTAP Discussions https://community.netapp.com/t5/ONTAP-Discussions/ONTAP-Select-9-x-best-practice-for-aggregate-creation/m-p/128280#M27797 <P>From ONTAP Select document and TR-4517, I have following understanding:</P><P>&nbsp;</P><OL><LI>General guidance of&nbsp;single–RAID group/single-LUN from underlying server DAS<UL><LI>LUN size limit by hypervisor extent limitation (64TB)</LI><LI>Create multiple equal-sized LUNs if limit reached, then provision the vSphere datastore using all attached LUNs</LI><LI>ONTAP Select receives no performance benefits by increasing the number of LUNs within the RAID group. Adding additional LUNs should only be done to bypass hypervisor file system limitations.</LI></UL></LI><LI>After ONTAP select VM is deployed&nbsp;and root disks provisioned, the underlying attached storage is breaks up the into <STRONG>even number set of&nbsp;equal-sized virtual disks</STRONG>, each <STRONG>not exceeding 8TB</STRONG><UL><LI>Similar to creating multiple LUNs, ONTAP Select receives no performance benefits by increasing the number of virtual disks used by the system.</LI></UL></LI><LI>When the second RAID group is added (server DAS), a second LUN must be provisioned and should be added as a new extent to the existing datastore.<UL><LI>NetApp recommends that newly attached storage be added to the existing datastore as a new extent, rather than configured as a second datastore on the system.</LI><LI>the newly assigned storage should be split into an <STRONG>even number set </STRONG>of <STRONG>equal-sized</STRONG> virtual disks, <STRONG>not exceeding </STRONG><STRONG>8TB</STRONG></LI><LI><STRONG>Currently, the ONTAP Deploy tool does not support the workflow of adding space to a Select node, so this process must be done using the native vSphere tooling. </STRONG></LI></UL></LI><LI>For four node ONTAP select cluster, all aggregate is RAID 0 and must be mirrored.<UL><LI>maximum aggregate size is 100TiB</LI><LI>maximun volume size is 60TiB</LI></UL></LI></OL><P><STRONG>My question are:</STRONG></P><OL><LI>Can I create aggreate with more than 2 disks (X = even mumber)?&nbsp;<UL><LI>this means&nbsp;X/2 number of raidgroup in each plex? (one raidgroup per disk)</LI><LI>Will there be any performance penalty?</LI></UL></LI><LI>If I increased the underlying datastore size and created more virtual disk, can I add the disks to the existing aggregate?<UL><LI>what are the consideration?&nbsp;</LI></UL></LI></OL><P>&nbsp;</P> Wed, 04 Jun 2025 15:25:52 GMT jiayih 2025-06-04T15:25:52Z ONTAP Select 9.x best practice for aggregate creation https://community.netapp.com/t5/ONTAP-Discussions/ONTAP-Select-9-x-best-practice-for-aggregate-creation/m-p/128280#M27797 <P>From ONTAP Select document and TR-4517, I have following understanding:</P><P>&nbsp;</P><OL><LI>General guidance of&nbsp;single–RAID group/single-LUN from underlying server DAS<UL><LI>LUN size limit by hypervisor extent limitation (64TB)</LI><LI>Create multiple equal-sized LUNs if limit reached, then provision the vSphere datastore using all attached LUNs</LI><LI>ONTAP Select receives no performance benefits by increasing the number of LUNs within the RAID group. Adding additional LUNs should only be done to bypass hypervisor file system limitations.</LI></UL></LI><LI>After ONTAP select VM is deployed&nbsp;and root disks provisioned, the underlying attached storage is breaks up the into <STRONG>even number set of&nbsp;equal-sized virtual disks</STRONG>, each <STRONG>not exceeding 8TB</STRONG><UL><LI>Similar to creating multiple LUNs, ONTAP Select receives no performance benefits by increasing the number of virtual disks used by the system.</LI></UL></LI><LI>When the second RAID group is added (server DAS), a second LUN must be provisioned and should be added as a new extent to the existing datastore.<UL><LI>NetApp recommends that newly attached storage be added to the existing datastore as a new extent, rather than configured as a second datastore on the system.</LI><LI>the newly assigned storage should be split into an <STRONG>even number set </STRONG>of <STRONG>equal-sized</STRONG> virtual disks, <STRONG>not exceeding </STRONG><STRONG>8TB</STRONG></LI><LI><STRONG>Currently, the ONTAP Deploy tool does not support the workflow of adding space to a Select node, so this process must be done using the native vSphere tooling. </STRONG></LI></UL></LI><LI>For four node ONTAP select cluster, all aggregate is RAID 0 and must be mirrored.<UL><LI>maximum aggregate size is 100TiB</LI><LI>maximun volume size is 60TiB</LI></UL></LI></OL><P><STRONG>My question are:</STRONG></P><OL><LI>Can I create aggreate with more than 2 disks (X = even mumber)?&nbsp;<UL><LI>this means&nbsp;X/2 number of raidgroup in each plex? (one raidgroup per disk)</LI><LI>Will there be any performance penalty?</LI></UL></LI><LI>If I increased the underlying datastore size and created more virtual disk, can I add the disks to the existing aggregate?<UL><LI>what are the consideration?&nbsp;</LI></UL></LI></OL><P>&nbsp;</P> Wed, 04 Jun 2025 15:25:52 GMT https://community.netapp.com/t5/ONTAP-Discussions/ONTAP-Select-9-x-best-practice-for-aggregate-creation/m-p/128280#M27797 jiayih 2025-06-04T15:25:52Z