HP MSA 1040 HP MSA 1040 SMU Reference Guide (762784-001, March 2014) - Page 27

Table 3, Application, RAID level, level, disks, Description, Strengths, Weaknesses - cli reference guide

Get HP MSA 1040 PDF manuals and user guides View all HP MSA 1040 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

NOTE: To create an NRAID, RAID-0, or RAID-3 vdisk, you must use the CLI create vdisk command. For more information on this command, see the CLI Reference Guide. Table 3 Example applications and RAID levels Application Testing multiple operating systems or software development (where redundancy is not an issue) Fast temporary storage or scratch disks for graphics, page layout, and image rendering Workgroup servers Video editing and production 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 RAID level NRAID 0 1 or 10 3 5 50 6 Table 4 RAID level comparison RAID Min. Description level disks Strengths Weaknesses NRAID 1 0 2 Non-RAID, nonstriped Ability to use a single disk to store Not protected, lower performance mapping to a single disk additional data (not striped) Data striping without redundancy Highest performance No data protection: if one disk fails all data is lost 1 2 Disk mirroring Very high performance and data protection; minimal penalty on write performance; protects against single disk failure High redundancy cost overhead: because all data is duplicated, twice the storage capacity is required 3 3 Block-level data striping Excellent performance for large, Not well-suited for with dedicated parity sequential data requests (fast transaction-oriented network disk read); protects against single disk applications; write performance is failure lower on short writes (less than 1 stripe) 5 3 Block-level data striping Best cost/performance for Write performance is slower than with distributed parity transaction-oriented networks; RAID 0 or RAID 1 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 6 4 Block-level data striping Best suited for large sequential Higher redundancy cost than with double distributed workloads; non-sequential read RAID 5 because the parity parity and sequential read/write overhead is twice that of RAID 5; performance is comparable to not well-suited for RAID 5; protects against dual disk transaction-oriented network failure applications; non-sequential write performance is slower than RAID 5 System concepts 27

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
System concepts
27
NOTE:
To create an NRAID, RAID-0, or RAID-3 vdisk, you must use the CLI
create vdisk
command. For more
information on this command, see the CLI Reference Guide.
Table 3
Example applications and RAID levels
Application
RAID level
Testing multiple operating systems or software development (where redundancy is not an issue)
NRAID
Fast temporary storage or scratch disks for graphics, page layout, and image rendering
0
Workgroup servers
1 or 10
Video editing and production
3
Network operating system, databases, high availability applications, workgroup servers
5
Very large databases, web server, video on demand
50
Mission-critical environments that demand high availability and use large sequential workloads
6
Table 4
RAID level comparison
RAID
level
Min.
disks
Description
Strengths
Weaknesses
NRAID
1
Non-RAID, nonstriped
mapping to a single disk
Ability to use a single disk to store
additional data
Not protected, lower performance
(not striped)
0
2
Data striping without
redundancy
Highest performance
No data protection: if one disk
fails all data is lost
1
2
Disk mirroring
Very high performance and data
protection; minimal penalty on
write performance; protects
against single disk failure
High redundancy cost overhead:
because all data is duplicated,
twice the storage capacity is
required
3
3
Block-level data striping
with dedicated parity
disk
Excellent performance for large,
sequential data requests (fast
read); protects against single disk
failure
Not well-suited for
transaction-oriented network
applications; write performance is
lower on short writes (less than 1
stripe)
5
3
Block-level data striping
with distributed parity
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
Write performance is slower than
RAID 0 or RAID 1
6
4
Block-level data striping
with double distributed
parity
Best suited for large sequential
workloads; non-sequential read
and sequential read/write
performance is comparable to
RAID 5; protects against dual disk
failure
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