<?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 MSA1000 SAN network traffic capacity in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428859#M9931</link>
    <description>How can one estimate the ability of a SAN to take on the load from other servers once the data from the other servers is migrated over to the SAN? For instance, three older servers will have the data on them transfered to the SAN and the network users will still need to access the data (one part of the data will be the users home drive folders).  &lt;BR /&gt;</description>
    <pubDate>Tue, 23 Nov 2004 11:41:01 GMT</pubDate>
    <dc:creator>Bill O'Brien_6</dc:creator>
    <dc:date>2004-11-23T11:41:01Z</dc:date>
    <item>
      <title>MSA1000 SAN network traffic capacity</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428859#M9931</link>
      <description>How can one estimate the ability of a SAN to take on the load from other servers once the data from the other servers is migrated over to the SAN? For instance, three older servers will have the data on them transfered to the SAN and the network users will still need to access the data (one part of the data will be the users home drive folders).  &lt;BR /&gt;</description>
      <pubDate>Tue, 23 Nov 2004 11:41:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428859#M9931</guid>
      <dc:creator>Bill O'Brien_6</dc:creator>
      <dc:date>2004-11-23T11:41:01Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 SAN network traffic capacity</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428860#M9932</link>
      <description>How many servers are currently attached to the msa. How many MSA LUNs.  Will your server count change after the data transfer.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Nov 2004 11:51:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428860#M9932</guid>
      <dc:creator>John Kufrovich</dc:creator>
      <dc:date>2004-11-23T11:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 SAN network traffic capacity</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428861#M9933</link>
      <description>There is only one server attached to the MSA right now. The plan is to phase out 2-3 other older servers and to migrate that data to the MSA.</description>
      <pubDate>Mon, 29 Nov 2004 11:25:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428861#M9933</guid>
      <dc:creator>Bill O'Brien_6</dc:creator>
      <dc:date>2004-11-29T11:25:44Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 SAN network traffic capacity</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428862#M9934</link>
      <description>Bill, there really is no way to estimate the load of a SAN.   &lt;BR /&gt;From the information you provided, their shouldn't be any problems with the MSA to handle the additional load.  &lt;BR /&gt;&lt;BR /&gt;If this would ease your mind, I've worked with customers that had multiple exchange servers to a single MSA.  No problems.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Nov 2004 17:35:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428862#M9934</guid>
      <dc:creator>John Kufrovich</dc:creator>
      <dc:date>2004-11-30T17:35:52Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 SAN network traffic capacity</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428863#M9935</link>
      <description>There are many points of throughput saturation that can occur.  The HBA, FC switch, controller ports, controller cache and user applications are the main bottleneck areas.  Each of the items need to be analyzes to get a complete performance matrix.</description>
      <pubDate>Fri, 03 Dec 2004 10:58:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428863#M9935</guid>
      <dc:creator>Clint Placette_2</dc:creator>
      <dc:date>2004-12-03T10:58:30Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 SAN network traffic capacity</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428864#M9936</link>
      <description>We did some stress testing of the MSA1000s and found that with 32 (36GB 15K) disks and with cache turned off, we could do about 10,000 I/Os per second of random 1KB reads.&lt;BR /&gt;&lt;BR /&gt;YMMV of course but the controllers seem to handle a lot.  &lt;BR /&gt;&lt;BR /&gt;Cass</description>
      <pubDate>Mon, 20 Dec 2004 16:38:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-san-network-traffic-capacity/m-p/3428864#M9936</guid>
      <dc:creator>Cass Witkowski</dc:creator>
      <dc:date>2004-12-20T16:38:37Z</dc:date>
    </item>
  </channel>
</rss>

