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

Table 2 Candidates for Source and Target Volumes by Program Product (continued)
Target Volume Candidate? Source Volume Candidate? Volume Type/Status Program Product
No No A volume with data stored
in cache Cache Residency and Cache
Residency Z
No Yes Individual LDEV within
expanded LU LUN Expansion (LUSE)
No Yes. If all LDEVs are used,
make sure that an adequate All LDEVs in an expanded
LU
amount of target volumes
are reserved.
No No A volume undergoing an
Auto LUN operation via
RAID Manager RAID Manager
No No A volume having the Read
Only or Protect attribute
turned on Volume Retention
No No A volume having the Read
Only or Protect attribute
turned on Data Retention
No No A volume disabled to be
used as a secondary volume
Auto LUN with Thin Provisioning virtual volumes
You can perform a manual migration plan on a Thin Provisioning virtual volume or an external
volume. However, you cannot examine the estimated usage rate after the migration because the
usage rate of an external volume cannot be collected.
The following table summarizes the internal volume and Thin Provisioning virtual volume (V-VOL)
combinations under which a volume migration plan can be created.
Table 3 Permissible Internal and V-VOL Combinations
V-VOL in Normal State as Target
Volume Internal Volume as Target Volume Source Volume
A migration plan can be created.
If operations change the configuration
of the storage system after the initial A migration plan can be created. Internal Volume
volume migration, any subsequent
volume migration must be executed at
an interval which is calculated by the
following formula:
(Pool_Capacity x 3 (seconds)) + 40
(minutes)
A migration plan can be created. A
warning message appears if there is a A migration plan can be created. V-VOL in Normal state
possibility that the data size may
exceed the pool threshold after
migration.
A migration plan can be created. A
warning message appears if there is a A migration plan can be created. V-VOL in Blocked state due to full
capacity
possibility that the data size may
exceed the pool threshold after
migration.
The migration plan might not be executed if the storage system is experiencing a heavy workload.
Auto LUN with Thin Provisioning virtual volumes 13