Supported and prohibited source and target volumes

Virtual Storage Platform One Block Volume Migration User Guide

Version
10.3.x
Audience
anonymous
Part Number
MK-23VSP1B018-01

Prohibited source volumes

The following list includes volumes and volume types that cannot be used as source volumes for Volume Migration:

  • Volumes configured as command devices
  • Journal volumes used by Universal Replicator
  • Volumes that are being moved by Command Control Interface
  • Volumes and virtual volumes constituting Thin Image pairs
  • Pool volumes used by Dynamic Provisioning
  • Volumes with reserve attribute of global-active device
  • Quorum disk volumes of global-active device
  • External volumes of which Data Direct Mapping attribute is enabled
  • Deduplication System Data Volume
  • Volumes for which the capacity saving status is Deleting Volume, Deleting Volume (nn%), or Failed

Prohibited target volumes

The following list includes volumes and volume types that cannot be used as target volumes for Volume Migration:

  • Volumes configured as command devices (devices reserved for use by hosts)
  • Volumes assigned to pairs of ShadowImage or remote copy (TrueCopy)
  • Volumes (data volumes and journal volumes) used by Universal Replicator
  • Volumes with the Read Only or Protect attributes set in the Data Retention Utility, or volumes that are set to unable to use as secondary volume
  • Volumes that are being moved by Command Control Interface
  • Volumes and virtual volumes constituting Thin Image pairs
  • Pool volumes used by Dynamic Provisioning
  • Volumes in abnormal state, or volumes in inaccessible state
  • Volumes to which LU path is not set or that are not assigned as namespaces for NVMe
  • Volumes that constituting global-active device pair, and volumes with reserve attribute of global-active device
  • Quorum disk volumes of global-active device
  • External volumes of which Data Direct Mapping attribute is enabled
  • Deduplication System Data Volume
  • Volumes for which the capacity saving status is Deleting Volume, Deleting Volume (nn%), or Failed

Supported and prohibited source and target volumes for individual products

The following table lists the volumes and volume types that can and cannot be considered as candidates for source and/or target volumes for Volume Migration operation. The table is categorized by product.

Product

Volume Type/Status

Source Volume Candidate?

Target Volume Candidate?

Dynamic Provisioning

DP-VOL

Yes

Note that the maximum capacity of DP-VOL which can be used as the source volume is the same size of the maximum capacity of DP-VOL.1

Yes, but the target volume may not be associated with the same Dynamic Provisioning pool as the source volume.2

Note that the maximum capacity of DP-VOL which can be used as the target volume is the same size of the maximum capacity of DP-VOL.1

Pool volume

No

No

Deduplication System Data Volume

No

No

Capacity Saving function is enabled

Yes

Yes

Capacity Saving Status is Deleting Volume, Deleting Volume(nn%), or Failed

No

No

TrueCopy

A volume in PSUS, PSUE, or PAIR status

Yes

No

Universal Replicator

A journal volume

No

No

A volume in COPY or PAIR status

No

No

ShadowImage

SI pair volumes

Yes

No

A primary volume in an SI pair where the primary volume to secondary volume ratio is 1:1 or 1:2

Yes

No

A primary volume in an SI pair where the primary volume to secondary volume ratio is 1:3

No

No

A secondary volume in anSI pair where the primary volume to secondary volume ratio is 1:1, 1:2, or 1:3

Yes

No

A primary volume in an L1 cascaded SI pair where the primary volume to secondary volume ratio is 1:1 or 1:2

Yes

No

A primary volume in an L1 cascaded SI pair where the primary volume to secondary volume ratio is 1:3

No

No

A primary volume in an L2 cascaded SI pair where the primary volume to secondary volume ratio is 1:1

Yes

No

A primary volume in an L2 cascaded SI pair where the primary volume to secondary volume ratio is 1:2

No

No

A secondary volume in an L1 cascaded SI pair where the primary volume to secondary volume ratio is 1:1, 1:2, or 1:3

Yes

No

A secondary volume in an L2 cascaded SI pair where the primary volume to secondary volume ratio is 1:1 or 1:2

No

No

A volume in COPY(SP) or PSUS(SP) status

No

No

CCI

A volume undergoing a Volume Migration operation via CCI

No

No

Data Retention Utility

A volume having the Read Only or Protect attribute turned on

No

No

A volume disabled to be used as a secondary volume

No

No

Global-active device

A volume that has the reserve attribute

No

No

A quorum disk volume

No

No

A volume in PSUS, PSUE, SSUS, or SSWS status

Yes

No

  1. For the maximum capacity of the Dynamic Provisioning virtual volume, see the Provisioning Guide.
  2. If the DKCMAIN firmware version is A3-03-01-XX(TBD SVOS10.3 24_9E) or later, you can use CCI to specify for the target volume a volume that is associated with the same Dynamic Provisioning pool as the source volume. Use the same pool for the source and target volumes only when the load on the storage system is low because the load on the pool tends to increase in this situation.