HP MPX200 Multifunction Router User Manual

Page 97

The MPX200 warns you if it detects any valid metadata on the destination LUN. However,
you can continue and use the LUN for migration if you are aware of the consequences and
want to continue with the job scheduling.

10. Specify whether the destination LUN is a thin-provisioned LUN, and if “yes”, then specify

whether to validate the data on that LUN.

11.

At the prompts, specify the I/O size, job name, migration group, and scheduling type.
a.

Enter an I/O size between 32 K and 1 MB to optimize migration performance based on
the storage array under consideration.

(Optional) Enter a job name (maximum of 64 characters) to identify the job.

(Optional) For an offline migration job, select the option to verify data after the migration
job is complete.

Select one of the available migration groups.

Select a Migration Start Time: 1=Now, 2=Delayed, 3=JobSerialScheduling,
or 4=ConfigureOnly.

•

If you choose Delayed, the CLI prompts you to input the date and time to begin job
execution.

•

If you choose JobSerialScheduling, the CLI prompts you to to assign a priority
level at which the job should be started when all the serial scheduled jobs are
executed. The priority can range between 1 and 256. The jobs with priority 1 are
executed before the scheduler executes jobs with priority 2.

The CLI informs you if the migration job is created successfully, and saves any changes you
have made.

The MPX200 then schedules a migration job based on your inputs.

See the preceding examples for the prompts and output of the migration add command for
offline, online, and remote data migration.

The following example shows the migration pause command:

MPX200 <1> (miguser) #> migration pause
Job Type Status Job Description
ID
--- ---- ------------------------ ------------------------------------
0 Offline Running ( 67%) HP HSV200-0:LUN1 to DGC RAID-1:LUN0
Please select a Job Id from the list above ('q' to quit): 0
All attribute values for that have been changed will now be saved.

The following example shows the migration resume command:

MPX200 <1> (miguser) #> migration resume
Job Type Status Job Description
ID
--- ---- ------------------------ ------------------------------------
0 Offline Paused ( 80%) HP HSV200-0:LUN1 to DGC RAID-1:LUN0
Please select a Job Id from the list above ('q' to quit): 0
All attribute values for that have been changed will now be saved.

The following example shows the migration rm command:

MPX200 <1> (miguser) #> migration rm
Job Type Status Job Description
ID
--- ---- ----------------------- ------------------------------------
0 Offline Running ( 5%) DGC RAID-2:VPG4:001 to HP HSV210-3
Please select a Job Id from the list above ('q' to quit): 0
Do you wish to continue with the operation(yes/no)? [No] yes
All attribute values for that have been changed will now be saved.

The following example shows the migration rm_peer command when the peer blade is down:

Commands