- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA3000 with Progress database
Disk Enclosures
1748033
Members
4873
Online
108757
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2004 06:48 AM
10-24-2004 06:48 AM
EVA3000 with Progress database
We intend to buy a EVA3000 with two DL740 with Linux to serve our ERP applicattion.
We use Progress database to build our ERP.
But progress says that they don't support array virualization or NFS systems.
Anyone has any experience with EVAs and Progress ?
They say that they need separate phisical disks because of performance, the database and BeforeWrite transactions separeted.
How can I configure EVA to do that ?
And what about NFS ? Is EVA a NFS system, that is a volume only disponibilized by the appliance ?
Thanks
We use Progress database to build our ERP.
But progress says that they don't support array virualization or NFS systems.
Anyone has any experience with EVAs and Progress ?
They say that they need separate phisical disks because of performance, the database and BeforeWrite transactions separeted.
How can I configure EVA to do that ?
And what about NFS ? Is EVA a NFS system, that is a volume only disponibilized by the appliance ?
Thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2004 07:38 PM
10-24-2004 07:38 PM
Re: EVA3000 with Progress database
Typical response from someone who doesn't understand the concept of virtualisation.
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.
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.
A virtualised system like the EVA system will deliver more than enough perf. for your database probably either way.
Regards
Christian
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.
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.
A virtualised system like the EVA system will deliver more than enough perf. for your database probably either way.
Regards
Christian
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP