<?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 EVA3000 with Progress database in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva3000-with-progress-database/m-p/3406623#M14012</link>
    <description>We intend to buy a EVA3000 with two DL740 with Linux to serve our ERP applicattion.&lt;BR /&gt;We use Progress database to build our ERP.&lt;BR /&gt;But progress says that they don't support array virualization or NFS systems.&lt;BR /&gt;Anyone has any experience with EVAs and Progress ?&lt;BR /&gt;They say that they need separate phisical disks because of performance, the database and BeforeWrite transactions separeted.&lt;BR /&gt;How can I configure EVA to do that ?&lt;BR /&gt;And what about NFS ? Is EVA a NFS system, that is a volume only disponibilized by the appliance ?&lt;BR /&gt;Thanks</description>
    <pubDate>Sun, 24 Oct 2004 13:48:03 GMT</pubDate>
    <dc:creator>AFONSO SOTTOMAYOR</dc:creator>
    <dc:date>2004-10-24T13:48:03Z</dc:date>
    <item>
      <title>EVA3000 with Progress database</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-with-progress-database/m-p/3406623#M14012</link>
      <description>We intend to buy a EVA3000 with two DL740 with Linux to serve our ERP applicattion.&lt;BR /&gt;We use Progress database to build our ERP.&lt;BR /&gt;But progress says that they don't support array virualization or NFS systems.&lt;BR /&gt;Anyone has any experience with EVAs and Progress ?&lt;BR /&gt;They say that they need separate phisical disks because of performance, the database and BeforeWrite transactions separeted.&lt;BR /&gt;How can I configure EVA to do that ?&lt;BR /&gt;And what about NFS ? Is EVA a NFS system, that is a volume only disponibilized by the appliance ?&lt;BR /&gt;Thanks</description>
      <pubDate>Sun, 24 Oct 2004 13:48:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-with-progress-database/m-p/3406623#M14012</guid>
      <dc:creator>AFONSO SOTTOMAYOR</dc:creator>
      <dc:date>2004-10-24T13:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: EVA3000 with Progress database</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-with-progress-database/m-p/3406624#M14013</link>
      <description>Typical response from someone who doesn't understand the concept of virtualisation.&lt;BR /&gt;Either they do not understand it, because they are used to the traditional RAID systems, or because they have a hidden agenda, trying to push some other hardware vendors products with whom they have a partnership.&lt;BR /&gt;&lt;BR /&gt;There's app. 20% performance diference between VRAID 1 and VRAID 5. Depending on the number of drives you have in your EVA, you can configure 1 or 2 diskgroups. One group fra transaction logs and one for the database, thus seperating the 2 diffferent IO patterns. If you have a significant number of drives you can maintain 1 diskgroup, with a VR1 fra logs and a VR5 for data, og VR1 for data depending on your perf. requirements and redundancy.&lt;BR /&gt;A virtualised system like the EVA system will deliver more than enough perf. for your database probably either way.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Christian</description>
      <pubDate>Mon, 25 Oct 2004 02:38:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-with-progress-database/m-p/3406624#M14013</guid>
      <dc:creator>Christian Schwartz-Søre</dc:creator>
      <dc:date>2004-10-25T02:38:06Z</dc:date>
    </item>
  </channel>
</rss>

