<?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: MSA1000 Survivability in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/msa1000-survivability/m-p/529619#M1316</link>
    <description>Daniel,&lt;BR /&gt;The MSA line of controllers feature a battery backed cache.  If a controller fails and write caching has been enabled and there is any unflushed data in the cache, you can move the cache to a new controller and it will flush the data to the disks.  The cache can survive at least 72 hours.&lt;BR /&gt;As Uwe stated, the configuration info is stored both in the controller and on the disks so you won't lose the configuration but if data is lost in the cache you may have corruption.&lt;BR /&gt;&lt;BR /&gt;Glenn</description>
    <pubDate>Fri, 13 May 2005 07:10:11 GMT</pubDate>
    <dc:creator>CA1183745</dc:creator>
    <dc:date>2005-05-13T07:10:11Z</dc:date>
    <item>
      <title>MSA1000 Survivability</title>
      <link>https://community.hpe.com/t5/msa-storage/msa1000-survivability/m-p/529616#M1313</link>
      <description>I have a MSA1000 with a single controller with battery backup and a single 2/8 fiber switch. If my controller fails, do I have any hope of recovering the disk configuration when the controller is replaced? Is the only option for true survivability a second controller?</description>
      <pubDate>Thu, 12 May 2005 09:50:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa1000-survivability/m-p/529616#M1313</guid>
      <dc:creator>Daniel Conroy</dc:creator>
      <dc:date>2005-05-12T09:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Survivability</title>
      <link>https://community.hpe.com/t5/msa-storage/msa1000-survivability/m-p/529617#M1314</link>
      <description>The configuration is stored on the disks, so you have a good chance that a replacement controller can pick it up.</description>
      <pubDate>Thu, 12 May 2005 10:09:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa1000-survivability/m-p/529617#M1314</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-05-12T10:09:50Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Survivability</title>
      <link>https://community.hpe.com/t5/msa-storage/msa1000-survivability/m-p/529618#M1315</link>
      <description>thank you.</description>
      <pubDate>Thu, 12 May 2005 10:39:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa1000-survivability/m-p/529618#M1315</guid>
      <dc:creator>Daniel Conroy</dc:creator>
      <dc:date>2005-05-12T10:39:47Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 Survivability</title>
      <link>https://community.hpe.com/t5/msa-storage/msa1000-survivability/m-p/529619#M1316</link>
      <description>Daniel,&lt;BR /&gt;The MSA line of controllers feature a battery backed cache.  If a controller fails and write caching has been enabled and there is any unflushed data in the cache, you can move the cache to a new controller and it will flush the data to the disks.  The cache can survive at least 72 hours.&lt;BR /&gt;As Uwe stated, the configuration info is stored both in the controller and on the disks so you won't lose the configuration but if data is lost in the cache you may have corruption.&lt;BR /&gt;&lt;BR /&gt;Glenn</description>
      <pubDate>Fri, 13 May 2005 07:10:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/msa1000-survivability/m-p/529619#M1316</guid>
      <dc:creator>CA1183745</dc:creator>
      <dc:date>2005-05-13T07:10:11Z</dc:date>
    </item>
  </channel>
</rss>

