<?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: Disk Groups for Oralce Database in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/disk-groups-for-oralce-database/m-p/4125962#M25834</link>
    <description>Bonjour,&lt;BR /&gt;&lt;BR /&gt;HP has probably recommended 2 DG for security reasons.&lt;BR /&gt;&lt;BR /&gt;If you loose the datafile DG, you wil be able to restore accuratly with the LOGs. &lt;BR /&gt;&lt;BR /&gt;&lt;WHAT is="" the="" best="" configuration=""&gt;&lt;BR /&gt;&lt;BR /&gt;As always, it depends ... What is your focus ? Security or performances ? For performance reasons, choose only one DG, for security reasons 2 DG is enough, even if you have 3 databases.&lt;BR /&gt;&lt;BR /&gt;But don't forget that if you want to achieve the best level of security there are many others points you must take care of. For example yous must have at least 8 shielves in your EVA, redundant fabric paths, and so on ...&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Eric&lt;/WHAT&gt;</description>
    <pubDate>Tue, 08 Jan 2008 15:02:14 GMT</pubDate>
    <dc:creator>Eric SAUBIGNAC</dc:creator>
    <dc:date>2008-01-08T15:02:14Z</dc:date>
    <item>
      <title>Disk Groups for Oralce Database</title>
      <link>https://community.hpe.com/t5/disk-enclosures/disk-groups-for-oralce-database/m-p/4125961#M25833</link>
      <description>We have EVA 4000 we are preparing to create disk groups. HP recomends 2 disk groups one for datafile and 1 for log files.&lt;BR /&gt;&lt;BR /&gt;we have 3 databases do we need 6 diskgroup or we can use jus 1 disk groups.&lt;BR /&gt;&lt;BR /&gt;WHat is the best configuration??&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;James.</description>
      <pubDate>Tue, 08 Jan 2008 14:34:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/disk-groups-for-oralce-database/m-p/4125961#M25833</guid>
      <dc:creator>EVA 4000 Disk groups</dc:creator>
      <dc:date>2008-01-08T14:34:09Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Groups for Oralce Database</title>
      <link>https://community.hpe.com/t5/disk-enclosures/disk-groups-for-oralce-database/m-p/4125962#M25834</link>
      <description>Bonjour,&lt;BR /&gt;&lt;BR /&gt;HP has probably recommended 2 DG for security reasons.&lt;BR /&gt;&lt;BR /&gt;If you loose the datafile DG, you wil be able to restore accuratly with the LOGs. &lt;BR /&gt;&lt;BR /&gt;&lt;WHAT is="" the="" best="" configuration=""&gt;&lt;BR /&gt;&lt;BR /&gt;As always, it depends ... What is your focus ? Security or performances ? For performance reasons, choose only one DG, for security reasons 2 DG is enough, even if you have 3 databases.&lt;BR /&gt;&lt;BR /&gt;But don't forget that if you want to achieve the best level of security there are many others points you must take care of. For example yous must have at least 8 shielves in your EVA, redundant fabric paths, and so on ...&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Eric&lt;/WHAT&gt;</description>
      <pubDate>Tue, 08 Jan 2008 15:02:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/disk-groups-for-oralce-database/m-p/4125962#M25834</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2008-01-08T15:02:14Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Groups for Oralce Database</title>
      <link>https://community.hpe.com/t5/disk-enclosures/disk-groups-for-oralce-database/m-p/4125963#M25835</link>
      <description>Thanks Eric.</description>
      <pubDate>Tue, 08 Jan 2008 15:20:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/disk-groups-for-oralce-database/m-p/4125963#M25835</guid>
      <dc:creator>EVA 4000 Disk groups</dc:creator>
      <dc:date>2008-01-08T15:20:24Z</dc:date>
    </item>
  </channel>
</rss>

