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

Naming convention for SmartClone volumes, Naming and multiple identical disks in a server

Page 236 highlights

remote snapshot a volume, just like other volumes, so the space requirements for SmartClone volumes should take into account the space needed for their local and remote snapshots. • Number of SmartClone volumes-Plan the total number of SmartClone volumes you intend to create as part of your space requirements. Note that you can create up to 25 SmartClone volumes as one operation in the HP StorageWorks P4000 Centralized Management Console, and then repeat the process to create the desired number of SmartClone volumes. Use the CLI to create larger quantities of SmartClone volumes in a single operation. • Thin or full provisioning-The type of provisioning you select affects the amount of space required on the SAN, just as it does for regular volumes. • Data protection level-The data protection level of the source volume must be retained when creating SmartClone volumes, though you can change the data protection level after the SmartClone volumes are created. However, if you change the data protection level for any SmartClone volume, the data protection level for all replicated volumes automatically changes. Naming convention for SmartClone volumes A well-planned naming convention helps when you have many SmartClone volumes. Plan the naming ahead of time, since you cannot change volume or snapshot names after they have been created. You can design a custom naming convention when you create SmartClone volumes. Naming and multiple identical disks in a server Mounting multiple identical disks to servers typically requires that servers write new disk signatures to them. For example, VMware ESX servers require that resignaturing be enabled and will automatically name duplicate datastores. Most servers allow the duplicate disks to be renamed. Figure 82 Duplicate names on duplicate datastores in ESX Server . Server access Plan the servers you intend to assign to the SmartClone volumes. Configure the servers before creating the volumes, and you can then assign the servers when you create the volumes. See Chapter 16 on page 257. 236 SmartClone volumes

  • 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

remote snapshot a volume, just like other volumes, so the space requirements for SmartClone
volumes should take into account the space needed for their local and remote snapshots.
Number of SmartClone volumes
Plan the total number of SmartClone volumes you intend to
create as part of your space requirements.
Note that you can create up to 25 SmartClone volumes as one operation in the HP StorageWorks
P4000 Centralized Management Console, and then repeat the process to create the desired
number of SmartClone volumes.
Use the CLI to create larger quantities of SmartClone volumes in a single operation.
Thin or full provisioning
The type of provisioning you select affects the amount of space required
on the SAN, just as it does for regular volumes.
Data protection level
The data protection level of the source volume must be retained when cre-
ating SmartClone volumes, though you can change the data protection level after the SmartClone
volumes are created. However, if you change the data protection level for any SmartClone volume,
the data protection level for all replicated volumes automatically changes.
Naming convention for SmartClone volumes
A well-planned naming convention helps when you have many SmartClone volumes. Plan the naming
ahead of time, since you cannot change volume or snapshot names after they have been created.
You can design a custom naming convention when you create SmartClone volumes.
Naming and multiple identical disks in a server
Mounting multiple identical disks to servers typically requires that servers write new disk signatures
to them. For example, VMware ESX servers require that resignaturing be enabled and will automatically
name duplicate datastores. Most servers allow the duplicate disks to be renamed.
Figure 82 Duplicate names on duplicate datastores in ESX Server
.
Server access
Plan the servers you intend to assign to the SmartClone volumes. Configure the servers before creating
the volumes, and you can then assign the servers when you create the volumes. See
Chapter
16
on page 257.
SmartClone volumes
236