<?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 Resource pool provisioning policy ? in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Resource-pool-provisioning-policy/m-p/443#M104</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I looking information details about how PM make its secondary provisionning&lt;/P&gt;&lt;P&gt;I got information about how PM determine if a destination aggr is eligible&amp;nbsp; (The actual formula for calculating the Projected Size is to take the maximum of&amp;nbsp; ([1.2 times the Volume’s Total Size] or [2.0 times the Volume’s Used Size]) + 10%).&lt;/P&gt;&lt;P&gt;But I get any information on how PM selects a aggr among the eligible aggr list (when multiple aggr are passed successfully&amp;nbsp; the eligibility test) ?&lt;/P&gt;&lt;P&gt;Can someone give me this information&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ce message a été modifié par : Christian Gajan&amp;nbsp; After some tests, I found that PM first fills the first aggregate before proceeding to the next&amp;nbsp; Is there some options to change this behavior to get something like loadbalancing between available aggragate in the resource pool ?&amp;nbsp; Thanks in advance Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:16:04 GMT</pubDate>
    <dc:creator>christig</dc:creator>
    <dc:date>2025-06-05T06:16:04Z</dc:date>
    <item>
      <title>Resource pool provisioning policy ?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Resource-pool-provisioning-policy/m-p/443#M104</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I looking information details about how PM make its secondary provisionning&lt;/P&gt;&lt;P&gt;I got information about how PM determine if a destination aggr is eligible&amp;nbsp; (The actual formula for calculating the Projected Size is to take the maximum of&amp;nbsp; ([1.2 times the Volume’s Total Size] or [2.0 times the Volume’s Used Size]) + 10%).&lt;/P&gt;&lt;P&gt;But I get any information on how PM selects a aggr among the eligible aggr list (when multiple aggr are passed successfully&amp;nbsp; the eligibility test) ?&lt;/P&gt;&lt;P&gt;Can someone give me this information&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ce message a été modifié par : Christian Gajan&amp;nbsp; After some tests, I found that PM first fills the first aggregate before proceeding to the next&amp;nbsp; Is there some options to change this behavior to get something like loadbalancing between available aggragate in the resource pool ?&amp;nbsp; Thanks in advance Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:16:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Resource-pool-provisioning-policy/m-p/443#M104</guid>
      <dc:creator>christig</dc:creator>
      <dc:date>2025-06-05T06:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Resource pool provisioning policy ?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Resource-pool-provisioning-policy/m-p/448#M106</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are coming up with a Getting started course on how this selection is done when more than one aggr is eligible.&lt;/P&gt;&lt;P&gt;Least-Utilized (only option prior to 5.1)&lt;/P&gt;&lt;P&gt;–Selects aggregates with most available space&lt;/P&gt;&lt;P&gt;–Margin can be tuned to select acceptable range&lt;/P&gt;&lt;P&gt;Best-Fit (new with 5.1)&lt;/P&gt;&lt;P&gt;–Selects aggregates with the least available free space that would fulfill the need&lt;/P&gt;&lt;P&gt;–Margin can be tuned to select acceptable range&lt;/P&gt;&lt;P&gt;¡Global setting to select preferred algorithm&lt;/P&gt;&lt;P&gt;&amp;nbsp; Manually resource selecting&amp;nbsp; ignores both algorithms&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are two phases namely space balancing and load balancing.&lt;/P&gt;&lt;P&gt; In space balancing phase we pick the aggr with largest free space( if least used criterion which is default)&amp;nbsp; and all those within 75% of its capacity.&amp;nbsp; &lt;/P&gt;&lt;P&gt;By this we come up with a set of aggr, and on this set we apply the space balancing like number of qtree or relationships.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In case of Best fit criterion we take the aggr that just fit and all those with in 1.75x its capacity and apply the load balancing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In case of Primary provisioning the number of qtree is used and in case of secondary provisioning we use the number of relationships.&lt;/P&gt;&lt;P&gt;In the space balancing phase we select the aggr with largest free space and apply &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;adai&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 13:24:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Resource-pool-provisioning-policy/m-p/448#M106</guid>
      <dc:creator>adaikkap</dc:creator>
      <dc:date>2013-03-01T13:24:41Z</dc:date>
    </item>
  </channel>
</rss>

