HP P9000 Tiered Storage Manager Software 7.2 CLI Reference Guide

name=MegaTechXP12000-Primary
List of 1 MigrationGroup elements:
An instance of MigrationGroup(1 of 1)
name=MG011
canMigrate=Yes
notifyToURL=
remindAt=
reminderDescription=
arrayGroupSelectionRule=MinimumCoverage
arrayGroupAvoidanceOfMigrationGroups=MG012,MG013
description=MigrationGroup011
List of 1 Volume elements:
An instance of Volume(1 of 1)
controllerDeviceNumber=3:A7
emulationType=OPEN-V
CVS=Yes
capacityInKB=10,240,320
RAIDLevel=RAID5(3D+1P)
diskType=Unknown
controllerArrayGroupName=E9980-1
arrayGroupName=1-9-1
volumeStatus=Used
volumeLockStatus=Unlocked
hostNames=
Commands for creating tasks
This section explains the CLI commands for creating tasks.
CreateMigrationPlan
It is too time-consuming to create pairs of migration source LDEVs and migration target LDEVs
individually. You can use the CreateMigrationPlan command to make Tiered Storage Manager
software automatically select all the appropriate LDEVs for migration source LDEVs. The combination
of migration source and target LDEVs is output to the standard output as text data, or output to the
redirect file specified for the --output option. The text file created by using the
CreateMigrationPlan command is called a candidate migration plan.
The storage tier chosen as the migration target decides, among all the volumes in the migration group,
which volumes can be a candidate for the migration target. When you use the filtercondition
parameter to specify a volume filter condition, candidates for the migration target volume are chosen
based on that condition.
Volumes that are candidates for the migration target are chosen from the SLPR to which the migration
source volume belongs. Volumes that are candidates for the migration target are displayed in pairs
in the candidate migration plan with the applicable migration source volume.
There are comment lines (lines that begin with #) in the candidate migration plan. If multiple migration
target volume candidates exist, they are all shown within comment lines as well. Note that all volumes,
other than the first candidate, are chosen not only from the SLPR to which the migration source volume
belongs, but also from the other SLPRs.
Even if you cannot select candidates for the migration target volume for all the migration source
volumes, the candidate migration plans with selected migration targets will be created. However, in
such a case, an error will occur.
Details of CLI commands90