Prohibited source volumes
The following volumes and volume types cannot be used as source volumes for Volume Migration:
- Volumes configured as command devices
- Journal volumes used by Universal Replicator or Universal Replicator for Mainframe
- Volumes that are being moved by Command Control Interface
- Volumes used in Thin Image Advanced pairs
- Volumes with the vClone Parent attribute of Thin Image Advanced
You can specify volumes with the vClone attribute as Volume Migration source volumes. However, if a volume being used in a ShadowImage or Volume Migration pair exists in the Thin Image Advanced family containing the vClone volume you want to use, you cannot create the Volume Migration pair.
- Pool volumes used by Dynamic Provisioning or Dynamic Provisioning for Mainframe
- Volumes that are configured for Concurrent Copy (CC)
- Target volumes of Compatible FlashCopy® V2 or Compatible FlashCopy® SE
- Volumes with emulation type 3390-V
- Volumes for which the Soft Fence attribute is enabled
- Volumes that use the PPRC multi-target function of TrueCopy for Mainframe
- Volumes undergoing a Quick Format operation
- Volumes with the reserve attribute of global-active device
- Quorum disk volumes of global-active device
- External volumes for which Data Direct Mapping is enabled
- Deduplication system data volume (DSD-VOL)
- Volumes for which the capacity saving status is Deleting Volume(nn%) or Failed
Prohibited target volumes
The following volumes and volume types cannot be used as target volumes for Volume Migration:
- Volumes configured as command devices (devices reserved for use by hosts)
- Volumes assigned to ShadowImage pairs or TrueCopy pairs
- Volumes assigned to ShadowImage for Mainframe pairs or TrueCopy for Mainframe pairs
- Volumes (data volumes and journal volumes) used by Universal Replicator or Universal Replicator for Mainframe
- Volumes with the Read Only or Protect attributes set in Data Retention Utility, or volumes that are set so they cannot be used as secondary volumes
- Volumes that are being moved by Command Control Interface
- Volumes constituting Thin Image Advanced pairs
- Volumes with the vClone Parent attribute or the vClone attribute of Thin Image Advanced
- Pool volumes used by Dynamic Provisioning or Dynamic Provisioning for Mainframe
- Volumes that are configured for Concurrent Copy (CC)
- Target volumes of Compatible FlashCopy® V2 or Compatible FlashCopy® SE
- Volumes with emulation type 3390-V
- Volumes for which the Soft Fence attribute is enabled
- Volumes that use the PPRC multi-target function of TrueCopy for Mainframe
- Volumes in an abnormal state, or volumes in an inaccessible state
- Volumes undergoing a Quick Format operation
- 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(nn%) or Failed
Supported and prohibited source and target volumes for individual products
The following table lists the volumes and volume types and indicates whether the volumes can be source or target volumes for Volume Migration. 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.* |
Yes, but the target volume may not be associated with the same Dynamic Provisioning pool as the source volume. 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.* |
|
Pool volume |
No |
No |
|
|
Deduplication System Data Volume |
No |
No |
|
|
Capacity Saving function is enabled |
Yes |
Yes |
|
|
Capacity Saving Status is Deleting Volume(nn%) or Failed |
No |
No |
|
|
Dynamic Provisioning for Mainframe |
DP-VOL |
Yes, but you cannot specify the volume whose emulation type is 3390-V as the source volume. 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.* |
Yes, but the target volume may not be associated with the same Dynamic Provisioning for Mainframe pool as the source volume. You cannot specify the volume whose emulation type is 3390-V as the target volume. 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.* |
|
Pool volume |
No |
No |
|
|
Deduplication System Data Volume |
No |
No |
|
|
Capacity Saving function is enabled |
Yes |
Yes |
|
|
Capacity Saving Status of Capacity Saving Status is Deleting Volume, Deleting Volume(nn%), or Failed |
No |
No |
|
|
TrueCopy |
A volume in PSUS, PSUE, or PAIR status |
Yes |
No |
|
Deleted pair volumes from a storage system in a primary site |
Yes, if volumes are in SMPL status |
No |
|
|
Deleted secondary volume from a storage system in a primary site |
Yes, if volume is in SMPL status |
No |
|
|
Deleted primary volume from a storage system in a secondary site |
Yes, if volume is in SMPL status |
No |
|
|
TrueCopy for Mainframe |
A volume in suspended, simplex, or duplex status |
Yes |
No |
|
An external primary volume |
Yes, if volume is in suspended status |
No |
|
|
An external secondary volume |
Yes, if volume is in simplex status |
No |
|
|
Universal Replicator |
A data volume pair |
Yes. Note that the target volume must be in the same CLPR. |
No |
|
A journal volume |
No |
No |
|
|
A primary volume in any status |
Yes. Note that the target volume must be in the same CLPR. |
No |
|
|
A secondary volume in PSUS status |
Yes. Note that the target volume must be in the same CLPR. |
No |
|
|
A volume in COPY or PAIR status |
No |
No |
|
| Universal Replicator for Mainframe |
A data volume pair |
Yes. Note that the target volume must be in the same CLPR. |
No |
|
A journal volume |
No |
No |
|
|
A primary volume in any status |
Yes. Note that the target volume must be in the same CLPR. |
No |
|
|
A secondary volume in suspend status |
Yes. Note that the target volume must be in the same CLPR. |
No |
|
|
A volume in Pending Duplex or Duplex status |
No |
No |
|
|
Compatible XRC |
A normal volume |
No |
No |
|
Compatible FlashCopy® V2 and Compatible Software for IBM® FlashCopy® SE |
Source volume |
Yes |
No |
|
Target volume |
No |
No |
|
|
ShadowImage and ShadowImage for Mainframe |
SI pair volumes |
Yes |
No |
|
A primary volume in an SI pair in which the primary volume to secondary volume ratio is 1:1 or 1:2 |
Yes |
No |
|
|
A primary volume in an SI pair in which the primary volume to secondary volume ratio is 1:3 |
No |
No |
|
|
A secondary volume in anSI pair in which 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 |
|
|
ShadowImage |
A volume in COPY(SP)/COPY or PSUS(SP)/PSUS status |
No |
No |
|
ShadowImage for Mainframe |
A volume in SP-Pend/TRANS, V-Split/SUSPVS status |
No |
No |
|
CCI |
A volume undergoing a Volume Migrationoperation via CCI |
No |
No |
|
A volume that LU path is not set to, or that is not set for a namespace in the NVMe-oF connection environment |
Yes |
No |
|
|
Volume Retention Manager |
A volume having the Read Only or Protect attribute turned on |
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 |
|
| Device Manager - Storage Navigator |
A volume that LU path is set to, or that is set for a namespace in the NVMe-oF connection environment |
Yes |
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 |
|
|
* For the maximum capacity of a Dynamic Provisioning or Dynamic Provisioning for Mainframe virtual volume, see the Provisioning Guide. |
|||