HP StorageWorks 6000 HP StorageWorks VLS and D2D Solutions Guide (AG306-96028, - Page 121

Storage Pooling, what is considered a catastrophic

Get HP StorageWorks 6000 - Virtual Library System PDF manuals and user guides View all HP StorageWorks 6000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 121 highlights

• The EVA LUNs must be fully initialized and ready for use before attaching the VLS to the EVA. It can take several hours to initialize an entire EVA; therefore, HP advises you to create the LUNs in advance of the installation. • Ensure that all VRaid LUNs required for the VLS have been created on the EVA such that the LUNs are RAID 6 (preferred) or RAID 5, are not configured as read-only, and are roughly the same size. • The maximum supported EVA LUN size is 2047GB. Do not create LUNs for the VLS larger than this even if the EVA model supports it. • On the EVA 8000, there are 4 Fibre Channel ports per controller which allows up to eight paths to each LUN; however, configuring more than four paths per LUN will limit the maximum capacity of the device without adding performance benefits. For this reason, HP recommends use of only four paths per LUN. • It is possible to share an EVA between the VLS12000 and other applications. If the EVA is shared, VLS traffic may overwhelm the array and significantly reduce performance across all applications sharing the array. Alternately, the other applications may slow down the performance of the VLS. If this happens, manual load-balancing between applications is required (that is, you will have to schedule the VLS traffic only when all other applications are inactive). For this reason, HP recommends using a dedicated EVA for the VLS12000. Storage Pooling On the VLS12000 and VLS9000, physical disk capacity can be separated into storage pools. Virtual tapes can then be assigned to a specific storage pool. Having multiple storage pools allows you to: • Minimize the impact if multiple disks fail at the same time - what is considered a catastrophic array failure. If a catastrophic array failure destroys one or more LUNs on an array, only the storage pool containing that array loses its data; all others retain their data. • Keep specific backup data physically separate from other backup data. For example, businesses can keep data from one customer separate from that of another customer, or data from different organizations can be kept separate. Despite the benefits of creating multiple storage pools, maintenance is easier on a system with only one storage pool because the VLS balances performance automatically for a single pool. Load balancing the backup jobs across the pools with the VLS12000 and VLS9000 must be done manually. See Figure 47. HP StorageWorks VLS and D2D Solutions Guide 121

  • 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
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
•
The EVA LUNs must be fully initialized and ready for use before attaching the VLS to the EVA. It
can take several hours to initialize an entire EVA; therefore, HP advises you to create the LUNs in
advance of the installation.
•
Ensure that all VRaid LUNs required for the VLS have been created on the EVA such that the LUNs
are RAID 6 (preferred) or RAID 5, are not configured as read-only, and are roughly the same size.
•
The maximum supported EVA LUN size is 2047GB. Do not create LUNs for the VLS larger than
this even if the EVA model supports it.
•
On the EVA 8000, there are 4 Fibre Channel ports per controller which allows up to eight paths
to each LUN; however, configuring more than four paths per LUN will limit the maximum capacity
of the device without adding performance benefits. For this reason, HP recommends use of only
four paths per LUN.
•
It is possible to share an EVA between the VLS12000 and other applications. If the EVA is shared,
VLS traffic may overwhelm the array and significantly reduce performance across all applications
sharing the array. Alternately, the other applications may slow down the performance of the VLS.
If this happens, manual load-balancing between applications is required (that is, you will have to
schedule the VLS traffic only when all other applications are inactive). For this reason, HP recom-
mends using a dedicated EVA for the VLS12000.
Storage Pooling
On the VLS12000 and VLS9000, physical disk capacity can be separated into storage pools. Virtual
tapes can then be assigned to a specific storage pool. Having multiple storage pools allows you to:
•
Minimize the impact if multiple disks fail at the same time
—
what is considered a catastrophic
array failure. If a catastrophic array failure destroys one or more LUNs on an array, only the
storage pool containing that array loses its data; all others retain their data.
•
Keep specific backup data physically separate from other backup data. For example, businesses
can keep data from one customer separate from that of another customer, or data from different
organizations can be kept separate.
Despite the benefits of creating multiple storage pools, maintenance is easier on a system with only
one storage pool because the VLS balances performance automatically for a single pool. Load
balancing the backup jobs across the pools with the VLS12000 and VLS9000 must be done manually.
See
Figure 47
.
HP StorageWorks VLS and D2D Solutions Guide
121