HP P4000 9.0 HP StorageWorks P4000 SAN Solution User Guide - Page 209

Volumes map view, Editing a volume, Requirements for Changing

Page 209 highlights

2. Change the desired characteristics and click OK when you are finished. Configuring a volume for either Network RAID-5 or Network RAID-6 automatically creates a snapshot schedule. This default schedule is named VolumeName_Schedule, recurs once daily, and retains 1 copy. The first snapshot is created one day after the schedule is created. You can edit this schedule as desired, as described in "Editing scheduled snapshots" on page 225. Volumes map view After you create volumes and finish setting up the SAN, use the Map View tab for viewing the relationships between volumes, snapshots, servers, and remote copies. For more information on using the map view tools, see "Manipulating the Map View" on page 29. Volumes map views include the following: • Volume Hierarchy • Remote Copies • Remote Copies (Volume Hierarchies) • Servers to Volumes Editing a volume When editing a primary volume, you can change the description, size, and advanced characteristics such as the cluster, data protection level, type and provisioning. NOTE: Moving the volume to a different cluster requires restriping the data in both clusters. Restriping can take hours, or even days. Table 46 Requirements for changing volume characteristics Item Description Requirements for Changing Must be from 1 to 127 characters. Server Cluster Server must have already been created in the management group. The target cluster must • Reside in the same management group. • Have sufficient storage systems and unallocated space for the size and data protection level of the volume being moved. • Use a Virtual IP if the originating cluster has a Virtual IP The volume resides on both clusters until all of the data is moved to the new cluster. This causes a restripe of the data on both clusters. For example, you restructure your storage and create an additional cluster. You want to migrate an existing volume to the new cluster as part of the restructuring. NOTE: The volume remains fault-tolerant while being moved. P4000 SAN Solution user guide 209

  • 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
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350

2.
Change the desired characteristics and click OK when you are finished.
Configuring a volume for either Network RAID-5 or Network RAID-6 automatically creates a snapshot
schedule. This default schedule is named
VolumeName
_Schedule, recurs once daily, and retains 1
copy. The first snapshot is created one day after the schedule is created. You can edit this schedule
as desired, as described in
Editing scheduled snapshots
on page 225.
Volumes map view
After you create volumes and finish setting up the SAN, use the Map View tab for viewing the
relationships between volumes, snapshots, servers, and remote copies. For more information on using
the map view tools, see
Manipulating the Map View
on page 29.
Volumes map views include the following:
Volume Hierarchy
Remote Copies
Remote Copies (Volume Hierarchies)
Servers to Volumes
Editing a volume
When editing a primary volume, you can change the description, size, and advanced characteristics
such as the cluster, data protection level, type and provisioning.
NOTE:
Moving the volume to a different cluster requires restriping the data in both clusters. Restriping can
take hours, or even days.
Table 46 Requirements for changing volume characteristics
Requirements for Changing
Item
Must be from 1 to 127 characters.
Description
Server must have already been created in the management group.
Server
The target cluster must
Reside in the same management group.
Have sufficient storage systems and unallocated space for the size and data protection
level of the volume being moved.
Use a Virtual IP if the originating cluster has a Virtual IP
The volume resides on both clusters until all of the data is moved to the new cluster. This causes
a restripe of the data on both clusters. For example, you restructure your storage and create
an additional cluster. You want to migrate an existing volume to the new cluster as part of
the restructuring.
NOTE:
The volume remains fault-tolerant while being moved.
Cluster
P4000 SAN Solution user guide
209