HP XP Array Manager Software User Manual

Page 115

Advertising
background image

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

Target

Source

Volume Type, State

Y

Y

Normal volumes

Y

Y

External volumes

Y

Y

1

LUSE volumes

N

N

Smart volumes to which a data placement profile is applied

THP/Smart
volumes

2

N

N

Virtual volumes that are not associated with a THP/Smart pool

Y

Y

Volumes other than the above

Y

3

N

THP/Smart pools

N

N

THP/Smart pool volumes

N

N

Volumes for which Cache Residency, Cache Residency for Mainframe is set

N

N

Command Device

N

N

Volumes that are configured as a Cross-system Copy pair

N

Y

NAS system volumes

N

N

System Disk

N

N

Volumes that are configured for concurrent copying

N

N

On-demand device volumes

N

N

Intermediate volumes

User Guide

115

Advertising