Notes on using DP-VOLs

Volume Migration User Guide for VSP One Block 85

Version
10.5.x
File Size
100 KB
Audience
anonymous
Part Number
MK-26VSP1B039-01
ft:lastEdition
2026-03-06

The supported Volume Migration operations differ depending on the status of the pool to which the target DP-VOL belongs. In some cases, Volume Migration cannot be performed.

The following table shows the available Volume Migration operations for each combination of source and target volumes.

Source volume

Target volume

External volume

DP-VOL in Normal state

DP-VOL in Blocked state DP-VOL for which the pool is full

Normal

Data size will exceed the pool threshold after migration Pool will be full after migration

External volume

Available

Available

Available

Not available

Not available

Not available

DP-VOL in Normal state

Available

DP-VOL in Blocked state

Not available

Not available

Not available

DP-VOL in a pool that is full

Available

Available

Available

The following table shows whether Volume Migration operations are available for each status of capacity expansion.

Source volume Target Vvolume Volume Migration behavior
Volume Capacity expansion Volume Capacity expansion Volume Migration Canceling Volume Migration

DP-VOL

Capacity is expanding

DP-VOL

Capacity is expanding

Not available1

Not available

Capacity has expanded, or capacity is not expanded.

Not available1

Not available

Standard volume2 or external volume

None

Not available1

Not available

Capacity has expanded, or capacity is not expanded.

DP-VOL

Capacity is expanding

Not available1

Not available

Capacity has expanded, or capacity is not expanded.

Available

Available

Standard volume2 or external volume

None

Available

Available

Standard volume2 or external volume

None

DP-VOL

Capacity is expanding

Not available1

Not available

Capacity has expanded, or capacity is not expanded.

Available

Available

Standard volume2 or external volume

None

Available

Available

Notes:

  1. Confirm that capacity expansion is complete, and then migrate the volume again by specifying a volume whose capacity is the same as the one for the volume after expansion.
  2. The standard volume is supported by mainframe systems only.
  • If you create a Volume Migration pair by using a DP-VOL whose capacity is larger than 4,194,304MB (8,589,934,592 block), the differential data is managed in the pool to which the migration source and target volumes are associated. In this case, a maximum of four pages are required as the pool capacity for data managing differences, for each unit (4,123,168,604,160 bytes) of the volume.
  • When you create a Volume Migration pair by using a DP-VOL whose capacity is larger than 262,668 cylinders, the differential data is managed in the pool that the source and target volumes of the Volume Migration pair are associated with. In this case, one page of pool capacity is required for the differential data for each 4,096 cylinders of volume capacity.
  • If you create a Volume Migration pair during the processing of reclaiming zero data (including reclaiming zero data by the Write Same/Unmap command or rebalancing), the processing of reclaiming zero data will be suspended.
  • If reclaiming zero pages is in progress on a source or target volume during Volume Migration pair creation, the pair might not be created. Therefore, to create a pair, avoid the time period when reclaiming zero pages is in progress.
  • If the Write Same/Unmap command is issued for the source or target volume of the Volume Migration pair, the processing of reclaiming the zero data, by the Write Same/Unmap command, is not performed.
  • Even if rebalancing operates, the processing of reclaiming zero data by rebalancing is not performed for the source or target volume of the Volume Migration pair.
  • When you use a standard volume or an external volume as the source volume and a DP-VOL as the target volume, pages are allocated to the entire area of the DP-VOL (target volume).
  • When you use a DP-VOL as the target volume and the pool to which the target volume belongs is full, the migration of the volume fails. Confirm that the pool to which the target volume belongs has sufficient free space, and then migrate the volume.