<?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: MSA 2052 tiering in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7008571#M11889</link>
    <description>&lt;P&gt;Yes your understanding is correct&lt;/P&gt;&lt;P&gt;When we have tier model then any volume part of that Pool will be using tier architecture until and unless we have any specific rule set as Volume Tier Affinity&lt;/P&gt;&lt;P&gt;now if you have any specific application requirement for example let's say you have any backup application or something which is not so important and you want these data always should go to your Archive tier - in that case you should assign your Volume Tier Affinity for that volume as "Archive" so that these 4MB pages of data will never touch SSD which may be require for handling some important production data.&lt;/P&gt;&lt;P&gt;So Volume Tier Affinity is volume specific and this is not applicable to any volume part of that Pool. Other volumes will be using 3 Tier Architecture of that Pool as it is.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;BR /&gt;Regards&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;Subhajit&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;If you feel this was helpful please click the &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;KUDOS!&lt;/STRONG&gt;&lt;/FONT&gt; thumb below!&lt;/P&gt;&lt;P&gt;***********************************************************************************&lt;/P&gt;</description>
    <pubDate>Tue, 12 Jun 2018 00:13:07 GMT</pubDate>
    <dc:creator>SUBHAJIT KHANBARMAN_1</dc:creator>
    <dc:date>2018-06-12T00:13:07Z</dc:date>
    <item>
      <title>MSA 2052 tiering</title>
      <link>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7008161#M11884</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;IM just trying to understand my new MSA 2052.&lt;/P&gt;&lt;P&gt;So i have just created a raid 1 with two SSD'S within Pool A and Raid 5 Diskgroup - Volume also within Pool A ( HD 2,5 10000rpm)&lt;/P&gt;&lt;P&gt;Us i understand the best practise evyrthing within the same Pool will use automaticly tier performance.&lt;/P&gt;&lt;P&gt;1. Waht i not really understand do i have to selct&amp;nbsp;&lt;SPAN&gt;Tier Affinity: performance on the volumes?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;and&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. Is there a chance to see if tiering is running? somwhere on performance tab maybe?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;and&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;3. how to understand the performacen tab, i can't find any info about that.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Hope you can help me.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Many thansk&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;to all&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jun 2018 18:13:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7008161#M11884</guid>
      <dc:creator>homermg</dc:creator>
      <dc:date>2018-06-06T18:13:03Z</dc:date>
    </item>
    <item>
      <title>Re: MSA 2052 tiering</title>
      <link>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7008249#M11885</link>
      <description>&lt;P&gt;Dear&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1310407"&gt;@homermg&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Thank you for your questions.&lt;/P&gt;&lt;P&gt;The answer to all your questions can be found in the best practice guide.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Volume Tier Affinity&lt;/STRONG&gt; is a settable attribute that allows a storage administrator to define quality of service (QoS) preferences for virtual volumes in a tiered environment. There are three Volume Tier Affinity options—Archive, Performance, and No Affinity. A setting of Archive will prefer the lowest tier of service, Performance will prefer the higher tiers of service, and No Affinity will use the Standard Tiering strategy. Tier Affinity is not the same as Tier Pinning and does not restrict data to a given tier and capacity. &lt;STRONG&gt;Data on a volume with Archive affinity can still to be promoted to a Performance Tier if that data becomes in demand to the host application.&lt;/STRONG&gt;&lt;BR /&gt;Refer Best Practice: &lt;A href="https://h20195.www2.hpe.com/v2/Getdocument.aspx?docname=a00015961enw" target="_blank"&gt;https://h20195.www2.hpe.com/v2/Getdocument.aspx?docname=a00015961enw&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The tier I/O panel in the footer shows a color-coded bar for each virtual pool (A, B, or both) that has active I/O. The bars are sized to represent the relative IOPS for each pool. Each bar contains a segment for each tier that has active I/O. Hover the cursor anywhere in this panel to display the Tier I/O Information panel, which shows the following details for each tier in each virtual pool:&lt;BR /&gt;• Current IOPS for the pool, calculated over the interval since these statistics were last requested or reset.&lt;BR /&gt;• Current data throughput (MB/s) for the pool, calculated over the interval since these statistics were last requested or reset.&lt;BR /&gt;The panel also contains combined total percentages of IOPS and current data throughput (MB/s) for both pools.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HPE MSA 1040/2040/P2000 G3 Systems - Performance Monitoring via SMU (Understanding performance tab):&lt;BR /&gt;&lt;A href="https://support.hpe.com/hpsc/doc/public/display?docId=mmr_kc-0119548" target="_blank"&gt;https://support.hpe.com/hpsc/doc/public/display?docId=mmr_kc-0119548&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please refer best practice guide for more information:&lt;BR /&gt;&lt;A href="https://h20195.www2.hpe.com/v2/Getdocument.aspx?docname=a00015961enw" target="_blank"&gt;https://h20195.www2.hpe.com/v2/Getdocument.aspx?docname=a00015961enw&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Vikas&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jun 2018 16:12:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7008249#M11885</guid>
      <dc:creator>VikasMandal</dc:creator>
      <dc:date>2018-06-07T16:12:46Z</dc:date>
    </item>
    <item>
      <title>Re: MSA 2052 tiering</title>
      <link>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7008505#M11886</link>
      <description>&lt;P&gt;Hi Vikas,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;im still not sure what&amp;nbsp;it means?&lt;/P&gt;&lt;P&gt;As i understand i need just to create a raid 1 with my both ssd's disk types: esas performance on e.g. Pool A.&lt;/P&gt;&lt;P&gt;Than evyrthing i craets on pool A will uses the ssd's for performance tiering without to selcet any affinity.&lt;/P&gt;&lt;P&gt;Is that correct?&lt;/P&gt;&lt;P&gt;So affinity need is only to control&amp;nbsp; that if e.g. the Pool A with the SSD's has several volumes but i don't use the SSD's for all the volumes, is that right?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jun 2018 13:43:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7008505#M11886</guid>
      <dc:creator>homermg</dc:creator>
      <dc:date>2018-06-11T13:43:15Z</dc:date>
    </item>
    <item>
      <title>Re: MSA 2052 tiering</title>
      <link>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7008571#M11889</link>
      <description>&lt;P&gt;Yes your understanding is correct&lt;/P&gt;&lt;P&gt;When we have tier model then any volume part of that Pool will be using tier architecture until and unless we have any specific rule set as Volume Tier Affinity&lt;/P&gt;&lt;P&gt;now if you have any specific application requirement for example let's say you have any backup application or something which is not so important and you want these data always should go to your Archive tier - in that case you should assign your Volume Tier Affinity for that volume as "Archive" so that these 4MB pages of data will never touch SSD which may be require for handling some important production data.&lt;/P&gt;&lt;P&gt;So Volume Tier Affinity is volume specific and this is not applicable to any volume part of that Pool. Other volumes will be using 3 Tier Architecture of that Pool as it is.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;BR /&gt;Regards&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;Subhajit&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;If you feel this was helpful please click the &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;KUDOS!&lt;/STRONG&gt;&lt;/FONT&gt; thumb below!&lt;/P&gt;&lt;P&gt;***********************************************************************************&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jun 2018 00:13:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7008571#M11889</guid>
      <dc:creator>SUBHAJIT KHANBARMAN_1</dc:creator>
      <dc:date>2018-06-12T00:13:07Z</dc:date>
    </item>
    <item>
      <title>Re: MSA 2052 tiering</title>
      <link>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7009760#M11915</link>
      <description>&lt;P&gt;cool many thanks! got it :-)&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jun 2018 15:45:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7009760#M11915</guid>
      <dc:creator>homermg</dc:creator>
      <dc:date>2018-06-25T15:45:02Z</dc:date>
    </item>
    <item>
      <title>Re: MSA 2052 tiering</title>
      <link>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7030344#M12538</link>
      <description>&lt;P&gt;what is best throughput is expected from MSA2052 with 30 x 12tb 7.2k rpm disks&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2019 08:07:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7030344#M12538</guid>
      <dc:creator>arora_newtech</dc:creator>
      <dc:date>2019-01-08T08:07:06Z</dc:date>
    </item>
    <item>
      <title>Re: MSA 2052 tiering</title>
      <link>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7030357#M12539</link>
      <description>&lt;P&gt;Request you to kindly open new discussion forum with your new query as we need to address each issue seperately so that everyone can track the same based on topic.&lt;/P&gt;&lt;P&gt;I would suggest to check&lt;STRONG&gt; page no 9&lt;/STRONG&gt; onwards topic "&lt;STRONG&gt;Performance&lt;/STRONG&gt;" from quickspec that will give you idea of what all inputs required before we can calculate approx throughput which you are asking,&lt;/P&gt;&lt;P&gt;&lt;A href="https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=a00008277enw" target="_blank"&gt;https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=a00008277enw&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;BR /&gt;Regards&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;Subhajit&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;If you feel this was helpful please click the &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;KUDOS!&lt;/STRONG&gt;&lt;/FONT&gt; thumb below!&lt;/P&gt;&lt;P&gt;***********************************************************************************&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2019 09:37:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa-2052-tiering/m-p/7030357#M12539</guid>
      <dc:creator>SUBHAJIT KHANBARMAN_1</dc:creator>
      <dc:date>2019-01-08T09:37:41Z</dc:date>
    </item>
  </channel>
</rss>

