
Volume migration requirements
All volumes for which data migration is to be performed must meet the following conditions:
• Migration-source and migration-target volumes exist within one of the following storage systems
(chassis):
• HP P9500
• XP24000/XP20000
• XP12000/XP10000/SVS200
• The emulation type, number of blocks, and size are the same for the source and target migration
volumes. However, note the following exceptions:
• If the micro version of XP24000/XP20000 is 60-03-20-00/00-xx or later and if both the mi-
gration source and the migration target volumes are THP/Smart volumes, the emulation type
can be between OPEN-V and OPEN-0V.
• If a volume whose emulation type is OPEN-V is a normal volume, and if the size of a migration
target volume is larger than a migration source volume, a volume that has the same size of the
migration source volume is re-created. The remaining capacity can be reused. If you set a
value for the property migration.plan.candidateCapacityGroupDisplayMaxCount
in the migration.properties file, you can specify how many volumes with a larger capacity
than the migration source volume to display, in addition to the volumes with the same capacity
as the migration source volume.
• The LDKC:CU:LDEV number for the volume is in the range from 00:00:00 to 00:FF:FF
• Volumes can be accessed, and are not reserved by other programs, Device Manager, or tasks.
• If the emulation type is not OPEN-V, and both the migration source and the migration target
volumes are normal, or both are CVS volumes.
Volume migration requirements related to volume type
Whether you can select a volume as a migration source or migration target depends on the volume
type. The following table shows which volume types can and cannot be selected as migration sources
and targets.
Table 10 Migration sources and targets by volume type and state
TargetSourceVolume Type, State
YYNormal volumes
YYExternal volumes
Y
Y
1
LUSE volumes
NNSmart volumes to which a data placement profile is applied
THP/Smart
volumes
2
NNVirtual volumes that are not associated with a THP/Smart pool
YYVolumes other than the above
Y
3
NTHP/Smart pools
NNTHP/Smart pool volumes
NNVolumes for which Cache Residency, Cache Residency for Mainframe is set
NNCommand Device
User Guide 125
Komentarze do niniejszej Instrukcji