Volume types that can be shared with TrueCopy

TrueCopy® User Guide

Version
9.8.7
Audience
anonymous
Part Number
MK-98RD9022-18

You can use other software product volumes as TrueCopy P-VOL or S-VOL, if you have those other software products.

The following table lists the types of volumes by software product and indicates whether the volume can also be used as a TC P-VOL or a TC S-VOL.

Volume type

Used as TC P-VOL?

Used as TC S-VOL?

Active flash

DP-VOL

Yes

Yes

Pool-VOL

No

No

Cache Residency Manager (VSP 5000 series)

Cache Residency Manager volume

Yes

Yes

Virtual LUN

Virtual LUN volume

Yes

Yes

Thin Image 6

P-VOL in all statuses except RCPY

Yes

Yes

P-VOL in RCPY status

No

No

S-VOL

No

No

Pool-VOL

No

No

Thin Image Advanced 6

P-VOL in all statuses except RCPY

Yes Yes

P-VOL in RCPY status

No No

S-VOL

No No

Cross-OS File Exchange

Volume usable by both mainframe and open systems

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

DP-VOL

Yes

Yes

Pool-VOL

No

No

V-VOL with capacity saving enabled

Yes

Yes

Deduplication system data volume

No

No

Dynamic Tiering

DP-VOL

Yes

Yes

Pool-VOL

No

No

Global-active device (GAD)

P-VOL

No

No

S-VOL

No

No

Quorum disk

No

No

Volume with reserve attribute for S-VOL

No

No

Global storage virtualization

Volumes in a virtual storage machine1

Yes

Yes

LUN Manager

Volume to which an LU path is defined

Yes

Yes

Volume defined as a namespace for NVMe

Yes9

Yes9

Volume that is protected by namespace security for NVMe-oF

Yes9

Yes9

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

Yes7

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

Yes7

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

Yes

No

S-VOL (none of the above)

No

No

Reserved volume (VSP 5000 series)

No

No

Universal Replicator (UR)

P-VOL in COPY status

No

No

P-VOL in PAIR status

Yes2, 8, 10

No3

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

Yes2, 8,10

No3

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

Yes2, 8, 10

No3

S-VOL in COPY status

No

No

S-VOL in PAIR status

No

No

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

Yes2, 8, 10

No

S-VOL in SSWS status

Yes2, 8, 10

No

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

Yes2, 8, 10

No

Journal Volume (VSP Gx00 models and VSP Fx00 models, VSP E series)

No

No

Universal Volume Manager

Mapped external volume

Yes

Yes

Virtual Partition Manager (VPM)

Volume belonging to the Virtual Partition Manager CLPR

Yes

Yes

Volume Migration5

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.)4

Source volume (after volume migration is finished)

Yes

Yes

Target volume

No

No

Reserved volume (VSP 5000 series)

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. For VSP 5000 series, the volume shared with two UR pairs cannot be used with TC in a 3DC multi-target or 3DC cascade configuration with the three UR sites.
  3. (VSP 5000 series) The volume can be used only when you resynchronize a TC pair or perform a CCI horc takeover operation.
  4. If the TC S-VOL is a DP-VOL, the TC pair cannot be created. Create the TC pair after completing volume migration or stopping the Volume Migration operation.
  5. For more information about using Volume Migration, contact customer support.
  6. For the node volume and the leaf volume of Thin Image or Thin Image Advanced, see the description of S-VOL, not P-VOL.
  7. (VSP E series) When both TrueCopy P-VOL and S-VOL are Dynamic Provisioning virtual volumes (DP-VOL), the TC S-VOL cannot be used as a P-VOL of a ShadowImage pair.
  8. Three data center (3DC) configurations with TC and UR using a volume connected to a host via NVMe-oF are supported by the following storage system and DKCMAIN microcode versions: VSP 5000 series: 90-09-21-xx/xx or later. For details, see the Hitachi Universal Replicator User Guide.
  9. Volumes that are set as NVMe Namespaces can be used for TrueCopy pair volumes with DKCMAIN version 90-08-21 or later (VSP 5000 series) or 93-06-61 or later (VSP E series).
  10. (VSP 5000 series) The pair creation or the pair resync operation is available.