Volume types that can be shared with TrueCopy

Virtual LUN

Virtual LUN volume

Yes

Yes

P-VOL in all statuses except RCPY

Yes

Yes

P-VOL in RCPY status

No

No

Volume with the vClone Parent attribute

Yes

Yes

Volume with the vClone attribute

Yes

Yes

S-VOL

No

No

Data Retention Utility

Volume with Read/Write attribute

Yes

Yes

Volume with Read Only attribute

Yes

Yes

Volume with Protect attribute

Yes

Yes

Volume that is disabled for use as an S-VOL

Yes

No

Dynamic Provisioning

V-VOL with the data direct mapping attribute

Yes

Yes

Pool-VOL

No

No

V-VOL with capacity saving enabled

Yes

Yes

Deduplication system data volume

No

No

Global-active device (GAD)

P-VOL

No

No

S-VOL

No

No

Quorum disk

No

No

Volume with reserve attribute for GAD

No

No

Global storage virtualization

Volumes in a virtual storage machine¹

Yes

Yes

LUN Manager

Volume to which an LU path is defined

Yes

Yes

Volume defined as a namespace for NVMe

Yes

Yes

Volume that is protected by namespace security for NVMe-oF

Yes

Yes

Volume to which no LU path is defined or a volume that is not defined as a namespace for NVMe

No

No

Volume to which LUN security is applied

Yes

Yes

ShadowImage (SI)

P-VOL in PSUS (Delete pair to RCU) status

Yes

Yes⁵

P-VOL in COPY(RS-R)/RCPY status

No

No

SI P-VOL is also used as a UR P-VOL or S-VOL

No

No

P-VOL (none of the above)

Yes

Yes⁵

S-VOL in PSUS (Delete pair to RCU) status

Yes

No

S-VOL (none of the above)

No

No

Universal Replicator (UR)⁷

P-VOL in COPY status

No

No

P-VOL in PAIR status

Yes^{2, 6}

No

P-VOL in PSUS (Delete pair to RCU) status

Yes^{2, 6}

No

P-VOL in PSUE (pair suspended-error) status

Yes^{2, 6}

No

S-VOL in COPY status

No

No

S-VOL in PAIR status

No

No

S-VOL in PSUS (Delete pair to RCU) status

Yes^{2, 6}

No

S-VOL in SSWS status

Yes^{2, 6}

No

S-VOL in PSUE (pair suspended-error) status

Yes^{2, 6}

No

Journal Volume

No

No

Universal Volume Manager

Mapped external volume

Yes

Yes

Volume Migration

Source volume (when volume migration is in progress)

Yes. (If the source volume is a P-VOL, volume migration will stop.)

Yes. (If the source volume is an S-VOL, volume migration will stop.)³

Source volume (after volume migration is finished)

Yes

Yes

Target volume

No

No

Notes:

1. The volume whose virtual LDEV ID is deleted cannot be used as pair volume of TC.
2. A volume used with TC cannot be used as a volume shared with two UR pairs.
3. If the TC S-VOL is a virtual volume enabled with capacity saving, the TC pair cannot be created. Create the TC pair after completing volume migration or stopping the Volume Migration operation.
4. For the node volume and the leaf volume of Thin Image Advanced, see the description of S-VOL, not P-VOL.
5. When both TrueCopy P-VOL and S-VOL are virtual volume enabled with capacity saving (DP-VOL), the TC S-VOL can be used as a P-VOL of a ShadowImage pair. However, if you want to use a DP-VOL already used as an SI P-VOL as a TC S-VOL, delete the SI pair before creating a TC pair.
6. Three data center (3DC) configurations (cascade, multi-target, and delta resync) with TC and UR using a volume connected to a host via NVMe-oF are not supported.
7. If a volume is paired with a VSP One SDS Block volume as a UR pair, the volume cannot be used for a TC pair.