0% found this document useful (0 votes)

9 views80 pages

ShadowImage User Guide

The ShadowImage User Guide provides detailed information on Hitachi's ShadowImage technology, which allows for local mirroring of data volumes to create full copies without interrupting production I/O. It outlines the process of creating volume pairs, the necessary hardware and software components, and the tools for managing these operations, including HDvM - SN and CCI. Additionally, it discusses system requirements, recommended usage, and differences between ShadowImage and Thin Image for data backup and recovery.

Uploaded by

Sajesh P

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

9 views80 pages

ShadowImage User Guide

Uploaded by

Sajesh P

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

6/16/25, 6:04 PM ShadowImage User Guide

ShadowImage User Guide

9.8.7

SVOS

MK-98RD9021-17

Last updated: 2023-10-30

Generated from docs.hitachivantara.com

Overview of ShadowImage
Hitachi ShadowImage® (SI) uses local mirroring technology that your site can use to create and maintain full copies of
data volumes within a storage system.

Using SI volume copies (for example: backups, secondary host applications, data mining, testing) allows you to continue
working without stopping host application input/output (I/O) in the production volume.

How ShadowImage works

A pair is created when you:

Select a volume that you want to duplicate. This becomes the primary volume (P-VOL).
Identify another volume to contain the copy. This becomes the secondary volume (S-VOL).
Associate the P-VOL and S-VOLs.
Perform the initial copy.

During the initial copy, the P-VOL remains available for read/write. After the copy is completed, subsequent write
operations to the P-VOL are regularly duplicated to the S-VOL.

The P-VOL and S-VOLs remain paired until they are split. The P-VOL for a split pair continues to be updated but data in
the S-VOL remains as it was at the time of the split. The S-VOL contains a mirror image of the original volume at that point
in time.

S-VOL data is consistent and usable. It is available for read/write access by secondary host applications.
Changes to the P-VOLs and S-VOLs are managed by differential bitmaps.
You can pair the volumes again by resynchronizing the update data from P-VOL to S-VOL, or from S-VOL to P-
VOL.

Note:In Device Manager - Storage Navigator (HDvM - SN), the source volume is called P-VOL and the destination volume
is called S-VOL.

Hardware and software components

A typical configuration consists of a storage system, a host connected to the storage system, the SI software, a primary or
source volume (P-VOL), and secondary or target volumes (S-VOLs), and interface tools for operating SI.

The following image shows a typical configuration.

Interface tools

Interface tools used to operate ShadowImage include the following:

HDvM - SN graphical user interface (GUI)

Command Control Interface (CCI)

If a logical volume assigned as a namespace on the NVM subsystem with the NVMe-oF connection is specified as
a P-VOL or an S-VOL of the SI pair, CCI must be used. The pair operations cannot be performed from HDvM - SN.

Device Manager - Storage Navigator

Use HDvM - SN to perform the following tasks:

Install the SI license key, which enables it.

Configure the storage system.
Perform the initial and update copy operations.

HDvM - SN communicates with the storage system over defined TCP/IP connections. HDvM - SN is LAN-attached to the
storage system.

For more information about using HDvM - SN, see the System Administrator Guide.

Command Control Interface

CCI is a tool that uses the command line interface to perform operations that are necessary to use storage systems. You
can either run pair commands directly from a host, or you can script CCI commands to have pair operations performed
automatically.

For more information about using CCI, see the Command Control Interface User and Reference Guide.

Consistency groups

Use a consistency group (CTG) to perform tasks on the SI pairs in the group at the same time, including CTG pair-split
tasks. Using a CTG to perform tasks ensures the consistency of the pair status for all pairs in the group.

Related reference
Supported ShadowImage consistency group actions and options

Volume pairs

A volume pair consists of a P-VOL and one to three layer-1 (L1) pair S-VOLs.

Because S-VOLs are updated asynchronously, the P-VOL and S-VOLs might not be identical except immediately after a
split. If a pair is split, any further updates to the P-VOL will not be reflected in the S-VOL.

Splitting or deleting a pair allows the host access to the S-VOL.

Related concepts
Creating ShadowImage pairs
Splitting ShadowImage pairs
Resynchronizing ShadowImage pairs
Deleting ShadowImage pairs

Cascaded pairs

Cascaded pairs are volume pairs created in the first and second layer. A pair made up of an L1 S-VOL and a layer-2 (L2)
S-VOL is an L2 pair. You can pair each SI L1 S-VOL with two L2 S-VOLs. You can pair nine L1 and L2 S-VOLs with a P-
VOL.

The following image shows the structure of cascaded pairs.

In cascaded pairs, the P-VOL for an L1 pair is a root volume and the S-VOL is a node volume. The P-VOL for an L2 pair is
the S-VOL of an L1 pair, a node volume, and the S-VOL is a leaf volume.

Initial and update copy operations

Creating a pair causes the storage system to start the initial copy. During the initial copy, the P-VOL remains available for
read and write operations from the host. After the initial copy, the storage system periodically copies the differential data in
the P-VOL to the S-VOL. Subsequent write operations to the P-VOL are regularly duplicated to the S-VOL. The data in the
P-VOL is copied to the S-VOL.

Initial copy workflow

Initial copy is performed when you create a copy pair. Data on the P-VOL is copied to the S-VOL for the initial copy using
the following workflow.

The storage system goes through the following workflow to create an initial copy:

1. The S-VOLs are not paired. You create the copy pair.
Note:The storage system accepts read/write for unpaired volumes.
2. The initial copy is in progress (COPY(PD)/COPY status). The storage system copies the P-VOL data to the S-VOL.
3. The initial copy is complete and the volumes are paired (PAIR status).
Note:Data consistency is not ensured for SI pairs in PAIR status.

A P-VOL continues receiving updates from the host during the initial copy.

Related concepts
Creating ShadowImage pairs

Update copy workflow

Update copy is performed to asynchronously copy new data (differential data) from the P-VOL of a copy volume to the S-
VOL.

The storage system goes through the following process to create an update copy:

1. The storage system marks I/O to the P-VOL in PAIR status as differential data and stores the location of the data in
bitmaps for transfer to the S-VOL.
2. After there are write I/O operations to a P-VOL, the storage system starts the update copy operation.
Note:The timing of the update copy operation is based on the amount of differential data that accumulates and the
elapsed time since the previous update.

The following image shows the update copy operation.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 6/80
6/16/25, 6:04 PM ShadowImage User Guide
Updated data is copied asynchronously. Therefore, even when the initial copy completes and the pair status changes to
PAIR, data in the P-VOL and in the S-VOL might not be the same. If you want data in the P-VOL and in the S-VOL to
match at a certain date and time, you must split the pair.

Note:Data in the P-VOL and in the S-VOL might not be the same if the host did not write data to the P-VOL during copy
operation. To ensure matching data in the P-VOL and the S-VOL, you must split the pair to change its status to PSUS.
Related concepts
Splitting ShadowImage pairs

Data backup and recovery differences between ShadowImage and Thin Image

The following table lists and describes the differences between data backup and recovery for ShadowImage (SI) and Thin
Image (HTI).
Item ShadowImage Thin Image

P-VOL physical failures such as hard P-VOL data can be recovered using P-VOL data cannot be guaranteed.
disks the S-VOL.

P-VOL logical failures such as data P-VOL data can be recovered using P-VOL data can be recovered using
update errors or viruses the S-VOL. the S-VOL.

Capacity required for backup More capacity is required for backup Less capacity is required for backups
because all data in the P-VOL is because only differential data of the P-
retained. VOL is retained.1

Impact on P-VOL performance when P-VOL performance is not affected P-VOL performance is affected
accessing backed up data because the P-VOL and the S-VOL because data in the P-VOL is shared.2
can be disconnected.

S-VOL or pool physical failures If a physical failure occurs in an S- If a physical failure occurs in a pool3,
VOL, data in the S-VOL cannot be data in all S-VOLs that use the pool
guaranteed. cannot be guaranteed.

Notes:

1. For snapshot pairs. When a cloned pair is created, all data in the P-VOL is retained and more capacity is required
for backup.
2. For snapshot pairs. When a cloned pair is created, the P-VOL and the S-VOL can be separated and the P-VOL
performance is not affected.
3. When a pool is full (the depletion threshold is exceeded in a pool for which the capacity for TI pairs is limited),
data in all S-VOLs using the pool cannot be guaranteed.

Recommended usage

To maintain backed up data for long periods, save it on magnetic tapes or other media. For temporary backups use HTI or
SI. When backing up data to magnetic tapes use SI. To reduce the capacity necessary for backups use HTI, but note that
this affects P-VOL performance.

Use SI to minimize the impact from P-VOL physical failures. If you need four or more generations of backups, use both SI
and HTI as shown in the following figure.

Use HTI to minimize P-VOL logical failures.

ShadowImage system requirements and

planning
Before getting started with SI storage systems, review the system requirements and planning tasks.

System requirements

The following table describes requirements for SI.

Item Requirement

SI license capacity The installed license capacity must be greater than or equal to the combined size of all P-
VOLs and S-VOLs.

For more information about license capacity requirements, see ShadowImage licensed
capacity requirements.

License key Must be installed.

RAID level RAID 1, RAID 5, RAID 6

HDvM - SN Required

CCI Required if you are running commands through an in-band Fibre Channel connection.
Otherwise, CCI is not required.

Item Requirement

For more information about CCI and running commands through an in-band Fibre Channel
connection, see the Command Control Interface User and Reference Guide.

Pair volumes The pair volumes.

Values:

Number of P-VOLs per S-VOL: 1

Number of S-VOLs per P-VOL:

L1 pairs: 1 to 3

L2 pairs: 1 or 2

For more information about cascading pairs, see Cascaded pairs.

Volume Capacity: The P-VOL and S-VOL must be the same size in blocks.

If the capacity is displayed in GB or TB, a small difference between P-VOL and S-

VOL capacity might not be displayed. To view the capacity in blocks in HDvM - SN,
select Options > Capacity Unit > block in the Logical Devices window.

The maximum size of the P-VOLs is the maximum size of the volumes that can be
created in a storage system. The maximum size of the S-VOLs is also the maximum
size of the volumes that can be created in a storage system. However, the total size
of the P-VOLs and the S-VOLs cannot exceed the maximum size of the volumes
that can be created in a storage system. For details, see the Provisioning Guide for
your system.
Supported volume types:
Internal volumes
External volumes

Note: Universal Volume Manager license is required.

Custom-sized volumes (VSP 5000 series)

Note:VLL is required. Pair volumes must have the same capacity and
emulation type.
Mirror Unit number (MU number):

Values:

L1 pairs: 0, 1, or 2
L2 pairs: 1 or 2
You can share volumes with other software applications (see Sharing
ShadowImage volumes).

You cannot use the following volumes as pair volumes:

UR journal volumes
Virtual volumes except Dynamic Provisioning (HDP) volumes
Pool volumes
Volumes that belong to parity groups for which accelerated compression is
enabled
Deduplication system data volume
The value of the T10 PI attribute must be the same for the P-VOL and S-VOL.
LU paths or namespaces on the NVM subsystem with an NVM subsystem port
added for NVMe must be defined on both the P-VOL and S-VOL before SI paired
volumes are created. In addition, while the P-VOL and S-VOL are used as paired
volumes, at least one LU path or namespaces on the NVM subsystem with an NVM
subsystem port added for NVMe must be defined on both the P-VOL and S-VOL.

Maximum number of pairs Pairs per storage system (if you pair one S-VOL per P-VOL):

VSP 5000 series: 32,768

VSP E990, VSP E1090: 32,768
VSP E790: 24,576

Item Requirement

VSP E590: 16,384

Note:The maximum is dependent on the amount of installed shared memory.

For more information about installed shared memory, see Maximum number of tables
based on installed shared memory.

For more information about the number of pairs your VSP 5000 series configuration
supports, see Workflow for determining the maximum number of ShadowImage pairs.

Consistency groups Maximum per storage system: 2,048 (including SI, SIz, Thin Image, and Thin Image
Advanced)

Maximum for SI and SIz: 128

Note: You cannot place SI, SIz, Thin Image, and Thin Image Advanced pairs in the same
CTG.

Maximum SI pairs per CTG:

VSP 5000 series: 8,192

VSP E series: 8,192

CTG IDs are numbers between 0 and 7FF. CTG IDs 00 to 7F (or 0 to 127) are used for SI,
SIz, Thin Image, and Thin Image Advanced. CTG IDs 80 to 7FF (or 128 to 2,047) are used
for Thin Image and Thin Image Advanced only.

ShadowImage licensed capacity requirements

The capacity of P-VOLs and S-VOLs must be less than or equal to the installed license capacity. Volume capacity is
counted only once, even if you use the volume more than once. You do not need to multiply the capacity by the number of
times a volume is used (For example, a P-VOL used as the source volume for three pairs is counted only once).

For a normal volume, the total volume capacity is counted, but for a DP-VOL (a virtual volume used in Dynamic
Provisioning, Dynamic Tiering, or active flash), the pool capacity being used by the volume is counted. For the volume with
the capacity saving enabled, the licensed capacity is the data capacity before saving. The pair with the available licensed
capacity exceeded cannot be created.

After you start performing pair tasks, monitor your capacity requirements to keep the used capacity within the capacity of
the installed license.

You can continue using ShadowImage volumes in pairs for 30 days after licensed capacity is exceeded, regardless of
whether a normal volume or a DP-VOL is used. After 30 days, the only allowed operation is pair deletion. The problem of
exceeding the licensed capacity can be resolved by reducing the capacity to less than or equal to the licensed capacity.
However, the warning message will remain displayed. The warning message is updated once a day, therefore when the
problem is resolved, the warning message will automatically disappear within 24 hours.

For more information about licenses, see the System Administrator Guide.

Workflow for determining the maximum number of ShadowImage pairs

Complete the following steps to determine the maximum number of SI pairs that you can create in your storage system:

1. Determine the number of differential and pair tables your storage system needs to create SI pairs:
Calculate the number of tables for volumes.
Query the number of differential tables required to create SI pairs.
Note:These calculations assume that you are only using SI in the system.
2. Determine the maximum number of SI pairs that you can create on your storage system.

Related reference
Differential tables and pair tables
Maximum number of tables based on installed shared memory

Differential tables and pair tables

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 10/80
6/16/25, 6:04 PM ShadowImage User Guide
Differential tables and pair tables are required to create SI pairs. Differential tables are tables that manage the differential
bitmaps, and pair tables are tables that contain the information needed to manage SI pairs. Create enough tables to
handle the SI pairs you plan to create.

The storage system uses a single pair table for up to 36 differential tables.

Software applications that use tables

The following software applications use differential tables:

ShadowImage for Mainframe (VSP 5000 series)

Volume Migration

The following software applications use pair tables:

ShadowImage for Mainframe (VSP 5000 series)

Volume Migration (using migration plans)

Maximum number of tables based on installed shared memory

The following tables show the number of differential tables and pair tables.

Table and volume limits (VSP 5000 series)

Differential table limit Pair table limit System volume limit

419,200 32,768 65,536

The maximum number of SI pairs you can create is half the number of system volumes in the table if the P-VOLs and S-
VOLs are in a one-to-one relationship.

For example, if the maximum amount of system volumes you can create is 65,536, then you can only create 32,768 SI
pairs. If there are more S-VOLs than P-VOLs, then the number of allowed SI pairs decreases.

For VSP E series, the maximum number of differential tables and pair tables in a storage system depends on the amount
of installed shared memory. Ensure that you have sufficient shared memory to handle the number of pairs you plan to
create.

The following tables show the number of differential tables and pair tables according to the amount of installed shared
memory.

Table and volume limits (VSP E series)

Shared memory Differential table Pair table limit

limit

Base (no additional shared 419,200

memory) VSP E590, VSP E790, VSP E990, VSP E1090:
32,768

Extension 1 419,200
VSP E590, VSP E790, VSP E990, VSP E1090:
32,768

Extension 2 419,200
VSP E790,VSP E990, VSP E1090: 32,768

VSP E590: N/A

Extension 3 419,200
VSP E990, VSP E1090: 32,768

VSP E590, VSP E790: N/A

Extension 4 419,200
VSP E1090: 32,768

Shared memory Differential table Pair table limit

limit
VSP E590, VSP E790, VSP E990: N/A

Calculating the number of tables for each pair

You can calculate the number of differential tables and pair tables that you will need for each pair.

Note:If a DP-VOL exceeds 4 TB, differential tables are placed in the hierarchy memory instead of the shared memory, and
differential tables in the shared memory are not used. Therefore, it is not necessary to calculate the number of differential
tables for DP-VOLs over 4 TB.

1. Use the following formula:

Total number of the differential tables per pair =

(volume capacity KB / 256) ÷ 20,448*

* The number of slots that a differential table can manage.

2. Round up the total number to the nearest whole number.

For example, if the capacity of the divided volume is 3,019,898,880 KB, the calculation is as follows:

(3,019,898,880 / 256) / 20,448 = 576.9014...

Round up 576.9014 to the nearest whole number, 577.

3. Use the following formula for calculating total number of the pair tables per pair:

Total number of the pair tables per pair =

Total number of the differential tables per pair ÷ 36*

* The number of differential tables used for each pair table.

577 ÷ 36 = 16.0277...

Round up 16.0277 to the nearest whole number and it will become 17.

Therefore, total number of the pair tables per pair is 17 in this example.

One or more pair tables can be used for each pair. However, the pair tables assigned to a pair cannot be used by a
different pair until the pair is deleted.

Calculating the number of SI pairs

After you determine the necessary number of differential and pair tables, determine whether the planned number of pairs
can be created.

The number of differential and pair tables for a pair depends on the volume capacity.

1. Calculate how many differential tables are required for the planned number of pairs:

number-of-differential-tables-per-pair × planned-number-of-pairs

2. Calculate how many pair tables are required for the planned number of pairs:

number-of-pair-tables-per-pair × planned-number-of-pairs

3. Verify that the storage system has enough differential tables and pair tables available.
The number of differential tables calculated in step 1 must not exceed the number of available differential
tables
The number of pair tables calculated in step 2 must not exceed the number of available pair tables
Note:
When creating ShadowImage pairs with multiple volumes that have different capacities, apply the total
numbers of differential tables calculated for each volume.
When creating ShadowImage pairs with multiple volumes that have different capacities, apply the total
numbers of pair tables calculated for each volume.
The number of available differential tables and pair tables depends on the amount of installed shared
memory.

Example

if you plan to create 20 pairs in a storage system that has 57,600 differential tables, use the following calculation:

577 × 20 = 11,570, which is ≤ 57,600

If the capacity of the volume is 3,019,898,880 KB, you will need 577 differential tables and 17 pair tables.

Apply these numbers to the following formula:

577 × 20 = 11,570 ≤ 57,600

and

17 × 20 = 340 ≤ 8,192

Therefore, you can create 20 pairs.

Quick Split and Steady Split performance planning

The following dependencies affect the performance of pairs that are in the process of Quick Split (PSUS(SP)/PSUS status)
or Steady Split (COPY(SP)/COPY status):

Whether system option mode (SOM) 459 is ON.

Whether the S-VOL is an external or internal volume.
If the S-VOL is a DP-VOL.

The following table lists the affects of these conditions.

SOM 459 S-VOL* PSUS(SP)/PSUS or COPY(SP)/COPY status

OFF Internal volume Differential data is copied to the cache in the storage system. The pair
is in the process of Quick Split (PSUS(SP)/PSUS status).

External volume

ON Internal volume

External volume Differential data is copied to the cache in the storage system, and
destaging to the external storage system has completed. The pair is
split (PSUS status).

* If the S-VOL is a DP-VOL, this column indicates whether the top pool volume allocated to the S-VOL is internal or
external.

Performance planning for ShadowImage

Performing pair tasks, such as creating, splitting, and resynchronizing SI pairs, can affect host server I/O performance on
the storage system.

Consider the following items for performance planning:

Host server I/O performance and number of SI pairs.

Compare the importance of host server I/O performance with the number of SI pairs and the copy pace.
Assigning multiple S-VOLs to a P-VOL uses more system resources and lowers the potential performance.
Load sharing on parity groups.
S-VOLs and P-VOLs should be assigned to different parity groups in case of failure. Make sure that enough
parity groups are used to provision the P-VOLs and S-VOLs and provide the performance capability
desired.
P-VOLs and S-VOLs should be distributed across the appropriate parity groups. If you plan to have multiple
copies of the same P-VOLs, consider placing the S-VOLs in different combinations of parity groups.
SI can create high levels of internal activity in your storage system. Ensure the configuration is appropriate
for the internal and host workload. Items that can help are additional parity groups, cache adapters, cache,
BEDs, and MPUs.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 13/80
6/16/25, 6:04 PM ShadowImage User Guide
Limit the number of volumes performing initial copy operations provisioned in the same parity group.
If you need to perform copy operations for multiple pairs in the same parity group, perform the operation for
a pair at a time.
When the system load is high, add a parity group, cache, channel board (CHB), and disk board (DKB).
Allocate an S-VOL to the newly installed parity group.
If you plan to simultaneously use multiple software applications, make sure that your storage system is configured
for optimal performance, such as sufficient cache. Concurrent use affects the performance and operation of the
other software applications.
If use AIX® host servers, for best performance, place the P-VOLs on one AIX® host server and the paired S-VOLs
on another.

Using a single AIX® host server for the P-VOLs and S-VOLs changes the P-VOL and S-VOLs to the same Port
VLAN ID when you create or resynchronize the SI pairs. If the Port VLAN IDs of the P-VOLs and S-VOLs are the
same and you reboot the host server, the volumes can be misidentified. For example, the S-VOL can be identified
as the P-VOL.

Quick Restore. You can maximize performance when you restore pairs using Quick Restore (see Workflow for
maximizing Quick Restore performance).

For more information about the guidelines for maximizing host server I/O performance while performing pair operations,
see Optimizing host server I/O performance.

Optimizing host server I/O performance

Creating, splitting, and resynchronizing SI pairs can affect host server I/O performance. You can take the following actions
to minimize the impact of pair operations on host server I/O performance:

When you are creating pairs:

Create the pairs when the I/O load is relatively light.
Limit the number of pairs that you create at the same time.
When you are creating, splitting, or resynchronizing pairs, select a slower copy pace. You can enable the local
replica option for copy pace, or you can select a specific copy pace while performing the task. In HDvM - SN, select
Slower. In CCI, use the paircreate -c command, and set 1 or 2 as the copy pace.

Related tasks
Setting the local replica options

Workflow for maximizing Quick Restore performance

Complete the following steps to maximize performance when restoring pairs with Quick Restore:

1. Use the same RAID level and drive type for the P-VOL and S-VOL.
2. If the P-VOL and S-VOLs are in different cache partitions, place them into the same cache partition.
3. Restore the pairs using Quick Restore.
4. Resume the original RAID levels if they were changed by a reverse resynchronization action.

Related tasks
Setting the RAID level
Related reference
Reverse resynchronization

Sharing ShadowImage volumes

Before sharing SI volumes with other Hitachi software application volumes, review the associated requirements,
restrictions, and guidelines.

Sharing volumes and Data Retention Utility access attributes

You can share volumes on which you set Data Retention Utility access attributes.

Access attributes and supported ShadowImage tasks

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 14/80
6/16/25, 6:04 PM ShadowImage User Guide
You can create SI pairs using volumes on which you set Data Retention Utility access attributes.

Note:Performing SI tasks does not change Data Retention Utility access attributes.

The volume access attributes that you have specified for the SI pair determines the SI pair tasks that you can perform. The
pair tasks you can perform are vary, depending on whether you set Data Retention Utility access attributes using HDvM -
SN or CCI.

The following table lists the volume access attributes specified for the SI pair and the pair tasks that you can perform when
using HDvM - SN to set access attributes.

Volume access attributes specified for the SI SI pair tasks

pair

P-VOL S-VOL Create, Split, Resync Resync (Reverse Suspend,

(Normal Copy) Copy) Delete

Read/Write Read/Write YES YES YES

Read Only, Protect, S-VOL Read/Write YES NO YES

Disable

Read/Write, Read Only, Read Only, Protect, S- NO NO YES

Protect, S-VOL Disable VOL Disable

The following table lists the volume access attributes specified for the SI pair and the pair tasks that you can perform when
using CCI to set access attributes.

Volume access attributes specified for the SI SI pair tasks

pair

P-VOL S-VOL Create, Split, Resync Resync (Reverse Suspend,

(Normal Copy) Copy) Delete

Read/Write, Read Only, Read/Write, Read YES YES YES

Protect Only, Protect

S-VOL Disable Read/Write, Read YES NO YES

Only, Protect

Read/Write, Read Only, S-VOL Disable NO NO YES

Protect, S-VOL Disable

Access attribute setting for existing pair volumes

A pair's status determines the access attributes you can set for existing P-VOLs or S-VOLs. Depending on the SI pair
status, you might not be able to set access attributes for SI P-VOLs and S-VOLs for Data Retention Utility. Access attribute
settings also depend on whether you set Data Retention Utility access attributes when using HDvM - SN or CCI.

The following table lists which attributes you can set depending on the pair status when using HDvM - SN to set access
attributes.

Volume specified by SI Attribute setting

Pair status Volume Read/Write Read Only, Protect, or S-VOL Disable

COPY(PD)/COPY P-VOL YES YES

S-VOL YES NO

PAIR P-VOL YES YES

S-VOL YES NO

COPY(SP)/COPY P-VOL YES YES

S-VOL YES NO

PSUS(SP)/PSUS P-VOL or S-VOL YES YES

PSUS P-VOL or S-VOL YES YES

SMPL(PD) P-VOL or S-VOL YES YES

COPY(RS)/COPY P-VOL YES YES

S-VOL YES NO

COPY(RS-R)/RCPY P-VOL or S-VOL YES NO

PSUE P-VOL or S-VOL YES YES

The following table lists which attributes you can set depending on the pair status when using CCI to set access attributes.

Volume specified by SI Attribute setting

Pair status Volume Read/Write, Read Only, or Protect S-VOL Disable

COPY(PD)/COPY P-VOL YES YES

S-VOL YES NO

PAIR P-VOL YES YES

S-VOL YES NO

COPY(SP)/COPY P-VOL YES YES

Volume specified by SI Attribute setting

Pair status Volume Read/Write, Read Only, or Protect S-VOL Disable

S-VOL YES NO

PSUS(SP)/PSUS P-VOL or S-VOL YES YES

PSUS P-VOL or S-VOL YES YES

SMPL(PD) P-VOL or S-VOL YES YES

COPY(RS)/COPY P-VOL YES YES

S-VOL YES NO

COPY(RS-R)/RCPY P-VOL or S-VOL YES NO

PSUE P-VOL or S-VOL YES YES

Sharing volumes with Dynamic Provisioning

Volumes created using Dynamic Provisioning can be used as SI P-VOLs or S-VOLs.

If you are using HDP volumes as SI P-VOLs or S-VOLs, the capacity of the HDP pool allocated to the volume is added to
the SI licensed capacity. A volume with capacity saving enabled can be used as a P-VOL or S-VOL.

The term Dynamic Provisioning in this manual includes Dynamic Provisioning, Dynamic Tiering, or active flash.

Restrictions

The following restrictions apply:

(VSP 5000 series) Data compressed or deduplicated by the capacity saving function is copied to a volume after
compression and deduplication are released. The capacity saving function is not performed immediately for copied
data. Before creating or resynchronizing a ShadowImage pair, make sure that the available capacity in the copy
destination volume is greater than the used capacity in the copy origination volume before capacity saving. For
details, see the Provisioning Guide for your storage system.
If you create SI pairs using a volume for which the capacity saving function is used, compressed or deduplicated
data is copied. Because of this, copy or I/O performance may be degraded.
When the capacity saving function is used, management information is stored in a pool. As a result, there may be
difference between a P-VOL and an S-VOL in the number of used pages or licensed capacity.
Because the S-VOL uses the same pool capacity as the P-VOL, best practice is to avoid the following volume
combinations:
Using only the S-VOL as a Dynamic Provisioning volume (DP-VOL).
Using the P-VOL as a DP-VOL with the Data Direct Mapping attribute, and using the S-VOL as a normal
DP-VOL.
You cannot perform a Quick Restore if only the P-VOL or only the S-VOL is a DP-VOL or the capacity saving of the
P-VOL or S-VOL is enabled. For Quick Restore, you must use DP-VOLs for both the P-VOL and S-VOL.
The deduplication system data volume cannot be used as a P-VOL or S-VOL.
You can use a maximum size Dynamic Provisioning volume as an SI P-VOL or S-VOL. For information about the
maximum size for Dynamic Provisioning volumes, see the Provisioning Guide for your storage system.
You must use the block specification for SI volumes shared with DP-VOLs. You cannot use TB, GB, or MB. For
example, 4 TB = 8,589,934,592 blocks.
When you create an SI pair using a DP-VOL greater than 4,194,304 MB (8,589,934,592 blocks), the differential
data is managed in a pool associated with the SI pair volume. In this case, the required pool capacity for managing

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 17/80
6/16/25, 6:04 PM ShadowImage User Guide
the differential data varies depending on the product configuration, with a maximum of four pages for every
4,123,168,604,160 bytes.
(VSP 5000 series) If you downgrade to a microcode version that does not support pair creation with a DP-VOL
greater than 4,194,304 MB, release the differential data (pages) managed in a pool.
For details about whether zero pages can be reclaimed when you specify SI P-VOLs or SI S-VOLs on Device
Manager - Storage Navigator or Command Control Interface, see the Provisioning Guide for your storage system.
If you perform an SI paircreate or pairresync operation while zero pages are being reclaimed (including operations
by WriteSame or Unmap, or by rebalancing the usage level), it results in zero-page reclamation interruption.
If reclaiming zero pages is in progress on a P-VOL or an S-VOL during SI pair creation, the pair might not be
created. Therefore, avoid the time period when reclaiming zero pages is in progress when creating a pair.
If you create an SI pair during WriteSame or Unmap command processing, the pair creation may fail. In this case,
create the pair again after the WriteSame or Unmap command processing finishes.
If the WriteSame or Unmap command was issued to the SI P-VOL or S-VOL, zero pages are not reclaimed by the
command.
Zero pages are not reclaimed for the SI P-VOL or S-VOL even if you rebalance the usage level.
SI pair creation may be rejected if the Unmap command operation is in progress with system option mode 905 ON.
Wait a while, and then retry. If the operation still fails, set system option mode 905 to OFF and retry.
(VSP E series) If the copy origination page of an SI pair is not allocated, but the copy destination page is already
allocated, zero data is copied to the copy destination. In this case, zero data pages are not reclaimed. If you want
to reclaim zero data pages, split the SI pair to change its status to PSUS, and then reclaim zero data pages of the
applicable volume.

Sharing volumes with global-active device

The following table lists the volumes that can be shared between global-active device (GAD) and ShadowImage.

GAD volume ShadowImage volume

(CCI command)
P-VOL S-VOL

YES*
GAD P-VOL YES

YES*
GAD S-VOL YES

GAD S-VOL Reserve attribute NO NO

volume

GAD quorum disk volume NO NO

* SI S-VOL is supported by the following storage systems:

VSP 5000 series: 90-05-01-xx/xx or later

VSP E series: 93-06-81-xx/xx or later
VSP G/F350, G/F370, G/F700, G/F900: 88-08-08-xx/xx or later

The following tables list the relationship between GAD pair statuses and ShadowImage tasks when sharing GAD pair
volumes and ShadowImage pair volumes.

Note:

If a pair that cannot be split is in a consistency group (CTG), pairs in the CTG are suspended (PSUE status) when
executing a CTG pair split function for ShadowImage.
To split a ShadowImage pair that links with a GAD pair and obtain a backup, stop I/O for the target backup volume,
and then split the ShadowImage pair.

ShadowImage tasks when sharing GAD P-VOL and ShadowImage P-VOL

ShadowImage task GAD pair status and I/O mode

(CCI command)
COPY PAIR PSUS PSUE

Mirror Mirror Local Block Local Block

(RL) (RL)

Create a pair YES YES YES YES YES YES

(paircreate)

Create and split a pair YES YES YES YES YES YES

(paircreate -split)

Split a pair YES YES YES YES YES YES

(pairsplit)

Resynchronize a pair YES YES YES YES YES YES

(pairresync)

Reverse Copy a pair NO NO YES NO YES NO

(pairresync -restore)

Quick restore a pair NO NO YES* NO YES* NO

(pairresync -restore)

Suspend a pair task YES YES YES YES YES YES

(pairsplit -E)

Delete a pair YES YES YES YES YES YES

(pairsplit -S)

*This task cannot be performed if the migration source volume of Hitachi Volume Migration is contained in the same
volume.

ShadowImage tasks when sharing GAD S-VOL and ShadowImage P-VOL

ShadowImage task GAD pair status and I/O mode

(CCI command)
COPY PAIR SSUS PSUE SSWS

Block Mirror Block Block Local

(RL)

Create a pair YES YES YES YES YES

ShadowImage task GAD pair status and I/O mode

(CCI command)
COPY PAIR SSUS PSUE SSWS

Block Mirror Block Block Local

(RL)

(paircreate)

Create and split a pair NO YES YES YES YES

(paircreate -split)

Split a pair NO YES YES YES YES

(pairsplit)

Resynchronize a pair NO YES YES YES YES

(pairresync)

Reverse Copy a pair NO NO NO NO YES

(pairresync -restore)

Quick restore a pair NO NO NO NO YES*

(pairresync -restore)

Suspend a pair task YES YES YES YES YES

(pairsplit -E)

Delete a pair YES YES YES YES YES

(pairsplit -S)

*This task cannot be performed if the migration source volume of Hitachi Volume Migration is contained in the same
volume.

(VSP 5000 series) ShadowImage tasks when sharing GAD P-VOL and ShadowImage S-
VOL

GAD pair status and I/O mode

ShadowImage task
COPY PAIR PSUS PSUE
(CCI command)
Mirror(RL) Mirror(RL) Local Block Local Block

NO NO YES NO YES NO
Create a pair

(paircreate)

Create and split a pair (paircreate -split) NO NO YES NO YES NO

GAD pair status and I/O mode

ShadowImage task
COPY PAIR PSUS PSUE
(CCI command)
Mirror(RL) Mirror(RL) Local Block Local Block

NO NO YES NO YES NO
Split a pair

(pairsplit)

Resynchronize a pair (pairresync) NO NO YES NO YES NO

Reverse Copy a pair (pairresync -restore) NO NO YES NO YES NO

Quick restore a pair (pairresync -restore) NO NO NO NO NO NO

YES YES YES YES YES YES

Suspend a pair task

(pairsplit -E)

YES YES YES YES YES YES

Delete a pair

(pairsplit -S)

(VSP 5000 series) ShadowImage tasks when sharing GAD S-VOL and ShadowImage S-
VOL

GAD pair status and I/O mode

ShadowImage task
COPY PAIR SSUS PSUE SSWS
(CCI command)
Block Mirror(RL) Block Block Local

NO NO NO NO YES
Create a pair

(paircreate)

Create and split a pair (paircreate -split) NO NO NO NO YES

NO NO NO NO YES
Split a pair

(pairsplit)

Resynchronize a pair (pairresync) NO NO NO YES

Reverse Copy a pair (pairresync -restore) NO NO NO NO YES

Quick restore a pair (pairresync -restore) NO NO NO NO NO

YES YES YES YES YES

Suspend a pair task

(pairsplit -E)

YES YES YES YES YES

Delete a pair

(pairsplit -S)

Sharing volumes with LUN Manager

LUN Manager tasks do not affect SI tasks. You can assign volumes that are under secure ports or that are assigned to
World Wide Name (WWN) groups and/or LUN groups to SI pairs. You can also use volumes that are assigned to SI pairs in
LUN Manager tasks, such as assignment to WWN groups and/or LUN groups.

A host cannot access SI S-VOLs except when you split the pair.

Sharing volumes with Resource Partition Manager

You can share SI P-VOLs and S-VOLs with Resource Partition Manager by specifying them in a Resource Partition
Manager resource group.

For more information about Resource Partition Manager, see the System Administrator Guide for your storage system.

Before you begin

The resource group must be assigned to a user group for which you have privileges.

Sharing volumes with Thin Image

You can share SI volumes with HTI volumes. You can assign shared pairs to CTGs, but not to the same CTG. For the node
or leaf volume of a Thin Image pair, see the S-VOL description in the following table.

The following table describes how you can share HTI volumes.

HTI volume SI volume

P-VOL S-
VOL

P-VOL (RCPY status)

NO NO

P-VOL (all statuses except RCPY)1 YES YES2

S-VOL NO NO

HTI pool volume NO NO

Notes:

1. SI cannot use a Thin Image P-VOL in RCPY status.

For more information about sharing volumes, see the following tables.

2. You must create the SI pair before you create the HTI pair.

SI pair tasks that you can perform are limited according to the Thin Image pair status. The following topics show the
supported SI tasks.

Pair tasks with Thin Image primary volume shared with ShadowImage primary volume

The following table lists the pair tasks that you can perform when you share the SI P-VOL with the Thin Image P-VOL.

SI task Thin Image pair status

(CCI command)
COPY PAIR, PSUS, SMPL(PD) RCPY PSUE
PFUL PFUS

Create a pair (paircreate) YES YES YES YES NO YES

Create and split a pair (paircreate - YES YES YES YES NO YES
split)

SI task Thin Image pair status

(CCI command)
COPY PAIR, PSUS, SMPL(PD) RCPY PSUE
PFUL PFUS

Split a pair (pairsplit) YES YES YES YES NO YES

Resynchronize a pair (pairresync) YES YES YES YES NO YES

Reverse Copy a pair (pairresync - YES YES* YES YES NO YES

restore)

Quick Restore a pair (pairresync - NO NO NO NO NO NO

restore)

Suspend a pair task (pairsplit -E) YES YES YES YES YES YES

Delete a pair (pairsplit -S) YES YES YES YES YES YES

Notes:

*The snapshot data must be consistent with P-VOL data and ready to use in the SI task.

After issuing the pairsplit command for a Thin Image pair for which a consistency group is configured, verify that the
status of all pairs in the Thin Image consistency group is PSUS or unpaired, and then execute the SI task. If you do not,
the Thin Image snapshot data and P-VOL data when the storage system accepted the pairsplit command will not be
consistent. For details about Thin Image pair status and operations, see the Hitachi Thin Image User Guide.

For more information about ensuring the snapshot data is consistent with P-VOL data, see Ensuring snapshot data is
consistent with P-VOL data.

Pair tasks with Thin Image primary volume shared with ShadowImage secondary volume

The following table lists the pair tasks that are supported when you share the SI S-VOL with the Thin Image P-VOL.

SI task Thin Image pair status

(CCI command)
COPY PAIR, PSUS, SMPL(PD) RCPY PSUE
PFUL PFUS

Create a pair (paircreate) NO NO NO NO NO NO

Create and split a pair (paircreate - NO NO NO NO NO NO

split)

Split a pair (pairsplit) YES YES1 YES YES NO YES

Resynchronize a pair (pairresync) YES YES1 YES YES NO YES

SI task Thin Image pair status

(CCI command)
COPY PAIR, PSUS, SMPL(PD) RCPY PSUE
PFUL PFUS

Reverse Copy a pair (pairresync - YES YES1 YES YES NO YES

restore)

Quick Restore a pair2 (pairresync - NO NO NO NO NO NO

restore)

Suspend a pair task (pairsplit -E) YES YES YES YES NO YES

Delete a pair (pairsplit -S) YES YES YES YES YES YES

Notes:

1. The snapshot data must be consistent with P-VOL data and ready to use in the SI task.

After issuing the pairsplit command for a Thin Image pair for which a consistency group is configured, verify that
the status of all pairs in the Thin Image consistency group is PSUS or unpaired, and then execute the SI task. If
you do not, the Thin Image snapshot data and P-VOL data when the storage system accepted the pairsplit
command will not be consistent. For details about Thin Image pair status and operations, see the Hitachi Thin
Image User Guide.

For more information about ensuring the snapshot data is consistent with P-VOL data, see Ensuring snapshot
data is consistent with P-VOL data.

2. When the host accesses the Thin Image S-VOL, the Thin Image P-VOL data might be used to return a reply. For
this reason, you cannot Quick Restore to exchange the SI P-VOL and S-VOL (which is the Thin Image P-VOL).

Sharing volumes with Thin Image Advanced

You should understand the relationship between Thin Image Advanced pair statuses and ShadowImage operations when
the P-VOL of a Thin Image Advanced pair is shared as the P-VOL or an S-VOL of a ShadowImage pair.

Pair tasks with Thin Image Advanced primary volume shared with ShadowImage primary
volume

SI task (CCI Thin Image Advanced pair task

command)
COPY(PD) PAIR PSUS(SP) COPY(SP) PSUS COPY(RS) COPY(RS- SMPL(PD) PSUE
R)

Create a pair YES YES YES YES YES YES NO YES YES
(paircreate)

Create and YES YES YES YES YES YES NO YES YES
split a pair
(paircreate -
split)

Split a pair YES YES YES YES YES YES NO YES YES
(pairsplit)

Resynchronize YES YES YES YES YES YES NO YES YES

a pair
(pairresync)

Reverse Copy YES YES* NO YES YES YES NO YES YES

a pair

SI task (CCI Thin Image Advanced pair task

command)
COPY(PD) PAIR PSUS(SP) COPY(SP) PSUS COPY(RS) COPY(RS- SMPL(PD) PSUE
R)
(pairresync -
restore)

Quick Restore NO NO NO NO NO NO NO NO NO
a pair
(pairrespync -
restore)

Suspend a YES YES YES YES YES YES YES YES YES
pair (pairsplit -
E)

Delete a pair YES YES YES YES YES YES YES YES YES
(pairsplit -S)

*After issuing the raidcom modify snapshot -snapshot_data split command for a Thin Image Advanced pair for which a
consistency group is configured, verify that the status of all pairs in the Thin Image Advanced consistency group is PSUS
or unpaired, and then execute the SI task. If you do not, the Thin Image Advanced snapshot data and P-VOL data when
the VSP 5000 series storage system accepted the raidcom modify snapshot -snapshot_data split command will not be
consistent. For details about Thin Image Advanced pair status and operations, see the Hitachi Thin Image Advanced
User Guide.

Pair tasks with Thin Image Advanced primary volume shared with ShadowImage secondary
volume

SI task (CCI Thin Image Advanced pair task

command)
COPY(PD) PAIR PSUS(SP) COPY(SP) PSUS COPY(RS) COPY(RS- SMPL(PD) PSUE
R)

Create a pair1 NO NO NO NO NO NO NO NO NO
(paircreate)

Create and NO NO NO NO NO NO NO NO NO
split a pair
(paircreate -
split)

Split a pair YES YES2 NO YES YES YES NO YES YES

(pairsplit)

Resynchronize YES YES2 NO YES YES YES NO YES YES

a pair
(pairresync)

Reverse Copy YES YES2 NO YES YES YES NO YES YES

a pair
(pairresync -
restore)

Quick Restore NO NO NO NO NO NO NO NO NO
a pair3
(pairrespync -
restore)

Suspend a YES YES YES YES YES YES NO YES YES

pair (pairsplit -
E)

Delete a pair YES YES YES YES YES YES YES YES YES
(pairsplit -S)

Notes:

1. When you use an S-VOL of an SI pair as the P-VOL of a Thin Image Advanced pair, you must create the SI pair
first and then create the Thin Image Advanced pair.

SI task (CCI Thin Image Advanced pair task

command)
COPY(PD) PAIR PSUS(SP) COPY(SP) PSUS COPY(RS) COPY(RS- SMPL(PD) PSUE
R)
2. After issuing the raidcom modify snapshot -snapshot_data split command for a Thin Image Advanced pair for
which a consistency group is configured, verify that the status of all pairs in the Thin Image Advanced consistency
group is PSUS or unpaired, and then execute the SI task. If you do not, the Thin Image Advanced snapshot data
and P-VOL data when the VSP 5000 series storage system accepted the raidcom modify snapshot -
snapshot_data split command will not be consistent. For details about Thin Image Advanced pair status and
operations, see the Hitachi Thin Image Advanced User Guide
3. When the host accesses the Thin Image Advanced S-VOL, the Thin Image Advanced P-VOL data might be used
to return a reply. For this reason, you cannot Quick Restore to exchange the SI P-VOL and S-VOL (which is the
Thin Image Advanced P-VOL).

Sharing volumes with TrueCopy

You can share SI P-VOLs and S-VOLs with TC P-VOLs and S-VOLs. However, you cannot share SI S-VOLs with TC S-
VOLs.

The write operation on the TC P-VOL takes more time when you share an SI P-VOL with a TC S-VOL.

For more information about splitting pairs, see Pair splitting methods.

Restrictions

The following restrictions apply:

When you share an SI P-VOL with a TC S-VOL, if you split the SI pair during write I/Os to the TC P-VOL, only part
of write I/Os might be written to the SI S-VOL. To keep data consistency in the SI S-VOL, stop I/Os to the TC P-
VOL first, and then split the SI pair.
You can use SI cascaded pairs as TC pairs. TC does not distinguish between node and leaf volumes in cascaded
pairs. Both are considered S-VOLs.

For more information about cascaded pairs, see Cascaded pairs.

If you plan to Quick Restore the SI pair, you must first suspend the TC pair.
You can perform a CTG pair-split on SI pairs that share volumes with TC S-VOLs.

For more information about CTG pair-split for shared volumes, see Using consistency group pair-split with shared
volumes

If you want to use the SI S-VOL as the TI P-VOL, create the SI pair first, and then create the TI pair.

For more information about sharing SI and TC volumes, see the Hitachi TrueCopy® User Guide.

The following table describes ShadowImage operations when SI P-VOLs are shared with TC P-VOLs or S-VOLs.

ShadowImage operation
TC
Create Split Suspend copy Release Resync pairs
pair pairs pairs operation pairs
Normal Quick Reverse Quick
status
copy resync copy restore

COPY YES YES YES YES YES YES NO NO

PAIR YES YES YES YES YES YES NO NO

PSUS YES YES YES YES YES YES YES YES

PSUE YES YES YES YES YES YES YES YES

The following table describes ShadowImage operations when SI S-VOLs are shared with TC P-VOLs.

ShadowImage operation
TC
Create Split Suspend copy Release Resync pairs
pair pairs pairs operation pairs
Normal Reverse Quick
Quick
status copy copy restore

COPY NO NO YES YES NO NO NO NO

PAIR NO NO YES YES NO NO NO NO

PSUS NO YES YES YES YES YES YES YES

PSUE NO YES YES YES YES YES YES YES

Sharing volumes with Universal Replicator

You can share SI P-VOLs with UR P-VOLs and S-VOLs.

You can use SI cascaded pairs as UR pairs. In cascaded pairs, UR does not distinguish between node and leaf
volumes. Both are considered as S-VOLs.

For more information about cascaded pairs, see Cascaded pairs.

(VSP 5000 series) When you share the SI P-VOL with a UR S-VOL, if you split the SI pair during write I/Os to the
UR P-VOL, only part of write I/Os might be written to the SI S-VOL. To keep data consistency in the SI S-VOL, use
consistency group pair-split to split the SI pair.
If you plan to Quick Restore the SI pair, you must first suspend the UR pair.

For more information about Quick Restore, see Reverse resynchronization.

You can perform a CTG pair-split on SI pairs that share volumes with UR S-VOLs.

For more information about using CTG pair-split on pairs with shared volumes, see Using consistency group pair-
split with shared volumes.

For more information about sharing SI and UR volumes, see the related appendix in the Hitachi Universal Replicator User
Guide.

The following table describes ShadowImage operations when SI P-VOLs are shared with UR P-VOLs or S-VOLs.

ShadowImage operation
UR
Create Split Suspend copy Release Resync pairs
pair pairs pairs operation pairs
Normal Quick Reverse Quick
status
copy resync copy restore

COPY YES YES YES YES YES YES NO NO

PAIR YES YES YES YES YES YES NO NO

PSUS YES YES YES YES YES YES YES YES

PSUE YES YES YES YES YES YES YES YES

Suspending YES YES YES YES YES YES NO NO

Deleting YES YES YES YES YES YES NO NO

The following table describes ShadowImage operations when SI S-VOLs are shared with UR P-VOLs.

ShadowImage operation
UR
Create Split Suspend copy Release Resync pairs
pair pairs pairs operation pairs
Normal Reverse Quick
Quick
status copy copy restore
resync

COPY NO NO YES YES NO NO NO NO

PAIR NO NO YES YES NO NO NO NO

PSUS NO YES YES YES YES YES YES YES

PSUE NO YES YES YES YES YES YES YES

Suspending NO NO YES YES NO NO NO NO

Deleting NO NO YES YES NO NO NO NO

Sharing volumes with UR in 3DC configurations with three UR sites

You can share SI P-VOLs and S-VOLs with UR P-VOLs and S-VOLs that are in 3DC configurations with three UR sites.

The following figures show examples of sharing SI and UR volumes in the following configurations:

3DC multi-target configuration

3DC multi-target configuration using delta resync
3DC cascade configuration
3DC cascade configuration using delta resync

(1) When a UR P-VOL is shared with an SI P-VOL in a 3DC multi-target configuration

(2) When a UR P-VOL is shared with an SI S-VOL in a 3DC multi-target configuration

(3) When a UR S-VOL is shared with an SI P-VOL in a 3DC multi-target configuration

(4) When a UR P-VOL is shared with an SI P-VOL on the primary storage system in a 3DC
cascade configuration

(5) When a UR P-VOL is shared with an SI S-VOL on the primary storage system in a 3DC
cascade configuration

(6) When a UR S-VOL is shared with an SI P-VOL on the intermediate storage system in a
3DC cascade configuration

(7) When a UR S-VOL is shared with an SI P-VOL on the secondary storage system in a
3DC cascade configuration

(8) When each UR volume is shared with an SI P-VOL in a 3DC multi-target configuration
using delta resync

(9) When a UR P-VOL is shared with an SI S-VOL, and a UR S-VOL is shared with an SI P-
VOL in a 3DC multi-target configuration using delta resync

(10) When each UR volume is shared with an SI P-VOL in a 3DC cascade configuration
using delta resync

(11) When a UR P-VOL is shared with an SI S-VOL, and a UR S-VOL is shared with an SI
P-VOL in a 3DC cascade configuration using delta resync

ShadowImage operations in a 3DC multi-target configuration

You can perform ShadowImage operations on Universal Replicator volumes that are used in a 3DC multi-target
configuration.

The following tables specify whether SI operations can be performed when UR volumes are shared with SI volumes in a
3DC multi-target configuration.

Table. 3DC multi-target: Sharing a UR P-VOL with an SI P-VOL

UR pair UR pair ShadowImage operation
status (P- status (P-
Create Split pair Suspend Release Resync pair
VOL: x) VOL: y)
pair copy pair
Normal Quick Reverse Quick
copy resync restore

PAIR PAIR YES YES YES YES YES YES NO NO

COPY YES YES YES YES YES YES NO NO

PSUS/ YES YES YES YES YES YES NO NO

PSUE

COPY COPY YES YES YES YES YES YES NO NO

PSUS/ YES YES YES YES YES YES NO NO

PSUE

PSUS/ PSUS/ YES YES YES YES YES YES YES NO

PSUE PSUE
Table. 3DC multi-target: Sharing a UR P-VOL with an SI S-VOL
UR pair UR pair ShadowImage operation
status (P- status (P-
Create Split pair Suspend Release Resync pair
VOL: x) VOL: y)
pair copy pair
Normal Quick Reverse Quick
copy resync restore

PAIR PAIR NO NO YES YES NO NO NO NO

COPY NO NO YES YES NO NO NO NO

PSUS/ NO NO YES YES NO NO NO NO

PSUE

COPY COPY NO NO YES YES NO NO NO NO

PSUS/ NO NO YES YES NO NO NO NO

PSUE

UR pair UR pair ShadowImage operation

status (P- status (P-
Create Split pair Suspend Release Resync pair
VOL: x) VOL: y)
pair copy pair
Normal Quick Reverse Quick
copy resync restore

PSUS/ PSUS/ NO YES YES YES YES YES YES NO

PSUE PSUE
Table. 3DC multi-target: Sharing a UR S-VOL with an SI P-VOL
UR pair ShadowImage operation
status (S-
Create pair Split pair Suspend Release Resync pair
VOL)
copy pair
Normal Quick Reverse Quick
copy resync restore

PAIR YES YES YES YES YES YES NO NO

COPY YES YES YES YES YES YES NO NO

PSUS/ YES YES YES YES YES YES YES NO

PSUE

ShadowImage operations in a 3DC multi-target configuration using delta

resync

You can perform ShadowImage operations on Universal Replicator volumes that are used in a 3DC multi-target delta
resync configuration.

The following table specifies whether SI operations can be performed when a UR S-VOL and a UR S-VOL for delta resync
are shared with SI P-VOLs in a 3DC multi-target delta resync configuration.

Table. 3DC multi-target delta resync: Sharing a UR S-VOL and a UR S-VOL for delta resync with SI P-VOLs
UR pair UR delta ShadowImage operation
status (S- resync
Create Split pair Suspend Release Resync pair
VOL) pair
pair copy pair
status Normal Quick Reverse Quick
copy resync restore

PAIR HOLD/ YES YES YES YES YES YES NO NO

HLDE

COPY HOLD/ YES YES YES YES YES YES NO NO

HLDE

PSUS/ HOLD/ YES YES YES YES YES YES NO NO

PSUE HLDE

ShadowImage operations in a 3DC cascade configuration

You can perform ShadowImage operations when ShadowImage and Universal Replicator are used in a 3DC cascade
configuration.

The following tables specify whether SI operations can be performed when UR volumes are shared with SI volumes in a
3DC cascade configuration.

Table. 3DC cascade: Sharing a UR P-VOL with an SI P-VOL on the primary storage system
UR pair ShadowImage operation
status (P-
Create pair Split pair Suspend Release Resync pair
VOL)
copy pair
Normal Quick Reverse Quick
copy resync restore

PAIR YES YES YES YES YES YES NO NO

COPY YES YES YES YES YES YES NO NO

UR pair ShadowImage operation

status (P-
Create pair Split pair Suspend Release Resync pair
VOL)
copy pair
Normal Quick Reverse Quick
copy resync restore

PSUS/ YES YES YES YES YES YES YES NO

PSUE
Table. 3DC cascade: Sharing a UR P-VOL with an SI S-VOL on the primary storage system
UR pair ShadowImage operation
status (P-
Create pair Split pair Suspend Release Resync pair
VOL)
copy pair
Normal Quick Reverse Quick
copy resync restore

PAIR NO NO YES YES NO NO NO NO

COPY NO NO YES YES NO NO NO NO

PSUS/ NO YES YES YES YES YES YES NO

PSUE
Table. 3DC cascade: Sharing a UR S-VOL or P-VOL with an SI S-VOL on the intermediate storage system
UR pair UR pair ShadowImage operation
status (S- status (P-
Create Split pair Suspend Release Resync pair
VOL) VOL)
pair copy pair
Normal Quick Reverse Quick
copy resync restore

PAIR PAIR YES YES YES YES YES YES NO NO

COPY YES YES YES YES YES YES NO NO

PSUS/ YES YES YES YES YES YES NO NO

PSUE

COPY COPY YES YES YES YES YES YES NO NO

PSUS/ YES YES YES YES YES YES NO NO

PSUE

PSUS/ PSUS/ YES YES YES YES YES YES YES NO

PSUE PSUE
Table. 3DC cascade: Sharing a UR S-VOL with an SI P-VOL on the secondary storage system
UR pair ShadowImage operation
status (S-
Create pair Split pair Suspend Release Resync pair
VOL)
copy pair
Normal Quick Reverse Quick
copy resync restore

PAIR YES YES YES YES YES YES NO NO

COPY YES YES YES YES YES YES NO NO

PSUS/ YES YES YES YES YES YES YES NO

PSUE

ShadowImage operations in a 3DC cascade configuration using delta resync

You can perform ShadowImage operations on Universal Replicator volumes that are used in a 3DC cascade configuration
with delta resync.

The following tables specify whether SI operations can be performed when UR volumes are shared with SI volumes in a
3DC cascade delta resync configuration.

Table. 3DC cascade delta resync: Sharing a UR P-VOL on the primary system and a UR S-VOL for delta resync with SI P-
VOLs

UR pair UR delta ShadowImage operation

status (P- resync
Create Split pair Suspend Release Resync pair
VOL) pair
pair copy pair
status Normal Quick Reverse Quick
copy resync restore

PAIR HOLD/ YES YES YES YES YES YES NO NO

HLDE

COPY HOLD/ YES YES YES YES YES YES NO NO

HLDE

PSUS/ HOLD/ YES YES YES YES YES YES NO NO

PSUE HLDE
Table. 3DC cascade delta resync: Sharing a UR P-VOL on the primary system and a UR S-VOL for delta resync with SI S-
VOLs
UR pair UR delta ShadowImage operation
status (P- resync
Create Split pair Suspend Release Resync pair
VOL) pair
pair copy pair
status Normal Quick Reverse Quick
copy resync restore

PAIR HOLD/ NO NO NO YES NO NO NO NO

HLDE

COPY HOLD/ NO NO NO YES NO NO NO NO

HLDE

PSUS/ HOLD/ NO NO NO YES NO NO NO NO

PSUE HLDE
Table. 3DC cascade delta resync: Sharing a UR S-VOL on the secondary system and a UR S-VOL for delta resync with SI
P-VOLs
UR pair UR delta ShadowImage operation
status (S- resync
Create Split pair Suspend Release Resync pair
VOL) pair
pair copy pair
status Normal Quick Reverse Quick
copy resync restore

PAIR HOLD/ YES YES YES YES YES YES NO NO

HLDE

COPY HOLD/ YES YES YES YES YES YES NO NO

HLDE

PSUS/ HOLD/ YES YES YES YES YES YES NO NO

PSUE HLDE

Sharing volumes with TrueCopy and Universal Replicator

Example of a pair shared by UR S-VOL and TC P-VOL

The following figures provide configuration examples when ShadowImage, TrueCopy, and Universal Replicator are used.

Example of a pair shared by TC S-VOL and UR P-VOL

For the above configurations, you cannot perform Quick Restore for SI pairs.

The following image illustrates a 3DC multi-target configuration with the following pairs:

Universal Replicator pair

Universal Replicator delta resync pair
ShadowImage pair
TrueCopy pair

For details about 3DC multi-target configurations, see the Hitachi Universal Replicator User Guide.

Example of combining an SI pair, TC pair, and UR pair in the 3DC multi-target configuration

The following tables describe ShadowImage operations according to the status of TC pairs and UR delta resync pairs in
the storage system of the TC secondary site.

Table. ShadowImage operations in the TC secondary storage system

TC Pair UR delta ShadowImage operation

Status resync
pair
status Create Split Suspend Release Resync pairs
pairs pairs copy pairs
operation
Normal Quick Reverse Quick
copy resync copy restore

PAIR HOLD YES YES YES YES YES YES NO NO

COPY YES YES YES YES YES YES NO NO

PSUS/PSUE YES YES YES YES YES YES YES NO

PAIR HLDE YES YES YES YES YES YES NO NO

COPY YES YES YES YES YES YES NO NO

PSUS/PSUE YES YES YES YES YES YES YES NO

Table. ShadowImage operations in the UR secondary storage system

UR Pair UR delta ShadowImage operation

Status resync
pair
status Create Split Suspend Release Resync pairs
pairs pairs copy pairs
operation
Normal Quick Reverse Quick
copy resync copy restore

UR Pair UR delta ShadowImage operation

Status resync
pair
status Create Split Suspend Release Resync pairs
pairs pairs copy pairs
operation
Normal Quick Reverse Quick
copy resync copy restore

PAIR HOLD YES YES YES YES YES YES NO NO

COPY YES YES YES YES YES YES NO NO

PSUS/PSUE YES YES YES YES YES YES YES NO

The following table describes ShadowImage operations according to the status of TC and UR pairs in the storage system
of the TC or UR local site.

The following table applies when there is no UR delta resync pair.

Table. ShadowImage operations in the TC or UR primary storage system

TC pair UR pair ShadowImage operation
status status
Create Split Suspend Release Resync pairs
pairs pairs copy pairs
Normal Quick Reverse Quick
copy resync copy restore

PAIR PAIR YES YES YES YES YES YES NO NO

COPY YES YES YES YES YES YES NO NO

YES YES YES YES YES YES NO NO

PSUS/

PSUE

COPY PAIR YES YES YES YES YES YES NO NO

COPY YES YES YES YES YES YES NO NO

YES YES YES YES YES YES NO NO

PSUS/

PSUE

PAIR YES YES YES YES YES YES NO NO

PSUS/
COPY YES YES YES YES YES YES NO NO
PSUE
YES YES YES YES YES YES YES NO
PSUS/

PSUE

Sharing volumes with Universal Volume Manager

You can create SI pairs using Universal Volume Manager external volumes.

For more information about Universal Volume Manager external volumes, see the Hitachi Universal Volume Manager User
Guide.

Access to the external volumes used for SI pairs, only from or through the local storage system. Do not access, for
example, from a host connected with the external storage system, or by using a copy functionality on the external storage
system.

Sharing volumes with Hitachi Volume Migration

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 39/80
6/16/25, 6:04 PM ShadowImage User Guide
You can migrate the following types of SI pair volumes as Volume Migration source volumes:

L1 P-VOL with up to two S-VOLs.

L2 P-VOL with at least one S-VOL.

To assign another type of SI pair volume as a Volume Migration source volume, you must delete the SI pair first.

SI pair volumes cannot be migrated as Volume Migration target volumes.

Volume Migration volumes cannot be used in SI pair tasks; you must release a volume in Volume Migration before you can
use it as an SI volume.

Configuring your ShadowImage environment

Before you start creating pairs, you must prepare the volumes that will be the P-VOLs and S-VOLs and set the local replica
options on your storage system.

Workflow for setting up ShadowImage

Before you start creating the copy pairs, use the following procedure to set up your SI environment. You must have the
Storage Administrator (Local Copy) role to perform SI operations.

1. Prepare the volumes for SI operations (see Preparing volumes for ShadowImage).
2. Review the local replica options (see Local replica options).

If necessary, change the settings as needed for your environment (see Setting the local replica options).

Preparing volumes for ShadowImage

You must set up and prepare the P-VOLs and S-VOLs for SI pairing before creating SI pairs. The volumes you use must
meet the requirements for pair volumes.

The following table provides example volumes to guide you in preparing volumes for SI pairing.

CU Port GID: LUN Pair Volume Associated L1 Associated L1 Associated L2 Associated L2

Type S-VOLs P-VOLs S-VOLs P-VOL

0 1A 0:00 L1 P-VOL 1B-0:00, 2A- N/A N/A N/A

0:00, 2B-0:00

0 1A 0:01 L1 P-VOL 1B-0:01, 2A- N/A N/A N/A

0:01, 2B-0:01

0 1B 0:00 L1 S-VOL N/A 1A-0:00 3A-0:00, 3A- N/A

0:01
L2 P-VOL

0 1B 0:01 L1 S-VOL N/A 1A-0:00 3B-0:00, 3B- N/A

0:01
L2 P-VOL

0 2A 0:00 L1 S-VOL N/A 1A-0:00 4A-0:00, 3B- N/A

0:01
L2 P-VOL

0 2A 0:01 L1 S-VOL N/A 1A-0:00 4B-0:00, 3B- N/A

0:01
L2 P-VOL

CU Port GID: LUN Pair Volume Associated L1 Associated L1 Associated L2 Associated L2

Type S-VOLs P-VOLs S-VOLs P-VOL

0 3A 0:00 L2 S-VOL N/A N/A N/A 1B-0:00

0 3A 0:01 L2 S-VOL N/A N/A N/A 1B-0:00

Options for ShadowImage

ShadowImage has the following two options:

System option modes

For information about system option modes, see the System Administrator Guide. Contact customer support if you
want to ask for settings.

Local replica options

You can set local replica options by using HDvM - SN or CCI. For details, see Local replica options.

Local replica options

The local replica options provide additional settings to enable you to tailor your local replication environment to your
specific operating requirements. The local replica options include the Copy Threshold option that your service
representative can set and the options that you can set.

Copy Threshold option

The Copy Threshold option temporarily stops copy operations when the workload of the storage system is high to prevent
degradation of host I/O performance. When this option is enabled, the following copy operations are stopped:

ShadowImage
Thin Image
Volume Migration
ShadowImage for Mainframe
Compatible FlashCopy® V2

When you want to enable and disable the Copy Threshold option, contact your service representative.

Other local replica options

The following table lists and describes the local replica options that you can set by using Device Manager - Storage
Navigator or CCI.

Note the following when you use the Quick/Steady Split Multiplexing, Reverse Copy Multiplexing, and Normal Resync
Multiplexing options:

The increase in copy volume increases the amount of data to be written to the target volume.
If the parity group performance is less than the pair split or resync performance, the amount of data waiting to be
written to cache memory (write pending ratio) may increase until it exceeds 60%, and the copy processing might be
placed in the wait state. In such a case, consider the copy order to reduce the number of pairs for which copy
processing is executed concurrently for volumes provisioned by the same parity group.
If the number of volumes to be resynchronized or split increases, the maximum number of jobs for pair split or
resynchronization that can execute concurrently for a pair decreases. In this case, when you split or resynchronize
many pairs concurrently with this option set, the pair split or resynchronization performance might not be changed.
The maximum number of copy operations that can be run concurrently is 126 (including the number for
ShadowImage/ShadowImage for Mainframe). This number includes initial copying, resynchronization, update
copying, and differential data copying. When copy operations other than pair split and resynchronization are
running concurrently, if you set this option, the pair split or resynchronization performance might not be changed.
The maximum number of pairs that can be copied concurrently in the background is 504. If the number of pairs
being copied reaches 504, the next pair to be copied waits until one of the copy processing finishes.
The Quick/Steady Split Multiplexing option is enabled for Steady Split and Quick Split.
Reverse Copy Multiplexing is enabled for Reverse Copy.
Normal Resync Multiplexing is enabled for Normal Resync.
If the Increase Background Copy Performance (ShadowImage/ShadowImage for Mainframe) option is enabled, the
amount of copy data increases over the entire storage system while the pair is in the PAIR status. Therefore, you

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 41/80
6/16/25, 6:04 PM ShadowImage User Guide
can decrease the amount of differential data when the pair-split operation starts. However, the MP operating ratio
and write pending rate increase because the amount of copy data increases in the storage system. Understand the
trade-offs when you use this option.

Tip:Difference between the Host I/O Performance option and the Copy Pace Ext. options:

The Host I/O Performance option reduces the impact on host I/O by lowering the copy activity when pairs are in
COPY(PD)/COPY, PAIR, COPY(SP)/COPY, PSUS(SP)/PSUS, COPY(RS)/COPY or COPY(RS-R)/RCPY status.
The Copy Pace Ext. options reduce the impact on host I/O by lowering the copy activity when pairs are in the PAIR
status.

These options can be set concurrently. If you set both options, you can benefit from both.

Default
No. Option Description

OFF
1 Swap & Freeze Saves ShadowImage data as-is immediately
after Quick Restore. Used with the Quick
Restore, inhibits the update copy operation after
Quick Restore, and the paired S-VOL in PAIR
status is not updated and remains unchanged.

OFF
2 Host I/O Performance Gives weight to host I/O responses rather than
the copy time of a volume. This option controls SI
copy operations and improves host I/O
responses. This option suppresses copy
operations at any time regardless of workload.

Caution: The Host I/O Performance option

suppresses copy processing and prolongs the
copy time. Also, if there is an SIz pair, host I/O
responses might not be improved. In this case,
enable this option for both SI and SIz.

OFF
9 to 13 HOST I/O priority mode 1 to 5 Makes the copy processing for SI pairs fail for
the host I/O that causes copy processing for SI
pairs so that the host I/O is prioritized. This
function is performed if the write pending rate
does not decrease and the host I/O does not
finish within the time period specified by the
option. After the copy processing fails, all data is
copied as the resynchronization. See Time until
the copy processing fails.

OFF
20 Copy Pace Ext. Slower1 Reducing the copy volume in the PAIR status
curbs the influence to the I/O performance of the
21 Copy Pace Ext. Slower2
host server. This option is available to all SI pairs
in the PAIR status. The I/O performance of the
22 Copy Pace Ext. None
host server is improved most effectively with
Copy Pace Ext. None, followed by Copy Pace
Ext. Slower2, and Copy Pace Ext. Slower1. Copy
Pace Ext. None takes precedence over Copy
Pace Ext. Slower2, and Copy Pace Ext. Slower2
takes precedence over Copy Pace Ext. Slower1.

This function is enabled only when the pair status

is PAIR. If the pair status is COPY(PD)/COPY,
COPY(SP)/COPY, PSUS(SP)/PSUS,
COPY(RS)/COPY and COPY(RS-R)/RCPY, this
function cannot reduce the impact on the host
server's I/O performance.

Note:When the Copy Pace Ext. None option is

set, copy operation is not performed for the pair

Default
No. Option Description

in the PAIR status and the synchronization rate

during split operation might become lower. In this
case, the PSUS(SP)/PSUS and
COPY(SP)/COPY status during split operation
might last longer. If this is a problem, perform
either of or both the following actions:

Minimize the time that the pair status is

PAIR to avoid lowering the sychronization
ratio in the PAIR status.
Use this option to change the status to
Copy Pace Ext. Slower1 or Copy Pace
Ext. Slower2. If you select either of them,
the write response might be larger than
the one for Copy Pace Ext. None.

ON
24 Quick/Steady Split Multiplexing Accelerates SI pair split. The number of jobs
used for concurrent copy processing for each
(ShadowImage/ShadowImage for
pair is changed from 1 to 24.
Mainframe)

ON
25 Reverse Copy Multiplexing Accelerates resynchronization (secondary to
primary) of SI pairs.
(ShadowImage/ShadowImage for
Mainframe) The number of jobs used for concurrent copy
processing for each pair is changed from 1 to 24.

ON
26 Normal Resync Multiplexing Accelerates resynchronization (primary to
secondary) of SI pairs.
(ShadowImage/ShadowImage for
Mainframe) The number of jobs used for concurrent copy
processing for each pair is changed from 1 to 24.

This option applies to the VSP E series as

31 OFF Increase Background Copy follows. Increases the maximum multiplicity of
Performance
asynchronous copy processing run in the
background when a ShadowImage pair is in the
(ShadowImage/ShadowImage for
Mainframe) PAIR status as follows:

VSP E790, VSP E990, VSP E1090, VSP

5000 series: From 64 to 126
VSP E590: From 64 to 96

Time until the copy processing fails

The time until the copy processing fails differs depending on the configuration.

When ShadowImage works alone, the available setting rage of the time is 1 to 31 seconds.
When the P-VOL of ShadowImage works with other software:
Configuration Available setting range of the time
until copy processing fails
(seconds)

Working with the P-VOL of other software1 1 to 31

Working with the S-VOL of other Performing host I/O on the P-VOL of 1 to 31
1 ShadowImage
software , or working with both the
P-VOL and S-VOL of other
Performing host I/O on the P-VOL of 1 to 14
software1
other software1, 2

Configuration Available setting range of the time

until copy processing fails
(seconds)

Note:
1. Only TrueCopy, Universal Replicator, and global-active device apply. For other software, the configuration
is regarded as the same as when ShadowImage works alone.
2. The function of these options is disabled when host I/O is performed on the P-VOL of Universal
Replicator.

Setting the local replica options

You can enable and disable the local replica options as needed to optimize the performance of your storage system.

You must have the Storage Administrator (Local Copy) role.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication.
2. In the Replication window, click Edit Options > Local Replication.
3. In the Edit Local Replica Options window, complete the following steps:
a. For System Type, verify that Open is selected.
The default setting is Open.
b. In the SI/TI System Options table, select the local replica options that you want to enable, and then click
Enable.
4. Click Finish, and then confirm the settings.
5. Accept the default task name or enter a unique name.
You can enter up to 32 letters, numbers, and symbols, except the following:

\/:,;*?"<>|

6. If you want to monitor the task after submitting it, select Go to tasks window for status.
7. Click Apply to submit the task.

Managing ShadowImage pairs

You can review information related to using HDvM - SN to complete SI pair tasks, and for using CCI to split pairs by
consistency group.

Workflow for managing ShadowImage pairs

During most pair tasks, the P-VOL remains available to the host for I/O operations. You must have the Storage
Administrator (Local Copy) role to perform SI pair tasks.

Complete the following steps to complete pair tasks:

1. Check the SI pair status and the status of related L1 and L2 pairs to determine if you can perform a task.
2. Create the SI pairs.
3. (Optional) Suspend SI pair creation.
4. (Optional) Suppress update copy operations during pair restoration.
5. Split the pairs. You can do the following:

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 44/80
6/16/25, 6:04 PM ShadowImage User Guide
Split SI pairs.
Split SI pairs in a CTG.
6. Resynchronize or restore the SI pairs.
7. (Optional) If you have performed a Quick Resync on the pair (PAIR status), suppress copy processing.
8. Delete the unnecessary SI pairs, which ends the pair relationship between the pair volumes.

It may be a long time before a ShadowImage copy operation starts, because differential tables are initialized for the
relevant pairs, one pair at a time, before the copy operation starts. Especially when the pairs use a large volume of data,
initialization can be a very long process.
Related concepts
Creating ShadowImage pairs
Related tasks
Suspending ShadowImage pairs
Suppressing update copy operations during pair restoration
Splitting ShadowImage pairs
Workflow for splitting pairs in a consistency group
Resynchronizing or restoring ShadowImage pairs
Deleting ShadowImage pairs

Creating ShadowImage pairs

When you create a pair, the storage system performs an initial copy to copy data in the P-VOL to the S-VOL. You can
create the SI pair and immediately split the pair so that you can access the S-VOL. You can also create a cascaded pairs.

Creating an SI pair causes the MP unit that is responsible for processing the P-VOL LDEV's I/O to assume processing
responsibility for the S-VOL LDEV's I/O operations.

Related concepts
Considerations for creating ShadowImage pairs
MP unit and pair deletion
Related tasks
Creating ShadowImage pairs in HDvM - SN
Related information
Select Pair Configuration window

Workflow for creating ShadowImage pairs

Complete the following steps to create an SI pair:

1. If you are creating L1 and L2 pairs, check the status (see L1, L2 pair status and supported pair tasks).
2. Select the volume that you want to duplicate. This becomes the primary volume (P-VOL).
Note:In Device Manager - Storage Navigator (HDvM - SN), the source volume is called "P-VOL" and the destination
volume is called "S-VOL."

You cannot use volumes in use by SI as destination volumes.

3. Identify the volume that will contain the copy. This becomes the secondary volume (S-VOL).

If you are creating L1 and L2 pairs with different topologies, specify the pair configuration settings (see Creating L1
and L2 pairs with different topologies in HDvM - SN).

4. Create the pair by associating the P-VOL and the S-VOLs (see Creating ShadowImage pairs in HDvM - SN).

The storage system starts the initial copy (see Initial copy workflow).

5. (Optional) Suppress copy processing (see Suppressing update copy operations).

Considerations for creating ShadowImage pairs

Keep the following considerations in mind when creating SI pairs:

The P-VOL and S-VOL must be the same size in blocks. If the capacity is displayed in GB or TB, a small difference
between P-VOL and S-VOL capacity might not be displayed. To view the capacity in blocks, click Options >
Capacity Unit > block in the Logical Devices window.
If your storage system has encryption BEDs, you can copy an encrypted volume to an unencrypted volume. There
is no guard logic to enforce copying encrypted P-VOLs to only encrypted S-VOLs. Unless there is a specific reason
for the data to become unencrypted, make sure you maintain the encryption by using only encrypted S-VOLs.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 45/80
6/16/25, 6:04 PM ShadowImage User Guide
The larger the volume capacity, the longer the time from creation of a pair until it transitions to PAIR status. For
virtual volumes, the more pages allocated to a virtual volume, the longer the time from pair creation to PAIR status.
Even when no pages are allocated to a virtual volume, if the volume capacity is 60 TB, it takes at least 30 minutes
until the status changes to PAIR after pair creation. If the volume capacity is 256 TB, it takes at least an hour.
The value of the T10 PI attribute must be the same for the P-VOL and S-VOL.
When you simultaneously create an L1 pair and an L2 pair, if you select Quick Split or Steady Split for Split Type in
HDvM - SN or specify the -split command in CCI, the L2 pair split begins before the L1 pair status changes to
PSUS. Because of this, the operation might fail.
After creating an SI pair, if the number of pairs displayed in the summary section and the number of listed pairs in
the HDvM - SN window are different, the configuration might be changed. Wait a while, and then select File >
Refresh All to update the configuration information.
Initial copy is performed with a maximum of 24 multiplicities (number of jobs for which concurrent copy can be
performed) for each pair. However, if Steady Split or Quick Split is set as the split type, the multiplicity is set to 1.
Because of this, the processing time becomes longer than when Non Split is set as the split type. In the Edit Local
Replica Options window, if Quick/Steady Split Multiplexing (ShadowImage/ShadowImage for Mainframe) option is
enabled, the maximum number of multiplexing becomes 24 even when Steady Split or Quick Split is set as the split
type.
If only the P-VOL capacity of an L1 pair has been expanded, an L2 pair cannot be created. Make sure to create the
L2 pair after expanding all of the volume capacity used in the pairs.

Creating ShadowImage pairs in HDvM - SN

Creating an SI pair copies the P-VOL to the S-VOL.

Note:If you create an SI pair during WriteSame or Unmap command processing, the pair creation might fail. In this case,
create the pair again after the WriteSame or Unmap command processing finishes.

You must have Storage Administrator (Local Copy) role.

In CCI, use the paircreate command.
The P-VOL and S-VOL must be unpaired.
If the P-VOL is already paired with other S-VOLs (PAIR status), you have determined that the status of existing S-
VOLs is the status that is required to create the new pair.

For more information about S-VOL status, see Unaffected S-VOL status and pair tasks.

If you are concerned with host server I/O performance, make sure that the I/O load is light.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication > Local
Replication.
2. In the Local Replication window, select the SI Pairs tab.

3. On the SI Pairs tab, click Create SI Pairs.

4. In the Select Pair Configuration window, complete the following steps, and then click Next:
For Copy Type, select ShadowImage.
For Emulation Type, select the emulation type.
For Pair Topology Type, select the pair topologies that match your configuration.

For more information about creating L1 and L2 pairs with different topologies, see Creating L1 and L2 pairs
with different topologies in HDvM - SN.

For Split Type, select how you want to split the pair.

Values:

- Non Split: The pair is not split.

Note:If you are simultaneously creating an L1 pair and an L2 pair, to prevent a failure and splitting the L2
pair before the pair is split (PSUS status), select Non Split.

- Quick Split (default): Splits the new pair, and then copies the data so that the S-VOL is immediately
available for read and write I/O. The storage system copies the remaining differential data to the S-VOL in
the background.

- Steady Split: Copies the differential data to the S-VOL, and then splits the new pair.

For Copy Pace, select the rate at which you want the storage system to copy data.

Values:

- Slower: Improved host server I/O performance but slower processing speed.

- Medium (default): Average processing speed and host server I/O performance.

- Faster: Faster processing speed but slower host server I/O performance.

Note:The pace you select affects processing speed and host server I/O performance.

For more information about performance, see Performance planning for ShadowImage.

5. In the Select Primary Volumes window of the Create SI Pairs wizard, complete the following steps:
a. Optional: Filter LDEVs by port ID, host group name, or iSCSI target alias.
b. In the Available LDEVs table, select one or more LDEVs you want to be P-VOLs, and then click Add.
Note:nondisruptive migration volumes do not appear in the Available LDEVs table.

Selected LDEVs are moved to the Selected LDEVs table.

c. Click Next.

6. In the Select Secondary Volumes window of the Create SI Pairs wizard, assign LDEVs as S-VOLs to the specified
P-VOL LDEVs.
If you specified one P-VOL, select a secondary LDEV from the Available LDEVs table, and click Set. Repeat
this step to assign additional S-VOLs.
If you specified multiple P-VOLs, select an LDEV from the Available LDEVs table, select a P-VOL LDEV
from the Selected Pairs table, and then click Set. Repeat this step as many times as needed to make all
your pairings.
If you do not select a P-VOL from the Selected Pairs table, the S-VOL you select and set is assigned to P-
VOLs in the order they are listed in the table.
Note:nondisruptive migration volumes do not appear in the Available LDEVs table.
After an S-VOL is selected, you can also perform the following optional steps:
To sort the Available LDEVs and Selected Pairs tables according to the capacity, choose a capacity item for
Capacity.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 48/80
6/16/25, 6:04 PM ShadowImage User Guide
The remaining number you have to select refers to the P-VOLs that do not have an assigned S-VOL, as
seen in the Selected Pairs table.
To filter the Available LDEVs by a specific port ID, host group name, or iSCSI target alias, select Port ID,
Host Group Name, or iSCSI Target Alias.
Select the Exclude Paired Volumes check box to exclude paired LDEVs from display.
To sort the Selected Pairs table, click Sort Pairs above the table.
To change the split type and the rate at which data is copied, which applies to all new pairs, change the pair
options (see Changing ShadowImage pair options).
To change MU numbers, complete the following steps:

a. Select the line for the LDEV in the Selected Pairs table.

b. Click Edit Mirror Units.

c. In the Edit Mirror Units dialog box, specify the S-VOL's L1 and L2 mirror unit numbers, and click OK.

The pair topology is modified.

For more information about changing a pair's topology, see Creating L1 and L2 pairs with different
topologies in HDvM - SN.

Change the pair options (see Changing ShadowImage pair options).

To remove an unwanted LDEV or pair from the Selected Pairs table, select the line for the LDEV or pair you
want to remove and click Remove.

The pair's topology is refined.

7. Click Finish, and then confirm the settings.

8. Accept the default task name or enter a unique name.

You can enter up to 32 letters, numbers, and symbols, except the following:

\/:,;*?"<>|

9. If you want to monitor the task after submitting it, select Go to tasks window for status.
10. Click Apply to submit the task.
The SI pair is created and the status is PAIR.
Related concepts
Pair splitting methods
Related tasks
Changing ShadowImage pair options

Creating L1 and L2 pairs with different topologies in HDvM - SN

Begin creating a pair by specifying the L1 and L2 pair topology in the Select Pair Configuration window of the Create Pairs
wizard.

Specify the pair topology one time. This topology applies to all P-VOLs in the task.

To change L1 and L2 pair configuration, set the topology for the pair with the largest topology.

The following image shows an example of the P-VOL with the largest topology of all the pairs you create in a single task.

Example: Changing a pair L1 and L2 combination

You can change L1 and L2 pair configurations that do not match the specified configuration in the Create SI Pairs wizard.
You can also change L1 and L2 pair configurations when you create a new pair using an existing P-VOL with an existing
configuration.

For example, use the following steps to pair the L2 S-VOL labeled 4 (MU1) in the preceding topology with the L1 volume
labeled 1 (MU0).

1. Open the Select Secondary Volumes window of the Create SI Pairs wizard.

2. From the Selected Pairs table, select the line for the S-VOL that has the pair topology you want to configure, and
then click Edit Mirror Units.

3. In the Edit Mirror Units dialog box, for Mirror Unit, select 0 for L1, and select 2 for L2.

Refining pair topology

You can refine a pair topology by removing unwanted volumes.

1. Open the Select Secondary Volumes window of the Create SI Pairs wizard.

2. In the Selected Pairs table, select the line for the pair you want to remove and click Remove.
The volume is removed from the table.

Suppressing update copy operations

You can suppress update copy operations after you create pairs. Suppressing update copy operations keeps the P-VOL
and S-VOL unsynchronized and reduces the effect on host server I/O performance.

The pair status is PAIR.

Enable the Swap & Freeze system option.

Releasing differential data for ShadowImage pairs

When an SI pair contains a DP-VOL that is larger than 4,194,304 MB (8,589,934,592 blocks), the differential data is
managed by the pool to which the pair is related. If differential data management fails due to insufficient pool capacity, you
need to release the differential data (pages) managed in the pool. You also need to release pages when you downgrade to
a microcode version that does not support SI pairs with volumes larger than 4,194,304 MB.

1. Delete all pairs using the V-VOL that contains the differential data (pages) that needs to be released.
2. Set system option mode 755 to OFF, so that you can reclaim zero pages.
3. Restore the blocked pool.
4. Release pages in the V-VOL.
To release pages in Device Manager - Storage Navigator, use the Reclaim Zero Pages window. In CCI, use the rai
dcom modify ldev command. Releasing pages might take some time.

Changing ShadowImage pair options

You can change the default setting for the Split Type and Copy Pace system options for all new pairs that you create.

1. Open the Select Secondary Volumes window of the Create SI Pairs wizard.

2. In the Select Secondary Volumes window of the Create SI Pairs wizard, click Change Options.

3. In the Change Options dialog box, complete the following steps, and then click OK:
For Split Type, select a split type.

Values:

Non Split (default): The pair is not split.

Quick Split: The pair is split, and then the differential data is copied so that the S-VOL is immediately
available for read and write I/O. Any remaining differential data is copied to the S-VOL in the
background.
Steady Split: Differential data is copied, and then the pair is split.
For Copy Pace, select the rate at which you want the storage system to copy data.

Values:

Slower: Improved host server I/O performance but slower processing speed.
Medium (default): Average processing speed and host server I/O performance.
Faster: Faster processing speed but slower host server I/O performance.
Related concepts
Pair splitting methods
Initial copy workflow

Splitting ShadowImage pairs

Splitting an SI pair suspends the pairing of the P-VOL and S-VOLs until a resync or delete operation is performed. Host
updates to the P-VOL continue and are tracked as delta tracks in the bitmap. The S-VOL data is available and can be

Splitting an SI pair ensures data consistency and that the data in the S-VOL at the time of the split is usable. The S-VOL
contains a mirror image of the original volume at that point in time, and it is available for read/write access by secondary
host applications.

The P-VOL for a split pair continues to be updated, but the S-VOL remains unchanged. The differential data that accrues
while the pair is split is stored in the differential bitmaps. Changes to the P-VOL and S-VOLs are managed in these
differential bitmaps. The differential data accrues until you resynchronize the pair, which copies the differential data to the
S-VOL.

If you have assigned an SI P-VOL or S-VOL to a volume reserved for Volume Migration, splitting the volume cancels
migration.

If you are splitting SI pairs with shared TC or UR volumes, see the restrictions (see Requirements_ restrictions_ and
guidelines for using consistency group pair-split with shared volumes).

If you are sharing SI S-VOLs with UR P-VOLs and the R-JNL has a timeout period that ends after the split time, the
storage system might not detect the journal data. In this case, the SI split operation runs after the timeout period.

You set the timeout value according to your requirements.

Default: 6 hours
Related concepts
Pair splitting methods
Resynchronizing ShadowImage pairs
Related tasks
Splitting ShadowImage pairs
Workflow for splitting pairs in a consistency group
Related information
Split Pairs window

Pair splitting methods

By default, for pair split (Non Split, Steady Split, or Quick Split), the maximum multiple copy processing for each pair is set
to 24. However, if you set the Quick/Steady Split Multiplexing option of the local replica option to OFF, the multiplicity can
be changed to 1. Make sure to set the Quick/Steady Split Multiplexing option to OFF if the host I/O performance is
prioritized. The local replica options can be set using HDvM - SN or CCI.

You can use one of the following methods to split pairs:

HDvM - SN CCI Description

Non Split paircreate Pairs are not split after they are
created.

Steady Split paircreate –split -fq normal When copy of all differential data
completes, the pairs are split.

Quick Split paircreate –split -fq quick Pairs are split immediately after pair
split is specified. Use this method if
you want to read or write data of the S-
VOL immediately after pair split is
specified. Remaining differential data
is copied to the S-VOL in background
after the split.

- paircreate –g <group> -m grp [CTG ID] Split all pairs in a consistency group at
one time. CCI is required for this
operation. For details, see the
Command Control Interface User and
Reference Guide.

Splitting ShadowImage pairs

You must have Storage Administrator (Local Copy) role.

In CCI, use the pairsplit command.
If you split a pair when there are write I/Os to the P-VOL, only some of the write I/Os may be written to the S-VOL.
To ensure that all write I/Os are written to the S-VOL, stop I/Os to the P-VOL before splitting the pair. You can
maintain data consistency of the S-VOL (maintain the order in which data is written to the S-VOL) by using a
consistency group pair-split to split a pair, or by stopping all I/Os to the P-VOL before splitting the pair.
P-VOL data and S-VOL data are synchronized when the pair status changes from COPY(SP)/COPY or
PSUS(SP)/PSUS to PSUS. Because SI update copy is performed asynchronously, it takes some time before the
pair status changes.

To ensure data consistency in the P-VOL and the S-VOL after a split, stop write I/Os from the host to the P-VOL in
advance. By this method, you can keep the P-VOL from being updated during a split, and ensure data consistency
between the P-VOL and the S-VOL.

The pair status must be one of the following:

If you are splitting an existing pair, the pair status must be PAIR.
If you are creating and then immediately splitting an L1 pair, the volumes are unpaired (SMPL).
If you are splitting an L1 pair that has L2 pairs, see L1, L2 pair status and supported pair tasks.
If you are splitting, or creating and immediately splitting, an L2 pair, the status of the L1 pair must be PSUS.
To split pairs quickly, stop host access to the P-VOL before splitting the pairs.
Check the I/O load to verify that it will not affect host server performance.

For more information about checking I/O performance, see the System Administrator Guide.

If you split a pair during initial copy, the initial copy operation is canceled, and it is performed again after the split.
For initial copy, the maximum copying multiplicity (the number of jobs used for concurrent copy processing) for each
pair is 24, but the number might change to 1 after the split. As a result, if you split a pair during initial copy, copy
processing might take longer than splitting a pair after initial copy completes.
The copy processing to split a pair requires some time to check if the differential data exists even if there is no
differential data. The amount of time to check the differential data takes longer as the volume capacity increases,
and it might take 10 minutes or more for 256 TB.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication > Local
Replication.
2. In the Local Replication window, select the SI Pairs tab.

3. On the SI Pairs tab, select the pair you want to split, and then click Split Pairs.

4. In the Split Pairs window of the Split Pairs wizard, complete the following steps:
For Split Type, select the split type.

Values:

- Steady Split: Copies the differential data to the S-VOL, and then splits the new pair.

For more information about the methods you can use to split pairs, see Pair splitting methods.

For Copy Pace, select the rate at which you want the storage system to copy data.

Values:

- Slower: Improved host server I/O performance but slower processing speed.

- Medium (default): Average processing speed and host server I/O performance.

- Faster: Faster processing speed but slower host server I/O performance.

Note:The pace you select affects processing speed and host server I/O performance.

For more information about performance, see Performance planning for ShadowImage.

5. Click Finish, and then confirm the settings.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 56/80
6/16/25, 6:04 PM ShadowImage User Guide
6. Accept the default task name or enter a unique name.
You can enter up to 32 letters, numbers, and symbols, except the following:

\/:,;*?"<>|

7. If you want to monitor the task after submitting it, select Go to tasks window for status.
8. Click Apply to submit the task.
The SI pair is split and the pair status changes from PSUS(SP)/PSUS or COPY(SP)/COPY to PSUS. The snapshot
data is consistent with the P-VOL data and is ready to use in SI pair tasks.
Related concepts
Pair splitting methods
Related tasks
Workflow for splitting pairs in a consistency group
Related reference
Device Manager - Storage Navigator pair status names and descriptions

Using consistency groups to split pairs

A consistency group (CTG) lets you perform tasks and change pair status on a group of SI pairs. With CTG pair-split, you
can simultaneously split all of the pairs in a CTG.

Using consistency group pair-split with shared volumes

If you share SI P-VOLs in a storage system with TC or UR S-VOLs, you can use consistency group (CTG) pair-split to
keep SI S-VOLs consistent.

When an SI P-VOL shares a UR or TC S-VOL to create pairs, you can assign the same CTG ID to the SI pairs in order to
use the CTG pair-split function to maintain consistency among the SI S-VOLs.

The following image illustrates CTG pair-split with TC.

The following image illustrates CTG pair-split with UR.

When you perform a CTG pair-split on shared UR P-VOLs, the following operations occur:

1. UR restores the journal data that was created before you restored the split time to UR S-VOLs (SI P-VOLs).
Note:If an SI pair is suspended due to a failure, the split time and the actual task start time must be the same in
order to restore UR journal data that you created before the split time to the UR/SI volume after the split. The task
start time is determined by the amount of journal data in the journal volume at the time of the split.

For example, if the journal volume contains data that needs one hour to be restored, the starting time of the split
operation delays for an hour.

2. The SI pair is split.

3. UR resumes the suspended R-JNL operations.

Workflow for splitting pairs in a consistency group

1. Define a CTG to which you want to assign the SI pairs using IBM PPRC or CCI.
2. Verify that all the SI pairs you want to be consistent are assigned to the same SI CTG.
3. If the pair-split operation fails, troubleshoot CTG pair-split failures (see Consistency group pair-split failures).
4. Create the pairs.

Related concepts
Pair splitting methods
Related reference
Restrictions for consistency group pair-split
Requirements, restrictions, and guidelines for using consistency group pair-split with shared volumes

Requirements, restrictions, and guidelines for using consistency group pair-split with shared volumes

You can share SI P-VOLs with TC or UR S-VOLs but there are requirements, restrictions, and guidelines for using
consistency group (CTG) pair-split in these cases.

Requirements

If you are sharing SI P-VOLs with TC or UR S-VOLs, CTG pair-split has the following requirements:

All pair operations must be performed using CCI.

You must share SI P-VOLs with the TC or UR S-VOLs.
The TC or UR S-VOLs that you are sharing with the SI CTG pairs must have the same status.
If you are sharing SI volumes with UR volumes, the pair status must be the following:
(For UR) PAIR or PSUS.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 58/80
6/16/25, 6:04 PM ShadowImage User Guide
(For SI) PAIR or COPY(PD)/COPY.
If you are sharing SI volumes with TC volumes, the pair status must be the following:
(For TC) PAIR or PSUS.
(For SI) PAIR or COPY(PD)/COPY.

Restrictions

If you are sharing SI P-VOLs with TC or UR S-VOLs, CTG pair-split has the following restrictions:

You can perform one split operation for each SI CTG.

You can:
Split each UR journal up to three times (equivalent to three SI CTGs).
Quick Split or Steady Split the pairs.

For more information about the methods you can use to split pairs, see Pair splitting methods.

Guidelines

If you are sharing SI P-VOLs with TC or UR S-VOLs, use the following guidelines when performing a CTG pair-split:

Make sure that the SI S-VOLs are in a consistent state.

For more information about maintaining consistent backups of volumes, see Maintaining consistent ShadowImage
secondary volume backups.

Ensure that all SI pairs in the CTG are in PAIR or COPY(PD)/COPY status.
Note:If you share SI pair P-VOLs with UR S-VOLs and you include SI pairs in a status other than PAIR or
COPY(PD)/COPY in the CTG, you cannot maintain SI S-VOL consistency.

Restrictions for consistency group pair-split

Consistency group (CTG) pair-split has the following restrictions:

To perform a CTG pair-split on SI pairs, the pairs must have been created using IBM PPRC or CCI. You cannot use
CTG pair-split if the pairs were created using the HDvM - SN.

Related reference
Requirements, restrictions, and guidelines for using consistency group pair-split with shared volumes

Supported pair statuses for consistency group pair-split

The pair status for all of the SI pairs in the CTG determines if you can perform a consistency group (CTG) pair-split. If all of
the SI pairs in the CTG are paired (PAIR status), you can perform a CTG pair-split.

The following table describes when you can perform a CTG pair-split, based on the SI pairs in the CTG that are not paired
(a status other than PAIR), and the resulting pair status after you perform the pair-split.

The status of the pairs in the Can you perform Status after you perform a CTG
CTG that have a status other pair-split
a CTG pair-split?
than PAIR

COPY(PD)/COPY YES PSUS

COPY(SP)/COPY YES2 PSUS

PSUS(SP)/PSUS YES2 PSUS

PSUS YES2 PSUS

COPY(RS)/COPY NO The pair statuses remain the same.

The command ends abnormally and shows the

following information:

The status of the pairs in the Can you perform Status after you perform a CTG
CTG that have a status other pair-split
a CTG pair-split?
than PAIR

[EX_CMDRJE] An order to the control/com

mand device was rejected1

COPY(RS-R)/RCPY NO The pair statuses remain the same.

The command ends abnormally and shows the

following information:

[EX_CMDRJE] An order to the control/com

mand device was rejected1

PSUE NO The pair statuses remain the same.

The command ends abnormally and shows the

following information:

[EX_CMDRJE] An order to the control/com

mand device was rejected

Notes:

1. If you share a UR S-VOL and an SI P-VOL, the command might end normally after you perform a CTG pair-split.
Ensure the status of the pairs within the CTG have changed to PSUS (use the pairdisplay command).
2. Consistency is guaranteed only for SI pairs in PAIR or COPY(PD)/COPY status.

The following are examples of when you can perform a CTG pair-split based on status of the SI pairs in the CTG:

Example 1

The are six SI pairs in a CTG. Two of the pairs are paired (PAIR status), two are in COPY(PD)/COPY status, and
two are in PSUS status. In this case, you can perform a CTG pair-split, and doing so changes the status of all of
the pairs in the CTG to PSUS. However, the S-VOLs that were in PSUS might not be consistent with the other
volumes in the CTG.

Example 2

There are two SI pairs in a CTG and one is paired (PAIR status) and the other is in the process of being
resynchronized (COPY(RS)/COPY status). In this case, you cannot perform a CTG pair-split.

Example 3

The are six SI pairs in a CTG. Two of the pairs are paired (PAIR status), two are in the process of Quick Split
(PSUS(SP)/PSUS status), and two are in PSUE status. In this case, the CTG pair-split ends abnormally and the
status of all of the pairs in the CTG remains the same.

Maintaining consistent ShadowImage secondary volume backups

If you are sharing SI P-VOLs with TC or UR S-VOLs, assign UR pairs to the same journal group to maintain a consistent
backup of SI S-VOLs.

For more information about assigning SI pairs to journals, see the Hitachi Universal Replicator User Guide.

1. Assign UR pairs to the same journal group.

For more information about assigning SI pairs to journals, see the Hitachi Universal Replicator User Guide.
2. Register the journal group data volumes in an SI CTG that is not already being used.

Ensuring snapshot data is consistent with P-VOL data

Split the pair to ensure the snapshot data is consistent with the P-VOL data and is ready to use in an SI pair task.

Complete one of the following actions to split the pair.

The volume is split (PSUS status).

For more information about how to perform a CTG pair-split, see Workflow for splitting pairs in a consistency group.

If you are using CCI to run commands, run the following command on the SI pair:

pairsplit

Resynchronizing ShadowImage pairs

You can resynchronize split (PSUS status) or suspend (PSUE status) pairs. Resynchronization changes the status of the
split volume pairs to PAIR. Resynchronizing a split pair copies the P-VOL's differential data to the S-VOL and again pairs
the S-VOL with the P-VOL. Resynchronizing a suspended pair copies the entire P-VOL to the S-VOL and takes the same
amount of time as the initial copy operation.

Note:Resynchronizing a pair does not ensure data consistency. Data in the two volumes is consistent only if the following
conditions exist:

The P-VOL is offline.

The pair is split (the S-VOL status is PSUS).

For more information about pair status, see Device Manager - Storage Navigator pair status names and
descriptions.

Note:If you perform a Quick Restore for a pair consisting of an encrypted volume and an unencrypted volume, the
encryption statuses of the volumes are reversed.
Related concepts
Workflow for resynchronizing ShadowImage pairs
Volume pairs
Initial and update copy operations
Related tasks
Resynchronizing or restoring ShadowImage pairs
Related information
Types of pair resynchronization

Types of pair resynchronization

You can forward or reverse resynchronize pairs. A forward resynchronization resynchronizes from the P-VOL to the S-VOL.
A reverse resynchronization restores pairs by resynchronizing from the S-VOL to the P-VOL.

Related reference
Forward resynchronization
Reverse resynchronization

Forward resynchronization

You can use one of the following methods to forward resynchronize pairs:

Normal Copy (Primary > Secondary): A full forward resynchronization from the P-VOL to the S-VOL. During a
Normal Copy, only the P-VOL is accessible to hosts for read/write operations.
Quick Resync (Primary > Secondary): A forward resynchronization from the P-VOL to the S-VOL where data is not
copied or resynchronized. The volumes are paired (PAIR status). The update copy operation copies the differential
data to the S-VOL.

During a Quick Resync, the P-VOL is accessible to hosts for read/write operations. Quick Resync does not ensure
data consistency, even if there is no host I/O during the resynchronization.

Related concepts
Splitting ShadowImage pairs

Reverse resynchronization

You can use one of the following methods to restore pairs:

Reverse Copy (Secondary > Primary): A full restoration from the S-VOL to the P-VOL. The differential data is
updated to the P-VOL.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 61/80
6/16/25, 6:04 PM ShadowImage User Guide
During a Reverse Copy you can delete or suspend the pairs, but you cannot create, split, or resynchronize pairs
that share the same P-VOL. The P-VOL is inaccessible to hosts.

If you are sharing a TC or UR volume with an SI volume, you cannot create a TC or UR pair with the shared
volume.

You cannot use Reverse Copy with an SI L2 pair.

Quick Restore (Secondary > Primary): A partial restoration that does not copy the data but does the following:
Swaps the P-VOL and S-VOLs including their RAID levels and drive types.
Pairs the volumes (PAIR status*).

*The pair status changes to COPY(RS-R)/RCPY first, and then it changes to PAIR.

Exchanges the P-VOL and S-VOL encryption statuses if an SI pair consists of encrypted volumes and a
nonencrypted volume.
CAUTION:
To prevent the two volumes from being swapped, the P-VOL and S-VOLs must be assigned to the same cache
logical partition (CLPR).

During a Quick Restore, the P-VOL and S-VOL are inaccessible. After a Quick Restore, the P-VOL is accessible.

Best Practice: If you have a small amount of differential data, use Reverse Copy instead of Quick Restore, since
Reverse Copy completes faster.

If you use volumes for which you set Data Retention Utility access attributes, Quick Restore does not exchange the
P-VOL and S-VOL access attributes.

For more information about using volumes for which you set Data Retention Utility access attributes, see Sharing
volumes and Data Retention Utility access attributes.

Note:HDvM - SN can show outdated information after a Quick Restore. To show the latest information, click
Refresh View.
Note:To minimize the time it takes to Quick Restore an SI pair, do not perform LDEV maintenance while the Quick
Restore is processing.

You can delete or suspend the pair while you are restoring the pair using Quick Restore but you cannot do the
following:

Create, split, or resynchronize pairs that share the same P-VOL.

Create a TC or UR pair with a volume shared by SI.

You cannot Quick Restore the following pairs:

An SI L2 pair
A pair volume for which you are formatting either internal volume using Quick Format.

For more information about formatting volumes using Quick Format, see the Provisioning Guide for your
storage system.

A pair in which one volume is a DP-VOL, though not both.

The capacity saving of either P-VOL or S-VOL is enabled.
An SI S-VOL you are sharing with an HTI volume.

By default, for pair resynchronization (Normal Resync or Reverse Copy), the maximum multiplicity of copy
processing for each pair is set to 24. However, if you set the Normal Resync Multiplexing option or Reverse Copy
Multiplexing option of local replica options to OFF, the multiplicity can be changed to 1. Make sure to set the Normal
Resync Multiplexing option or Reverse Copy Multiplexing option to OFF if the host I/O performance is prioritized.
These local replica options can be set by using HDvM - SN or CCI.

Workflow for resynchronizing ShadowImage pairs

Complete the following steps to resynchronize SI pairs:

1. Place the S-VOL offline.

2. Split or suspend the pair.
Note:The pair can also be in the process of being Quick Split (PSUS(SP)/PSUS status).
3. (Optional) If you are concerned about host server I/O performance, check to make sure the I/O load is light.

For more information about checking I/O performance, see the System Administrator Guide.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 62/80
6/16/25, 6:04 PM ShadowImage User Guide
4. Resynchronize the pair (see Resynchronizing or restoring ShadowImage pairs).
Related concepts
Pair splitting methods
Related reference
Forward resynchronization

Workflow for restoring ShadowImage pairs

Complete the following steps to restore SI pairs:

1. Place the P-VOL offline.

2. Split or suspend the pair.

If you plan to restore pairs using Reverse Copy, split or suspend the pairs sharing the same P-VOL.

If the SI pair you plan to restore shares a volume with TC or UR, suspend the TC or UR pair.

For more information about splitting or suspending pairs, see Splitting ShadowImage pairs or Suspending
ShadowImage pairs, respectively.

3. Restore the pair (see Resynchronizing or restoring ShadowImage pairs).

Related concepts
Pair splitting methods
Related reference
Reverse resynchronization
Sharing volumes with Universal Replicator

Resynchronizing or restoring ShadowImage pairs

Use this task to resynchronize or restore split or suspended pairs.

Resynchronizing split pairs typically takes less time than resynchronizing suspended pairs (PSUE status). Split pairs
typically contain much less accumulated differential data than the total amount of data in the P-VOL.

You can only resynchronize L2 pairs.

After performing a Quick Split, wait 20 seconds before a Normal Copy or Quick Resync resynchronization,
otherwise the operation might end abnormally.
The pair resynchronization (Normal Resync or Reverse Copy) requires some time to check if the differential data
exists even if there is no differential data. The amount of time to check the differential data takes longer as the
volume capacity increases, and it might take 10 minutes or more for 256 TB.

If you are using CCI to run commands, run the following command to resynchronize split pairs (PSUS status): pairresync

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication > Local
Replication.
2. In the Local Replication window, select the SI Pairs tab.

3. On the SI Pairs tab, select the pair you want to resynchronize, and then click Resync Pairs.

4. In the Resync Pairs window of the Resync Pairs wizard, complete the following steps:
For Resync Type, select the type of resynchronization you want to perform.

Values:

- Normal Copy (Primary > Secondary) (default): A full forward resynchronization.

- Quick Resync (Primary > Secondary): A partial forward resynchronization.

- Reverse Copy (Secondary > Primary): A full restoration of the P-VOL from the S-VOL.

- Quick Restore (Secondary > Primary): A partial restoration of the P-VOL from the S-VOL.

For more information about the types of SI pair resynchronization you can use, including complete
descriptions of the types, see Types of pair resynchronization.

For Copy Pace, select the rate at which you want the storage system to copy data.

Values:

- Slower: Improved host server I/O performance but slower processing speed.

- Medium (default): Average processing speed and host server I/O performance.

- Faster: Faster processing speed but slower host server I/O performance.

Note:The pace you select affects processing speed and host server I/O performance

For more information about performance, see Performance planning for ShadowImage.

5. Click Finish, and then confirm the settings.

6. Accept the default task name or enter a unique name.

You can enter up to 32 letters, numbers, and symbols, except the following:

\/:,;*?"<>|

7. If you want to monitor the task after submitting it, select Go to tasks window for status.
8. Click Apply to submit the task.
The pairs are resynchronized and the volumes are paired (PAIR status).
Note:If you are reverse resynchronizing and the task ends abnormally, the pair is suspended (PSUE status).

For more information about the PSUE status, see Device Manager - Storage Navigator pair status names and
descriptions.
Related information
Types of pair resynchronization
Resync Pairs wizard

Suppressing update copy operations during pair restoration

You can suppress update copy operations when you restore pairs using Quick Restore. Suppressing update copy
operations keeps the P-VOL and S-VOL unsynchronized and reduces the effect on host server I/O performance.

The pair status is PAIR.

Enable the Swap & Freeze system option.

Setting the RAID level

Complete the following steps to return to the original RAID level for the S-VOL and P-VOL after a Quick Restore when the
RAID levels of the volumes are different.

1. Split the pair.

2. Restore the pair using Quick Restore.

Related tasks
Splitting ShadowImage pairs
Resynchronizing or restoring ShadowImage pairs

Suspending ShadowImage pairs

When the following conditions apply, a ShadowImage pair is suspended, and the status of the pair is changed to PSUE:

the storage system detects an error condition related to an update copy operation
the storage system cannot keep the pair mirrored

At this time, write I/Os to the P-VOL continue and all tracks of the P-VOL are saved as differential data. When the pair is
resynchronized, the pair status changes to Resync/PENDING, and the entire P-VOL is copied to the S-VOL. For a split

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 65/80
6/16/25, 6:04 PM ShadowImage User Guide
pair, resynchronization is completed in a short time. But it takes the same period of time for a suspended pair to be
resynchronized as the initial copy operation.

You can use CCI to change the status of the pair to PSUE by using the pairsplit -S command.

You can change the status of the pair to PSUE by using the following procedure.

You must have Storage Administrator (Local Copy) role.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication > Local
Replication.
2. In the Local Replication window, select the SI Pairs tab.

3. On the SI Pairs tab, select the pair that you do not want to create, click More Actions > Suspend Pairs, and confirm
the settings.

4. Accept the default task name or enter a unique name.

You can enter up to 32 letters, numbers, and symbols, except the following:

\/:,;*?"<>|

5. If you want to monitor the task after submitting it, select Go to tasks window for status.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 66/80
6/16/25, 6:04 PM ShadowImage User Guide
6. Click Apply to submit the task.
The pair is suspended (PSUE status).
Related concepts
Creating ShadowImage pairs
Initial copy workflow
Update copy workflow

Deleting ShadowImage pairs

Delete the SI pairs that you no longer need. Deleting a pair unpairs the P-VOL and S-VOL but does not delete their data.
You can use the volumes of deleted pairs in another pair.

Related concepts
MP unit and pair deletion
Related tasks
Deleting ShadowImage pairs
Monitoring ShadowImage pair activity and status
Related reference
Prerequisites for deleting ShadowImage pairs

Prerequisites for deleting ShadowImage pairs

The pair must be unpaired and not in the process of being deleted and the volumes are not in the process of being
unpaired (SMPL(PD) status).

Items to consider before deleting ShadowImage pairs

Review the following list to understand what happens after an SI pair is deleted.

If an SI pair is deleted, the volume status changes from SMPL(PD) to SMPL. When the status changes to SMPL,
the pair is no longer displayed in the window. You can use the pairdisplay command of CCI to check the volume
status, but this command cannot differentiate SMPL from SMPL(PD). To differentiate them in CCI, use the inqraid
command to check if the volume is used by SI. If it is used by SI, the status is SMPL(PD). If it is not used by SI, the
status is SMPL.
After deleting an SI pair, if the number of pairs displayed in the summary section and the number of listed pairs in
the HDvM - SN window are different, configuration might being changed. Wait a while, and then select File >
Refresh All to update the configuration information.

Workflow for deleting ShadowImage pairs

Complete the following steps to delete an SI pair:

1. Ensure that all of the write I/O operations to the P-VOL have completed and that all secondary host applications
that access the P-VOL have stopped.
2. Set the P-VOL offline.
3. Verify that the SI pair is unpaired and not in the process of being unpaired.
4. Split the SI pair.
5. Delete the SI pair.

Related tasks
Splitting ShadowImage pairs
Deleting ShadowImage pairs

Deleting ShadowImage pairs

You must have Storage Administrator (Local Copy) role.

The P-VOL and the S-VOL must be synchronized.
In CCI, use the pairsplit -S command.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication > Local
Replication.
2. In the Local Replication window, select the SI Pairs tab.

3. On the SI Pairs tab, select the pair you want to delete, click More Actions > Delete Pairs, and then confirm the
settings.

4. Accept the default task name or enter a unique name.

You can enter up to 32 letters, numbers, and symbols, except the following:

\/:,;*?"<>|

5. If you want to monitor the task after submitting it, select Go to tasks window for status.
6. Click Apply to submit the task.
Note:To prevent the task from ending abnormally, wait until the P-VOL and S-VOL are unpaired (about 10 seconds)
before completing another pair task, such as creating pairs, or event waiting.
The pair is deleted and the P-VOL and S-VOL are unpaired.
Related reference
Prerequisites for deleting ShadowImage pairs
Delete Pairs window

MP unit and pair deletion

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 68/80
6/16/25, 6:04 PM ShadowImage User Guide
The MP unit assigned to an S-VOL cannot be used if a pair is created because the MP unit assigned to the P-VOL is also
assigned to the S-VOL. Deleting the pairs returns the allocation of processor responsibility to the state it was before the
pairs were created. However, the allocation cannot be returned in either of the following cases:

A user changed the allocation of the MP unit assigned to an S-VOL cannot be used if a pair is created because the
MP unit for the P-VOL or S-VOL of the SI pair.
When the pair is deleted, the write pending rate of the MP unit assigned to an S-VOL cannot be used if a pair is
created because the MP unit to which the S-VOL belongs is 50% or more, or the write pending rate of the original
MP unit assigned to an S-VOL cannot be used if a pair is created because the MP unit is 50% or more.

If the original MP unit assigned to an S-VOL cannot be used if a pair is created because the MP unit is already removed,
assign another MP unit assigned to an S-VOL.

Monitoring and maintaining ShadowImage

Monitor your SI system on an ongoing basis to keep track of pairs and volumes and their current and past conditions. You
can monitor pair status as well as pair synchronization rates, and you can check the pair task history to review and confirm
replication operations.

Note:The following maintenance activities do not affect your SI replication pairs:

Cache maintenance can reduce overall performance and should be scheduled during times of low system activity.
Maintenance of physical disk drives that provision LDEVs used by SI can be performed without impacting SI.
If a physical device failure occurs, the pair status is not affected because of the RAID architecture.
If a physical device failure requires the storage system to use dynamic sparing or automatic correction copy, the
pair status is not be affected.
If an LDEV failure occurs, the storage system suspends the pair.
If an SI pair is using an LDEV, certain activities are not allowed. You can only block (for maintenance), format, or
restore an LDEV that is in use by only a pair in PSUE status.

Viewing pair information for local replication

You can view pair information for local replication in the Replication window and in the summary section of the Local
Replication window in HDvM - SN. These windows show information such as the number of pairs in the storage system.

Note:If the information in the summary section is not up to date, the system has not completed processing the information.
Click the refresh icon to refresh the information in the window.

In CCI, use the pairdisplay command.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 69/80
6/16/25, 6:04 PM ShadowImage User Guide
2. The Replica LDEVs tab in the Replication window shows a list of LDEVs. From this window, you can perform the
following tasks:
Click the LDEV ID for a specific replica LDEV and open the LDEV Properties window.
View information for a list of replica LDEVs for the selected LDEV.

Monitoring ShadowImage pair activity and status

You can monitor the status of SI pairs using HDvM - SN.

The status of pairs displayed by HDvM - SN changes as the pair status changes in the storage system. The displayed state
is refreshed by HDvM - SN automatically. To manually refresh the HDvM - SN information, click the refresh icon.

Note:Unpaired P-VOLs and S-VOLs are not shown in HDvM - SN.

You must have Storage Administrator (Local Copy) role.

In CCI, use the pairdisplay command.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication > Local
Replication.
2. In the Local Replication window, select the SI Pairs tab.

3. In the summary section of the Local Replication page, view license information.
If the information in the window is not up to date, click the refresh icon to refresh the information in the window.
4. On the SI Pairs tab, locate the pair whose status you want to review, and then check the Status column.
HDvM - SNand the CCI pair status names are shown in the Status column in the format of HDvM - SN status/CCI
status, unless the names are the same. If they are the same, only the HDvM - SN status is displayed. For more
information about the items on this tab, see Monitoring ShadowImage pair and volume details.
5. (Optional) Click More Actions > View Pair Properties to view more details for a selected pair.

Related tasks
Monitoring ShadowImage pair and volume details
Related reference
Device Manager - Storage Navigator pair status names and descriptions
Pair status and available pair tasks
Command Control Interface pair status names
Unaffected S-VOL status and pair tasks
Local Replication window

Device Manager - Storage Navigator pair status names and descriptions

The following table lists HDvM - SN pair status names and descriptions, including the level of S-VOL access.

HDvM - SN CCI status Description P-VOL S-VOL

status access access

SMPL - The volume is not part of a pair. Read/write Read/write

enabled enabled

SMPL(PD) - The pair is in the process of being deleted. Read/write Read/write

disabled4 disabled

COPY(PD)2 COPY2 The paircreate initial copy is in progress.1 The Read/write Read only
storage system accepts read/write to the P-VOL enabled
but does not accept write operations to the S-
VOL.

PAIR - The initial copy operation has completed and the Read/write Read only
volumes are paired. The storage system performs enabled
update copy operations.

Data consistency is not ensured for SI pairs in this

status.

HDvM - SN CCI status Description P-VOL S-VOL

status access access

For more information about the initial and update

copy operations, see Initial and update copy
operations.

COPY2
COPY(SP)2 The pair is in the process of being Steady Split. Read/write Read only
The storage system: enabled

1. Copies the differential data to the S-VOL.1

The data in the S-VOL is identical to the
data in the P-VOL.
2. Splits the pair.

For more information about the Steady Split

method of splitting pairs, see Pair splitting
methods.

PSUS2
PSUS(SP)2 The pair is in the process of being Quick Split. The Read/write Read/write
differential data is copied to the S-VOL in the enabled enabled
1
background. You cannot delete pairs in this
status.

For more information about the Quick Split

method of splitting pairs, see Pair splitting
methods.

PSUS3
PSUS The pair has been split. The storage system stops Read/write Read/write
performing update copy operations but accepts enabled enabled
write I/Os for the S-VOL. The storage system
keeps track of updates to split P-VOLs and S-VOL
so that you can Quick Resync.

COPY2
COPY(RS)2 The pairresync CCI command is in progress.1 The Read/write Read only
storage system does not accept write I/Os for S- enabled
VOL. Resynchronizing split pairs copies only the
differential data to the S-VOL.

RCPY2
COPY(RS- The reverse pairresync CCI command is in Read only Read only

R) 2 progress.1 The storage system copies only the S-

VOL differential data to the P-VOL. The storage
system does not perform update copy operations
during a Reverse Copy or a Quick Restore. The
storage system does not accept write I/O
operations to S-VOL.

-
PSUE The storage system does the following: Read/write Read only
enabled
Suspends the pair.
Continues accepting read and write I/Os to
the P-VOL.
Stops update copy operations to the S-
VOL.
Marks the P-VOL as differential data.
Resynchronizing a pair copies the P-VOL
to the S-VOL.

HDvM - SN CCI status Description P-VOL S-VOL

status access access

Notes:

1. The starting time of the copy depends on the numbers of pairs and the storage system environment.
2. The pair status is displayed in the format of screen pair status/CCI pair status.
3. CCI display is as follows:
P-VOL: PSUS
S-VOL: SSUS
4. If the status was Read/write enabled before the transition to SMPL(PD), it is Read/write enabled.

Related reference
Command Control Interface pair status names

Command Control Interface pair status names

The following table lists the HDvM - SN pair status names and the corresponding CCI pair status names. The SMPL status
is not displayed on the Local Replication window SI Pairs tab (volumes in SMPL state are not listed).

HDvM - SN pair status name CCI pair status name

SMPL SMPL

COPY(PD)/COPY COPY

PAIR PAIR

COPY(SP)/COPY COPY

PSUS(SP)/PSUS PSUS

PSUS (P-VOL) PSUS

(S-VOL) SSUS

COPY(RS)/COPY COPY

COPY(RS-R)/RCPY RCPY

PSUE PSUE

Related reference
Device Manager - Storage Navigator pair status names and descriptions

Pair status and available pair tasks

The status of a pair determines the actions you can perform.

The following table lists the pair tasks that you can perform for each status.

Pair status Pair task

Create pairs Split pairs Resync pairs Resync pairs Suspend Delete
pairs pairs
(Normal Copy) (Reverse Copy)

SMPL(PD) NO NO NO NO NO NO

COPY(PD)/COPY YES YES NO NO YES YES

PAIR YES YES NO NO YES YES

COPY(SP)/COPY YES NO NO NO YES YES

PSUS(SP)/PSUS YES NO YES NO YES NO

PSUS YES NO YES YES YES YES

COPY(RS)/COPY YES NO NO NO YES YES

COPY(RS-R)/RCPY NO NO NO NO YES YES

PSUE YES NO YES NO NO YES

Related reference
Unaffected S-VOL status and pair tasks

L1, L2 pair status and supported pair tasks

The pair tasks you can complete on cascaded pairs depend on the L1 and L2 pair status. The tasks are dependent on the
following:

To perform an L1 pair task, the status of the L2 pair.

To perform an L2 pair task, the status of the L1 pair.
Supported read/write on L1 and L2 S-VOLs.

The following table lists the L1 pair tasks that you can complete based on the related L2 status.

L2 pair status L1 pair task

Create pairs Split pairs Resync pairs Resync pairs Suspend Delete pairs
pairs
(Normal copy) (Reverse
copy)

COPY(PD)/COPY Yes Yes Yes Yes Yes Yes

PAIR Yes Yes Yes Yes Yes Yes

COPY(SP)/COPY No No No No Yes Yes

PSUS(SP)/PSUS No No No No Yes Yes

PSUS Yes Yes Yes Yes Yes Yes

COPY(RS)/COPY Yes Yes Yes Yes Yes Yes

PSUE Yes Yes Yes Yes Yes Yes

The following table lists the L2 pair tasks that you can perform based on the related L1 status.
https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 73/80
6/16/25, 6:04 PM ShadowImage User Guide

L1 pair status L2 pair task

Create pairs Split pairs Resync pairs Resync pairs Suspend Delete
(Normal (Reverse pairs pairs
1 1
Copy) Copy)

COPY(PD)/COPY YES NO YES NO YES YES

PAIR YES NO YES NO YES YES

COPY(SP)/COPY YES NO YES NO YES YES

PSUS(SP)/PSUS NO NO YES NO YES YES

PSUS YES YES NO YES YES

YES2

COPY(RS)/COPY YES NO YES NO YES YES

COPY(RS- YES NO YES NO YES YES

R)/RCPY

PSUE YES NO YES NO YES YES

1. For L2 pairs, only Normal Copy or Quick Resync can be performed. You cannot perform a reverse
resynchronization (Reverse Copy or Quick Restore). For more information about resynchronizing L2 pairs, see
Resynchronizing or restoring ShadowImage pairs.
2. To split L2 pairs, the L1 pair status must be PSUS. For more information about the prerequisites for splitting L2
pairs, see Splitting ShadowImage pairs.

The following table lists the node volume read/write L1 and L2 pair status.

L1 Pair Status L2 pair status

COPY(PD)/COPY PAIR COPY(SP)/COPY PSUS(SP)/PSUS PSUS COPY(RS)/COPY PSUE

COPY(PD)/COPY Read only Read only Read only Read only Read only Read only Read only

PAIR

COPY(SP)/COPY

PSUS(SP)/PSUS Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write

PSUS

COPY(RS)/COPY Read only Read only Read only Read only Read only Read only Read only

COPY(RS-
R)/RCPY

PSUE

The following table lists the leaf vol read/write per L2 pair status.

L2 pair status

COPY(PD)/COPY PAIR COPY(SP)/COPY PSUS(SP)/PSUS PSUS COPY(RS)/COPY PSUE

Read only Read only Read only Read/Write Read/Write Read only Read only

Unaffected S-VOL status and pair tasks

The SI pair tasks you can perform depend on the pair's status and the status of unaffected S-VOLs.

The following table lists the pair tasks you can perform based on the status of S-VOLs related to the P-VOL in other pairs.

Status of unaffected Pair task

S-VOLs

Create pairs Split pairs Resync pairs Resync pairs Suspend Delete
pairs pairs
(Normal (Reverse
Copy) Copy)

SMPL(PD) NO NO NO NO NO NO

COPY(PD)/COPY YES YES YES NO YES YES

PAIR YES YES YES NO YES YES

COPY(SP)/COPY YES YES YES NO YES YES

PSUS(SP)/PSUS YES YES YES NO YES YES

PSUS YES YES YES YES YES YES

COPY(RS)/COPY YES YES YES NO YES YES

COPY(RS-R)/RCPY NO NO NO NO YES YES

PSUE YES YES YES YES YES YES

Monitoring ShadowImage pair and volume details

You can review the data related to L1 and L2 pairs and their volumes, including volume capacity, pair status, P-VOL and S-
VOL, and identifiers.

In CCI, use the pairdisplay command.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication > Local
Replication.
2. In the Local Replication window, select the SI Pairs tab.

3. In the SI Pairs tab, select the pair, and then click More Actions > View Pair Properties.
4. In the View Pair Properties window, view the pair properties.

Related tasks
Monitoring ShadowImage pair activity and status
Related reference
View Pair Properties window
Local Replication window

Monitoring ShadowImage pair synchronization rates

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 76/80
6/16/25, 6:04 PM ShadowImage User Guide
You can view the percentage of synchronized data between the P-VOL and S-VOL from the View Pair Synchronization
Rate window.

In CCI, use the pairdisplay command.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication > Local
Replication.
2. In the Local Replication window, select the SI Pairs tab.

3. On the SI Pairs tab, select the pair, and then click More Actions > View Pair Synchronization Rate.

4. On the View Pair Synchronization Rate window, click Refresh to show the latest synchronization rate.
Note:If you close the window, information in the Local Replication window might not be up to date. Click the refresh
icon to refresh the information in the window.

Related reference
View Pair Synchronization Rate window

Monitoring consistency groups

You can view the number of consistency groups (CTGs) and the details and individual properties for CTGs from the
following section and tabs in the Local Replication window in HDvM - SN:

Note:CCI does not have a command to view the number of consistency groups.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 77/80
6/16/25, 6:04 PM ShadowImage User Guide
The summary section. Use this section to view the number of CTGs and the number of pairs.
The SI Pairs tab. Use this tab to:
View a list of SI pairs.
Monitor pair activity and status (see Monitoring ShadowImage pair activity and status).
Monitor pair synchronization rates (see Monitoring ShadowImage pair synchronization rates).
The TI Root Volumes tab. Use this tab to view a list of HTI pairs (see Viewing a list of Thin Image pairs).
The Consistency Groups tab. Use this tab to:
View a list of CTGs.
View CTG properties (see Viewing consistency group properties).

The following figure shows the Local Replication window displaying the summary section and the SI Pairs tab.

Viewing consistency group properties

Note:CCI does not have a command to view consistency group properties.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication > Local
Replication.
2. In the Local Replication window, select the Consistency Groups tab.

3. On the Consistency Groups tab, click the CTG ID for the CTG you want to view properties.

4. In the Consistency Group Properties window, view the CTG's properties, such as group information for local
replication.

Viewing a list of Thin Image pairs

You can view a list of HTI pairs on the TI Root Volumes tab in the Local Replication window in HDvM - SN.

In CCI, use the pairdisplay command.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication > Local
Replication.
2. In the Local Replication window, select the TI Root Volumes tab.

3. On the TI Root Volumes tab, view the list of HTI pairs.

Monitoring pair task history

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 79/80
6/16/25, 6:04 PM ShadowImage User Guide
You can review a history of the tasks you have completed on a pair from the History window in HDvM - SN. The storage
system stores a history of up to 1,024,000 of the last tasks. If you use 1,000 or more pairs concurrently, some operation
history might not be recorded.

Note:You can also check the task history of SI pairs by using audit logs. For details, see the Hitachi Audit Log User Guide.

1. In the Explorer pane, click Storage Systems, expand the storage system tree, and then click Replication.

https://docs.hitachivantara.com/internal/api/webapp/print/0630c1f2-adc0-403f-8521-525d041f80ec 80/80

ShadowImage User Guide For VSP One Block
No ratings yet
ShadowImage User Guide For VSP One Block
85 pages
ShadowImage Guide
No ratings yet
ShadowImage Guide
84 pages
GAD Knowledge Transfer - Customer Presentation 04272015
No ratings yet
GAD Knowledge Transfer - Customer Presentation 04272015
112 pages
Oracle Backup with Hitachi Systems
No ratings yet
Oracle Backup with Hitachi Systems
27 pages
TXI6752 Course Description v1-0
No ratings yet
TXI6752 Course Description v1-0
3 pages
Hitachi Unified Storage Replication User Guide
No ratings yet
Hitachi Unified Storage Replication User Guide
822 pages
PDF Feature Integrated Data Protection0211
No ratings yet
PDF Feature Integrated Data Protection0211
8 pages
Module 06 Advanced Features
No ratings yet
Module 06 Advanced Features
11 pages
Nbu82adm Les06
No ratings yet
Nbu82adm Les06
43 pages
Volume Shadow Copy Service
No ratings yet
Volume Shadow Copy Service
19 pages
OpenStorageLogging060811 Symconnect 4
No ratings yet
OpenStorageLogging060811 Symconnect 4
25 pages
Hitachi ShadowImage For zOS User Guide
No ratings yet
Hitachi ShadowImage For zOS User Guide
162 pages
HpXPShadowImage For zOS GU Rootsan Technologies PVT LTD
No ratings yet
HpXPShadowImage For zOS GU Rootsan Technologies PVT LTD
144 pages
Storage Mirroring Guide 1
No ratings yet
Storage Mirroring Guide 1
197 pages
Hitachi Shadow Image CCI
No ratings yet
Hitachi Shadow Image CCI
37 pages
02 - StorageUnit
No ratings yet
02 - StorageUnit
8 pages
1209tot Article Secondary PDF
No ratings yet
1209tot Article Secondary PDF
10 pages
Storage Overview & Architecture
No ratings yet
Storage Overview & Architecture
57 pages
EMC ProtectPoint For VMAX3 Overview - SRG
No ratings yet
EMC ProtectPoint For VMAX3 Overview - SRG
18 pages
Volume Shadow Copy Services
No ratings yet
Volume Shadow Copy Services
10 pages
Block Volume 100
No ratings yet
Block Volume 100
27 pages
Increase Storage Capacity by 25GB
No ratings yet
Increase Storage Capacity by 25GB
56 pages
Wipro RPS Assignment Day 6
No ratings yet
Wipro RPS Assignment Day 6
15 pages
Day 3 Storage
No ratings yet
Day 3 Storage
62 pages
TSI0556-Hitachi TagmaStore USP Software Solutions SG v2.0-2
No ratings yet
TSI0556-Hitachi TagmaStore USP Software Solutions SG v2.0-2
168 pages
NBU Best Practice - AdvancedDisk (April 2011) PDF
No ratings yet
NBU Best Practice - AdvancedDisk (April 2011) PDF
23 pages
VMAX Local Replication
No ratings yet
VMAX Local Replication
30 pages
Symmetrix Local Replication
No ratings yet
Symmetrix Local Replication
10 pages
Netapp Storage Efficiency: Author Srisuba Selvachamy
No ratings yet
Netapp Storage Efficiency: Author Srisuba Selvachamy
45 pages
Copy On WriteSnapshotUserGuide
No ratings yet
Copy On WriteSnapshotUserGuide
162 pages
Volume Shadow
No ratings yet
Volume Shadow
11 pages
NetBackup Guide for IT Professionals
No ratings yet
NetBackup Guide for IT Professionals
93 pages
Nbu82adm Les02
No ratings yet
Nbu82adm Les02
33 pages
What Is New in Netbackup 6 5
No ratings yet
What Is New in Netbackup 6 5
42 pages
Volume Shadow Copy: Pmp/Mcse
No ratings yet
Volume Shadow Copy: Pmp/Mcse
26 pages
Understanding RAID Levels and Benefits
No ratings yet
Understanding RAID Levels and Benefits
50 pages
Hus VM Block Module Hitachi Thin Image User Guide V 73-03-3x
No ratings yet
Hus VM Block Module Hitachi Thin Image User Guide V 73-03-3x
164 pages
ALL Notes
No ratings yet
ALL Notes
45 pages
EMC TimeFinder: Mirror, Clone, Snap Comparison
No ratings yet
EMC TimeFinder: Mirror, Clone, Snap Comparison
4 pages
VSP MICROCODE VERSION 70-02-13-00/00 RELEASED 09/07/2011 Newly Supported Features and Functions For Version 70-02-13-00/00
No ratings yet
VSP MICROCODE VERSION 70-02-13-00/00 RELEASED 09/07/2011 Newly Supported Features and Functions For Version 70-02-13-00/00
25 pages
Enterprise Storage Solutions Guide
No ratings yet
Enterprise Storage Solutions Guide
57 pages
Database SanpMirroring Proposal
No ratings yet
Database SanpMirroring Proposal
15 pages
HPE 3PAR Features: HPI RFQ - 28 July 2016
No ratings yet
HPE 3PAR Features: HPI RFQ - 28 July 2016
20 pages
IT436-week 3 - Physical Layer-Storage
No ratings yet
IT436-week 3 - Physical Layer-Storage
62 pages
SIT452-Week 5 - Physical Layer-Storage
No ratings yet
SIT452-Week 5 - Physical Layer-Storage
62 pages
HUS SnapshotAdministrationGuide USF0083
No ratings yet
HUS SnapshotAdministrationGuide USF0083
28 pages
Symantec NetBackup Interview Questions and Answers Tecz PDF
No ratings yet
Symantec NetBackup Interview Questions and Answers Tecz PDF
3 pages
Symantec NetBackup Interview Questions and Answers - Tecz
50% (2)
Symantec NetBackup Interview Questions and Answers - Tecz
3 pages
Open-E Data Replication
No ratings yet
Open-E Data Replication
2 pages
NetApp Disk Administration
No ratings yet
NetApp Disk Administration
30 pages
Untitled Document
No ratings yet
Untitled Document
8 pages
Ax45 Software Overview
No ratings yet
Ax45 Software Overview
12 pages
Hitachi THI0517 Data Systems Storage Foundations Student Guide Vol 2 PDF
No ratings yet
Hitachi THI0517 Data Systems Storage Foundations Student Guide Vol 2 PDF
280 pages
Local Replication: Section 3: Business Continuity
No ratings yet
Local Replication: Section 3: Business Continuity
39 pages
Learn TSM
No ratings yet
Learn TSM
9 pages
What Is New in Netbackup 6.5
No ratings yet
What Is New in Netbackup 6.5
42 pages
Login Vulnerabilities Overview
No ratings yet
Login Vulnerabilities Overview
72 pages
Reference Manual For The CLOUD 370x F Contactless Desktop Readers
No ratings yet
Reference Manual For The CLOUD 370x F Contactless Desktop Readers
82 pages
Tutorial On Seismic Reflection CDP Data Processing in The Radexpro Plus Software
No ratings yet
Tutorial On Seismic Reflection CDP Data Processing in The Radexpro Plus Software
58 pages
Booting AIX Into Maintenance Mode
No ratings yet
Booting AIX Into Maintenance Mode
6 pages
PDP PPT Project
No ratings yet
PDP PPT Project
13 pages
Anybus Communicator Profinet With Siemens s7 1500 PLC Tia Portal PDF
No ratings yet
Anybus Communicator Profinet With Siemens s7 1500 PLC Tia Portal PDF
16 pages
5bda3f516ed0d
No ratings yet
5bda3f516ed0d
2 pages
@achyarnurandi - Simple Configuration TDM Emulation Service On Your Nokia 7705-SAR8 and 7705-SARF
100% (1)
@achyarnurandi - Simple Configuration TDM Emulation Service On Your Nokia 7705-SAR8 and 7705-SARF
10 pages
st2100 1849957
No ratings yet
st2100 1849957
39 pages
Examine The Benefits and Disadvantages of Direct Mail.
No ratings yet
Examine The Benefits and Disadvantages of Direct Mail.
31 pages
Unit 7 Sample Test
No ratings yet
Unit 7 Sample Test
7 pages
User Exit Enhancement: and Explained in Detail
No ratings yet
User Exit Enhancement: and Explained in Detail
5 pages
ExaGrid-Retention Time-Lock For Ransomware Recovery DS
No ratings yet
ExaGrid-Retention Time-Lock For Ransomware Recovery DS
3 pages
Computer Organisation and Architecture.
100% (1)
Computer Organisation and Architecture.
178 pages
Linux Installation
No ratings yet
Linux Installation
7 pages
SQL & Database Basics for BBA Students
No ratings yet
SQL & Database Basics for BBA Students
25 pages
Comparing Global System For Mobile and G-NetTrack Signal Strength in Drive Test Study
No ratings yet
Comparing Global System For Mobile and G-NetTrack Signal Strength in Drive Test Study
8 pages
Digital Integrated Circuits
No ratings yet
Digital Integrated Circuits
58 pages
SOP Subscriber Details Updation Version 1.1
No ratings yet
SOP Subscriber Details Updation Version 1.1
49 pages
01-MA5600T Product Introduction ISSUE1.00
No ratings yet
01-MA5600T Product Introduction ISSUE1.00
48 pages
2023 Unity Immortality Case Study
No ratings yet
2023 Unity Immortality Case Study
14 pages
OEE Monitoring System with Raspberry Pi
No ratings yet
OEE Monitoring System with Raspberry Pi
14 pages
PHP 6 MYSQL Programming For The Absolute Beginner 1st Edition Andrew B. (Andrew B. Harris) Harris Available Full Chapters
No ratings yet
PHP 6 MYSQL Programming For The Absolute Beginner 1st Edition Andrew B. (Andrew B. Harris) Harris Available Full Chapters
106 pages
Schneider Electric - Advantys-STB - STBNIP2311
No ratings yet
Schneider Electric - Advantys-STB - STBNIP2311
4 pages
Setting Up TomoChain Development Environment
No ratings yet
Setting Up TomoChain Development Environment
26 pages
Appbot Riley User Manual
No ratings yet
Appbot Riley User Manual
10 pages
Bca DTP Practiles
No ratings yet
Bca DTP Practiles
7 pages
examSectionGuide1987 - AdmitCard - 2025 03 06 03 08
No ratings yet
examSectionGuide1987 - AdmitCard - 2025 03 06 03 08
4 pages
CN Mid Imp Questions
No ratings yet
CN Mid Imp Questions
2 pages
Sample Resume - Fresher
No ratings yet
Sample Resume - Fresher
4 pages