HP 3PAR StoreServ 7400 2-node HP 3PAR Management Console 4.3.0 Software User&a - Page 231

Migrating Data, Create Peer Volumes

Page 231 highlights

Migrating Data To use the Migrate Data wizard, the following conditions are required: • Super user role • Peer Motion license • Any Peer Motion configuration that includes a source and destination system whose status is Normal and that has no other admitted or importing volumes. Perform the following tasks before using the wizard: • Configure the data migration process by using the Create PM Configuration wizard. • Copy the desired settings from the source system to the destination system using the Copy Storage Settings and Configurations wizard. • Determine the best time to do the data migration. (A period of low usage is best, as migration incurs I/O latency.) The Migrate Data wizard guides you in migrating volumes from the source system to the destination system. The types of migration are as follows: • Online - Used to migrate virtual volumes that are exported to a host. This migration type requires unzoning the host system from the source system. • Minimally Disruptive - Used to migrate virtual volumes that are exported to a host. This migration type requires shutting down the host system for a short period of time. Additionally, the destination system must be running OS version 3.1.2 or higher. • Offline - Used to migrate virtual volumes that are not exported to a host. Exported volumes that you want to migrate must first be unexported to use offline migration. No unzoning or system shutdown is required. WARNING! On Windows Server 2012, Windows Server 2008 R2 and non-R2, do not use the mpclaim CLI command or attempt to display the MPIO information via the Disk Management GUI during the Peer Motion migration admitvv stage. Doing so will result in the host becoming unresponsive. The default migration type is online. NOTE: You will receive a warning message if either of the following licenses is missing: • Thin provisioning (which is needed to create a thin volume) • Domain (which is needed to add the volumes to a domain that is not the domain) When the migration host exists, there will be a warning to clean it up. To migrate data: 1. Select Peer Motion in the Manger Pane. 2. In the Common Actions Panel, click Migrate Data. The Migrate Data wizard appears. Create Peer Volumes 1. Select Online Migration, Minimally Disruptive Migration, or Offline Migration. Migrating Data 231

  • 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
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424

Migrating Data
To use the Migrate Data wizard, the following conditions are required:
Super user role
Peer Motion license
Any Peer Motion configuration that includes a source and destination system whose status is
Normal and that has no other admitted or importing volumes.
Perform the following tasks before using the wizard:
Configure the data migration process by using the
Create PM Configuration
wizard.
Copy the desired settings from the source system to the destination system using the
Copy
Storage Settings and Configurations
wizard.
Determine the best time to do the data migration. (A period of low usage is best, as migration
incurs I/O latency.)
The Migrate Data wizard guides you in migrating volumes from the source system to the destination
system. The types of migration are as follows:
Online
– Used to migrate virtual volumes that are exported to a host. This migration type
requires unzoning the host system from the source system.
Minimally Disruptive
– Used to migrate virtual volumes that are exported to a host. This
migration type requires shutting down the host system for a short period of time. Additionally,
the destination system must be running OS version 3.1.2 or higher.
Offline
– Used to migrate virtual volumes that are not exported to a host. Exported volumes
that you want to migrate must first be unexported to use offline migration. No unzoning or
system shutdown is required.
WARNING!
On Windows Server 2012, Windows Server 2008 R2 and non-R2, do not use the
mpclaim CLI command or attempt to display the MPIO information via the Disk Management GUI
during the Peer Motion migration admitvv stage. Doing so will result in the host becoming
unresponsive.
The default migration type is online.
NOTE:
You will receive a warning message if either of the following licenses is missing:
Thin provisioning (which is needed to create a thin volume)
Domain (which is needed to add the volumes to a domain that is not the <none> domain)
When the migration host exists, there will be a warning to clean it up.
To migrate data:
1.
Select
Peer Motion
in the Manger Pane.
2.
In the Common Actions Panel, click
Migrate Data
.
The
Migrate Data
wizard appears.
Create Peer Volumes
1.
Select
Online Migration
,
Minimally Disruptive Migration
, or
Offline Migration
.
Migrating Data
231