- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA vraid1; redundancy
Disk Enclosures
1748165
Members
3900
Online
108758
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
Go to solution
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
02-06-2006 04:08 AM
02-06-2006 04:08 AM
We're in the process of installing a new system with an EVA4000 as its' storage system. I just have a few questions:
1. Our vendor says that the EVA gives you 30% redundancy; that you could lose 30% of your drives and still be up and running. All of our virtual disks are VRaid1. If I look at the properties of our disk groups, the "Disk drive failure protection" actual level is set to "None". I'm asking myself how can that be? Does the EVA provide redundancy within itself which might explain this 30% drive loss with no interruption.
2. Which brings me to VRaid1. Everything I know about RAID1 (mirroring) is that data on one disk is duplicated onto another separate disk. So, if we lost a mirrored pair, we'd be hosed. If that's the case then how can the EVA continue to run if we did lose a mirrored pair? Is there some other technology (raid 5) working behind the scenes when you select VRaid1 for a virtual disk? Are there any HP docs around which talk about each level of VRaid in technical detail?; i.e. what's *actually* going on behind the scenes for each VRaid level.
TIA,
Brad Kozak.
1. Our vendor says that the EVA gives you 30% redundancy; that you could lose 30% of your drives and still be up and running. All of our virtual disks are VRaid1. If I look at the properties of our disk groups, the "Disk drive failure protection" actual level is set to "None". I'm asking myself how can that be? Does the EVA provide redundancy within itself which might explain this 30% drive loss with no interruption.
2. Which brings me to VRaid1. Everything I know about RAID1 (mirroring) is that data on one disk is duplicated onto another separate disk. So, if we lost a mirrored pair, we'd be hosed. If that's the case then how can the EVA continue to run if we did lose a mirrored pair? Is there some other technology (raid 5) working behind the scenes when you select VRaid1 for a virtual disk? Are there any HP docs around which talk about each level of VRaid in technical detail?; i.e. what's *actually* going on behind the scenes for each VRaid level.
TIA,
Brad Kozak.
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2006 05:19 AM
02-06-2006 05:19 AM
Solution
The "protection level", a characteristic of a disk group, is only a space reservation, which is used for recovery in case of a disk drive failure. Just think of it as a set of spare disks that is flipped by 90 degrees and distributed over all disk drive in the disk group. It does not really protect any data. If you create a VRAID-0 virtual disk and you loose a disk drive, no setting of the "protection level" can prevent data loss.
For a VRAID-1 virtual disk, the data chunks are stored on two different physical disk drives - the EVA even tries to distribute the mirror over two different disk drive enclosures. If you loose both chunks, you have lost data - there is no additional protection in the background.
That covers VRAID-0 and 1. For VRAID-5, the EVA takes 4 data chunks, calculates the parity chunk and stores the result on 5 different physical disk drives. If two disk drives which are used by this stripe fail, gess what? You have lost data! Again, no setting of the "protection level" can prevent data loss.
So the EVA works very similar to a traditional RAID storage array - it cannot do wonders eiher ;-)
For a VRAID-1 virtual disk, the data chunks are stored on two different physical disk drives - the EVA even tries to distribute the mirror over two different disk drive enclosures. If you loose both chunks, you have lost data - there is no additional protection in the background.
That covers VRAID-0 and 1. For VRAID-5, the EVA takes 4 data chunks, calculates the parity chunk and stores the result on 5 different physical disk drives. If two disk drives which are used by this stripe fail, gess what? You have lost data! Again, no setting of the "protection level" can prevent data loss.
So the EVA works very similar to a traditional RAID storage array - it cannot do wonders eiher ;-)
.
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