HP XP P9500 User Manual page 42

Hp p9000 auto lun user guide (av400-96385, october 2011)
Hide thumbs Also See for XP P9500:
Table of Contents

Advertisement

Table 18 RAID Manager Errors Related to Manual Migration Plans (continued)
Error Code
(SSB2)
2096
2098
2099
209A
20A5
20A6
20AD
20AE
20BA
20BB
22FA
22FB
2301
2302
2306
2309
42
Using RAID Manager for manual Auto LUN
Message
Tiers virtual volumes that are associated with the
same pool.
The migration source volume is used by Continuous
Access Synchronous or Continuous Access Journal.
The migration target volume is a Thin Provisioning
or Smart Tiers virtual volume.
The specified volume cannot be migrated because
the information about system configuration updates
due to volume migration is being backed up.
The volume cannot be migrated if the emulation
type of either the migration source volume or the
migration target volume is OPEN-0V. To migrate
the volume, ensure that the emulation type of both
volumes is OPEN-0V.
Migration is not allowed between the normal
volume specified as a LUSE volume and the Thin
Provisioning or Smart Tiers virtual volume.
The migration source volume is a Thin Provisioning
or Smart Tiers virtual volume whose capacity is
increasing.
The migration target volume is a Thin Provisioning
or Smart Tiers virtual volume whose capacity is
increasing.
The migration source volume is a Thin Provisioning
or Smart Tiers virtual volume in which the zero
data are being discarded.
The migration target volume is the Thin
Provisioning or Smart Tiers virtual volume in which
the zero data are being discarded.
The volume specified as a migration source volume
has no LU path.
The volume specified as a migration target volume
has no LU path.
The migration source volume is the primary or
secondary volume of Compatible FlashCopy.
The migration target volume is the primary or
secondary volume of Compatible FlashCopy.
Auto LUN is not installed on the storage system.
The shared memory which is necessary to use Auto
LUN is not installed or the initial setting is not
completed.
The LBA size does not match between the
migration target volume and the migration source
volume.
The maximum number of pairs which can be set
in the storage system is exceeded.
Required Action
Release the pair containing the migration source
volume, and then migrate the volume.
Perform the migration plan at least 40 minutes
after the system configuration is changed.
None. This migration plan cannot be executed.
None. This migration plan cannot be executed.
Wait until the capacity increase is completed.
Then, you must specify a target volume which has
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 same capacity as the volume whose capacity
is increased and migrate the volume.
Wait until the Thin Provisioning or Smart Tiers
virtual volume discards zero data, and then
migrate the volume.
Wait until the Thin Provisioning or Smart Tiers
virtual volume discards zero data, and then
migrate the volume.
Set an LU path to the volume and then migrate the
volume.
Set an LU path to the volume and then migrate the
volume.
Release the Compatible FlashCopy pair, and then
migrate the volume.
Release the Compatible FlashCopy pair, and then
migrate the volume.
Install Auto LUN, and then migrate the volume.
Check the configuration information of your
storage system.
None. This migration plan cannot be executed.
Reduce the number of pairs set in the storage
system, and then migrate the volume.

Advertisement

Table of Contents
loading

This manual is also suitable for:

Auto lun

Table of Contents