<?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: BC &amp;amp; EVA - performance in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/bc-amp-eva-performance/m-p/4283049#M28783</link>
    <description>Hi,&lt;BR /&gt;are you speaking on the BC Mirrorclones pls?</description>
    <pubDate>Wed, 08 Oct 2008 10:43:21 GMT</pubDate>
    <dc:creator>IBaltay</dc:creator>
    <dc:date>2008-10-08T10:43:21Z</dc:date>
    <item>
      <title>BC &amp; EVA - performance</title>
      <link>https://community.hpe.com/t5/disk-enclosures/bc-amp-eva-performance/m-p/4283048#M28782</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;we have BC implemented on EVA, and when link goes down, the performance became a mess (very slow on disks production) on storage. Is there any timeout parameter to configure ? &lt;BR /&gt;&lt;BR /&gt;tks &lt;BR /&gt;rgds</description>
      <pubDate>Wed, 08 Oct 2008 09:48:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/bc-amp-eva-performance/m-p/4283048#M28782</guid>
      <dc:creator>Marcia Ferreira_5</dc:creator>
      <dc:date>2008-10-08T09:48:20Z</dc:date>
    </item>
    <item>
      <title>Re: BC &amp; EVA - performance</title>
      <link>https://community.hpe.com/t5/disk-enclosures/bc-amp-eva-performance/m-p/4283049#M28783</link>
      <description>Hi,&lt;BR /&gt;are you speaking on the BC Mirrorclones pls?</description>
      <pubDate>Wed, 08 Oct 2008 10:43:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/bc-amp-eva-performance/m-p/4283049#M28783</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2008-10-08T10:43:21Z</dc:date>
    </item>
  </channel>
</rss>

