Troubleshooting when migrations take a long time to complete

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

If it is taking a long time to migrate volumes, there might be a bottleneck. The following table lists the causes of bottlenecks and provides recommended action for each cause.

Note: The maximum number of simultaneous volume migration pairs is 256. When there are more than 256 migration pairs, the volume migration operations for the additional pairs are started after the migration of the first 256 pairs is complete.

Cause

Recommended action

The Host I/O Performance option of ShadowImage is enabled.

Disable the Host I/O Performance option of ShadowImage.

The Host I/O Performance option of ShadowImage for Mainframe is enabled.

Disable the Host I/O Performance option of ShadowImage for Mainframe.

Performance of the data drive or the external storage of the target volume is lower than one of the source volume.

Review the configuration.

The MP usage rate of all processors of the MP unit to which the source volume and the target volume are allocated exceeds 80%.

Review the configuration.

For details about how to check the MP usage rate, see the VSP One Block Administrator Guide.

An error occurs in the data drive or the external storage of the target volume.

Remove the error in the data drive or the external storage of the target volume.

An error occurs in the data drive or the external storage of the source volume.

Remove the error in the data drive or the external storage of the source volume.

The cache write pending rate of the MP unit to which the target volume belongs exceeds 60%.

Review the configuration.

The free space of the pool to which the target volume (DRS-VOL) belongs is no more than 120 GB.

Review the configuration.

And check whether SIM (DP pool is full: 622xxx, etc.) of Dynamic Provisioning pool failure is reported. If it is reported, follow the solutions of each SIM.

The Compatible Multiplicity Mode (local replica option No. 5) is enabled.

Review the configuration, and then disable the Compatible Multiplicity Mode (local replica option No. 5).