HP XP P9000 Auto LUN Software - Manual (Page 47)

Table 25 RAID Manager errors related to manual migration plans (continued)
Required Action Message Error Code
(SSB2)
Wait for the quick formatting to complete and then
migrate the volume. The migration source volume is undergoing quick
formatting. 2089
The volume cannot be migrated. Check the
configuration definition file. The migration source volume or the migration
target volume is a Mainframe Fibre Data Migration
volume. 208f
Wait for the quick formatting to complete and then
migrate the volume. The migration target volume is undergoing quick
formatting. 208A
Associate the Thin Provisioning or Smart Tiers
virtual volume with a pool, and then migrate the
volume. The migration target volume is the Thin
Provisioning or Smart Tiers virtual volume which
is not associated with a pool. 2090
Associate the Thin Provisioning or Smart Tiers
virtual volume with a pool, and then migrate the
volume. The migration source volume is the Thin
Provisioning or Smart Tiers virtual volume which
is not associated with a pool. 2091
None. This migration plan cannot be executed. The migration source volume is P-VOL of the Fast
Snap pair. 2093
None. This migration plan cannot be executed. The migration target volume and the migration
source volume are the Thin Provisioning or Smart 2095
Tiers virtual volumes that are associated with the
same pool.
Release the pair containing the migration source
volume, and then migrate the volume. The migration source volume is used by Continuous
Access Synchronous or Continuous Access Journal. 2096
The migration target volume is a Thin Provisioning
or Smart Tiers virtual volume.
You can attempt to execute the migration plan
about 40 minutes after the system configuration is
changed. The specified volume cannot be migrated because
the information about system configuration updates
due to volume migration is being backed up. 2098
None. This migration plan cannot be executed. The volume cannot be migrated if the emulation
type of either the migration source volume or the 2099
migration target volume is OPEN-0V. To migrate
the volume, ensure that the emulation type of both
volumes is OPEN-0V.
None. This migration plan cannot be executed. Migration is not allowed between the normal
volume specified as a LUSE volume and the Thin
Provisioning or Smart Tiers virtual volume. 209A
Wait until the capacity increase is completed.
Then, you must specify a target volume which has The migration source volume is a Thin Provisioning
or Smart Tiers virtual volume whose capacity is
increasing. 20A5
the same capacity as the volume whose capacity
is increased and migrate the volume.
Wait until the capacity increase is completed.
Then, you must specify a source volume which has The migration target volume is a Thin Provisioning
or Smart Tiers virtual volume whose capacity is
increasing. 20A6
the same capacity as the volume whose capacity
is increased and migrate the volume.
Wait until the Thin Provisioning or Smart Tiers
virtual volume reclaims zero pages, and then
migrate the volume. The migration source volume is a Thin Provisioning
or Smart Tiers virtual volume in which the zero
pages are being reclaimed. 20AD
Wait until the Thin Provisioning or Smart Tiers
virtual volume reclaims zero pages, and then
migrate the volume. The migration target volume is the Thin
Provisioning or Smart Tiers virtual volume in which
the zero pages are being reclaimed. 20AE
Set an LU path to the volume and then migrate the
volume. The volume specified as a migration source volume
has no LU path. 20BA
Troubleshooting when using RAID Manager 47