HP P2000 G3 Reference Manual page 31
Storageworks msa system
Hide thumbs
Also See for P2000 G3:
- Cli reference manual (532 pages) ,
- User manual (76 pages) ,
- Reference manual (68 pages)
Table of Contents
Advertisement
Table 4
Example applications and RAID levels
Application
Network operating system, databases, high availability applications, workgroup servers
Very large databases, web server, video on demand
Mission-critical environments that demand high availability and use large sequential workloads
Table 5
RAID level comparison
RAID
Min.
Description
level
disks
NRAID 1
Non-RAID, nonstriped
mapping to a single disk
0
2
Data striping without
redundancy
1
2
Disk mirroring
3
3
Block-level data striping
with dedicated parity
disk
5
3
Block-level data striping
with distributed parity
6
4
Block-level data striping
with double distributed
parity
10
4
Stripes data across
(1+0)
multiple RAID- 1
sub-vdisks
50
6
Stripes data across
(5+0)
multiple RAID-5
sub-vdisks
Strengths
Ability to use a single disk to store
additional data
Highest performance
Very high performance and data
protection; minimal penalty on
write performance; protects
against single disk failure
Excellent performance for large,
sequential data requests (fast
read); protects against single disk
failure
Best cost/performance for
transaction-oriented networks;
very high performance and data
protection; supports multiple
simultaneous reads and writes;
can also be optimized for large,
sequential requests; protects
against single disk failure
Best suited for large sequential
workloads; non-sequential read
and sequential read/write
performance is comparable to
RAID 5; protects against dual disk
failure
Highest performance and data
protection (protects against
multiple disk failures)
Better random read and write
performance and data protection
than RAID 5; supports more disks
than RAID 5; protects against
multiple disk failures
HP StorageWorks P2000 G3 MSA System SMU Reference Guide
RAID level
5
50
6
Weaknesses
Not protected, lower performance
(not striped)
No data protection: if one disk
fails all data is lost
High redundancy cost overhead:
because all data is duplicated,
twice the storage capacity is
required
Not well-suited for
transaction-oriented network
applications: single parity disk
does not support multiple,
concurrent write requests
Write performance is slower than
RAID 0 or RAID 1
Higher redundancy cost than
RAID 5 because the parity
overhead is twice that of RAID 5;
not well-suited for
transaction-oriented network
applications; non-sequential write
performance is slower than RAID
5
High redundancy cost overhead:
because all data is duplicated,
twice the storage capacity is
required; requires minimum of four
disks
Lower storage capacity than RAID
5
31
Advertisement
Table of Contents
