- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- MSA2000's vdisks fault-tolerance behavior vs. Virt...
HPE EVA Storage
1752866
Members
3989
Online
108791
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
08-25-2010 09:22 AM
08-25-2010 09:22 AM
MSA2000's vdisks fault-tolerance behavior vs. Virtual Server's VMs
Hello,
I have a few BL460 blades connected to a MSA2212 FC SAN. In the MSA I have two enclosures, each with 12 SAS hard disks.
I have created 4 vdisks, all in RAID10; each of them uses 6 hard disks (3 from an enclosure, 3 from the other one). No spare disks.
Now, one of the blades is a WS2003 machine working as Microsoft Virtual Server host (Virtual Server installed on C: drive, not in the SAN). I have created 10 volumes on the SAN (not all on the same vdisk), and linked them to this host. One volume per virtual machine.
Today one hard disk failed.
While I expected impacts only on the vdisk this HDD is member of, all the vdisks were impacted (general poor response time on all the volumes linked to the blades). But that is maybe acceptable.
What I don't understand is why all the virtual machines became totally unresponsive, even if placed in volumes not created in the affected vdisk.
And if i try to reboot them (the VMs), I often get "no boot disk found", as if the VHD is corrupt, but then if I move the VHD on a disk outside of the SAN, it works fine.
Is this normal?
Is there any configuration I can apply to the SAN so not to have such a behavior if a single disk fails?
thanks,
fabio
I have a few BL460 blades connected to a MSA2212 FC SAN. In the MSA I have two enclosures, each with 12 SAS hard disks.
I have created 4 vdisks, all in RAID10; each of them uses 6 hard disks (3 from an enclosure, 3 from the other one). No spare disks.
Now, one of the blades is a WS2003 machine working as Microsoft Virtual Server host (Virtual Server installed on C: drive, not in the SAN). I have created 10 volumes on the SAN (not all on the same vdisk), and linked them to this host. One volume per virtual machine.
Today one hard disk failed.
While I expected impacts only on the vdisk this HDD is member of, all the vdisks were impacted (general poor response time on all the volumes linked to the blades). But that is maybe acceptable.
What I don't understand is why all the virtual machines became totally unresponsive, even if placed in volumes not created in the affected vdisk.
And if i try to reboot them (the VMs), I often get "no boot disk found", as if the VHD is corrupt, but then if I move the VHD on a disk outside of the SAN, it works fine.
Is this normal?
Is there any configuration I can apply to the SAN so not to have such a behavior if a single disk fails?
thanks,
fabio
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