HP XP P9000 Command View Advanced Edition Software Licenses - Manual (Page 221)

Target Source Volume Type, State
Legend:
• Y: Can be selected
• N: Cannot be selected
• [ ]: Names indicated are those for mainframe-based programs
Notes:
1. When the migration source volume is a LUSE, a migration target must be selected for each volume that
constitutes the LUSE. Migration target volumes must also satisfy the following conditions:
• All of the migration target volumes are internal volumes, or all are external volumes.
• The I/O suppression mode, cache mode, and CLPR of all migration target volumes are the same.
• Migration target volumes are not THP/Smart volumes.
Also, for Tiered Storage Manager to automatically create pairs for migration sources and migration targets,
we recommend that the following conditions also be met:
• If the migration target volumes are external volumes, all of the volumes are in the same external storage
system.
• The RAID level, drive type, and SLPR (storage management logical partition) of all migration target
volumes are the same.
Note that if you are migrating a LUSE volume of an XP24000/XP20000 storage system for which the
micro version is earlier than 60-05-12-00/00, you must not perform I/O operations on the volumes while
migration is being executed.
2. The migration source volumes and migration target volumes or pools are in different THP/Smart pools.
3. The following conditions must be satisfied:
• The status is not blocked.
• The THP/Smart pool has more unused capacity than the migration source volumes.
• Used THP/Smart pool capacity does not exceed both used thresholds 1 and 2 (even after a migration
is performed).
• THP/Smart pool subscription does not exceed the subscription warning and subscription limit (even
after a migration is performed).
• The number of virtual volumes in the THP/Smart pool is less than the limit (HP P9500: 63,232;
XP24000/XP20000: 8,192).
4. The CLPRs for the migration target and migration source are the same.
5. If an external storage system is locked (not Read/Write), it cannot be a migration source or migration
target.
Reasons why volumes cannot be used as migration sources or migration targets
If a volume cannot be used as a migration source or migration target and the reason for it is displayed,
one of the following character strings is displayed in the Migration Restrictions column.
Table 24 Volumes that cannot be used as migration sources or targets
Reason preventing use as a migration source or target Displayed character string
Cache Residency or Cache Residency Manager for Mainframe is set
for the volume.
Cache LUN XP
The volume is used as a command device. Command Device
User Guide 221