Enterprise Storage

Examining Hitachi Copy-on-Write

Snapshot Software Capabilities
for Hitachi Thunder 9500 V Series Storage Systems
A Technical White Paper

By Christophe Bertrand

August 2004
Executive Summary
For most businesses around the globe, limited availability of business-critical data is
simply not an option: data must be protected and available, 24/7.

From a storage infrastructure perspective, this translates into the ability to blend high-
availability solutions with advanced disaster recovery techniques so that recovery will
happen almost automatically, whatever the reason for the failure, with no loss of data
and no impact to the production environment. For the Hitachi Thunder 9500 V
Series modular storage systems, Hitachi Data Systems offers two internal mirroring
solutions: Hitachi ShadowImage In-System Replication and Hitachi Copy-on-Write
Snapshot software (formerly known as Hitachi QuickShadow). This paper provides a
brief look at these software solutions and then presents an in-depth evaluation of
Copy-on-Write Snapshot software capabilities, with periodic comparisons to
ShadowImage In-System Replication software facilities.

The use of snapshot technology is becoming more pervasive in many organizations

because of its benefits over other traditional methods of backup. Copy-on-Write
Snapshot software is really a first line of defense for data protection, and, because it
performs in-system replication, it offers a fast and reliable process. While it differs from
ShadowImage In-System Replication software, Copy-on-Write Snapshot software
provides similar data protection benefits and requires less storage to maintain
duplicate volumes, delivering advanced enterprise-class data protection for Thunder
9500 V Series storage systems.
Contents
Introduction: Overview of Mirroring Solutions for Thunder 9500 V Series Storage Systems .......... 1
Hitachi ShadowImage In-System Replication Software.......................................................................................1
Hitachi Copy-on-Write Snapshot Software.................................................................................................................2
General Use and Purpose of Copy-on-Write Snapshot Software ....................................................................2
Copy-on-Write Snapshot Software Specifications............................................................................... 5
Copy-on-Write Snapshot Software Commands ................................................................................. 10
Creating Pairs (Paircreate).................................................................................................................................................10
Snapshot Instruction (Pairresync and Pairsplit)......................................................................................................11
Deleting Pairs (Pairsplit -S) ................................................................................................................................................11
Restore Instruction (Pairresync -restore).....................................................................................................................11
Copy-on-Write Snapshot Software Pair Status .................................................................................. 12
Pair Status Transitions ........................................................................................................................................................12
Pair Status Conditions ........................................................................................................................................................13
Internal Processing and Accessibility in Each Pair Status .................................................................................14
Copy-on-Write Snapshot Software Control Method ......................................................................... 14
Read/Write control method in PSUS status.............................................................................................................14
Read/Write control method ............................................................................................................................................15
Differential bit management ..........................................................................................................................................15
Error processing.....................................................................................................................................................................16
Overview of RAID Manager ................................................................................................................. 18
RAID Manager Features .....................................................................................................................................................18
Supported Platforms...........................................................................................................................................................19
Overview of Command Control Interface (CCI).....................................................................................................19
Examples of Copy-on-Write Snapshot Software Usage..................................................................... 20
Overnight Backup Operation..........................................................................................................................................20
Backup Operation within the Same Storage System Enclosure ...................................................................22
Restore Operation ................................................................................................................................................................24
Copy-on-Write Snapshot for Thunder 9500 V Series Systems: Conclusion..................................... 25
Examining Hitachi Copy-on-Write
Snapshot Software Capabilities
for Hitachi Thunder 9500 V Series Storage Systems
A Technical White Paper

By Christophe Bertrand

Introduction: Overview of Mirroring Solutions for Thunder

9500 V Series Storage Systems
In today's very challenging economic environment, the difference between success and failure for any
organization is based on savvy leadership supported by resilient and predictable information and
storage systems. The increasingly competitive world of e-commerce only exacerbates the burden on
the storage infrastructure and places significant demands on data availability and redundancy. In many
cases, limited availability of business-critical data is simply not an option: data must be protected and
available, 24/7.

From a storage infrastructure perspective, this translates into the ability to blend high-availability
solutions with advanced disaster recovery techniques so that recovery will happen almost automatically,
whatever the reason for the failure, with no loss of data and no impact to the production environment.
For the Hitachi Thunder 9500 V Series storage systems, Hitachi Data Systems offers two internal
mirroring solutions: Hitachi ShadowImage In-System Replication and Hitachi Copy-on-Write Snapshot
software (formerly known as Hitachi QuickShadow). This paper provides a brief look at these software
solutions and then presents an in-depth evaluation of Copy-on-Write Snapshot software capabilities,
specifically those applicable to Thunder 9500 V Series systems. It also offers periodic comparisons to
ShadowImage In-System Replication software capabilities to illustrate which of these similar software
products is the best choice in various scenarios.

Hitachi ShadowImage In-System Replication Software

ShadowImage In-System Replication software provides a nondisruptive, customer-managed, and host-
independent data replication solution for creating RAID-protected copies of any customer-accessible data
within a single Hitachi storage system. ShadowImage software replicates large volumes of information
within Hitachi storage systems without impacting service levels, timing out, or affecting performance
levels. The information volumes can then be split away from the host application and used for business
continuance, testing, data mining applications, and nondisruptive system backups while your business
continues to run at full capacity. (See Table 1.)

1
Table 1: ShadowImage In-System Replication Software Features.

Feature Hitachi Thunder 9500 V Series Storage Systems

Operating Systems Supported All those supported by the Thunder 9500 V Series systems
Maximum Number of Copies per Source 1
Volume
Maximum Number of Copy Pairs per System 31
Built-in Additional RAID Protection Yes
All Volumes Customer Configurable Yes
Support for IBM PPRC Host Software Functions N/A

Support for IBM DFSMSdss Host Software N/A

Functions
Support for IBM FlashCopy Functions N/A

Hitachi Copy-on-Write Snapshot Software

Copy-on-Write Snapshot software accelerates backup and recovery processes by reducing the amount
of disk storage with the capability for quick restoration of production data. Copy-on-Write Snapshot
software builds Copy-on-Write snapshots (point-in-time copies) and full-copy business continuance
volumes of production data for nondisruptive backup. As a result, Copy-on-Write Snapshot software
reduces traditional, tape-based application restore time from hours to seconds.

Copy-on-Write Snapshot software is Hitachis latest storage-based hardware solution designed to reduce
backup time and provide point-in-time backup copies. The Copy-on-Write Snapshot software primary
volumes (P-VOLs) contain the original data, and the snapshot images (V-VOLs) contain the snapshot data.
Since each P-VOL is paired with its V-VOL independently, each volume can be maintained as an
independent copy set. Copy-on-Write Snapshot software supports up to 14 Copy-on-Write snapshot
images per P-VOL or source volume.

Copy-on-Write Snapshot software operations can be performed from a UNIX and/or PC server host
using command control interface (CCI) software. Copy-on-Write Snapshot software commands are
issued from CCI (RAID Manager) through command devices in the storage system.

General Use and Purpose of Copy-on-Write Snapshot Software

Copy-on-Write Snapshot software enables the storage system to internally retain a logical replica of
primary data at the point in time the Copy-on-Write Snapshot software command is issued. Copy-on-
Write Snapshot software is used to restore the data to that point in time if a logical error occurs in the
primary volume.

2
The Copy-on-Write Snapshot program configuration includes a P-VOL, a number of V-VOLs, a data pool
(POOL), Hitachi Resource Manager utility package (DAMP), and the CCI (RAID Manager).

: : Thunder 9500 V Series systems manage both the original and copied data that exists at the time of
snapshot instruction. Copy-on-Write Snapshot software supports 254 pairs on both Hitachi Thunder
9530V entry-level storage decks and Hitachi Thunder 9570V high-end modular storage systems.
Thunder 9580V and Thunder 9585V ultra high-end modular storage systems support 1,022
Copy-on-Write Snapshot pairs.
: : Each Copy-on-Write Snapshot pair consists of one P-VOL and up to 14 V-VOLs, which are located in
the same Thunder 9500 V Series storage systems controller. The Copy-on-Write Snapshot P-VOLs
are the primary (source) volumes that contain the original data. The Copy-on-Write Snapshot V-
VOLs are duplicated volumes that contain the Copy-on-Write data that is created at the time of
snapshot instruction.
: : The Copy-on-Write Snapshot V-VOL contains physical data from the primary volume and the
differential data is stored in the POOL. This differs from the ShadowImage In-System Replication
function where all the data is retained only in the secondary volume. One POOL can be defined for
each controller. Each POOL can handle two or more primary volumes and the differential data of
two or more V-VOLs.
: : Copy-on-Write Snapshot software operations can be performed from either an UNIX or PC server
host using CCI software and/or the Resource Manager software (DAMP) GUI interface.
: : The Resource Manager software (DAMP) GUI and the Command Control Interface have the
capabilities to set up the Copy-on-Write Snapshot environmentP-VOLs, V-VOLs, and POOLs. The
GUI and CCI also allow customers to perform Copy-on-Write Snapshot software operations, such as
Copy-on-Write Snapshot pair status information displays, defining the number of V-VOLs
(snapshots) per P-VOLs, and deleting Copy-on-Write Snapshot pairs.

Since the replicated volume created by Copy-on-Write Snapshot software comprises differential data
stored in the POOL and physical data from the primary volume (P-VOL), this is different from
ShadowImage In-System Replication software, which houses all data in the secondary volume.
Therefore, even if the capacity of the POOL volume used is smaller than the primary volume, Copy-on-
Write Snapshot software is able to logically create a replica volume of the data at the point in time of the
Snapshot Instruction. POOL is also able to share differential data of multiple primary volumes and
multiple Snapshot Images.

In this document, terms are defined as follows:

: : Data Pool: volume in which only differential data is stored (POOL)
: : Snapshot Image: a virtual replica volume for the primary volume (V-VOL); this is an internal volume
that is held for restoration purposes

When the Copy-on-Write Snapshot software pair is created, P-VOL data, at the point in time the pair is
created, is logically stored in the Snapshot Image. By restoring data in the Snapshot Image in the case of
a logical error of the P-VOL, the data can be restored back to the time it was created.

Different from ShadowImage In-System Replication software, Copy-on-Write Snapshot software can
create a maximum of 14 Snapshot Images per P-VOL. Therefore, multiple generations of data can be
managed within a disk storage system.

3
Instructions for paircreate and pairdelete for Copy-on-Write Snapshot software are issued from the RAID
Manager, a software program installed on the server.

Setting and deleting Snapshot Images, data pool, and command devices, instructions for which are
issued from the RAID Manager, is done through the Disk Array Management Program 2. Figure 1
highlights the capabilities and functionality of Copy-on-Write Snapshot software.

Figure 1: Overview of Copy-on-Write Snapshot Software.

Host
RAID Manager

Controlling Copy-on-Write Snapshot

Data (Paircreate, Pairsplit, etc.) Data
R/W R/W

Command
PC Device

Disk Array
Management P-VOL POOL V-VOL
Program 2 Copy-on-Write
Physical data Snapshot Volume Physical Data Logical Data
Pairs (Differential
Creating Pair Data)
Controlling Copy-on-Write Snapshot Splitting
(Specifying/Releasing Restore V-VOL
Command Device, POOL, and
Copy-on-Write Snapshot Image)
Logical Data
P-VOL: Primary Volume
POOL: Data Pool Area
V-VOL: Copy-on-Write Thunder 9500 V Series Storage System
Snapshot Image
R/W: Read/Write

The capabilities and functionality of Copy-on-Write Snapshot software allow management of multiple generations of
data within a disk storage system.

The general image of the restore operation, which is the purpose of this Copy-on-Write Snapshot software
function, is shown in Figure 2. In comparison, the Snapshot Image can be restored onto the P-VOL. In
the case where multiple V-VOLs exist, any Snapshot Image data can be restored onto the P-VOL.

4
Figure 2: Overview of the Restore Operation.

Logical
P-VOL Error P-VOL V-VOL Generation #1

Restored Using
Copy-on-Write Snapshot Software
Obtained at Generation #2 V-VOL Generation #2

V-VOL Generation #n

To restore from the logical error instance, Copy-on-Write Snapshot software is obtained at Generation#2 and employed
in the restore operation.

Copy-on-Write Snapshot Software Specifications

Table 2: Copy-on-Write Snapshot Software Specifications.

Item Copy-on-Write Snapshot ShadowImage In-System

Replication (reference)

Equipment type Thunder 9530V, Thunder 9570V, Thunder 9530V, Thunder 9570V, Thunder
Thunder 9580V, and Thunder 9585V 9580V, and Thunder 9585V systems
systems
User interface RAID Manager RAID Manager
Disk Array Management Program 2 Disk Array Management Program 2
(see Note 1) (see Note 1)
Unit of pair Manages per logical unit Manages per logical unit
management
Supported cache Thunder 9530V: 1GB / CTL 1GB or 2GB
memory capacity Thunder 9570V: 1GB, 2GB / CTL Thunder
9580V/ Thunder 9585V: 2GB, 3GB, 4GB / CTL

Max number of Unlimited Unlimited

HDDs
Max number Thunder 9530V: 254 pairs (254 P-VOL) 31 pairs per system (31 P-VOL)
of pairs Thunder 9570V: 254 pairs (254 P-VOL)
Thunder 9580V/Thunder 9585V: 1022 pairs
(1022 P-VOL)
Pair structure 1:14 (With no cascade function) 1:1 (With no cascade function)

5
Table 2: Copy-on-Write Snapshot Software Specifications (continued).

Item Copy-on-Write Snapshot ShadowImage In-System

Replication (reference)

Size of logical unit P-VOLPOOL The logical unit size must always be
(The POOL in this case means a POOL P-VOL=S-VOL
capacity used by a single Snapshot Image.)
Arrangement of Within the same controller Within the same controller
P-VOL and S-VOL
(POOL)

Supported RAID RAID-1, RAID-5, RAID-1+0 RAID-0, RAID-1, RAID-5, RAID-1+0

levels
RAID level of Applicable to a combination of Applicable to a combination of
P-VOL and S-VOL different RAIDs different RAIDs
(POOL) Difference between the drive configurations Difference between the drive configurations
is allowed is not allowed
Maximum capacity <4GB cache memory> No limitations (Drives with a capacity of up
of P-VOL/S-VOL Total P-VOL capacity + (Total POOL capacity) to 146GB are supported.)
(POOL) x 3 < 30TB
<3GB cache memory>
Total P-VOL capacity + (Total POOL capacity)
x 3 < 22.5 TB
<2GB cache memory>
Total P-VOL capacity + Total POOL capacity)
x 3 < 15TB
<1GB cache memory>
Total P-VOL capacity + Total POOL capacity)
x 3 < 4.2 TB (see Note 2)
Interface with Fibre Fibre
a host

Differential It manages It manages

management
Number of data One per each CTL
pools that can
be set
Access to the The data pool is not recognized from the
data pool host

Number of LUNs 64 LUNs!

that can be set in a
pool
Expansion of POOL Possible (The capacity is expandable by
capacity adding volume(s) to the data pool.)

6
Table 2: Copy-on-Write Snapshot Software Specifications (continued).

Item Copy-on-Write Snapshot ShadowImage In-System

Replication (reference)

Reduction of POOL Possible only when all Snapshot Images

capacity have been deleted
RAID levels of the Applicable to a combination of different
volumes in the RAIDs
same POOL Difference between the drive configurations
is allowed
Unification of the Not available
logical units to the
volume(s) in the
POOL

Formatting the Not available

volume(s) in the
POOL
Invalidation/ Not available
segmentation of
the logical units
in the POOL

Number of V-VOLs Thunder 9530V and Thunder 9570V systems:

that can be set up to 512, including normal LUNs
Thunder 9580V and Thunder 9585V systems:
up to 2048, including normal LUNs

Access to the V-VOL Read/Write not accepted

in the SMPL status
Unification of the Not available
logical units for the
V-VOLs

Formatting of the Not available

V-VOL

Reduction of the Possible only when pair status is SMPL

V-VOLs
Invalidation/ Not available
segmentation of
the V-VOLs
Initial copy Not required Required
Resynchronization Not required Available
(from P-VOL to
Snapshot Image)

7
Table 2: Copy-on-Write Snapshot Software Specifications (continued).

Item Copy-on-Write Snapshot ShadowImage In-System

Replication (reference)

Resynchronization Available Available

(from Snapshot
Image to P-VOL)
Pair Delete Available (see Note 3) Available (see Note 4)
Hitachi TrueCopy Available Available
Remote Replication
software (basic)

Cascade function Not available Available (only P-VOL)

with TrueCopy
software (basic)
ShadowImage In- Available
System Replication
software

Cascade function Not available

with ShadowImage
In-System
Replication
software
LUN management Available
LUN security Available
Interchange Not available Not available
between P-VOL and
Snapshot Image
Unification of LUN Not available Not available
on pair
Pair creation of Available Available
unified LUNs
Deletion/expansion Not available Not available
of paired LUNs

Screening/splitting Not available Not available

of paired LUNs
Formatting of Not available Not available
paired LUNs
Instruction to make Not available Not available
P-VOL/ Snapshot
Image resident

Hot replacement of Not available Not available

the microprogram

8
Table 2: Copy-on-Write Snapshot Software Specifications (continued).

Item Copy-on-Write Snapshot ShadowImage In-System

Replication (reference)

Controller The dual controller configuration is The dual controller configuration is

configuration indispensable indispensable
Potential effect Reboot is required Reboot is not required
caused by Program
Product installation

Extent of effect of Snapshot Image failure doesnt occur due to Snapshot Image failure occurs due to a
controller failure a controller failure controller failure

Action of threshold Send warning to RAID Manager No action

over POOL
Extent of effect of All V-VOLs become PSUE in 100% of using All V-VOLs delete in 100% of using size of
capacity over POOL size of POOL (the PSUE status means that POOL
P-VOL data, as of the point in time when the
Copy-on-Write Snapshot instruction is
given, cannot be retained in a Snapshot
Image because a failure has occurred in the
disk system)
Extent of effect of Since the P-VOL data is also used for A failure when P-VOL is being copied causes
P-VOL failure Snapshot Image, a Snapshot Image failure a data loss because data duplication is not
occurs due to a P-VOL failure completed
Except when the P-VOL is being copied,
there is no data loss
Note 1: To specify/cancel a command device, POOL, or Snapshot Image, use Disk Array Management Program 2.
Note 2: Copy-on-Write Snapshot software restricts the capacity of P-VOL/POOL. The support capacity value of P-VOL and POOL varies depending on
the capacity ratio of the P-VOL and POOL. The following table shows the support capacity for each capacity ratio. In addition, the maximum
capacity of the total P-VOL for the Thunder 9570V system is 8GB.
Note 3: The data of Snapshot Image is lost.
Note 4: The S-VOL data is not lost.

Table 3: Supported Capacity of P-VOL and POOL (Cache Memory 1GB/CTL).

The capacity ratio of Supported capacity of Supported capacity of

P-VOL and POOL P-VOL (TB) POOL (TB)

1:0.5 1.7 0.8

1:1 1.0 1.0
1:3 0.4 1.3

9
Table 4: Supported Capacity of P-VOL and POOL (Cache Memory 2GB/CTL).

The capacity ratio of Supported capacity of Supported capacity of

P-VOL and POOL P-VOL (TB) POOL (TB)

1:0.5 6.1 3.0

1:1 3.8 3.8
1:3 1.5 4.5

Table 5: Supported Capacity of P-VOL and POOL (Cache Memory 3GB/CTL).

The capacity ratio of Supported capacity of Supported capacity of

P-VOL and POOL P-VOL (TB) POOL (TB)

1:0.5 9.2 4.6

1:1 5.7 5.7
1:3 2.3 6.9

Table 6: Supported Capacity of P-VOL and POOL (Cache Memory 4GB/CTL).

The capacity ratio of Supported capacity of Supported capacity of

P-VOL and POOL P-VOL (TB) POOL (TB)

1:0.5 12.3 6.1

1:1 7.7 7.7
1:3 3.0 9.2

Copy-on-Write Snapshot Software Commands

Creating Pairs (Paircreate)
To create a Copy-on-Write Snapshot software pair, use the paircreate command. When the paircreate
command is issued, a Copy-on-Write Snapshot software pair is formed and the P-VOL data, as of the
point in time when the command is issued, is retained in the Snapshot Image. When issuing the
paircreate command, volumes to be assigned to a P-VOL and a Snapshot Image must be in the SMPL
(Simplex) status.

Pair creation will complete instantly, and status will become PAIR. If the split option is used, status after
paircreates will be PSUS.

10
Figure 3: Creating a Copy-on-Write Snapshot Software Pair.

SMPL V-VOL

After PAIR
paircreate P-VOL V-VOL

After PSUS
paircreate-split P-VOL V-VOL

When issuing the paircreate command, volumes to be assigned to a P-VOL and a Snapshot Image must be in the SMPL
(Simplex) status, after which pair creation will complete instantly.

Snapshot Instruction (Pairresync and Pairsplit)

Use the pairresync and pairsplit commands when the Copy-on-Write Snapshot software instruction (data
update) is executed after a Copy-on-Write Snapshot software pair has already been formed. Just like the
paircreate-split command, the P-VOL data, as of the point in time when the command is issued, is
retained in the Snapshot Image.

Deleting Pairs (Pairsplit -S)

Use the pairsplit -S command for the following:

: : When canceling a status (PSUS) in which a Snapshot Image retains P-VOL data as of the point in
time when the Copy-on-Write Snapshot software instruction was given
: : When canceling a status (PSUE) in which retention has been interrupted
: : When changing the status to one in which the volumes are not assigned to the Copy-on-Write
Snapshot pair (SMPL).

When this command is executed, the data of Snapshot Image is annulled immediately and invalidated.

Restore Instruction (Pairresync -restore)

A pairresync-restore command is used to restore backup data retained in the Snapshot Image to the P-
VOL. When a restore instruction is given, the P-VOL data is immediately replaced with the backup data
retained in the Snapshot Image. However, while the Snapshot Image backup data is being physically
duplicated into the P-VOL, the pair status changes to a COPY(RS-R) status. In the COPY(RS-S) status, no
Copy-on-Write Snapshot software instruction or pair splitting can be executed to the restoring pair.
Read/Write is not accepted when P-VOL is in COPY(RS-R) status.

11
During the restore operation, one can delete pairs while the status is COPY(RS-S); however, Read/Write of
P-VOL data can no longer be performed, and all V-VOLs that are linked to the restoring P-VOL will be PSUE.

Copy-on-Write Snapshot Software Pair Status

Pair Status Transitions
Figure 4 illustrates the Copy-on-Write Snapshot software pair status transitions and the relationship
between the pair status and the Copy-on-Write Snapshot software operations.

Figure 4: Copy-on-Write Snapshot Software Pair Status Transitions.

SMPL pairsplit -S PSUE

P-VOL V-VOL

Not synchronized

pairsplit -S
Error

PAIR Completion of COPY(RS-R)

restore operation
P-VOL V-VOL P-VOL V-VOL

paircreate
pairsplit

pairresync
pairresync
-restore
pairsplit -S PSUS

P-VOL V-VOL

Create Pair/Update Pair

paircreate
-split

Pair status transitions, including paircreate, pairresysnc, pairsplit, and pairresync-restore, occur, interacting with Copy-
on-Write Snapshot operations to complete restore operations.

12
Pair Status Conditions
Table 7 lists and describes the Copy-on-Write Snapshot software pair status conditions.

Table 7: Copy-on-Write Snapshot Software Pair Status Conditions.

Pair Status Description

SMPL The volume is not assigned to the Copy-on-Write Snapshot software pair. The P-VOL in the
SMPL status accepts I/O operation(s) of Read/Write.
PSUS This is a status where P-VOL data, at the point in time of Copy-on-Write Snapshot software
instruction, is logically retained in the Snapshot Image. Even if the P-VOL data is updated
after the Copy-on-Write Snapshot software instruction, the Snapshot Image retains the P-
VOL data at the point in time the Copy-on-Write Snapshot software instruction was given.
The host can access the data of the Snapshot Image with Read/Write commands.

PAIR This is a pseudo status that exists to provide interchangeability with the command system
of ShadowImage In-System Replication software. The actual status is the same as PSUS.
Since this is a pseudo status used only to update data retained in the Copy-on-Write
Snapshot software pair, it is not recommended that a system operate for a long period of
time while this status exists.
COPY (RS-R) This is a status in which the backup data retained in the Snapshot Image is being restored
to the P-VOL. In this status, Read/Write I/O instructions are accepted for the P-VOL as before
(in the PSUS status). It is not possible to execute a Copy-on-Write Snapshot software
instruction or to split a pair to the restoring pair. The PAIR status will be recovered after the
restore operation is completed. If an error occurs or pairdelete is performed during
restoration, all V-VOLs in the same P-VOL will become PSUE.
PSUE This is a status in which P-VOL data, as of the point in time when the Copy-on-Write
Snapshot instruction is given, cannot be retained in a Snapshot Image because a failure has
occurred in the disk system. In this status, I/O operations (Read and Write) concerning the P-
VOL are accepted in the same way as before (when the system is in PSUS status). The
Snapshot Image data is invalidated at this point in time. To resume the split pair, one must
execute the Copy-on-Write Snapshot software instruction (pairsplit -S) again after splitting
the pair once (using the paircreate -split). However, the Snapshot Image data created is not
the invalidated data, but rather, the P-VOL data as of the point in time when the new Copy-
on-Write Snapshot software instruction was given. If an error occurs during restoration, data
in the P-VOL cannot use Read/Write commands

13
Internal Processing and Accessibility in Each Pair Status
Table 8 lists and describes Copy-on-Write Snapshot software pair status and internal processing.

Table 8: Copy-on-Write Snapshot Software Pair Status and Internal Processing.

Status Name Internal P-VOL Read P-VOL Write Snapshot Snapshot

Processing Image Read Image Write

SMPL None (Normal Accepted Accepted Not Accepted Not Accepted

operation)
PSUS Differential Accepted Accepted Accepted Accepted
management (See Note 1) (See Note 1)

PAIR (See Note Differential Accepted Accepted Not Accepted Not Accepted
2) management
COPY (RS-R) Differential Accepted Accepted Not Accepted Not Accepted
management
PSUE None Accepted Accepted Not Accepted Not Accepted
(See Note 3) (See Note 3)
Note 1: Read/Write is not accepted when the P-VOL is COPY(RS-R).
Note 2: This is a pseudo status that exists to provide interchangeability with the command system of ShadowImage In-System Replication software.
The actual status is the same as PSUS.
Note 3: If error occurs during restoration, data in the P-VOL is Read/Write disabled.

Copy-on-Write Snapshot Software Control Method

Control methods for Copy-on-Write Snapshot software include Read/Write control and Read/Write
control in PSUS status, as well as differential bit management.

Read/Write control method in PSUS status

As shown in Figure 5, when Read access is made to a primary volume, the data in the accessed portion is
read from the primary volume.

When Write access is made to a primary volumeif the data in the accessed portion has not as yet been
copiedthat data is copied from the primary volume to the data pool and the data of the primary
volume is then updated. If the data in the accessed portion has already been copied, that data is not
copied from the primary volume to the data pool; the data of the primary volume is simply updated.

Because V-VOL access performance is more efficient if the area frequently accessed by the operating
system is a physical area, the beginning area of the V-VOL is a physical area, as is the case with
ShadowImage In-System Replication software. Therefore, the beginning area of the V-VOL is assigned
to a physical area in SMPL, and all the data in this area is copied into the Copy-on-Write Snapshot
software instruction.

14
Figure 5: Read/Write Control Method in PSUS status.

Physical Area
(In SMPL; copy data in Copy-on-Write
Snapshot instruction.)

P-VOL V-VOL

Virtual Area
Data exist in P-VOL or POOL.

Data in the accessed portion is read from the primary volume when Read access is made to the primary volume. During
Write access to the primary volume, if the data in the accessed portion has not as yet been copied, that data is copied
from the primary volume to the data pool and the data of the primary volume is then updated.

Read/Write control method

For Read commands, when the corresponding data requested by a Read command has already been
stored in the POOL, the data is read from the POOL. If the data has not been stored, the data is read
from the P-VOL.

For Write commands, when the corresponding data requested by the Write command has been stored
in the POOL, the data is written to the POOL. If it has not been stored, the corresponding data requested
by the Write command is written to the POOL after copying data from the P-VOL to the POOL.

Differential bit management

In order to decide if the data, at the point in time when the Copy-on-Write Snapshot software instruction
was given, exists in a primary volume or a data pool, make a check using the differential bit map. When the
differential bit map is ON, the data is in the data pool; when the bit map is OFF, data is in the primary
volume.

Because the beginning area of the V-VOL is a physical area, as is the case with ShadowImage In-
System Replication software, the beginning area of the V-VOL is not managed through a differential
bit. Table 9 lists and describes the width of the RAID group and the unit of differential bit
management, and offers a comparison to ShadowImage In-System Replication software.

15
Table 9: Width of RAID Group and Unit of Differential Bit Management.

Width of RAID Group Difference for Differential One Logical Unit Capacity for One Block (2KB)
Bit (Unit: KB) of the Difference (Unit: GB)

ShadowImage In-System Replication software

(2D ~ 15D+1P) 1,024 16
1D+1P ~ 8D+8P
Copy-on-Write Snapshot software

(2D ~ 15D+1P) 64 1
1D+1P ~ 8D+8P

Error processing
The duplicate volume (V-VOL) of Copy-on-Write Snapshot software consists of the P-VOL data and the
differential data of POOL. If a hardware failure occurs in the P-VOL, such as the dual failure of drives, the
same failure occurs in all V-VOLs belonging to the P-VOL, and they become PSUE, as shown in Figure 6.

POOL is able to share differential data of multiple primary volumes and multiple Snapshot Images. As
shown in Figure 7, if a hardware failure occurs in POOL, such as the dual failure of drives, the same
failure occurs in all V-VOLs that use the POOL, and they become PSUE.

If a hardware failure occurs in POOL during restoration, such as the dual failure of drives, as shown in
Figure 8, data in that P-VOL that is also being restored becomes Read/Write disabled.

Figure 6: Dual Failure of P-VOL.

V-VOL

P-VOL

Pair
V-VOL

POOL

V-VOL

Because V-VOL refers to the data of P-VOL, all V-VOLs belonging to the P-VOL become PSUE if a hardware
failure occurs in P-VOL.

16
Figure 7: Dual Failure of POOL.

V-VOL

P-VOL

Pair
V-VOL

POOL

V-VOL

V-VOL

Pair
P-VOL

V-VOL

Because V-VOL refers to the data of POOL, all V-VOLs that use the POOL become PSUE if the hardware
failure occurs in POOL.

Figure 8: Dual Failure of POOL During Restoration.

Restore V-VOL

P-VOL

Pair
V-VOL

POOL

V-VOL

V-VOL

Pair
P-VOL

V-VOL

If a hardware failure occurs in POOL during restoration, data in P-VOL that is being restored
becomes Read/Write disabled.

17
Overview of RAID Manager

Overview of RAID Manager

RAID Manager is software, resident on Thunder 9500 V Series systems, that manages and controls the
Copy-on-Write Snapshot software volumes.

RAID Manager Features

: : RAID Manager issues commands to Thunder 9500 V Series systems through command devices.
: : RAID Manager reports a message when an error occurs during the creation of pairs.
: : If a volume error caused by a hardware failure occurs, or if there is an excess threshold value of the
data POOL, and/or if overuse of the volume capacity occurs, RAID Manager will output an error
message into the syslog file.
: : RAID Manager provides CLIs and APIs.

Figure 9: RAID Manager Overview.

Database Server Backup Server

RAID Manager Instances LAN RAID Manager Instances

RAID Manager RAID Manager

RAID Manager RAID Manager
Command Command

Configuration Logging Communication Configuration Logging

Definition File Function between Definition File Function
RAID Manager

RAID Manager Issuing Commands

Snapshot
Command Device
paircreate
pairrestore
P-VOL Internal
pairsplit Copy

RAID Manager issues commands to Thunder 9500 V Series systems through command devices.

18
Supported Platforms
Table 10 lists the platforms supported by RAID Manager.

Table 10: RAID Manager Supported Platforms.

Vendor Platform_V4.0_ Platform_V5.0_

HP HP-UX 11i HP-UX 11i

SUN Sun Solaris
IBM AIX
Microsoft Microsoft Windows 2000 Windows NT 4.0 and Windows 2000

Overview of Command Control Interface (CCI)

Copy-on-Write Snapshot software uses commands and options of Command Control Interface (CCI) to
create pairs, obtain information, and execute copy operation. Table 11 shows the supported commands.

Table 11: Overview of CCI Commands.

Item Commands Meaning

Starting CCI Horcmstart Starts CCI

Terminating CCI Horcmshutdown Terminates CCI
Create pairs Paircreate Creates a new pair
Copy-on-Write Snapshot software will generate a Copy-on-
Write Snapshot software pair when split is added to the
command
Update pairs Pairresync Data of a pair is updated
Copy-on-Write Snapshot software will change the pair status
to a PAIR status (operated in the same way as PSUS); by adding
a restore option to the command, the Snapshot Image data
will be restored in the primary volume
Split or delete pair Pairsplit Splits or deletes the pair
Copy-on-Write Snapshot software will be activated when a
Copy-on-Write Snapshot software instruction is given under
the PAIR status; the pair is split by adding an S option to the
command

19
Table 11: Overview of CCI Commands (continued).

Item Commands Meaning

Confirming the pair Pairdisplay Displays the pair status

status and the
Pairmon Displays the status transition
configuration
Pairvolchk Acquires and reports the attribute of a volume
Raidscan Displays the connection configuration
Raidar Monitors the statistical information
Raidqry Confirms the connection between the server and the system
Horcctl Changes and displays CCI and the command trace control
parameter
Inqraid Confirms the connection of the device file

Examples of Copy-on-Write Snapshot Software Usage

Overnight Backup Operation
This operation is suitable for a customer who prefers to begin storing backup data in the tape device as
soon as the workday ends, instead of spending extra time on the initial copy or resynchronization.

ShadowImage In-System Replication software normally operates with pairs (PAIR) during the day, while
Copy-on-Write Snapshot software normally operates without pairs (SMPL).

Following are some situations for which Copy-on-Write Snapshot software would have applicable uses:
: : The number of host I/Os requested at night (24:00 to 08:00) is small.
: : Backup is performed only once a day.
: : Backup data is stored on tapes.

20
Figure 10: Comparison of ShadowImage In-System Replication and Copy-on-Write Snapshot
Software Used for an Overnight Backup Operation.

ShadowImage In-System Replication Software Copy-on-Write Snapshot Software

Heavy Host I/Os Heavy Host I/Os

Ordinary Pair
1 P-VOL S-VOL
1 P-VOL V-VOL Split Operation

Few Host I/Os Few Host I/Os

2 P-VOL S-VOL Split

2 P-VOL V-VOL Snap Status

Few Host I/Os Few Host I/Os

Backup Backup

3 P-VOL S-VOL Split

3 P-VOL V-VOL Snap Status

Few Host I/Os Few Host I/Os

4 P-VOL S-VOL Resynch

4 P-VOL V-VOL Splitting Pairs

ShadowImage In-System Replication software requires a double capacity primary volume for tape backup,
while Copy-on-Write Snapshot software enables tape backup using only a small amount of capacity.

Because Copy-on-Write Snapshot software doesnt require resynchronization, the backup operation
can be changed to a normal operation right away. Compared to ShadowImage In-System Replication
software, Copy-on-Write Snapshot software uses a smaller capacity (from the Thunder 9500 V Series
system to the tapes) in outputting data from the secondary volume (Snapshot Image) at the time of
backup operation.

21
Conclusion
From our examination of the basic features and functions of Copy-on-Write Snapshot software, we can
conclude the following:
: : Using Copy-on-Write Snapshot software during peak hours (daytime) is advantageous because it
does not require writing data in a secondary volume (data pool).
: : Operation of Copy-on-Write Snapshot software can be managed with small-capacity secondary
volumes (data pool).
: : Copy-on-Write Snapshot softwares backup performance is lower than that of ShadowImage In-
System Replication software during an off-peak (night) tape backup session.

Backup Operation within the Same Storage System Enclosure

This scenario is suitable for a customer who wishes to store backup data daily within the same storage
system enclosure, thereby reducing the frequency of backup operations to once per week. Applicable
uses include:
: : Nighttime on weekdays (24:00 to 08:00); an I/O command is sent out from the host occasionally.
: : Nighttime during weekends (24:00 to 08:00); an I/O command is small.

22
Figure 11: Comparison of ShadowImage In-System Replication and Copy-on-Write Snapshot
Software Used for Backup within the Same Storage System Enclosure.

ShadowImage In-System Replication Software Copy-on-Write Snapshot Software

Heavy Host I/Os Heavy Host I/Os

Ordinary Split Ordinary Pair

1 P-VOL S-VOL
1 P-VOL V-VOL
Operation Operation

Nighttime (Weekdays) Nighttime (Weekdays)

Heavy Host I/Os Heavy Host I/Os

2 P-VOL S-VOL Resynch

2 P-VOL V-VOL

V-VOL Snap
Heavy Host I/Os

3 Repeat the Operation from Step 1

3 to 2 on Weekdays (A V-VOL is Added)
P-VOL S-VOL Split

Nighttime (Weekdays)
Few Host I/Os

4 Repeat the Operation from Step 1 Back Up

to 3 on Weekdays

Nighttime (Weekdays) 4
P-VOL V-VOL
Few Host I/Os

Back Up
V-VOL

5
P-VOL S-VOL

ShadowImage In-System Replication software can make only one backup within the same storage system enclosure,
while Copy-on-Write Snapshot Software can support two or more generations of backup within the same storage
system enclosure.

23
With ShadowImage In-System Replication software, only one backup can be made within the same
storage system enclosure and the capacity of the secondary volume equals that of the primary volume.
On the other hand, Copy-on-Write Snapshot software can generate two or more Snapshot Images per
primary volume and can, therefore, acquire backup data in two or more generations within the same
storage system enclosure. Copy-on-Write Snapshot software can also use smaller-capacity secondary
volumes that can be shared, thus realizing unitary management.

ShadowImage In-System Replication software requires resynchronization during backup within the
same storage system enclosure and it takes some time to acquire complete backup data. In contrast,
Copy-on-Write Snapshot software manages this execution instantly. However, the performance for the
primary volumes using Copy-on-Write Snapshot software is not as good as that of ShadowImage In-
System Replication software during normal working hours.

Conclusion
In examining the backup operations within the same storage system enclosure and comparing the
capabilities of ShadowImage In-System Replication software and Copy-on-Write Snapshot software,
we can conclude the following about Copy-on-Write Snapshot software.
: : Copy-on-Write Snapshot software can acquire backup data in two or more generations.
: : Small-capacity data pool and unitary management are available.
: : The level of performance lowers for Copy-on-Write Snapshot software during normal
working hours.

Restore Operation
A restore operation writes (returns) secondary volume (Snapshot Image) data that has been retained as
a backup into a primary volume; that is, a resynchronization in reverse.

Both ShadowImage In-System Replication and Copy-on-Write Snapshot software can operate using
the reverse resynchronization function. For Copy-on-Write Snapshot software, it is possible to have
Snapshot Images in two or more generations and to execute reverse resynchronization from any of
the Snapshot Images.

For restoration via the tape device, both ShadowImage In-System Replication and Copy-on-Write
Snapshot software have a common basic method to rewrite the data into the primary volume using
reverse resynchronization after the data is returned to the secondary volume (Snapshot Image).
However, when the data is returned from the tape device to the Snapshot Image, both primary and
secondary volumes need to have the same capacity.

It is also possible to return the data directly from the tape device to the primary volume, although this is
not officially recommended.

For the restore operation, Copy-on-Write Snapshot software has the same function as ShadowImage
In-System Replication software.

24
Figure 12: Comparison of Using ShadowImage In-System Replication and Copy-on-Write
Snapshot Software for Restore Operation.

ShadowImage In-System Replication Software Copy-on-Write Snapshot Software

Method 1 Method 1

Tapes Tapes

P-VOL S-VOL P-VOL V-VOL

Reverse Reverse
P-VOL S-VOL resynch P-VOL V-VOL resynch

Method 2 Method 2

Tapes Tapes

P-VOL S-VOL P-VOL V-VOL

For restoration via the tape device, both ShadowImage In-System Replication and Copy-on-Write Snapshot software
have a common basic method to rewrite the data into the primary volume using reverse resynchronization after the data
is returned to the secondary volume (Snapshot Image).

Copy-on-Write Snapshot for Thunder 9500 V Series

Systems: Conclusion
The use of snapshot technology is becoming more pervasive in many organizations because of its
benefits over other traditional methods of backup. Copy-on-Write Snapshot software is really a first line
of defense for data protection, and, because it performs in-system replication, it offers a fast and reliable
process. While it differs from ShadowImage In-System Replication software, Copy-on-Write Snapshot
software provides similar data protection benefits and requires less storage to maintain duplicate
volumes. Also, for users and customers who have previous experience with Hitachi replication products,
Copy-on-Write Snapshot software builds on our CCI interface and uses familiar commands. The ability
to capture only changes to a volume while maintaining up to 14 generations of this primary data is
powerful, and it allows you to literally roll back the clock and recover your data at a specific point in
time. Copy-on-Write Snapshot software truly delivers advanced enterprise-class data protection for
Hitachi Thunder 9500 V Series modular storage systems.

25
 Hitachi Data Systems Corporation
Corporate Headquarters
750 Central Expressway
Santa Clara, California 95050-2627
U.S.A.
Phone: 1 408 970 1000
www.hds.com
info@hds.com

Asia Pacific and Latin America

750 Central Expressway
Santa Clara, California 95050-2627
U.S.A.
Phone: 1 408 970 1000
info@hds.com

Europe Headquarters
Sefton Park
Stoke Poges
Buckinghamshire SL2 4HD
United Kingdom
Phone: + 44 (0)1753 618000
info.eu@hds.com

Hitachi Data Systems is registered with the U.S. Patent and Trademark Office as a trademark and
service mark of Hitachi, Ltd. The Hitachi Data Systems logotype is a trademark and service mark of
Hitachi, Ltd.
Thunder 9500, Thunder 9530V, Thunder 9570V, Thunder 9580V, Thunder 9585V, ShadowImage, and
TrueCopy are trademarks of Hitachi Data Systems Corporation.
All other company names are, or may be, trademarks or service marks of their respective owners.
Notice: This document is for informational purposes only, and does not set forth any warranty, express or
implied, concerning any equipment or service offered or to be offered by Hitachi Data Systems. This
document describes some capabilities that are conditioned on a maintenance contract with Hitachi Data
Systems being in effect, and that may be configuration-dependent, and features that may not be currently
available. Contact your local Hitachi Data Systems sales office for information on feature and product
availability.
Hitachi Data Systems sells and licenses its products subject to certain terms and conditions, including
limited warranties. To see a copy of these terms and conditions prior to purchase or license, please go to
http://www.hds.com/products_services/support/license.html or call your local sales representative to
obtain a printed copy. If you purchase or license the product, you are deemed to have accepted these
terms and conditions.
2004, Hitachi Data Systems Corporation. All Rights Reserved.
WHP-162-00 August 2004

26