HP XP Racks - Manual (Page 134)

Reason preventing use as a migration target Displayed character string
The volume is one of the following:
• The volume is part of a Continuous Access Synchronous pair, and
the status is other than PSUS, PSUE, or PAIR
• The volume is part of an Hitachi TrueCopy for Mainframe pair,
and the status is suspended
• Applies only to P9500 Disk Array or XP24000/XP20000. The
volume is part of a Continuous Access Synchronous pair, and the
status is PAIR.
• Applies only to P9500 Disk Array or XP24000/XP20000. The
volume is part of an Hitachi TrueCopy for Mainframe pair, and
the status is Duplex.
Continuous Access Synchronous
(target)
Continuous Access XP Synchronous
(target)
The volume is one of the following:
• The volume is part of a Continuous Access Journal pair, and the
status is either COPY, or PAIR
• The volume is part of a Hitachi Universal Replicator for Mainframe
pair, and the status is either Pending duplex or Duplex
Continuous Access Journal (target)
Continuous Access XP Journal (target)
VOLSER is set for the volume. VOLSER (target)
Conditions for migration-target volumes when a
migration-source volume is a LUSE (Legacy mode)
If a LUSE volume is a migration source:
• A migration target must be selected for each volume that constitutes the LUSE.
• Target volumes must be either all internal or all external volumes.
• The LUSE volume can be migrated only if the target volume is not a THP/Smart volume.
• The emulation type, drive type, I/O suppression mode, cache mode, and CLPR of all migration
target volumes must be the same.
• For the Tiered Storage Manager to automatically determine migration target volumes, external
migration target volumes require that all of the volumes must be in the same external storage system
and the RAID level and SLPR (storage management logical partition) of all migration target volumes
be the same. If the micro version of XP24000/XP20000 is 60-05-12-00/00 or earlier, you must
not perform I/O operations on the volumes while migration is being executed.
Conditions when a migration target is a THP/Smart pool
(Legacy mode)
If a THP/Smart pool is the migration target:
• The status cannot be blocked.
• The number of virtual volumes in the THP/Smart pool must be fewer than 8,192.
• When the migration source is a THP/Smart volume, the source and target volumes must be in
different THP/Smart pools.
• The target THP/Smart pool must have more unused capacity than the source volume.
• The usage rate during data migration must not exceed the larger threshold value (threshold 1 or
threshold 2).
Operations in Legacy mode 134