HP XP7 Auto LUN User Guide (TK915-96001)

Table 2 Candidates for source and target volumes by program product (continued)
Target Volume Candidate?Source Volume Candidate?Volume Type/StatusProgram Product
NoNoA volume disabled to be
used as a secondary volume
NoYesA volume that LU path is set
to
Remote Web Console
*When you specify the capacity of a volume in TB, GB, or MB, you cannot create a volume whose capacity is 4 TB
(4,398,046,511,104 byte). To create a volume whose capacity is 4 TB (4,398,046,511,104 byte), specify the
capacity in blocks.
The maximum capacity of the volume that can be used as a source volume or a target volume of Auto LUN differs
depending on units.
• When you specify the capacity in TB, you can specify up to 3.99.
• When you specify the capacity in GB, you can specify up to 4,095.99.
• When you specify the capacity in MB, you can specify up to 4,194,303.75.
• When you specify the capacity in blocks, you can specify up to 8,589,934,592.
Auto LUN with Thin Provisioning or Thin Provisioning Z virtual volumes
You can perform a migration plan on a Thin Provisioning or Thin Provisioning Z virtual volume or
an external volume. However, you cannot examine the estimated usage rate after the migration
because the usage rate of the virtual volume or the external volume cannot be collected.
The following table summarizes the internal volume and Thin Provisioning or Thin Provisioning Z
virtual volume (THP V-VOL) combinations under which a volume migration plan can be created.
Table 3 Permissible Internal and THP V-VOL combinations
THP V-VOL in Normal State as Target
Volume
Internal Volume as Target VolumeSource Volume
A migration plan can be created*.A migration plan can be created.Internal Volume
A migration plan can be created*. A
warning message appears if there is a
A migration plan can be created*.THP 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*.THP V-VOL in Blocked state due to full
capacity
possibility that the data size may
exceed the pool threshold after
migration.
*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)
The migration plan might not be executed if the storage system is experiencing a heavy workload.
When you specify a Thin Provisioning or Thin Provisioning Z virtual volume or an internal volume
which is used for the Continuous Access Synchronous pair as a source volume, see the Table 5 (page
14) table for specifying a target volume. The Continuous Access Synchronous or Continuous Access
Synchronous Z pair combination of an internal volume as a primary volume and a Thin Provisioning
or Thin Provisioning Z virtual volume as a secondary volume is not recommended.
If the capacity of a Thin Provisioning or Thin Provisioning Z 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
12 Requirements