Auto Lun With Thin Provisioning Virtual Volumes - HP StorageWorks P9000 - Disk Arrays User Manual

Table 1 Candidates for Source and Target Volumes by Program Product (continued)
Program Product
Data Retention
Volume Security for
Mainframe

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 2 Permissible Internal and V-VOL Combinations
Source Volume
Internal Volume
V-VOL in Normal state
V-VOL in Blocked state due to full
capacity
The migration plan might not be executed if the storage system is experiencing a heavy workload.
When you specify a Thin Provisioning virtual volume or an internal volume which is used for the
Continuous Access Synchronous pair as a source volume, see the
specifying a target volume. The Continuous Access Synchronous pair combination of an internal
volume as a P-VOL and a Thin Provisioning virtual volume as an S-VOL is not recommended.
If the capacity of a Thin Provisioning virtual volume is increasing, this volume cannot be specified
as the source or target volume in an Auto LUN plan. It will also be impossible to reserve or remove
the reserve attribute for a virtual volume whose capacity is increasing. You must ensure that the
capacity of a Thin Provisioning virtual volume is not increasing if you plan on using that virtual
volume in an Auto LUN plan.
Volume Type/Status
A volume having the Read
Only or Protect attribute
turned on
A volume disabled to be
used as a secondary volume
A volume disabled to be
used as a secondary volume
Internal Volume as Target Volume
A migration plan can be created.
A migration plan can be created.
A migration plan can be created.
Source Volume Candidate?
No
No
No
V-VOL in Normal State as Target
Volume
A migration plan can be created.
If operations change the configuration
of the storage system after the initial
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
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
possibility that the data size may
exceed the pool threshold after
migration.
Table 3 (page 14)
Auto LUN with Thin Provisioning virtual volumes
Target Volume Candidate?
No
No
No
table for
13