2008 Hitachi Data Systems

Hitachi Data Systems

Enterprise Storage
Boot Camp
Hitachi ShadowImage

Heterogeneous Replication
Software
2
Module Objectives
Upon completion of this module, the learner should be able to:
Describe the key features and operations of Hitachi ShadowImage

Heterogeneous Replication software
List the rules associated with operations
Describe the key competitive advantages
Identify commands and the operations of each command
3
Overview
Replicates information within Hitachi storage systems without disrupting
operations
Creates a point-in-time (PiT) copy of the data
Once PiT copy is created, data can be used for
Data warehousing/data mining applications
Backup and recovery
Application development
Supports the creation of up to nine system protected copies from each
source volume for Hitachi enterprise storage systems
High performance achieved through asynchronous copy facility to
secondary volumes
4
Overview
P-VOL and S-VOL start out as
independent/simplex volumes
P-VOL Production Volume
S-VOL Secondary Volume
P-VOL and S-VOL are
synchronized using ShadowImage
Heterogeneous Replication
P-VOL and S-VOL are split
creating a Point-In-Time (PiT)
copy
S-VOL can be used independently
of P-VOL with no performance
impact on P-VOL
P-VOL
P-VOL
S-VOL P-VOL
S-VOL
S-VOL
Independent
Synchronize
Split
5
Overview
For Hitachi enterprise storage systems
Max. 3 S/P-VOL or 3 S-VOL
Total 9 Copies:
Three Level 1s
And
Six Level 2s
Max. 2 S-VOL
Max. 2 S-VOL
Asynchronous Write Asynchronous Write
Write Data
Write Data
Write Data
Cascade Connection
Max. 2 S-VOL
P-VOL
S-VOL
S-VOL
S-VOL
S-VOL
S-VOL
S-VOL
S-VOL
S-VOL
S-VOL
6
Overview
For the Hitachi Universal Storage Platforms

Supports a maximum of 16,382 ShadowImage Heterogeneous Replication
volumes: 8,191 pairs: (8,191 P-VOLs and 8,191 S-VOLs)
When pairs include size-expanded LUs, the maximum number of pairs
decreases
The license key code is required to enable the ShadowImage Heterogeneous
Replication option on the Universal Storage Platform
A separate license code is required for each Universal Storage Platform
Maximum concurrent copies is 128
7
Overview
Initial Copy Operation
Full Copy
Block for Block Copy
P-VOL
P-VOL
S-VOL P-VOL
S-VOL
S-VOL
SMPL
COPY (PD)
PAIR
Initial
Copy
Start
Finished
8
Overview
P-VOL
S-VOL
S-VOL
PAIR
Differential Data
P-VOL
Host I/O
Update Copy
Update Copy Operations
9
Overview
High Performance by Asynchronous Access to Secondary Volumes

Storage system replies write
complete to host as soon as the
data is written to cache memory
Data in cache memory is
asynchronously written to P-VOL
and S-VOL optimizing copy
performance
Fast response to host side
and
intelligent asynchronous copy
This S-VOL location is one example
DKA Pair DKA Pair
Max. 9 S-VOL
Cache

Cache Memory

(1) Write I/O
(2) Write complete
Data
P-VOL
S-VOL
S-VOL
S-VOL
SUN
Solaris
(3) Asynchronous write at the best timing
10
Overview
Rules
Two LDEVs which compose an ShadowImage Heterogeneous
Replication paired volume must be the same emulation type and size.
ShadowImage Heterogeneous Replication software supports LUSE
VOLs, VLL, and Flash Access VOLs.
Must be the same size
RAID level match is not required.
11
Commands
paircreate
pairsplit
Steady
Quick
pairresync
Normal
Quick
Reverse
Quick Restore
suspend (pairsplit E)
delete (pairsplit S)
12
paircreate
P-VOL S-VOL
Time
frame
VOL Status Host Access VOL Status Host Access
Before SMPL R/W SMPL R/W OR R
During COPY(PD) R/W COPY(PD) NA
After PAIR R/W PAIR NA
paircreate
1. Select a volume and issue paircreate
2. Initial copy takes place
3. Volume status changes to PAIR

13
pairsplit
P-VOL S-VOL
Time frame VOL Status Host Access VOL Status Host Access
Before PAIR R/W PAIR NA
During COPY(SP) R/W COPY(SP) NA
After PSUS R/W SSUS R/W
pairsplit - steady
1. Creates a PiT Copy of P-VOL
2. Bitmap transferred from P-VOL to S-VOL
3. Update copy takes place
4. Volume status changes to PSUS
5. S-VOL is now available
14
pairsplit
Steady Split
10:00:45 AM Status = PSUS

10:00:01 AM
Pairsplit (steady)

10:00 AM Status = PAIR

S-VOL
Dirty Tracks
10,18, 19, 23
H
O
S
T

I
/
O

P-VOL Asynch Updates
S-VOL
Tracks 10,18,19,23 sent
from P-VOL to S-VOL
Updates
P-VOL
Dirty Tracks
10,18, 19, 23
P-VOL
Dirty Tracks
H
O
S
T

I

/
O

S-VOL
Dirty Tracks
H
O
S
T

I

/
O

15
pairsplit
P-VOL S-VOL
Time
frame
VOL Status
Host
Access
VOL Status Host Access
Before PAIR R/W PAIR NA
During
COPY(SP) <
1sec
R/W
COPY(SP) <
1sec
R/W
After PSUS R/W SSUS R/W
pairsplit - quick
1. Creates a PiT Copy of P-VOL
2. Bitmap transferred from P-VOL to S-VOL
3. Volume status changes to PSUS
4. Update copy takes place in background
5. S-VOL is available almost instantly

16
pairsplit
Quick Split
10:00:02 AM Status = PSUS
Status almost Immediately
changes to PSUS

10:00:01 AM
Pairsplit (Quick)
Merge Dirty Track Tables
10:00 AM Status = PAIR

Asynch Updates
P-VOL
Dirty Tracks
S-VOL
Dirty Tracks
S-VOL
Dirty Tracks
3, 10, 15,18
P-VOL Asynch Updates
I
/
O

I
/
O

I
/
O
Tracks 3, 10, 15,18 sent
from P-VOL to S-VOL
Dirty Tracks
3, 10, 15,18
I
/
O

S-VOL
Track bitmaps merged
between S-VOL and P-VOL
P-VOL
17
pairresync
P-VOL S-VOL
Time
frame
VOL Status Host Access VOL Status Host Access
Before PSUS R/W SSUS R/W
During COPY(RS) R/W COPY(RS) NA
After PAIR R/W PAIR NA
pairresync - normal
S-VOL is no longer available to host
Bitmap transferred from S-VOL to P-VOL
Dirty tracks are marked
Update copy takes place from P-VOL to S-VOL
Volume status changes to PAIR

18
pairresync
Normal resync
10:00:45 AM Status = PAIR
10:00:01 AM
Pairresync (Normal)

10:00 AM Status = PSUS

Asynch Updates
P-VOL
Dirty
Tracks
I
/
O

S-VOL
Dirty Tracks
10,15,18, 29
Dirty Tracks
10,19,23 I
/
O

S-VOL P-VOL
I
/
O

Dirty Tracks
10,15,18, 19,
23, 29
S-VOL
Tracks 10,15,18,19,23, 29 sent
from P-VOL to S-VOL
Updates
P-VOL
I
/
O

19
pairresync
P-VOL S-VOL
Time frame VOL Status
Host
Access
VOL Status
Host
Access
Before PSUS R/W SSUS R/W
During COPY(RS) < 1sec R/W COPY(RS) < 1sec NA
After PAIR R/W PAIR NA
pairresync - quick
1. S-VOL is no longer available to host
2. Bitmap transferred from S-VOL to P-VOL
3. Volume status changes to PAIR
4. Dirty tracks are marked
5. Update copy takes place in background from P-VOL to S-VOL
20
pairresync
quick resync
10:00:02 AM Status = PAIR
Status almost Immediately
changes to PAIR

10:00:01 AM
Pairresync (Quick)
Merge Dirty Track Tables
10:00 AM Status = PSUS

Asynch Updates
P-VOL
Dirty
Tracks
I
/
O

S-VOL
Dirty Tracks
10,15,18, 29
I
/
O

P-VOL
Dirty Tracks
10,19,23
S-VOL
I
/
O

Tracks 10,15,18,19,23, 29 sent
from P-VOL to S-VOL
Dirty Tracks
10,15,18, 19,
23, 29
I
/
O

S-VOL
Track bitmaps merged
between S-VOL and P-VOL
P-VOL
21
pairresync
quickresync and quicksplit together
Reduces resync (primary to secondary) time
P-VOL S-VOL
Very Short Term
(almost zero)
Read/
Write
quick resync
DB I/O
Background copy of
pending delta data
Using S-VOL for
backup or batch
process
NA
Status: PSUS
quick split
Very Short Term
(almost zero)
Read/
Write
Status: COPY (RS)
Status: COPY (SP)
Status: PSUS
22
pairresync
P-VOL S-VOL
Time frame VOL Status Host Access VOL Status Host Access
Before PSUS R/W SSUS R/W
During COPY(RS-R) NA COPY(RS-R) R
After PAIR NA PAIR R/W
pairresync - reverse
1. Bitmap transferred from P-VOL to S-VOL
2. Dirty tracks are marked
3. Update copy takes place from S-VOL to P-VOL
4. Volume status changes to PAIR
Can only be done from L1 to P-VOL

23
pairresync
reverse resync Illustration
Start Host I/O to P_VOL
10:00:45 AM Status = PAIR

Stop Host I/O to P-VOL
and S-VOL
10:00:01 AM pairresync
(Reverse)

10:00 AM Status = PSUS
P-VOL Data is corrupted

Dirty Tracks

S-VOL
Tracks
10,15,18,19,23,29
sent from S-VOL to
P-VOL
<-- Updates
P-VOL
Dirty
Tracks
H
O
S
T

I
/

O

S-VOL
Dirty Tracks
10,15, 18, 29
Dirty
Tracks
10,19, 23
H
O
S
T

I

/
O

P-VOL
S-VOL
Asynchronous Updates
H
O
S
T

I
/

O

P-VOL
Dirty
Tracks
24
pairresync
P-VOL S-VOL
Time
frame
VOL Status Host Access VOL Status Host Access
Before PSUS R/W SSUS R/W
During COPY(RS-R) NA COPY(RS-R) R
After PAIR R/W PAIR NA
pairresync quick restore
1. Swap of LDEV ID takes place
Can only be done from L1 to P-VOL
Swap and freeze option available

25
pairresync quick restore
10:00:45 AM Status = PAIR
10:00:01 AM
Stop I/O to P-VOL and S-VOL
pairresync quick restore
Performs P-VOL/S-VOL Swap
Start Host I/O to P-VOL
10:00 AM
Status = PSUS
P-VOL Data is corrupted

10:00:46 AM Status = PAIR
Performs P-VOL/S-VOL Swap
P-VOL
Dirty
Tracks

I
/
O

S-VOL
Dirty Tracks
10,15,18

I
/
O

P-VOL
LDEV 2:03
RAID Group 1-1
LDEV 1:04
RAID Group 2-3 S-VOL
P-VOL
LDEV 1:04
RAID Group 1-1
LDEV 2:03
RAID Group 2-3
<-- Updates
Dirty Tracks
10,15,18
S-VOL
P-VOL

I
/
O

Async Updates
Dirty Tracks
S-VOL
Async Updates
LDEV 1:04
RAID Group 1-1
LDEV 2:03
RAID Group 2-3
LDEV 2:03
RAID Group 1-1
LDEV 1:04
RAID Group 2-3

I
/
O

26
P-VOL
2:03
pairresync quick restore
RAID Group 2 - 3
RAID Group 1 - 1
Time = 0 10:00 AM
Status = PSUS, SSUS

No I/O is allowed to the S-VOL.
S-VOL is reserved as part of
the backup process.
Time = 1 10:04 AM
Status = PSUS, SSUS

P-VOL Data is corrupted
S-VOL
1:04
I/O
CL3-G
I/O
27
P-VOL
2:03
Time = 3 10:07 AM
Status = PAIR, PAIR

Start I/O to the (new) P-VOL

Data is copied to the S-VOL in
the background
pairresync quick restore
RAID Group 2 - 3
RAID Group 1 - 1
Time = 2 10:06 AM
Status = PSUS, SSUS

Stop I/O to the P-VOL

pairresync quick restore

Performs a P-VOL/S-VOL Swap
S-VOL
1:04
Async Update
I/O
CL3-G
I/O
I/O
28
S-VOL
1:04
pairresync quick restore
RAID Group 2 - 3
RAID Group 1 - 1
P-VOL
2:03
Async Update
I/O
CL3-G
I/O
I/O
Time = 4 10:26 AM
Status = PAIR, PAIR

P-VOL and S-VOL are synchronized

Async Update
P-VOL/S-VOL are swapped
Returning to original configuration

I/O is redirected to the (original) P-VOL


29
pairsplit
P-VOL S-VOL
Time frame VOL Status Host Access VOL Status Host Access
Before PAIR R/W PAIR NA
After PSUE R/W SSUE R/W
pairsplit e (suspend)
1. Immediate access to S-VOL
No update copy
2. Forces an initial copy on resync
Marks the entire PVOL as dirty

30
pairsplit
P-VOL S-VOL
Time
frame
VOL Status Host Access VOL Status Host Access
Before PAIR R/W PAIR NA
After SMPL R/W SMPL R/W
pairsplit s (delete)
1. Immediate access to S-VOL
No update copy
2. Changes volume status back to simplex
31
Tools
Hitachi Storage Navigator program
GUI
Hitachi HiCommand

Dynamic Link Manager software

GUI
RAID Manager/CCI
HORCM
HORCM Files
Command Line
Used to script replication process

32
Tools
Open ShadowImage Heterogeneous Replication software Select
P-VOL
33
Live Demonstration
34
Questions/Discussion
35
Module Review
1. In an open systems environment, how many L1 point-in-time copies
can be made from a P-VOL (referred to as a ____________volume)?
2. In an open systems environment, how many L2 point-in-time copies
can be made from a L1 S-VOL?
3. ShadowImage Heterogeneous Replication operations are (a)
asynchronous or (b) synchronous?
4. S-VOLs become available for host access only after the pair has been
__________________.
5. Describe the difference between the pairsplit and pairsplit S
functions.
6. What are the three ways of re-synchronizing a Split Pair?
7. After performing a paircreate, when can you split the P-VOL and have
a consistent PiT copy on the S-VOL?
36
Module Review
8. A paircreate operation is performed on a 50GB P-VOL. The P-VOL is being
used as a file system and is half full. How much data is copied from the
P-VOL to the S-VOL?
a. 0GB
b. 50GB
c. 25GB
9. If a P-VOL is synchronized with three S-VOLs, what is the performance
impact to the host?
a. The host must wait until the write is written to all four volumes.
b. The host must wait until the write is written to the P-VOL.
c. The host must wait until the write is written to cache.

10. A P-VOL is in PAIR status with an S-VOL. What must be done to ensure a
consistent PiT copy on the S-VOL when performing a pair split?
37
Module Review
11. Data on a P-VOL is corrupted. The P-VOL is split from the S-VOL. A
reverse resync is performed on the P-VOL. When can the P-VOL be
accessed?
12. Bonus - A P-VOL S-VOL pair status is P-SUS and S-SUS and has
been split for 24 hours. The storage administrator needs a copy of the
S-VOL that is a copy of the current P-VOL data immediately.
a. How can this be done?
b. When reading from the S-VOL, where is the data coming from?