<?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: Write Cache for DB or Exchange in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/write-cache-for-db-or-exchange/m-p/2631640#M3611</link>
    <description>hi k-weibel &lt;BR /&gt; &lt;BR /&gt;YES it IS SAVE. the smart 53xx has a battery backed cache which will keep your data up to 4 days alive and will automatically write them back to the disks after a power outage. &lt;BR /&gt;espacially under randonm i/o (typical for databases) a read/write cache can give you up to 40 % of extra performance (my own benchmarks showed this - using ml370g2 with smart 5304 and intels iometer benchmark). &lt;BR /&gt;the write cache of compaq shipped hot-plug disks is disabled as a default so the whole thing is really save ... &lt;BR /&gt;and if the hw breaks (cache, controller) nobody will guarantee for anything because broken hw can really behave strange. this is why you need a backup even if you would use super-dupa raid technology. &lt;BR /&gt; &lt;BR /&gt;ernesto from germany</description>
    <pubDate>Tue, 15 Jan 2002 00:00:00 GMT</pubDate>
    <dc:creator>Ayman Altounji</dc:creator>
    <dc:date>2002-01-15T00:00:00Z</dc:date>
    <item>
      <title>Write Cache for DB or Exchange</title>
      <link>https://community.hpe.com/t5/disk-enclosures/write-cache-for-db-or-exchange/m-p/2631639#M3610</link>
      <description>Hello... &lt;BR /&gt;Is it save, to enable the write cache of the array controller for SQL (6.5, 7.0, 2000) or Exchange Data base ? &lt;BR /&gt;Any known problems with the array driver when it write back the data to the cache of the array controller and read the "same" data back (data are in cache and not yet on disk). &lt;BR /&gt;thanks for any info &lt;BR /&gt;k.weibel</description>
      <pubDate>Mon, 17 Dec 2001 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/write-cache-for-db-or-exchange/m-p/2631639#M3610</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-12-17T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Write Cache for DB or Exchange</title>
      <link>https://community.hpe.com/t5/disk-enclosures/write-cache-for-db-or-exchange/m-p/2631640#M3611</link>
      <description>hi k-weibel &lt;BR /&gt; &lt;BR /&gt;YES it IS SAVE. the smart 53xx has a battery backed cache which will keep your data up to 4 days alive and will automatically write them back to the disks after a power outage. &lt;BR /&gt;espacially under randonm i/o (typical for databases) a read/write cache can give you up to 40 % of extra performance (my own benchmarks showed this - using ml370g2 with smart 5304 and intels iometer benchmark). &lt;BR /&gt;the write cache of compaq shipped hot-plug disks is disabled as a default so the whole thing is really save ... &lt;BR /&gt;and if the hw breaks (cache, controller) nobody will guarantee for anything because broken hw can really behave strange. this is why you need a backup even if you would use super-dupa raid technology. &lt;BR /&gt; &lt;BR /&gt;ernesto from germany</description>
      <pubDate>Tue, 15 Jan 2002 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/write-cache-for-db-or-exchange/m-p/2631640#M3611</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2002-01-15T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>

