Copy On WriteSnapshotUserGuide

Hitachi Virtual Storage Platform
Hitachi Copy-on-Write Snapshot User Guide
FASTFIND LINKS
Document Organization
Product Version
Getting Help
Contents
MK-90RD7013-00
Copyright © 2010 Hitachi, Ltd. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording, or stored in a database or retrieval system for any
purpose without the express written permission of Hitachi, Ltd. (hereinafter referred to as “Hitachi”) and
Hitachi Data Systems Corporation (hereinafter referred to as “Hitachi Data Systems”).
Hitachi and Hitachi Data Systems reserve the right to make changes to this document at any time without
notice and assume no responsibility for its use. This document contains the most current information
available at the time of publication. When new and/or revised information becomes available, this entire
document will be updated and distributed to all registered users.
Some of the features described in this document may not be currently available. Refer to the most recent
product announcement or contact your local Hitachi Data Systems sales office for information about feature
and product availability.
Notice: Hitachi Data Systems products and services can be ordered only under the terms and conditions of
the applicable Hitachi Data Systems agreement(s). The use of Hitachi Data Systems products is governed
by the terms of your agreement(s) with Hitachi Data Systems.
Hitachi is a registered trademark of Hitachi, Ltd. in the United States and other countries. Hitachi Data
Systems is a registered trademark and service mark of Hitachi, Ltd. in the United States and other countries.
ShadowImage and TrueCopy are registered trademarks of Hitachi Data Systems.
AIX, ESCON, FICON, FlashCopy, IBM, MVS/ESA, MVS/XA, OS/390, S/390, VM/ESA, VSE/ESA, z/OS, zSeries,
z/VM, and zVSE are registered trademarks or trademarks of International Business Machines Corporation.
All other trademarks, service marks, and company names are properties of their respective owners.
Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.
ii
Hitachi VSP Copy-on-Write Snapshot User Guide
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Intended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . .viii
Product version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . .viii
Document revision level . . . . . . . . . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . .viii
Source documents for this revision . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . .viii
Changes in this revision . . . . . . . . . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . .viii
Referenced documents. . . . . . . . . . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . .viii
Document organization . . . . . . . . . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . . ix
Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . . ix
Convention for storage capacity values . . . . . . . . . . . . . . .... .. . . . . . . . . . . .x
Accessing product documentation . . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . . xi
Getting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . . xi
Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... .. . . . . . . . . . . xi
1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Copy-on-Write Snapshot software . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 1-2
How Snapshot works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 1-2
Volume pairs — P-VOLs and V-VOLs . . . . . . . . . . . . . . . . . .. . . . . . . . . . 1-2
Data pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 1-4
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 1-4
Licenses and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 1-4
Consistency groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 1-5
Interfaces for performing Snapshot operations . . . . . . . . . . . . . .. . . . . . . . . . 1-5
Storage Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 1-5
Command Control Interface (CCI) . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 1-5
Pair status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 1-5
2 Planning and design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Data pool requirements and restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Planning volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
iii
Planning V-VOLs, data pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Sizing the data pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Number of pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Calculating max. pairs based on differential tables . . . . . . . . . . . . . . . . . . 2-6
Calculating max. pairs based on V-VOL management area shared memory . 2-7
Calculate max. pairs based on pair tables . . . . . . . . . . . . . . . . . . . . . . . 2-10
Determining max. pairs allowed on your system . . . . . . . . . . . . . . . . . . . 2-10
Planning for external volumes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
3 Sharing Snapshot volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Interoperability with other products and functions . . . . .. . . . . . . . . . . . . . . . 3-2
Data Retention Utility. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 3-2
Volume Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 3-3
ShadowImage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 3-3
TrueCopy or Universal Replicator . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 3-5
Dynamic Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 3-6
4 Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Configuration workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Installing and removing Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Creating data pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Creating V-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
On setting up the command device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
5 Pair operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Pair operations workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Checking pair status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Creating a pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Creating pairs in a consistency group . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Splitting a pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Resynchronizing a pair. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Restoring a pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Deleting pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Deleting a single pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Deleting multiple pairs related to a port or host group . . . . . . . . . . . . . . . 5-5
Deleting multiple pairs related to a pool. . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
6 Monitoring and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Monitoring the system . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 6-2
Monitoring pair status . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 6-2
Pair status definitions. . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 6-3
Statuses required for pair operations . . .. . . . . . . . . . . . . . . . . . . . . . . 6-3
Monitoring pair, volume details . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 6-4
iv
Monitoring S-VOL path information . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 6-5
Monitoring number of pairs, license information . . . . . . . . . .. . . . . . . . . . 6-6
Monitoring a pair’s operations history . . . . . . . . . . . . . . . . .. . . . . . . . . . 6-8
Monitoring pool information . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . 6-9
Maintaining the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-10
Heavy-workload option. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-11
Managing pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-11
Increasing pool capacity . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-11
Recovering pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-12
Changing pool threshold. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-12
Changing pool name . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-13
Deleting pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-13
Managing V-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-14
Changing a V-VOL name. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-14
Deleting V-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-14
Powering-off, changing the microprogram . . . . . . . . . . . . . .. . . . . . . . . 6-15
Powering-off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 6-15
Replacing the microprogram offline . . . . . . . . . . . . . . . . .. . . . . . . . . 6-16
7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Copy-on-Write Snapshot general troubleshooting . . . . . . . . . . . . . . . . . . . . . . 7-2
Recovering from failure during pairresync -restore . . . . . . . . . . . . . . . . . . 7-4
Recovering a terminated HP-UX host server . . . . . . . . . . . . . . . . . . . . . . . 7-4
Recovering a blocked pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Processing pool-related SIMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Snapshot troubleshooting with Command Control Interface . . . . . . . . . . . . . . . 7-5
A CCI command reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Action names and CCI commands list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
B Snapshot GUI reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Pair Operation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . B-3
Volume list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . B-4
Preview List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . B-5
Command menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . B-6
Display filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . B-7
Detail dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . B-8
Pairsplit-S dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . B-9
History window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . B-10
Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . B-12
Snapshot window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . B-12
Top window when selecting Pool . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . B-16
Top window when selecting a pool volume group under Pool . .. . . . . . . . . . . B-19
Create Pools wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . B-22
v
Create Pools window . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-22
Confirm window . . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-26
Expand Pool wizard . . . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-28
Expand Pool window . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-28
Confirm window . . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-29
Edit Pools wizard . . . . . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-30
Edit Pools window . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-30
Confirm window . . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-32
Delete Pool wizard. . . . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-33
Delete Pool window . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-33
Confirm window . . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-34
Restore Pools window . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-35
Complete SIMs window . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-36
Select Pool window . . . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-37
Select Pool Volumes window. .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-38
Pool Property window . . . . . .... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . B-42
Glossary
Index
vi
Preface
Preface
This document provides instructions for performing Copy-on-Write

Snapshot operations on the Hitachi Virtual Storage Platform storage
systems.
Notice: The use of the features and/or products described in this manual
and all other Hitachi Data Systems products is governed by the terms of
your agreement(s) with Hitachi Data Systems.
□ Intended audience
□ Product version
□ Document revision level
□ Source documents for this revision
□ Changes in this revision
□ Referenced documents
□ Document organization
□ Document conventions
□ Convention for storage capacity values
□ Accessing product documentation
□ Getting help
□ Comments
Preface vii
Intended audience
This document is intended for system administrators, Hitachi Data Systems
representatives, and authorized service providers who are involved in
installing, configuring, and operating the Hitachi Virtual Storage Platform
storage system.
Readers of this document should meet the following requirements:
• You should have a background in data processing and understand RAID
storage systems and their basic functions.
• You should be familiar with the Hitachi Virtual Storage Platform storage
system, and you should have read the Hitachi Virtual Storage Platform
User and Reference Guide.
• You should be familiar with the Storage Navigator software for the
Hitachi Virtual Storage Platform, and you should have read the Hitachi
Storage Navigator User Guide.
Product version
This document revision applies to Hitachi Virtual Storage Platform
microcode 70-01-0x or later.
Document revision level

Revision Date Description
MK-90RD7013-00 October 2010 Initial release
Source documents for this revision

• Not applicable.
Changes in this revision

• Not applicable.
Referenced documents
Hitachi Virtual Storage Platform documentation:
• Hitachi Storage Navigator User Guide, MK-90RD7027
• Hitachi Storage Navigator Messages, MK-90RD7028
• Hitachi Virtual Storage Platform User and Reference Guide, MK-
90RD7042
viii Preface
Document organization
The following table provides an overview of the contents and organization
of this document. Click the chapter title in the left column to go to that
chapter. The first page of each chapter provides links to the sections in that
chapter.
Chapter Description
Chapter 1, Overview Provides an overview of Copy-on-Write Snapshot.
Chapter 2, Planning and Describes the system and operational requirements for
design Copy-on-Write Snapshot.
Chapter 3, Sharing Provides information about sharing Copy-on-Write
Snapshot volumes Snapshot volumes with other Hitachi features and
products.
Chapter 4, Installation Provides instructions for installing and configuring Copy-
and configuration on-Write Snapshot.
Chapter 5, Pair Provides instructions for Copy-on-Write Snapshot pair
operations operations.
Chapter 6, Monitoring Provides instructions for monitoring Copy-on-Write
and maintenance Snapshot information and maintenance.
Chapter 7, Provides troubleshooting information for Copy-on-Write
Troubleshooting Snapshot.
Chapter A, CCI command Provides the command line interface (CLI) commands for
reference Copy-on-Write Snapshot operations.
Chapter B, Snapshot GUI Describes the Storage Navigator windows and dialog boxes
reference for Copy-on-Write Snapshot.
Document conventions
This document uses the following typographic conventions:
Convention Description
Bold Indicates text on a window or dialog box, including window and
dialog box names, menus, menu options, buttons, fields, and
labels. Example: Click OK.
Italic Indicates a variable, which is a placeholder for actual text
provided by the user or system. Example: copy source-file
target-file
Note: Angled brackets (< >) are also used to indicate
variables.
screen/code Indicates text that is displayed on screen or entered by the
user. Example: # pairdisplay -g oradb
< > angled brackets Indicates a variable, which is a placeholder for actual text
provided by the user or system. Example: # pairdisplay -g
<group>
Note: Italic font is also used to indicate variables.
[ ] square brackets Indicates optional values. Example: [ a | b ] indicates that you
can choose a, b, or nothing.
{ } braces Indicates required or expected values. Example: { a | b }
indicates that you must choose either a or b.
Preface ix
Convention Description
| vertical bar Indicates that you have a choice between two or more options
or arguments. Examples:
[ a | b ] indicates that you can choose a, b, or nothing.
{ a | b } indicates that you must choose either a or b.
This document uses the following icons to draw attention to information:
Icon Meaning Description

Tip Provides helpful information, guidelines, or suggestions for
performing tasks more effectively.
Note Calls attention to important and/or additional information.
Caution Warns users of adverse conditions and consequences, such

as disruptive operations.
WARNING Warns users of severe conditions and consequences, such as

destructive operations.
Convention for storage capacity values

Physical storage capacity values (e.g., disk drive capacity) are calculated
based on the following values:
Physical capacity unit Value

1 KB 1,000 bytes
1 MB 1,0002 bytes
1 GB 1,0003 bytes
1 TB 1,0004 bytes
1 PB 1,0005 bytes
1 EB 1,0006 bytes
Logical storage capacity values (e.g., logical device capacity) are calculated
based on the following values:
Logical capacity unit Value

1 KB 1,024 bytes
1 MB 1,024 KB or 1,0242 bytes
1 GB 1,024 MB or 1,0243 bytes
1 TB 1,024 GB or 1,0244 bytes
1 PB 1,024 TB or 1,0245 bytes
1 EB 1,024 PB or 1,0246 bytes
x Preface
Logical capacity unit Value
1 block 512 bytes
Accessing product documentation

The Hitachi Virtual Storage Platform user documentation is available on the
Hitachi Data Systems Support Portal: https://hdssupport.hds.com. Please
check this site for the most current documentation, including important
updates that may have been made after the release of the product.
Getting help
The Hitachi Data Systems customer support staff is available 24 hours a
day, seven days a week. If you need technical support, log on to the Hitachi
Data Systems Support Portal for contact information:https://
hdssupport.hds.com
Comments
Please send us your comments on this document:
doc.comments@hds.com. Include the document title, number, and revision.
Please refer to specific sections and paragraphs whenever possible.
Thank you! (All comments become the property of Hitachi Data Systems.)
Preface xi
xii Preface
1
Overview
With Hitachi Copy-on-Write Snapshot software, you create virtual copies of

a data volume in the Hitachi Virtual Storage Platform.
This guide provides instructions for planning and designing, configuring,
operating, monitoring, and troubleshooting Copy-on-Write Snapshot.
□ Copy-on-Write Snapshot software
□ How Snapshot works
□ Components
□ Licenses and capacity
□ Consistency groups
□ Interfaces for performing Snapshot operations
□ Pair status
Overview 1–1
Copy-on-Write Snapshot software
Copy-on-Write Snapshot creates a virtual, point-in-time copy of a data
volume. Since only changed data blocks are stored in the Snapshot storage
pool, storage capacity is substantially less than the source volume. This
results in significant savings compared with full cloning methods
The most probable types of target applications for Snapshot are:
• Database copies for decision support and database inquiries.
• Non-disruptive backups from a Snapshot secondary volume.
• Periodic point-in-time disk copies for rapid restores in the event of a
corrupted data volume.
How Snapshot works

You create a volume “pair” when you:
• Select a volume that you want to replicate.
• Identify another volume that will contain the copy.
• Associate the primary and secondary volumes.
• Set up a data pool.
• Create the pair.
The primary volume (P-VOL) can continue being updated once a pair is
made. The virtual volume (V-VOL) points to the data in the P-VOL as it
exists at the moment.
When a pair is split, the P-VOL continues being updated, but the V-VOL
stops mirroring the current P-VOL. Instead, it maintains a point-in-time
virtual copy, or snapshot, from the time of the split. When new data is to be
written to the P-VOL, Snapshot maintains the point-in-time image by
copying the data that is to be changed to the data pool. The V-VOL, which
contains no actual data, points to the point-in-time data in the P-VOL and
data pool.
When the pair is resumed, pool data is deleted.
Volume pairs — P-VOLs and V-VOLs

A pair consists of a primary volume (P-VOL), which contains the original
data, and from 1 to 64 virtual volumes (V-VOLs), which contain virtual
copies of the P-VOL. The P-VOL and its V-VOL(s) are located in the same
storage system. A V-VOL is also referred to as a secondary volume (S-VOL).
Unlike the P-VOL, which contains actual data, the V-VOL is made up of
pointers to the data in the P-VOL, and, when the pair is split, to original data
moved to the data pool as the P-VOL is updated. The figure below illustrates
Snapshot volumes and data pool interaction during a split.
Though V-VOLs must be set up with the same capacity as the paired P-VOL,
the capacity is not actually used and remains available as free storage
capacity. This V-VOL sizing requirement (must be equal to the P-VOL), is
necessary for Snapshot and storage system logic. Also, V-VOL pointers to
1–2 Overview
data in the data pool and P-VOL actually reside in cache memory. Because
of this, part of your system’s cache is reserved for Snapshot when it is
enabled.
Figure 1-1 How V-VOL maintains point-in-time data when pair is split
(1)
(2)
Overview 1–3
(3)
Data pools
The data pool holds data from the P-VOL that is being replaced.
After a pair is split, the V-VOL maintains pointers to point-in-time data. If
updates are written to the P-VOL before the block is updated, the data that
is being replaced is first copied to the data pool. The V-VOL pointer to this
block is updated to the new address in the data pool.
A data pool is used by all pairs sharing the same P-VOL.
Components
A Copy-on-Write Snapshot system usually consists of the following
components:
• Copy-on-Write Snapshot software
• ShadowImage software
• A pair of volumes (primary and secondary)
• A data pool
• A consistency group
• Storage Navigator
• Command Control Interface (CCI)
Licenses and capacity

Copy-on-Write Snapshot requires Hitachi Virtual Storage Platform
ShadowImage to be installed on the same system. Sufficient licensed
capacity for both Copy-on-Write Snapshot and ShadowImage is required.
1–4 Overview
Copy-on-Write Snapshot uses a V-VOL management area for managing V-
VOLs and data pools. The V-VOL management area is created when
additional shared memory is installed.
Consistency groups
Snapshot pair operations can be performed on multiple pairs at the same
time when they are defined in consistency groups. Consistency groups are
set up during pair creation.
Interfaces for performing Snapshot operations

Setup and pair operations are performed using a combination of Storage
Navigator and Command Control Interface (CCI).
• Data pools and V-VOLs are set up using Storage Navigator. Also, pair and
data pool status can be viewed using Storage Navigator.
• Pair operations are performed using CCI.
Storage Navigator
Storage Navigator is connected to the Hitachi Virtual Storage Platform
storage system via the TCP/IP local-area network (LAN). Storage Navigator
communicates and exchanges data directly with the service processor (SVP)
of the connected storage system.
Command Control Interface (CCI)

CCI is set up on the host. Snapshot commands are sent from CCI to a
command device on the storage system. This is volume dedicated to CCI
communications and cannot be used by any other applications.
Pair status
A pair’s status is an indicator of its condition. By monitoring pair status, you
can see when an operation is completed, and when an operation can be
performed. Pairs must have a specific status for specific operations to be
executed.
The following provides a brief description of pair statuses. See Monitoring
pair status on page 6-2 for more detailed information about each status and
how to monitor.
• SMPL: A volume that is not assigned to a pair is in Simplex status, SMPL.
When a pair is deleted, the status of both volumes changes back to
SMPL.
• COPY: When the initial copy is started but not yet completed.
• PAIR: When the initial copy is completed. The V-VOL is a virtual mirror
image of the P-VOL.
• PSUS: When a pair is split by the user.
• PSUE: When the system cannot keep the P-VOL and the V-VOL
synchronized due to an error condition.
Overview 1–5
• SMPL(PD): When the pair relationship between the pair volumes is
deleted (released). After all internal processing is completed, the status
changes to SMPL.
1–6 Overview
2
Planning and design
This topic describes requirements for setting up and using Copy-on-Write

Snapshot, as well as data pool sizing information.
□ System requirements
□ Data pool requirements and restrictions
□ Planning volumes
□ Number of pairs
□ Planning for external volumes
Planning and design 2–1

System requirements
The following table lists the basic system requirements. The requirements
listed here are augmented with recommendations and restrictions later in
this topic.
Item Requirement
Software ShadowImage is required to operate Copy-on-Write Snapshot. All
Virtual Storage Platform hardware, microcode, and software required
for ShadowImage operations must be installed and enabled.
License Capacity for Snapshot is part of the licensed capacity for
capacity ShadowImage. Make sure that the licensed capacity for ShadowImage
is more than the combined capacity needed for both products.
The number of products using a volume does not increase the amount
of licensed capacity that must be purchased. Only the capacity of the
volume counts toward licensed capacity.
Shared • Required
memory - COW/VFS1: 714 MB. (RACK model is supported up to VFS1.)
- COW/VFS2: 1,021 MB (COW/VFS1 + 307 MB)
- COW/VFS3: 2,045 MB (COW/VFS1,2 + 1024 MB)
• The USP VM is limited in Shared Memory for Snapshot. A USP VM
can handle a 2.45 TB database with seven generations maximum.
However, a Virtual Storage Platform can handle a 7.15 TB database
with seven generations.
• Verify that your system has the appropriate Snapshot V-VOL
management area installed by HDS personnel.
• Memory for the V-VOL management area and Dynamic
Provisioning cannot be shared.
CCI • Required for performing Snapshot pair operations.
• CCI requires one volume to be used as a command device. See the
Hitachi Command Control Interface Command Reference for setup
information.
Volume P-VOL, V-VOL, and volumes must be logical volumes (LDEV).
type See also the following topics:
• Data pool requirements and restrictions on page 2-3
• Number of pairs on page 2-6
• Planning for external volumes on page 2-11
Emulation P-VOL, V-VOL, and data pool volumes: OPEN-V
type
Pair Maximum 64 V-VOLs per P-VOL
configuration
RAID level • RAID1, RAID1+0, RAID5, and RAID6 are supported.
• A data pool cannot contain different RAID levels.
LUSE • Supported for P-VOL, V-VOL
• Not supported for the pool-VOL
CLPR A data pool cannot contain pool-VOLs belonging to different CLPRs.
Maximum • P-VOL: 16,384
number of • V-VOL: 16,384
pool volumes • Data pool: 8,192
Maximum 128
number of
data pools
2–2 Planning and design

Item Requirement
Pool-vOL 8 GB to 4 TB
capacity
Maximum 1,024
number of
pool-VOLs in
a data pool
Expansion of Allowed, even if snapshots are using the pool.
data pool
capacity
Deletion of Allowed. Pairs using the pool must be deleted first.
data pool
Use of Allowed. See Planning for external volumes on page 2-11 for more
external information.
volumes in
pool
Data drive SAS, SATA, and flash drives can be used.
type Note the following:
• When internal volumes are used, Pool-VOLs with different drive
types cannot be used in the same pool.
• When external volumes are used, Pool-VOLs with different drive
types can be used in the same pool. For best performance, volumes
with the same drive types are recommended for a pool.
Operating For HP-UX host servers only:
system • A Snapshot pair must be created before attempting to recognize
restrictions the V-VOL on the host server.
• Do not use a volume already recognized by the host server as a V-
VOL, otherwise the host may be terminated.
Consistency Defined during the paircreate operation.
groups • Consistency group number: required. Must be in the 0-255 range.
If a number is not specified, an unused number is assigned.
• Maximum number of Snapshot pair per consistency group: 8,192
• Maximum number of consistency groups per storage system: 256
Restrictions:
• Pairs with the same P-VOL cannot be in the same consistency
group.
• ShadowImage, ShadowImage for Mainframe, and Snapshot pairs
cannot coexist in the same consistency group.
See the Hitachi Command Control Interface Installation and
Configuration Guide for more information.
Data pool requirements and restrictions

The following volumes cannot be used as data pools:
• LUSE or Cache Residency Manager volumes, system disks, command
devices, quorum disks.
• Volumes whose LDEV status is other than Normal or Normal (Quick
Format).
• Volumes in blocked status or volumes in copying process.
• Copy-on-Write Snapshot P-VOLs or V-VOLs.

• Volumes already used as data pools for Copy-on-Write Snapshot or
Dynamic Provisioning.
• Volumes used by another software product pair or migration plan.
• Volumes with Protect or Read Only attribute, or the “S-VOL Disable”
setting (Data Retention Utility).
• The combination of external volume pool-VOLs whose cache modes are
enabled and disabled. Cache mode for all external volumes in a pool-VOL
must be either enabled or disabled.
Also, note the following:
• External and internal volume pool-VOLs cannot be used in the same data
pool.
• The same pool must be used for all pairs sharing the same P-VOL. For
example, if a P-VOL is paired with three V-VOLs, all three pairs must use
the same data pool.
Planning volumes
Pair volumes and data pools must be set up prior to creating the pair. The
following topics provide planning information.
Planning V-VOLs, data pools

Keep the following considerations in mind when planning your Snapshot
implementation.
• How often a Snapshot of the P-VOL should be made (frequency).
• How long each Snapshot (V-VOL) should be held (lifespan).
• The number of Snapshots (V-VOLs). Up to 64 per P-VOL can be created.
Use copy frequency and V-VOL lifespan to determine the number of V-
VOLs your system requires per P-VOL. For example: If your data must
be copied every 12 hours, and business use of the V-VOL requires
holding it 48 hours, then you need four V-VOLs.
• The size of the data pool. Copy frequency, V-VOL lifespan, and the
number of V-VOLs are factors in determining data pool size. The more
time that elapses between Snapshots, the longer a Snapshot is held, and
the more Snapshots that exist are all factors that result in more data
accumulating in the data pool. See Sizing the data pool on page 2-5 for
more information.

Figure 2-1 V-VOL lifespan / copy frequency = number of V-VOLs
Sizing the data pool

The data pool holds data from the P-VOL that is being replaced by an
update. By holding this original data in the data pool, the image of the P-
VOL at the time of the Snapshot is maintained.
You determine the size of the data pool by:
• Measuring write workload over time from the host application to the P-
VOL. Write workload is the megabytes-per-second that are written to
the primary volume over a specific amount of time.
• Calculating the amount of data that would accumulate during the
lifespan of your V-VOL(s).
• Multiplying the amount of data that accumulates by the number of V-
VOLs.
Figure 2-2 Basic factors for data pool sizing

In addition, when finalizing a data pool’s capacity, it is advisable to factor in
the following:
• A safety factor of 20 percent. Having a safety factor calculated in
minimizes the chances of over-filling the data pool. To factor in a safety
factor of 20-percent, multiply the base data pool size by 1.2.
• Annual increase in data transactions. Your business data is likely to
grow. Multiply the base pool size by the percentage of expected annual
growth.

• Data is copied to a pool in units of 256 KB. This is true even when the
actual write data is smaller than 256kB. In such a case, 256 KB of the
pool capacity is consumed by the write. Therefore, when planning pool
size, you must factor in the unit size of 256 KB.
Number of pairs
The number of Snapshot pairs you can create in your storage system is
limited by available system resources for copy operations. Confirm with
your service provider that additional shared memory for differential tables
and the V-VOL management area are installed on your system.
The maximum number of pairs supported on a system is the lowest value
of the following three calculations:
• Maximum number of pairs based on the number of differential tables.
• Maximum number of pairs based on the capacity of shared memory for
the V-VOL management area.
• Maximum number of pairs based on the number of pair tables.
Calculating max. pairs based on differential tables

Differential tables keep track of the updates that take place in pairs. The
number of these tables a pair requires is determined by the size of the pair
volumes.
The number of differential tables on a system is determined by the amount
of shared memory installed on the system. When Snapshot is used, the
shared memory level is COW1 with Extension1 and Extension2. At these
levels, the number of differential tables is 57,600, 104,768, or 209,600.
In addition to Snapshot, the following Hitachi software products also use
differential tables:
• ShadowImage
• ShadowImage for Mainframe
• Compatible FlashCopy® V2
• Volume Migration
Calculate the number of differential tables these products use and subtract
the amount from the total number of differential tables. The remainder is
available for Snapshot pairs. See the products’ documentation for
instructions.
Using differential tables, find the maximum number of Snapshot pairs
allowed on your system using two calculations:
1. Number of differential tables required for each Snapshot pair.
2. Maximum number of Snapshot pairs your system supports.
Note: “ceil” indicates that the result within the parenthesis () that
follows must be rounded up.

1. Calculate the number of differential tables required for one
Snapshot pair (O) using the following formula:
ceil((X ÷ 256) ÷ Z)
where:
X = Capacity of the volume in kilobytes.
Z = Number of slots that a differential table can manage (639 × 32).
Round up to the nearest whole number.
For example:
(16,777,216 kB ÷ 256) ÷ (639 x 32)
= 3.19523, which rounds up to 4.
Therefore, four differential tables are required to create one Snapshot pair.
2. Calculate the maximum number of Snapshot pairs using the
following formula:
T ÷ D = M
where:
T = Total number of differential tables.
D = Number of differential tables required for one pair.
M = Maximum number of Snapshot pairs.
For example: (In this example, it is assumed that no other software
product is using differential tables, and that the number of differential
tables is 57,600.)
576,00 ÷ 4 = 14,400
In this example, the maximum number allowed for Snapshot based on

differential tables is 14,400 pairs.
Calculating max. pairs based on V-VOL management area shared

memory
The V-VOL management area consists of the following:
• Pool association information
• Pool management block
Shared memory capacity for the V-VOL management area depends on
additional shared memory. The following table shows the shared memory
capacity of a system based on the amount of additional shared memory.
Table 2-1 Shared memory capacity for V-VOL management area
Shared memory Shared memory capacity

Snapshot 751,619,276 bytes
Snapshot Extension 1 4,294,967,296 bytes

Using the shared memory capacity of your V-VOL management area, you
can calculate the maximum number of pairs. This is done by performing the
following calculations in the order presented. The result of each calculation
is used in the next calculation.
1. Total capacity of all pools (P).
2. Shared memory capacity of the pool management block (S2).
3. Shared memory capacity of pool association information (S1).
4. Total capacity of P-VOLs.
5. Maximum number of Snapshot pairs.
Note: “ceil” indicates that the result within the parenthesis () that
follows must be rounded up.
1. Calculate total capacity of all pools (P), using the following

formula:
P = Y – (4,116,000 + 84,000 × Number of pool-VOLs)
where Y = Total capacity of pool-VOLs (in kilobytes).

For example:
This example assumes that Y is 4 TB (4,294,967,296 KB) and the number
of pool-VOLs is 100.
P = 4,294,967,296 - (4,116,000 + 84,000 × 100)
= 4,282,451,296
Note: When copying Snapshot data to the pool, pool capacity is used in
multiples of 256 KB, even though Snapshot data may be smaller than 256
KB. When Snapshot data is stored consecutively, the actual size and usage
of pool capacity may be nearly the same, but when Snapshot data is stored
randomly, the pool capacity used is larger than the data’s actual size.
2. Calculate shared memory capacity for the pool management

block (S2), using the following formula:
S2 = ceil[{(Y ÷ 256) × 32} ÷ 8,640] × 8,736 + ceil[Y ÷ 2,097,152]
× 8,736
where:
Y = Total capacity of the pool-VOLs (in kilobytes).
256 = Capacity of one slot (in kilobytes).
32 = Capacity of the table that you need to manage the pool of one slot.
8,736 = Minimum size of pool management block (in bytes).
8,640 = Data size of pool management block (in bytes).
Note: You can check the capacity of the shared memory of pool
association and pool management block information in Storage Navigator’s
C.O.W. Snapshot window.
For example:

S2 = ceil[{(4,282,451,296 ÷ 256) × 32} ÷ 8,736] × 8,736 +
ceil[{(4,282,451,296 ÷ 256) ÷ 270} ÷ 2,048 ] × 8,736
= ceil[61,275.917...] × 8,736 + ceil[30.252...] × 8,736
= 61,276 × 8,736 + 31 × 8,736
= 535,577,952
3. Calculate shared memory capacity for pool association

information (S1), using the following formula:
S1 = S – S2
where:
S = Shared memory capacity for the whole V-VOL management area (in
bytes).
S2 = Shared memory capacity for pool management block (in bytes).
For example:
This example assumes that S is 716 MB (751.619,276 bytes).
S1 = 751,619,276 – 535,577,952
= 216,041,324
4. Calculate the total capacity of P-VOLs, using the following

formula:
Total capacity of P-VOLs = ceil(S1 ÷ 8,736) × 2,048 × 256
where:
S1 = Shared memory capacity for pool association information (in bytes).
8,736 = Capacity of pool association information per one table (in bytes).
2,048 = Number of slots of P-VOL that can be managed by the pool
association information of one table.
256 = Capacity of one slot (in kilobytes).
For example:
Total capacity of P-VOLs (kB) = ceil[(216,041,324 ÷ 8,736)] ×
2,048 × 256
= ceil[24,731.005...] × 2,048 × 256
= 24,731 × 2,048 × 256
= 12,966,166,528
5. Calculate maximum number of pairs, using the following formula:

Max. num. Snapshot pairs = Total capacity of P-VOLs (in kilobytes)
÷ {ceil[(Capacity of one P-VOL (in kilobytes) ÷ 524,288)] ×
524,288}
where:
524,288 = Unit by which pool association information manages the capacity
of a P-VOL (in kilobytes).
For example:
This example assumes that the capacity of one P-VOL is 10 GB.

Max. num. Snapshot pairs = 12,966,166,528 ÷
ceil[[{(10 × 1,024 × 1,024) ÷ 524,288}] × 524,288]
= 12,966,166,528 ÷ 10,485,760
= 1,236
All examples in order:

P = 4,294,967,296 – (4,116,000 + 84,000 × 100)
= 4,282,451,296
S2 = ceil[{(4,282,451,296 ÷ 256) × 32} ÷ 8,736] × 8,736 +
ceil[{(4,282,451,296 ÷ 256) ÷ 270} ÷ 2,048 ] × 8,736
= ceil[61,275.917...] × 8,736 + ceil[30.252...] × 8,736
= 61,276 × 8,736 + 31 × 8,736
= 535,577,952
S1 = 751,619,276 – 535,577,952
= 216,041,324
Total capacity of P-VOLs (kB) = ceil[(216,041,324 ÷ 8,736)] ×
2,048 × 256
= ceil[24,731.005...] × 2,048 × 256
= 24,731 × 2,048 × 256
= 12,966,166,528
Max. num. Snapshot pairs = 12,966,166,528 ÷ ceil[[{(10 × 1,024
× 1,024) ÷ 524,288}] × 524,288]
= 12,966,166,528 ÷ 10,485,760
= 1,236
Using these examples, the maximum number supported based on additional

shared memory in the V-VOL management area is 1,236 pairs.
Pool capacity for shared memory and capacity of the P-VOL that can be
created is shown in the following table.
Pool capacity (GB)

Shared
memory 2,04 4,09 6,14 8,19 10,24 12,28 14,33 20,48
30,720
8 6 4 2 0 8 6 0
Snapshot 26 11 - - - - - - -
(TB) (TB)
Snapshot 224 209 194 179 163 148 133 88 12
extension (TB) (TB) (TB) (TB) (TB) (TB) (TB) (TB) (TB)
Calculate max. pairs based on pair tables

A pair table keeps track of a pair’s status. One pair table is used for one pair.
A storage system contains 1,048,575 pair tables.
Pair tables are used by Snapshot and Compatible FlashCopy® V2 pairs.
Therefore, you must deduct the number of Compatible FlashCopy® V2 pairs
on the system from the number of pair tables to find out how many
Snapshot pairs you may create.
Determining max. pairs allowed on your system

Use the calculations in the preceding topics to determine the maximum
number of Snapshot pairs your system supports.
For example: The example calculations in the preceding topics produced
the following results:

• 6,544 Snapshot pairs were supported based on differential tables.
• 3,020 Snapshot pairs were supported based on shared memory of the
V-VOL management area.
• 1,048,575 Snapshot pairs were supported based on pair tables.
Using the lowest value, 3,020 pairs is the maximum number allowed on the
example system.
Planning for external volumes

External volumes are volumes on external systems. Multiple external
storage systems may be connected to a Virtual Storage Platform system.
External volumes can be used as pool VOLs when Universal Volume
Manager is installed. However, external volumes are more likely to fail than
internal volumes. Also, recovery from an external volume failure is more
complicated. For example, if an external volume used as a pool-VOL is
blocked, the pool becomes blocked as well.
You can minimize the effects of the external volume failure by adhering to
the following recommendations:
• Specify either all internal or all external volumes as pool VOLs in a
particular pool. Do not specify both kinds of volume in one pool.
• Specify external volumes from only one external system, not from
multiple external systems.
For details about external systems and the solutions for the errors related
to external volumes, see the Hitachi Universal Volume Manager User Guide.

3
Sharing Snapshot volumes
This topic discusses other Hitachi software product volumes that can be
shared with a Copy-on-Write Snapshot P-VOL.
□ Interoperability with other products and functions
□ Data Retention Utility
□ Volume Migration
□ ShadowImage
□ TrueCopy or Universal Replicator
□ Dynamic Provisioning
Sharing Snapshot volumes 3–1

Interoperability with other products and functions
Table 3-1 Types of volumes shared with Snapshot
Used as Snapshot Used as Snapshot

Volume types
P-VOL S-VOL
ShadowImage P-VOL Yes No
ShadowImage S-VOL Yes No
TrueCopy P-VOL Yes No
TrueCopy S-VOL Yes No
Universal Replicator P-VOL Yes No
Universal Replicator S-VOL Yes No
Volume Migration source volume Yes No
Volume Migration target volume No No
Read Only volume Yes Yes
Protect volume Yes Yes
“S-VOL Disable” volume Yes Yes
Zero Read Capacity volume Yes Yes
Invisible volume Yes Yes
Note: Observe the following:

• See the following topics for more information.
• Use CCI to set the Zero Read Capacity and Invisible attributes.
• Contact the Hitachi Data Systems Support Center for information on
Volume Migration.
Data Retention Utility

With Data Retention Utility, you can set the following access attributes on
Snapshot pair volumes: Read/Write, Read Only, Protect, and S-VOL Disable.
When working with these products, be aware of the following restrictions:
• Supported access attributes can be set on volumes that are already pair
volumes.
• The S-VOL Disable attribute cannot be set on a pair in one of the
following statuses:
• COPY
• SMPL(PD)
• COPY(RS)
• COPY(RS-R)
• PSUE
However, the attribute can be set on a P-VOL in these statuses, except
for COPY(RS-R).
3–2 Sharing Snapshot volumes

• If the S-VOL Disable attribute is currently set on a volume, the volume
cannot be used as a V-VOL in a subsequent paircreate operation.
• If the S-VOL Disable attribute is set on a P-VOL, the pair cannot be
restored.
Use the Storage Navigator Data Retention Utility window to check
whether a volume has the Read Only, Protect, S-VOL Disable, Zero Read
Capacity, or Invisible attribute.
Volume Migration
Observe the following when planning Snapshot pairs with Volume Migration
migration plans:
• When a P-VOL and the source volume of a migration plan are shared,
the Snapshot pair must be created before the migration plan is
executed.
• When a P-VOL and the source volume of a migration plan are shared,
the Snapshot status must be PAIR when you execute the migration plan.
• Deleting and canceling the migration plan are always allowed; these
actions are not affected by Snapshot pair status.
For information on using Volume Migration, contact the Hitachi Data
Systems Support Center.
ShadowImage
Snapshot (SS) P-VOLs can be shared with ShadowImage (SI) P-VOLs and
S-VOLs. However, Snapshot’s pair operations are limited according to the
ShadowImage pair’s status, and vice versa. The following tables show the
relationship between pair operations and status.
Table 3-2 SS Operations when P-VOL shared with SI P-VOL
ShadowImage status
Snapshot COPY
operation COPY PSUS COPY
COPY PAIR PSUS (RS- PSUE
(SP) (SP) (RS)
R)
Create pair Yes Yes Yes Yes Yes Yes No Yes
Split pair Yes Yes Yes Yes Yes Yes No Yes
Restore pair No No No No Yes No No Yes
Delete Snapshot Yes Yes Yes Yes Yes Yes Yes Yes
data
Delete pair Yes Yes Yes Yes Yes Yes Yes Yes

Table 3-3 SS Operations when P-VOL shared with SI S-VOL
ShadowImage status
Snapshot
operation COPY PSUS COPY COPY
COPY PAIR PSUS PSUE
(SP) (SP) (RS) (RS-R)
Create pair No No No No Yes No No No
Split pair N/A No No No Yes No No No
Restore pair N/A No No No Yes No No No
Delete Snapshot N/A Yes Yes Yes Yes Yes Yes Yes
data
Delete pair N/A Yes Yes Yes Yes Yes Yes Yes
Table 3-4 SI Operations when P-VOL shared with SS P-VOL
Snapshot status
ShadowImage
operation SMPL COPY COPY
COPY PAIR PSUS PSUE
(PD) (RS) (RS-R)
Create pair Yes Yes Yes Yes Yes No Yes
Create and split pair Yes Yes Yes Yes Yes No Yes
Split pair Yes Yes Yes Yes Yes No Yes
Forward pair Yes Yes Yes Yes Yes No Yes
resynchronization
Normal backward pair Yes Yes Yes Yes Yes No Yes
resynchronization
Quick backward pair No No No No No No No
resynchronization
Suspend pair Yes Yes Yes Yes Yes Yes Yes
Delete pair Yes Yes Yes Yes Yes Yes Yes
Table 3-5 SI Operations when S-VOL shared with SS P-VOL
Snapshot status
ShadowImage
operation SMPL COPY COPY
COPY PAIR PSUS PSUE
(PD) (RS) (RS-R)
Create pair No No No No No No No
Create and split pair No No No No No No No
Split pair Yes Yes Yes Yes Yes No Yes
Forward pair Yes Yes Yes Yes Yes No Yes
resynchronization
Normal backward pair Yes Yes Yes Yes Yes No Yes
resynchronization
Quick backward pair No No No No No No No
resynchronization
Suspend pair Yes Yes Yes Yes Yes No Yes

For more on ShadowImage pair status and operations, see the Hitachi
ShadowImage® User Guide.
Restrictions
• A Snapshot pair whose P-VOL is shared with a ShadowImage pair’s P-
VOL or S-VOL cannot have the same mirror unit (MU) number as the
ShadowImage pair.
• Because a Snapshot S-VOL uses the data in the P-VOL, the
ShadowImage Quick Restore operation is not allowed.
• A ShadowImage volume that is in a consistency group cannot be shared
with Snapshot.
• A Snapshot volume that is in a consistency group cannot be shared with
ShadowImage.
TrueCopy or Universal Replicator

Snapshot P-VOLs can be shared with TrueCopy (TC) or Universal Replicator
(UR) pair volumes. Snapshot’s pair operations are more restricted when
shared with these systems, according to the status of the shared pair, and
vice versa. The following tables show the relationship between pair
operations and status.
Table 3-6 SS Operations when P-VOL shared with TC or UR P-VOL
TrueCopy / Universal Replicator status

Snapshot operation
COPY PAIR PSUS PSUE Suspend Delete
Create pair Yes* Yes* Yes* Yes* Yes* Yes*
Split pair Yes Yes Yes Yes Yes Yes
Restore pair No No Yes Yes No No
Delete Snapshot data Yes Yes Yes Yes Yes Yes
Delete pair Yes Yes Yes Yes Yes Yes
* Cannot be used for delta resync.
Table 3-7 SS Operations when P-VOL shared with TC or UR S-VOL

Snapshot
operation SSWS*
1
Create pair Yes*3 Yes*3 Yes*3 Yes*3 Yes*3 Yes*3 Yes*3
Split pair No Yes Yes Yes Yes Yes Yes
Restore pair *2 No No No No No No No
Delete Snapshot data Yes Yes Yes Yes Yes Yes Yes

Snapshot
operation SSWS*
1
*1. SSWS is a UR pair status. TC pairs do not change to SSWS status.
*2. When restoring a SS pair whose P-VOL is used as a TC or UR S-VOL, switch
operations to the remote site using the horctakeover command.
*3. Cannot be used for delta resync.
Table 3-8 TC/UR Operations when P-VOL shared with SS P-VOL
Snapshot status
TC/UR operation SMPL COPY COPY
COPY PAIR PSUS PSUE
(PD) (RS) (RS-R)
Create pair Yes Yes Yes Yes Yes No Yes
Split pair Yes Yes Yes Yes Yes N/A Yes
Resynchronize pair Yes Yes Yes Yes Yes No Yes
Switch to remote site Yes Yes Yes Yes Yes No Yes
(horctakeover)
Table 3-9 TC/UR Operations when P-VOL shared with SS S-VOL
TrueCopy / Snapshot pair status

Universal
Replicator SMPL(P COPY(R COPY(R
COPY PAIR PSUS PSUE
operations D) S) S-R)
Create pair* No No No Yes No No No
Split pair Yes Yes Yes Yes Yes Yes Yes
Resynchronize pair Yes Yes Yes Yes Yes No Yes
Switch to remote site Yes Yes Yes Yes Yes No Yes
(horctakeover)
* If you want to use a TC or UR S-VOL as a Snapshot P-VOL, the Snapshot pair must
be created after the TC or UR pair is created.
Dynamic Provisioning
When sharing Snapshot and Dynamic Provisioning volumes, note the
following:
• Dynamic Provisioning pools cannot be used as Snapshot pools.
• The number of available pools for Snapshot decreases according to the
number of Dynamic Provisioning pools existing in the storage system. A
system can have a total of 128 pools.
• If a Dynamic Provisioning virtual volume is specified as the Snapshot P-
VOL, and the capacity of the Dynamic Provisioning virtual volume is
increasing, the Snapshot pair cannot be created.

4
Installation and configuration
This topic provides instructions and information for installing and

configuring Copy-on-Write Snapshot.
□ Configuration workflow
□ Installing and removing Snapshot
□ Creating data pools
□ Creating V-VOLs
□ On setting up the command device
Installation and configuration 4–1

Configuration workflow
Before configuring Snapshot, the following must be completed:
• Size the data pool and set up the volumes.
• Determine the maximum number of pairs allowed on your system.
• Set up the volumes to be used as P-VOL and V-VOL.
• Install the Copy-on-Write Snapshot software.
Setup for Snapshot consists of the following:
• Create the data pool.
• Create the V-VOL.
Note: In the procedures below, observe the following:
• When entering the Task Name, you can enter up to 32 alphanumeric
characters and symbols in all, except for \ / : , ; * ? ” < > |. Also, “date-
window name” is entered by default.
• If Go to tasks window for status is checked when you click Apply,
the task window appears.
Installing and removing Snapshot

In Storage Navigator, make sure ShadowImage is installed, then install the
Snapshot license key.
To remove, delete any Snapshot pairs, pools, and V-VOLs, then remove
Snapshot using Storage Navigator.
Creating data pools

The data pool stores data replaced in the P-VOL after the pair is split. This
allows the V-VOL to maintain a point-in-time image.
Prerequisite information
• Review the procedure before starting, to see the information needed for
selecting pool-VOLs.
• Pool capacity can range from 8 GB to 4 TB. A pool should be sized
according to write workload and other factors. See Sizing the data pool
on page 2-5 for more information.
• See System requirements on page 2-2 and Data pool requirements and
restrictions on page 2-3 for all pool requirements.
Caution: You cannot delete a pool-VOL after you add it to a pool, so make
sure the settings are correct on a pool-VOL before you add it.
To create a data pool:

1. In the Storage Navigator tree, select Pools.
2. In the Pools window, click Create Pools.
3. In the Create Pools window > Pool Type box, select COW snapshot
4–2 Installation and configuration

4. In the Pool Volume Selection box, proceed as follows:
a. In the Drive Type/RPM list, select your system’s data drive type
and RPM.
b. In the RAID Level list, select the system’s RAID level.
If you selected External Storage for Drive Type/RPM, “-” appears in
RAID Level, which indicates that the RAID level cannot be selected.
c. Click Select Pool VOLs.
d. In the Select Pool Volumes window > Available Pool Volumes
table, select the pool-VOLs you want in the table and click Add.
- To select all pool-VOLs in the list, click Select All Pages.
- To filter the rows, click ON in the Filter field.
- To specify the number of rows to be displayed, click Options and
make the selection.
5. Click OK.
6. In the Available Pool Volumes table, select the pool-VOLs you want in
Selected Pool Volumes.
7. In the Pool Name text box, enter a pool name. You can enter a total of
32 characters for the Prefix and Initial Number.
- In the Prefix text box, enter alphanumeric characters (case-sensitive).
- In the Initial Number text box, enter a number of up to nine digits.
8. Click Options.
9. In the Initial Pool ID text box, enter the number of the initial pool ID
from 0 to 127.
The smallest available number displays as the default. If no available
pool ID exists, then no number appears. When the registered pool ID is
entered, the smallest available pool ID automatically registered among
the subsequent pool ID that was entered.
10.In the User-Defined Threshold list, select a data pool capacity
threshold between 20% and 95% in 5% incrememts. The default is
80%.
11.Review your settings, then click Add, which places the new pool in the
Selected Pools table.
The Add button is disabled if required fields (indicated with “*”) are not
defined. If incorrect values were selected, an error displays.
12.Click Finish.
13.In the Confirm window, click Apply.
Creating V-VOLs
The V-VOL is the paired volume of the P-VOL. You must create a V-VOL
before you can create the pair.
Prerequisite Information
• The data pool must be set up prior to creating the V-VOL.

• The V-VOL must be the same size as the P-VOL.
• A maximum of 64 V-VOLs are allowed per P-VOL.
• For HP-UX: a volume already recognized by the HP-UX host server must
not be used as a V-VOL; otherwise an error occurs and the host server
is terminated. Recognize the volume from the host after the pair is
created.
• See System requirements on page 2-2 for V-VOL requirements.
• See Planning V-VOLs, data pools on page 2-4 for a discussion on the
number of V-VOLs to create, how long to hold a Snapshot, and other
planning considerations.
To create a V-VOL:
1. Tab window to make LDEVs.
- LDEV tab when Selecting Logical devices.
- LDEV tab when Selecting Pools.
2. Click Create LDEVs.
3. In the Create LDEVs wizard, in the Provisioning Type list, make sure
COW snapshot is selected.
4. In the System Type option, make sure OPEN is selected.
5. In the Emulation Type list, make sure OPEN-V is selected.
6. In the LDEV Capacity text box, enter the capacity of the V-VOL to be
created. A capacity range is shown below the text box. You can use
decimals, and you can change the capacity unit from the list.[Yosio]
(RSD writer/engineer, please explain last sentence.....) -> Users can
specify the capacity unit by using GB or else.
7. In the Number of LDEVs text box, enter the number of LDEVs to be
created.
8. In the LDEV Name text box, enter the V-VOL name.
- In the Initial Number text box, enter the initial number, which can be
up to nine digits.
You can enter a total of 32 characters for the Prefix and Initial Number.
9. Click Option.
10.In the Initial LDEV ID field, make sure the LDEV ID is set.
If you want to confirm the used number and unavailable number, click
View LDEV IDs to display the View LDEV IDs window.
Caution: You cannot change the LDEV ID, because it is automatically

registered.
11.In the Initial SSID text box, enter the SSID as the 4-digit
representation of a hexadecimal number (0004 to FFFE).
If you want to confirm the created SSID, click View SSID to display the
View SSID windows.
12.In the Cache Partition list, select CLPR.

13.In the Processor Blade list, select MP Blade ID.
14.Click Add.
The created V-VOLs now display in the Selected LDEVs table, unless
required values (indicated with “*”) were not selected, or invalid values
were set.
15.Click Finish.
16.In the Confirm window >Task Name text box, enter the task name.
17.Click Apply.
On setting up the command device

CCI requires a volume on the storage system to be set up and dedicated as
the CCI command device. This device acts as the interface between CCI and
the storage system. See the Hitachi Command Control Interface Command
Reference for information on how to set up the command device.

5
Pair operations
This topic provides instructions for performing pair operations.
□ Pair operations workflow
□ Checking pair status
□ Creating a pair
□ Splitting a pair
□ Resynchronizing a pair
□ Restoring a pair
□ Deleting pairs
Pair operations 5–1

Pair operations workflow
The operations workflow consists of the following:
• Check pair status. Each operation requires a pair to have a specific
status. You can also check status to see if an operation completed
successfully.
• Create the pair, in which the V-VOL becomes a virtual duplicate of the P-
VOL.
• Split the pair, which creates a point-in-time snapshot of the P-VOL in the
V-VOL, allowing use of the V-VOL by secondary applications.
• Resume the pair, in which Snapshot data is discarded and the V-VOL is
again a virtual copy of the P-VOL.
• Delete the pair, in which the pair relationship between the pair volumes
is ended.
• A pair can also be resynchronized or restored to the point-in-time data
of the last snapshot.
Checking pair status

Each pair operation requires a specific status. Check pair status before
performing an operation.
• For instructions on checking status, see Monitoring the system on page
6-2.
• For the operations allowed for specific statuses, see Pair status
definitions on page 6-3.
Creating a pair
When a pair is created, the V-VOL becomes a virtual copy of the P-VOL.
Updates to the P-VOL are reflected in the V-VOL until the pair is split.
Prerequisite Information
• The data pool and V-VOL for the new pair must created. See Installation
and configuration on page 4-1 for more information.
• Review pair volume requirements in Planning and design on page 2-1.
• The pair volumes must be in SMPL status.
• Use the same data pool for all pairs sharing a single P-VOL. For example,
three pairs with the same P-VOL must use the same data pool.
• If data pool capacity exceeds the threshold when the paircreate
command is issued, the command is rejected and the pair is not created.
• If you issue the paircreate command immediately after deleting previous
Snapshot data, be aware that the operation requires a longer time to
complete.
• The CCI hide mode (-m noread) is not supported for S-VOLs (V-VOLs).
If you specify it, the paircreate completes normally, but the hide mode
is ignored.
5–2 Pair operations

• When using an HP-UX host server, the Snapshot pair must be created
before you issue the command on the host to recognize the V-VOL
device.
Caution: If a volume is recognized by the HP-UX host server, do not
use the volume as a V-VOL. Otherwise an error occurs and the host
server may be terminated.
To create a Snapshot pair, run the CCI paircreate command. See the
Hitachi Command Control Interface Installation and Configuration Guide for
instructions.
When the paircreate completes, pair status changes to PAIR.
Creating pairs in a consistency group

This topic provides a summary of the steps needed to create pairs in a
consistency group. For the full information, see the Hitachi Command
Control Interface Installation and Configuration Guide.
• Use different consistency groups for each pair sharing a P-VOL.
• See the requirements for consistency groups in System requirements on
page 2-2. Also, review consistency group information in the Hitachi
Command Control Interface Installation and Configuration Guide.
• Do not mix pairs in the same CCI configuration file consistency group
that were created with the At-Time Snapshot option with pairs created
without the At-Time Snapshot option. Otherwise the pairsplit command
terminates abnormally and stored Snapshot data cannot be ensured.
To create pairs in a consistency group:
1. Execute the paircreate command, and include the option for specifying
the consistency group number. The At-Time Snapshot function is
enabled automatically when a consistency group number is specified.
2. Add more pairs to the same consistency group by executing the
paircreate command and specifying the same consistency group number
defined in Step 1.
Splitting a pair
Splitting a pair results in a virtual point-in-time copy of the P-VOL. When a
pair is split:
• The P-VOL continues receiving updates from the host, but updates are
not reflected in the V-VOL.
• P-VOL data blocks to be updated are first copied to the data pool.
Pointers in the V-VOL follow this original data to the data pool,
maintaining the point-in-time copy.
You can split one pair or multiple pairs belonging to a consistency group.
• Pair status must be PAIR.

• If a P-VOL is paired with two or more V-VOLs, none of the pairs may be
in COPY(RS-R) status, otherwise the pairsplit operation may end
abnormally.
• Do not execute the pairresync -restore command on a pair when a
pairsplit operation is being performed on a related pair (shares the same
P-VOL). Otherwise the pairsplit operation may end abnormally.
• Snapshot does not support Quick Split mode .
• See requirements for consistency group operations in System
requirements on page 2-2, if applicable.
To split a pair, use the CCI pairsplit command. See the Hitachi Command
Control Interface Installation and Configuration Guide for instructions.
To split pairs in a consistency group, use the CCI pairsplit command on
the consistency group that is a target of the At-Time Snapshot function.
When the pairsplit completes, pair status changes to PSUS.
Resynchronizing a pair
When a pair is resynchronized, the data in the data pool is deleted, and the
V-VOL again mirrors the current data in the P-VOL. A pairresync results in
increased capacity in the data pool.
• Pair status must be PSUS.
• If the Snapshot data in the data pool is also used by a related pair, then
only the Snapshot ID is deleted for the resynchronized pair; the data is
not deleted from the pool.
To resync a pair, use the CCI pairresync command. See the Hitachi
Command Control Interface Installation and Configuration Guide for
instructions.
When the pairresync completes, pair status changes to PAIR.
Restoring a pair
Restoring a pair results in any Snapshot data in the data pool being copied
back to the P-VOL. This restores P-VOL data to the point when the pair was
split.
• Pair status must be PSUS.
• Snapshot does not support Quick Restore.
To restore a pair, use the CCI pairresync -restore command.
When the restoration completes, pair status changes to PAIR.

Deleting pairs
When you delete a pair, the Snapshot relationship ends between the P-VOL
and V-VOL. Snapshot data for the pair is deleted from the pool.
• Pair status can be PAIR, PSUS, or PSUE.
• When the pair is deleted, status changes to SMPL (PD). After a period of
time, status changes to SMPL.
You cannot recreate the pair if the status is SMPL (PD). To shorten the
period when the pair is in SMPL (PD) status, delete the Snapshot data
(resynchronize the pair), wait until the pair status changes to PAIR, and
then delete the pair.
• The time in takes to delete a pair or pairs can be from several seconds
up to more than ten minutes. Time increases when a large area of the
pool is used for Snapshot data, or when multiple pairs are deleted at the
same time.
Deleting a single pair

To delete a single pair, use the CCI pairsplit -S command.
Deleting multiple pairs related to a port or host group

Use Storage Navigator to delete multiple pairs from a port or host group.
To delete multiple pairs related to a port or host group:
1. In Storage Navigator, click Actions > Local Copy > ShadowImage/
Copy-on-Write Snapshot > Pair Operation.
2. Change to Modify mode by clicking the icon.

3. In the Pair Operation window tree, select the port or host group that
contains the pairs you want to delete.
4. In the volume list, select the Snapshot pairs you want to delete, right-
click, and select the Pairsplit-S command from the menu.

Figure 5-1 Pairsplit-S Dialog box
5. In the Pairsplit-S dialog box, review the pairs you have selected and
click OK.
The Pairsplit-S dialog box closes and the list of the pairs to be deleted
displays in the Preview list,
6. Click Apply, then click OK on the confirmation message.
The pairs are deleted.
Deleting multiple pairs related to a pool

Use Storage Navigator to delete multiple pairs from a pool.
To delete multiple pairs related to a pool:
Copy-on-Write Snapshot > C.O.W Snapshot.
2. Change to Modify mode by clicking the icon.

3. In the C.O.W Snapshot window tree, select the pool containing the
pairs you want to delete.
4. From the list of pairs or volumes displaying in the volume list, select all
the pairs you want to delete, right-click, and select the Pairsplit-S
command from the menu.
5. In the Pairsplit-S dialog box, review the pairs you have selected and
click OK.
The Pairsplit-S dialog box closes and the list of pairs to be deleted
displays in the Preview list.
6. Click Apply, then click OK on the confirmation message.

The pairs are deleted.

6
Monitoring and maintenance
This topic provides information and instructions for monitoring and

maintaining the Copy-on-Write Snapshot system.
□ Monitoring the system
□ Maintaining the system
Monitoring and maintenance 6–1

Monitoring the system
Monitoring helps you to keep track of your pairs and volumes in their current
and past conditions. Monitoring is an ongoing activity. There are several
Snapshot elements you can monitor:
• Monitoring pair status on page 6-2 (status definitions included)
• Monitoring pair, volume details on page 6-4
• Monitoring S-VOL path information on page 6-5
• Monitoring number of pairs, license information on page 6-6
• Monitoring a pair’s operations history on page 6-8
• Monitoring pool information on page 6-9
Monitoring pair status

Monitor pair status before and after performing pair operations.
• Each operation requires a specific status or statuses. When you want to
perform a pair command, first check the pair’s status.
• Pair status changes when an operation is performed. Check status to see
that pairs are operating correctly and that status is changing to the
appropriate state during and after the operation.
Monitoring is done manually when using the Storage Navigator GUI. It
should be repeated frequently. Email notifications of problems in pair
operations can be set up using the GUI.
To monitor pair status:
Note: Both Snapshot and ShadowImage pairs display in the pair list.
Snapshot V-VOLs display in the “S-VOL” column.
2. In the Pair Operation window, locate the pair whose status you want
to review. Review pair status in the Status column.
Caution: Using monitoring software on a host: If a host has an application
installed to monitor the volumes of Snapshot pairs, some problems may
occur:
• An S-VOL whose status is not PSUS (or PFUS) rejects access from the
host, possibly causing problems for the monitoring application software
whose access is rejected.
• If the host computer connects to more than one port, other ports may
also go offline when the S-VOL rejects host access.
To solve these problems, stop the application software that monitors the
volumes.
You can view more details by right-clicking a pair and selecting Detail. See
Monitoring pair, volume details on page 6-4 for information.
6–2 Monitoring and maintenance

Pair status definitions
When checking your pairs’ status, click File/Refresh to make sure the data
is current. P-VOL/V-VOL access columns in the following table indicate
whether the volumes accept read/write.
Table 6-1 Pair status definitions
V-VOL
Status Description P-VOL access
access
SMPL The volume is not assigned to a pair. Yes No R/W
COPY The initial copy is in progress. If the P-VOL is already Yes No R/W
paired with another V-VOL, status does not change to
COPY.
PAIR (PFUL) The initial copy operation is complete and the volumes Yes No R/W
are paired. If pool capacity exceeds the threshold when
a pair is in PAIR status, the status changes to PFUL in
CCI.
PSUS (PFUS) The pairsplit operation has completed. Updates are Yes R/W enabled
written to the P-VOL but not are not mirrored in the V-
VOL. The V-VOL maintains pointers to P-VOL data at
the time of the split.
If pool capacity exceeds the threshold when a pair is in
PSUS status, the status changes to PFUS in CCI.
PSUE The pair is suspended by the system. The reason may Yes, unless a No R/W
be one of the following: failure occurs
• Snapshot data in the pool exceeds capacity. during a pair
• A failure occurred while restoring the pair. restore.
COPY (RS) The pairresync operation has begun on the PSUS or Yes No R/W
PFUS pair. This deletes Snapshot data from the pool.
The pair continues to exist.
COPY (RS-R) The pairresync-restore operation has begun on the Yes No R/W
PSUS pair. This writes Snapshot data from the pool
back to the P-VOL.
SMPL (PD) The pair deletion operation has begun. Yes No R/W
You cannot create pairs using a volume in SMPL (PD)
status. However, this status changes to SMPL status
after a brief interval. The volumes can then be used in
the paircreate operation.
Statuses required for pair operations

To perform a pair operation, the pair must have a specific status. The
following table shows the CCI pair operations and the statuses in which they
can be performed.
Table 6-2 Statuses required to run pair operations
CCI pair operation Required status

paircreate SMPL
paircreate –split PAIR/PFUL
pairsplit PAIR/PFUL

CCI pair operation Required status
pairresync PSUS/PFUS, PSUE
pairresync -restore PSUS/PFUS
pairsplit -S PAIR/PFUL, PSUS/PFUS, PSUE
Monitoring pair, volume details

You can review more details for a pair and pair volumes than are available
on the Pair Operation window. This includes volume capacity, related pool
ID, pool usage, and so on.
To check pair and volume details:
2. In the Pair Operation window, select the desired Snapshot pair on the
volume list, right-click, and select Detail from the menu.
Figure 6-1 Detail dialog box

3. In the Detail dialog box, check pair and volume details as desired. Fields
are described in the following table.
Table 6-3 Fields in the Detail dialog box
Items Descriptions
P-VOL P-VOL LDKC number, CU number, and LDEV number.
Emulation P-VOL emulation type.
Capacity (MB) P-VOL capacity in megabytes.
Capacity (blocks) P-VOL capacity in blocks.
CLPR (P) P-VOL cache logical partition.

Items Descriptions
Pool ID Pool ID of the pool in which the P-VOL is registered.
Amount of pool use Amount of the pool capacity used by the P-VOL.
by P-VOL (GB)
Pool usage rate by Pool usage rate of the P-VOL.
P-VOL
Snapshot Pair • MU: Snapshot ID.
Detail list • S-VOL: LDKC number, CU number, and LDEV number.
• Status: Pair’s status.
• Date: Time when the Snapshot data was stored in the pool.
• Pool used(GB): Capacity of the pool used by the S-VOL.
• Sync.: Consistency rate of data of the P-VOL and the S-VOL.
• CLPR (S): S-VOL’s cache logical partition (CLPR).
• CTG: Pair’s consistency group number.
When the consistency group is not specified, dotted lines (--
-) display.
Refresh the window If you select the check box, the information displayed in the
after this dialog ShadowImage Pair Operation window is updated after the Detail
box is closed. check dialog box closes. If you do not select the check box, the
box information stays the same when the dialog box is closed.
Refresh button Updates the information in the Detail dialog box.
Close button Closes the Detail dialog box.
Monitoring S-VOL path information

You can view path information for the S-VOL.
To monitor S-VOL path information:
2. In the Pair Operation window, select a pair in the volume list, right-
click, and select S-VOL Path from the menu.

Figure 6-2 S-VOL Path dialog box
3. In the S-VOL Path dialog box, check S-VOL information as desired.
Fields are described in the following table.
Table 6-4 Fields in S-VOL Path dialog box
Items Descriptions
Pair Information Path information for the selected pairs. P-VOL and S-VOL volumes
box are shown in the AAA-BB-CCC(XX:YY:ZZ) format.
• AAA : Port ID (cluster name and channel number)
• BB : Group number (G-ID) of host group
• CCC : LU number
• XX:YY:ZZ : LDKC number:CU number: LDEV number
S-VOL Path Path information for the S-VOLs selected in the Pair Information
Information box box.
• Port : The port ID
• GID: The group number of host group
• LUN: LU number
Close button Closes the S-VOL Path dialog box.
Monitoring number of pairs, license information

You can review information related to pairs and license capacity using the
Information dialog box.

To review pair and license information:
2. In the Pair Operation window, right-click anywhere in the Pair
Operation window, and select Information from the menu.
Figure 6-3 Information dialog box

3. In the Information dialog box, review pair and license information as
desired. Fields are described in the following table.
Table 6-5 Items of Information dialog box
Items Descriptions
ShadowImage Number of ShadowImage pairs in the XXXX / YYYY format, where
pair(s) XXXX is ShadowImage pairs and YYYY is the number of
ShadowImage pairs and ShadowImage for Mainframe pairs.
C.O.W. Snapshot Number of Snapshot pairs. The maximum number of pairs that
pair(s) can be created in one subsystem is 16,384. Therefore, if
ShadowImage pairs, Volume Migration, and Compatible
FlashCopy® V2 are created in the same subsystem, the
maximum number of pairs that you can create may be less than
16,384 minus YYYY.
Reserved The number of reserved volumes of ShadowImage is displayed in
volume(s) the format of XXXX / YYYY, where XXXX indicates the number of
reserved volumes of ShadowImage, and YYYY indicates the total
number of reserved volumes of ShadowImage and ShadowImage
for Mainframe.Reserved volumes include S-VOLs of
ShadowImage and ShadowImage for Mainframe.
Remaining pair Number of usable pair tables in the storage system displayed in
table(s) XXXXX / YYYYY format, where XXXXX is the number of usable pair
tables and YYYYY is the maximum number of pair tables. For
details about the maximum number of pair tables, see Calculate
max. pairs based on pair tables on page 2-10.

Items Descriptions
Remaining Number of usable differential tables in the storage system in the
differential table(s) XXXXXX / YYYYYY format, where XXXXXX is the number of usable
differential tables and YYYYYY is the maximum number of
differential tables. For details about the maximum number of
differential tables, see Calculating max. pairs based on differential
tables on page 2-6.
Used volume (TB) ShadowImage license information in the X(Y) format, where X is
license capacity used by ShadowImage and Y is total license
capacity reserved for ShadowImage. Unlimited displays when
there is no limit on license capacity.
C.O.W. Snapshot Snapshot license information in the X(Y) format, where X is
Used volume (TB) license capacity used by Snapshot and Y is total license capacity
reserved for Snapshot. Unlimited displays when there is no limit
on license capacity.
Close button Closes the Information dialog box.
Monitoring a pair’s operations history

You can review the operations that have been performed on a pair using the
History Window.
To review a pair’s operations history:
Copy-on-Write Snapshot > History.
If some of the pairs include LUSE volumes or if the total number of the
following pairs and migration plans is 500 or more in the subsystem, you
may need to wait for a while until the History window displays the
operation history.
• ShadowImage pairs
• Copy-on-Write Snapshot pairs
• ShadowImage for Mainframe pairs
2. In the History window, see Snapshot information in the bottom part of
the window. The list sorts based on the column heading you click.
3. To change the displaying order, click a column in the list. The list is
sorted based on the items in the clicked column.
• If there are more than 16,384 records of operations, the list is
divided into multiple pages and only the list that is currently
displayed is sorted.
• If you click the same column again, you can switch the sorting order
(Ascending or Descending).
4. If the information on the list is not updated, click File and then Refresh
on the menu bar of the Storage Navigator main window to update with
the latest information.

For operations involving the copying process, the History window does
not display information about the operations until the copying process
starts. If you perform an operation on a pair before the copying process
starts, the History window does not display information about the
operation.
5. If there are many records of operations, click the scroll button. The list
scrolls and you can see the operation history that has not been
displayed.
If you click and drag down the frame border that divides the History
window into upper and lower panes, you can expand the display area of
the list.
6. If there are more than 16,384 records of operations, click Next. The list
displays subsequent records of operations.
• If you click Previous, the list switches to the previous page.
• If there are 16,384 or fewer records of operations, you cannot click
Previous and Next.
• The subsystem saves up to 524,288 records of latest operations.
Monitoring pool information

You can view information about a pool.
To view pool information:
1. In the Storage Navigator tree, select Pool.
2. From the names that appear below Pool, click the pool that you want to
review.
3. In the Pool list on the right pane, review the desired pool information.

For more pool information, see Top window when selecting Pool on page B-
16, and Top window when selecting a pool volume group under Pool on page
B-19.
Maintaining the system

Some maintenance tasks are a response to behavior discovered during
system monitoring. Other tasks are performed to change settings for your
changing requirements. The following topics provide instructions for
managing the storage system, data pools, and V-VOLs.
• Heavy-workload option on page 6-11
• Managing pools on page 6-11
• Managing V-VOLs on page 6-14

Heavy-workload option
When the workload on the storage system increases, host I/O performance
may be degraded. If Snapshot performs the restore operation at this time,
performance may be further degraded.
You can set the Copy Threshold option to automatically stop copy
processing for the restore operation at this time. Copy operations resume
when the workload lightens. This option also affects the following
operations:
• ShadowImage
• ShadowImage for Mainframe
Contact the Hitachi Data Systems Support Center to set this option.
Managing pools
You can perform the following maintenance tasks on data pools:
• Increasing pool capacity on page 6-11
• Recovering pools on page 6-12
• Changing pool threshold on page 6-12
• Changing pool name on page 6-13
• Deleting pools on page 6-13
Increasing pool capacity

You should increase pool capacity when the pool threshold is reached more
than once or twice. Capacity is increased by adding pool volumes to the
pool. Check capacity in the Pool window (see Monitoring pool information on
page 6-9).
To increase pool capacity:
2. From the names that appear below Pool, click the pool whose capacity
you want to increase.
3. Click Expand.
4. In the Expand Pool window, select the pool-VOL according to the
following steps.
a. In the Drive Type/RPM list, select your system’s data drive type
and RPM.

b. In the RAID Level list, select the system’s RAID level.
If you selected External Storage for Drive Type/RPM, “-” appears in
RAID Level, which indicates that the RAID level cannot be selected.
c. Click Select Pool VOLs.
d. In the Select Pool Volumes window > Available Pool Volumes
table, select the pool-VOLs you want in the table.
- To select all pool-VOLs in the list, click Select All Pages.
- To filter the line, click ON in the Filter field.
- To specify the number of lines to be displayed, click Options and
make the selection.
e. Click OK.
The Select Pool Volumes window closes. The number of the
selected pool volumes is shown in Total Selected Pool Volumes,
and the total capacity of the selected pool-VOL is shown in Total
Selected Capacity.
5. Click Finish.
6. In the Confirm window’s Task Name box, enter the task name.
7. Click Apply.
Recovering pools
This operation is for failure recovery of a blocked pool. Ordinarily you should
not need to perform this operation.
To recover a blocked pool:
2. From the names that appear below Pool, select one or more pools that
you want to recover.
3. Click More Action > Restore Pools.
4. In the Restore Pools window’s Task Name text box, enter the task
name.
5. Click Apply.
Note: The recovery time for pools varies depending on pool or V-VOL
usage. Calculate roughly 20 minutes of recovery time for every 100 TB of
pool or V-VOL usage. Recovery time also varies according to the workload
on the system.
Changing pool threshold

When you want to change the pool threshold, perform the following
procedure. By monitoring the pool usage rate, you can prevent the pool
from reaching full capacity.
To change pool threshold:
2. From the names that appear below Pool, click the pool whose threshold
you want to change.

3. Click More Actions, and then select Edit Pools.
4. In the Edit Pools window, check User-Defined Threshold.
5. In the User-Defined Threshold list, select the new threshold.
6. Click Finish.
7. In the Confirm window’s Task Name text box, enter the task name.
8. Click Apply.
Changing pool name

You can change the name of a pool.
To change a pool name:
2. From the names that appear below Pool, click the pool whose name you
want to change.
3. Click More Actions, and then select Edit Pools.
4. In the Edit Pools window, check Pool Name.
5. In the Pool Name text box, enter a new pool name. You can enter a
total of 32 characters for the Prefix and Initial Number.
- In the Initial Number text box, enter a number of up to 9-digit.
6. Click Finish.
8. Click Apply.
Deleting pools
You can delete a single pool or multiple pools at the same time.
To delete pools:
2. From the names that appear below Pool, click the pool, select one or
more pools that you want to delete.
3. Click More Action to select Delete Pools.
4. In the Delete Pools window, click Finish.
6. Click Apply.
Note: Please observe the following:
• If the cache write pending rate exceeds 55%, the pool usage may not
be 0, because the V-VOL cannot be released from the pool.
• The capacity that appears in Total of Pool Capacity in the Pool
window may differ from the previous one even when the pools are
deleted.

Managing V-VOLs
Managing V-VOLs consists of the following tasks:
• Changing a V-VOL name on page 6-14
• Deleting V-VOLs on page 6-14
Changing a V-VOL name

You can change the name of a V-VOL.
To change a V-VOL name:
1. Do one of the following:
• In the Storage Navigator tree, select Logical Devices.
• In the Storage Navigator tree, select Pool.
- In the pool name that appears below Pool, click the pool associated
with the V-VOLs whose capacity you want to increase.
- Click the Virtual Volumes tab on the right pane.
2. In the list, select one or more V-VOLs whose name you want to change.
3. Select Edit LDEVs.
4. In the Edit LDEVs window’s LDEV Name box, enter a new pool name.
You can enter a total of 32 characters for the Prefix and Initial Number.
- In the Initial Number text box, enter a number of up to 9-digit.
5. Click Finish.
7. Click Apply.
Deleting V-VOLs
You can delete a single V-VOL or multiple V-VOLs at the same time.
• To be deleted, a V-VOL cannot be part of a Snapshot pair. The pair must
first be deleted before the V-VOL can be deleted.
To delete V-VOLs:
1. In the Storage Navigator tree, select Logical Devices.
2. In the list, click one or more V-VOLs that you want to delete.
• To select all pool-VOLs in the list, click Select All Pages.

• To filter the rows, click ON in the Filter field.
• To specify the number of rows to be displayed, click Options and
make the selection.
3. Click More Action > Delete LDEVs.
4. In the Delete LDEVs dialog’s Task Name box, enter the task name.
5. Click Apply.
Powering-off, changing the microprogram

This topic explains how pairs are maintained when the storage system is
powered off, and when the microprogram is replaced.
• Powering-off on page 6-15
• Replacing the microprogram offline on page 6-16
Powering-off
Stop host I/O to the P-VOL before switching off the power supply.
When power is restored, Snapshot’s behavior depends on whether data that
was in shared memory before powering off is present after powering on.
If information in shared memory before powering off is present

after powering on
If information in the shared memory is present after switching off the power
supply, the pools and Snapshot pairs can usually be used. However, since
the storage system checks the status of the pools and the pool volumes, if
the pool volumes are blocked at that moment, the pool will be blocked and
the status of the Snapshot pairs changes to PSUE. When this occurs, you
need to recover the pools after powering on.
When you store Snapshot data by consistency group, if the power supply is
switched off before the status of all the pairs in a consistency group has
changed completely, the storing of Snapshot data will not be resumed, and
the status of some pairs may remain unchanged when the power supply is
switched on again.
If information in shared memory is lost after switching off the

power supply
The storage system has a battery used to maintain the information in
shared memory. However, when a certain amount of time elapses after the
breaker is turned off, the battery dies and the information in the shared
memory is lost. If this occurs, the pools and pairs must be re-created after
powering on again.
For information about the amount of time before the information in the
shared memory is lost when the breaker is turned off, check with the Hitachi
Data Systems Support Center.

Replacing the microprogram offline
The microprogram is usually replaced online. In the cases when it is
replaced offline (for example, when configuration of shared memory needs
changing), pool and pair information in shared memory is lost and must be
re-created.

7
Troubleshooting
This topic provides Copy-on-Write Snapshot troubleshooting information.
□ Copy-on-Write Snapshot general troubleshooting
□ Snapshot troubleshooting with Command Control Interface
Troubleshooting 7–1
Copy-on-Write Snapshot general troubleshooting
The following table provides a list of general problems with possible causes
and solutions.
Problem Causes and solutions

Cannot install Snapshot. Causes:
• Shared memory for the V-VOL management area is not installed.
• Shared memory is not set for the V-VOL management area.
• Shared memory for the differential tables is not installed.
Solutions:
• Call the Hitachi Data Systems Support Center and check if the shared
memory for the V-VOL management area and the differential tables is
installed.
• Call the Hitachi Data Systems Support Center and check if the shared
memory for the V-VOL management area is correctly set.
Pool information is not Cause: The pool is blocked.
displayed. Solution: Implement the measures shown in Recovering a blocked pool on
page 7-5.
A pool is blocked. Cause: The pool-VOLs are blocked.
Solution: Implement the measures shown in Recovering a blocked pool on
page 7-5. After the problems are solved, make sure to complete the SIMs.
See Processing pool-related SIMs on page 7-5.
Pool usage rate exceeds Causes:
the threshold. • Too much Snapshot data is stored in the pool.
• Capacity of the pool is insufficient.
• Threshold of the pool is too low.
Solutions:
• Delete old or less important Snapshot data to decrease the usage rate of
the pool.
• Add more pool volumes to increase the capacity of the pool.
• Set a larger value to the threshold of the pool.
After the problems are solved, make sure to complete the SIMs. See
Processing pool-related SIMs on page 7-5.
Note: You need unused volumes to add the pool volumes. If there is no
unused volume, you need to create new volumes or ask the Hitachi Data
Systems Support Center to add the hard disks. Therefore, it may take time
to solve the problem.
Cannot add pool-VOLs. Causes:
• The maximum 1,024 pool-VOLs are already set in the pool.
• Available pool management block in the V-VOL management area in the
shared memory is insufficient.
• Pool-VOL requirements were not followed.
Solutions:
• Add pool-VOLs to another pool.
• Initialize the V-VOL management area.
• Check pool-VOLs requirements in Data pool requirements and
restrictions on page 2-3.
7–2 Troubleshooting
Cannot create Snapshot Causes:
pairs. • There are not enough differential tables to create the pairs.
• The conditions to create the pair are not fulfilled.
• The volume specified to create the pair is in SMPL(PD) status because the
pair is being deleted.
Solutions:
• Secure enough differential tables to create the Snapshot pairs.
• Fulfill the conditions to create the pair and try the pair creation again.
• View the ShadowImage Pair Operation window and verify that the status
of the volume changes to SMPL, and then try the pair creation again.
• Execute CCI’s inqraid command and verify that the volume is not used
by Snapshot, and then try the pair creation again.
Snapshot pairs are not Causes:
displayed in the volume • Snapshot pairs are not created.
list. • Displaying of the Snapshot pairs is prohibited by the filtering function.
Solutions:
• Create Snapshot pairs.
• Change the settings in the Display Filter dialog box.
An error occurred while Cause: A volume is blocked because a failure occurred in the data drive.
restoring the pair. Solution: Delete the Snapshot pair that is blocked, and call the Support
Center.
A volume is blocked. Causes:
• A failure occurred in two or more data drives.
• The breaker was turned off once and then the power supply switched on.
Solution: Ask the Hitachi Data Systems Support Center for assistance.
A problem occurred on Cause: Access to the volume is rejected.
the host application for Solution:
monitoring the volumes. 1. Stop the host application monitoring the volumes.
2. Change all Snapshot pair statuses to PSUS, then restart the monitoring
application on the host.
To see whether the host has access to pair volumes, see the P-VOL/S-VOL
access columns in Pair status definitions on page 6-3.
When the host computer Cause: A port may go offline because access to a volume on another port(s)
tries to access the port, is rejected.
an error occurs and the Solutions:
host cannot access the • Wait for a while then retry the operation.
port. • If a host application is installed to monitor the volume, stop the
application.
Storage Navigator Causes:
times-out frequently. • The load on Storage Navigator is too heavy and it cannot respond to the
SVP.
• The time-out period is not long enough.
Solutions:
• Wait for a while, then retry the operation.
• Verify the Storage Navigator RMI time-out period.
For information about how to set RMI time-out period, see the Hitachi
Storage Navigator User Guide.
Pairsplit on a Causes:
consistency group • All pairs in the consistency group are not in PAIR status. This may result
terminates abnormally. in rejection of the command, Timeout (Error code: EX_EWSTOT), or
suspension of the pair (Error code: EX_EWSUSE).
• During the operation, a pairresync or pairsplit-S operation is begun on
another pair or pairs in the consistency group. This may result in a
timeout (Error code: EX_EWSTOT), or suspension of the pair (Error code:
EX_EWSUSE)
Solutions:
• Make sure all pairs in the consistency group are in PAIR status and retry
the operation.
• Perform only one operation on the pairs in a consistency group at one
time.
Pairsplit on a Error code EX_EWSTOT is generated, and the status of some Snapshot pairs
consistency group in a consistency group cannot be changed.
terminates abnormally Possible causes:
when P-VOL shared with • When a UR S-VOL is used as Snapshot P-VOL, the capacity of the journal
Universal Replicator or volumes for this UR pair is insufficient.
TrueCopy. • The Snapshot license is invalid.
• Snapshot pair volumes are blocked.
• The Snapshot pair is in a status in which the pairsplit command cannot
be executed. See Statuses required for pair operations on page 6-3.
• The TC or UR pair is in a status in which the pairsplit command cannot
be executed.
Solution: After the cause or causes are corrected, change all pairs to PAIR
status and execute the pairsplit command again.
Restore pair operation Causes:
terminates abnormally. • The pair’s Snapshot data is being stored per consistency group.
• The P-VOL is also a P-VOL in another Snapshot pair, and the Snapshot
data in the second pair is stored per consistency group.
Creating consistency Problem: You can create a consistency group with no Snapshot pairs.
groups when host server However, pairs created with the At-Time Split option in this condition may be
is down or failed. rejected.
Solution: Find the consistency group number in the C.O.W. Snapshot or Pair
Operation window in Storage Navigator, and create a pair specifying the
consistency group number intentionally.
Recovering from failure during pairresync -restore

If a failure occurs during pair restoration and pair status changes to PSUE,
data in the P-VOL cannot be ensured. You can either delete the pair and
create a new pair, or resynchronize the pair to establish consistency in the
P-VOL, and then overwrite the P-VOL with backup data.
Recovering a terminated HP-UX host server

An error may occur and the HP-UX host server terminated if a volume that
has already been recognized by the host server is later used as a V-VOL in
a paircreate operation. Pairs should be created prior to issuing the
command to recognize a device.
To recover a terminated HP-UX host server:
1. Force the command process and its parent process to terminate.
2. Create a Snapshot pair. Make sure the emulation type is “0” (OPEN-0V)
for both the V-VOL volume and the VDEV for the V-VOL group.
3. Split the pair, storing Snapshot data in the pool.
4. Execute the command to recognize the device.
Recovering a blocked pool

When a pool is blocked, recovery must be performed in the following order:
pool-VOLs, pool, pairs, V-VOLs.
1. To recover a blocked pool-VOL, call the Support Center.
2. To recover the pool, perform one of the following:
• Add additional pool-VOLs to the pool.
• Delete Snapshot data from the pool to increase unused capacity.
• Delete pairs to lower the pool’s usage.
3. To recover the pair, delete the pair. This is necessary because, when
a pool is blocked, the status of all Snapshot pairs with Snapshot data in
the pool changes to PSUE. To recover the PSUE pairs, they must be
deleted and re-created.
4. To recover the V-VOL, call the Support Center.
Processing pool-related SIMs

Check and correct pool-related SIMs (Service Information Message) for the
following, if they occur:
• Reference code 601XXX—Pool usage rate exceeds the threshold.
• Reference code 602XXX—Pool is blocked.
XXX indicates the pool ID. Check SIMs using the System Information/Status
window in Storage Navigator.
After correcting a problem related to a SIM, complete the SIM, changing its
status to completed.
To complete a SIM:
1. After correcting the problem so that pool status is normal, open the Pool
window.
2. Click Complete SIM Action.
3. In the Confirmation window, enter the Task Name.
4. Click Apply.
Snapshot troubleshooting with Command Control

Interface
When an error occurs using CCI, you can identify the cause of the error by
referring to the following:
• The log displayed on the CCI window
• The CCI operation log file
To identify an error using the log on the CCI window:
1. Find the error code from the logs displayed on the CCI window.
Figure 7-1 Example of a log displayed on the CCI window

2. Locate the SSB1 and SSB2 codes. In the figure above, the error codes
appear to the right of "SSB=".
• The last four digits to the left of the comma (,) are the SSB1 code
(B9E1).
• The last four digits to the right of the comma (,) are the SSB2 code
(B901).
3. Locate the description of the SSB1/SSB2 error code combination in the
table above. For error codes not described in this table, contact the
Hitachi Data Systems Support Center.
To identify an error using the CCI operation log file:
1. Open the CCI log file, whose default location is:
/HORCM/log*/curlog/horcmlog_HOST/horcm.log
where:
• * is the instance number.
• HOST is the host name.
2. Find the error code. An example error code string is:
11:06:03-37897-10413- SSB = 0xB901,4A96
3. Locate the SSB1 and SSB2 codes. In the following figure, the error codes
appear to the right of "SSB=".
• The last four digits to the left of the comma (,) are the SSB1 code
(B901).
• The characters to the right of the comma (,) are the SSB2 code
(4A96).
4. Locate the description of the SSB1/SSB2 error code combination in the
following table.
For details about error codes not described in the table, contact the Hitachi
Data Systems Support Center.
Table 7-1 CCI error codes for SSB1: B901, B9A8, B9A9, B9AD, B9AE)
SSB2 CCI command Cause of error

9685 paircreate Because of a shortage of pair tables, Snapshot pair cannot
be created.
9686 paircreate Because of a shortage of differential tables, Snapshot pair
cannot be created.
9700 paircreate Since the pool is not available, Snapshot pair cannot be
created.
9702 paircreate When trying to create multiple Snapshot pairs by
specifying multiple S-VOLs for one P-VOL, you specified a
pool ID that is different from the pool ID used by the pairs
that are already created. Therefore, Snapshot pair cannot
be created.
9703 paircreate Since the volume you specified as the P-VOL is already
used by other Snapshot S-VOL, the pair cannot be created.
9704 paircreate Since the volume you specified as the S-VOL is already
used by other Snapshot P-VOL, the pair cannot be created.
9705 paircreate Since the volume you specified as the S-VOL is already
used by other Snapshot S-VOL, the pair cannot be created.
9706 paircreate Since the specified Snapshot ID is already used by other
Snapshot pair, the pair cannot be created.
9707 paircreate Since the capacity of the pair exceeds the licensed
capacity, the pair cannot be created.
9718 All commands The command ended abnormally because a command
other than the paircreate command was issued for the
volume in the pair other than the Snapshot pair.
This error also may be reported when the command is
executed with an unsupported parameter specified.
9719 All commands The command ended abnormally because the pair is in a
status that the command does not accept.
This error also may be reported when the command is
executed with an unsupported parameter specified.
971a paircreate Since the capacity of shared memory is insufficient, the
pair cannot be created.
971b paircreate Since the attribute of the specified pool is other than
Snapshot, Snapshot pair cannot be created.
971f pairresync - Since the volume you specified as the P-VOL has an S-VOL
restore Disable attribute, Snapshot pair cannot be restored.
9720 All commands Any errors have occurred because of the Snapshot
operation.
9721 paircreate, Since either Snapshot or ShadowImage is not installed,
pairsplit, the command ends abnormally.
pairresync,
pairresync -
restore
9723 All commands Because of no additional shared memory (FCv2, TPF,
Extention1), the command ends abnormally.
9724 All commands Because of no additional shared memory (more than
COW1), the command ends abnormally.
9725 All commands Since the LDEV number of the volume you specified as the
P-VOL is beyond the specified range, the command ends
abnormally.
9726 All commands Since you specified the unmounted volume as the
Snapshot P-VOL, the command ends abnormally.
9727 paircreate, Since you specified a blocked volume as the Snapshot P-
pairsplit, VOL, the command ends abnormally.
pairresync,
pairresync -
restore
9728 paircreate, Since you specified a volume that is in process of
pairsplit, formatting as the Snapshot P-VOL, the command ends
pairresync, abnormally.
pairresync -
restore
9729 paircreate, Since you specified a volume whose emulation type is
pairsplit, other than OPEN-V as the Snapshot P-VOL, the command
pairresync, ends abnormally.
pairresync -
restore
972a paircreate Since the volume you specified as the Snapshot P-VOL has
the command device setting, the pair cannot be created.
972c paircreate Since the capacity of the volume you specified as the
Snapshot P-VOL exceeds the supported size (4TB), the
972e paircreate Since the capacity of the volume you specified as the
Snapshot S-VOL exceeds the supported size (4TB), the
972f paircreate Since you specified a V-VOL as the Snapshot P-VOL, the
9730 paircreate Since you specified a pool-VOL as the Snapshot P-VOL, the
9731 pairresync - When Snapshot P-VOL and TrueCopy P-VOL share the
restore volume, the status of the TrueCopy pair is other than PSUS
or PSUE. Therefore, the Snapshot pair cannot be restored.
9732 pairresync - When Snapshot P-VOL and Universal Replicator P-VOL
restore share the volume, the status of the Universal Replicator
pair is other than PSUS or PSUE. Therefore, the Snapshot
pair cannot be restored.
9733 pairresync - Since Snapshot P-VOL and TrueCopy S-VOL share the
restore volume, the Snapshot pair cannot be restored.
9734 pairresync - Since Snapshot P-VOL and Universal Replicator S-VOL
restore share the volume, the Snapshot pair cannot be restored.
9735 paircreate Since you specified Universal Replicator’s journal volume
as the Snapshot P-VOL, the pair cannot be created.
9736 paircreate, Since the LUSE volumes you specified for the P-VOL and
pairsplit, S-VOL do not have the same structure, the command ends
pairresync -
restore
973a paircreate Since you specified a volume with the VMA setting as the
Snapshot P-VOL, the pair cannot be created.
973b All commands Since the LDEV number of the volume you specified as the
S-VOL is beyond the specified range, the command ends
abnormally.
973c All commands Since you specified an unmounted volume as the Snapshot
S-VOL, the command ends abnormally.
973d paircreate, Since you specified a blocked volume as the Snapshot S-
pairsplit, VOL, the command ends abnormally.
pairresync,
pairresync -
restore
973e paircreate, Since you specified a volume that is in process of
pairsplit, formatting as the Snapshot S-VOL, the command ends
pairresync -
restore
973f paircreate, Since you specified a volume whose emulation type is
pairsplit, other than OPEN-V as the Snapshot S-VOL, the command
pairresync -
restore
9740 paircreate Since the volume you specified as the Snapshot S-VOL has
the command device setting, the pair cannot be created.
9742 paircreate Since you specified an external volume as the Snapshot S-
VOL, the pair cannot be created.
9745 paircreate Since you specified a volume other than V-VOLs as the
Snapshot S-VOL, the pair cannot be created.
9746 paircreate Since you specified a pool-VOL as the Snapshot S-VOL, the
9747 paircreate Since you specified TrueCopy P-VOL as the Snapshot S-
9748 paircreate Since you specified TrueCopy S-VOL as the Snapshot S-
9749 paircreate Since you specified Universal Replicator data volume or
journal volume in the intermediate site of 3DC cascading
configuration as the Snapshot S-VOL, the Snapshot pair
cannot be created.
974a paircreate Since you specified Universal Replicator P-VOL as the
974b paircreate Since you specified Universal Replicator S-VOL as the
974c paircreate Since you specified Universal Replicator journal volume as
the Snapshot S-VOL, the pair cannot be created.
974f All commands Since the volume you specified as the S-VOL has an S-VOL
Disable attribute, the command ends abnormally.
9750 paircreate Since you specified a volume with the VMA setting as the
9752 paircreate, Since the Max LBA size of the volumes you specified as the
pairsplit, Snapshot P-VOL and S-VOL is different, the command
pairresync -
restore
9753 paircreate, Since the number of slots of the volumes you specified as
pairsplit, the Snapshot P-VOL and S-VOL is different, the command
pairresync -
restore
9754 paircreate Since you specified a Dynamic Provisioning V-VOL as the
9756 All commands Since you specified a ShadowImage reserved volume as
the Snapshot P-VOL, the command ends abnormally.
9757 All commands Since you specified a Volume Migration source volume as
For information about using Volume Migration, contact the
9758 All commands Since you specified a Volume Migration target volume as
9759 All commands Since you specified a Volume Migration reserved volume
as the Snapshot P-VOL, the command ends abnormally.
For information o about n using Volume Migration, contact
the Hitachi Data Systems Support Center.
975a All commands Since you specified a ShadowImage P-VOL as the
Snapshot S-VOL, the command ends abnormally.
975b All commands Since you specified a ShadowImage S-VOL as the
Snapshot S-VOL, the command ends abnormally.
975c All commands Since you specified a ShadowImage reserved volume as
the Snapshot S-VOL, the command ends abnormally.
975d All commands Since you specified a Volume Migration source volume as
975e All commands Since you specified a Volume Migration target volume as
975f All commands Since you specified a Volume Migration reserved volume
as the Snapshot S-VOL, the command ends abnormally.
9763 paircreate The Snapshot pair cannot be created for any of the
following reasons:
• The shared memory is not increased.
• Initialization is in process.
976a paircreate Unavailable parameter (unsupported parameter) is
specified in the command.
976c pairsplit Since the command was executed with the PSUE option,
the Snapshot data cannot be stored.
976e pairsplit When Snapshot P-VOL and TrueCopy S-VOL share the
volume, the status of the TrueCopy pair is COPY.
Therefore, the Snapshot data cannot be stored.
976f pairsplit When Snapshot P-VOL and Universal Replicator S-VOL
share the volume, the status of the Universal Replicator
pair is COPY. Therefore, the Snapshot data cannot be
stored.
9771 paircreate Since you specified Universal Replicator delta resync pair
volume as the Snapshot P-VOL, the Snapshot pair cannot
be created.
9772 paircreate Since you specified Universal Replicator delta resync pair
volume as the Snapshot S-VOL, the Snapshot pair cannot
be created.
9774 paircreate When the Snapshot P-VOL and ShadowImage P-VOL share
the volume, the MU number you specified for the Snapshot
pair is already used by the ShadowImage pair. Therefore,
the Snapshot pair cannot be created.
9776 paircreate When the Snapshot P-VOL and ShadowImage P-VOL share
the volume, the ShadowImage P-VOL you specified for the
Snapshot P-VOL has consistency group settings.
Therefore, the Snapshot pair cannot be created.
9777 paircreate When the Snapshot P-VOL and ShadowImage S-VOL share
the volume, you specified MU number zero (0) for the
Snapshot P-VOL. Therefore, the Snapshot pair cannot be
created.
9778 paircreate When the Snapshot P-VOL and ShadowImage S-VOL share
the volume, the ShadowImage S-VOL you specified for the
Snapshot P-VOL has consistency group settings.
Therefore, the Snapshot pair cannot be created.
977a paircreate, When the Snapshot P-VOL and ShadowImage P-VOL share
pairsplit the volume, the ShadowImage pair was in the process of
resynchronization. Therefore, the command ends
abnormally.
977b paircreate, When Snapshot P-VOL and ShadowImage S-VOL share the
pairsplit volume, the status of the ShadowImage pair is other than
PSUS. Therefore, the command ends abnormally.
977c pairresync - When Snapshot P-VOL and ShadowImage P-VOL share the
restore volume, the status of the ShadowImage pair is other than
PSUS or PSUE. Therefore, the Snapshot pair cannot be
restored.
977d pairresync - When Snapshot P-VOL and ShadowImage S-VOL share the
restore volume, the status of the ShadowImage pair is other than
PSUS. Therefore, the Snapshot pair cannot be restored.
977e pairsplit Since the pool or the pool-VOL is blocked, the Snapshot
data cannot be stored.
9783 pairresync - The Snapshot pair cannot be restored for any of the
restore following reasons:
• The Snapshot data of the Snapshot pair for restoration
is being stored per consistency group.
• The P-VOL of the Snapshot pair for restoration is used
as the P-VOL of another Snapshot pair, and the
Snapshot data of the latter Snapshot pair is being
stored per consistency group.
9786 paircreate, Since quorum disks are specified as P-VOLs of Snapshot
pairsplit, pairs, the command ends abnormally.
pairresync,
pairresync -
restore
9787 paircreate, Since quorum disks are specified as S-VOLs of Snapshot
pairsplit, pairs, the command ends abnormally.
pairresync,
pairresync -
restore
978a paircreate Since one of the following cases occurred, the Snapshot
pair cannot be created by specifying the consistency
number.
• The specified consistency group number is in use for
ShadowImage.
• The number of pairs has already exceeded the
maximum number of pairs that can be created for one
consistency group.
• The pair that uses the same P-VOL exists already in
the specified consistency group.
978b paircreate The Snapshot pair cannot be created because the specified
consistency group number is out of the range of the
number that can be specified.
978c pairsplit The Snapshot data cannot be stored because the TrueCopy
asynchronous pair status is other than PSUS or PSUE when
Snapshot (P-VOL) and TrueCopy asynchronous (S-VOL)
share the volume.
978e paircreate The Snapshot pair for which the consistency group is
specified cannot be created because the P-VOL or S-VOL
of the ShadowImage pair is specified as the P-VOL of the
Snapshot pair.
9790 paircreate The Dynamic Provisioning virtual volume, which is
undergoing capacity expansion, is specified as the Copy on
Write Snapshot P-VOL. Therefore, the Snapshot pair
cannot be created.
9793 paircreate The Snapshot pair cannot be created because the Dynamic
Provisioning V-VOL that is discarding zero data is specified
as a P-VOL of the Snapshot pair.
9796 paircreate, Since a volume without path definition is specified as a P-
pairsplit, VOL of the Snapshot pair, the command ends abnormally.
pairresync,
pairresync -
restore
9797 paircreate, Since a volume without path definition is specified as a S-
pairsplit, VOL of the Snapshot pair, the command ends abnormally.
pairresync,
pairresync -
restore
97A1 paircreate If you have already made the maximum number of
Snapshot pairs, no newpairs can be created.
B912 paircreate, The Snapshot pair operation failed because the specified
pairsplit, S-VOL is wrong.
pairresync
B9A7 All commands The consistency group information can not be obtained
because Snapshot is not installed.
A
CCI command reference
This topic describes CCI commands corresponding to Actions in the Storage

Navigator GUI.
□ Action names and CCI commands list
CCI command reference A–1

Action names and CCI commands list
This table lists Actions in Storage Navigator and the corresponding CCI
commands.
Item Action name CCI command

Logical Device Create LDEVs raidcom add ldev
Delete LDEVs raidcom delete ldev
Edit LDEVs raidcom modify ldev
Pool Create Pools raidcom add snap_pool
Expand Pool raidcom add snap_pool
Delete Pools raidcom delete pool
Edit Pools raidcom modify pool
Restore Pools raidcom modify pool
A–2 CCI command reference

B
Snapshot GUI reference
This topic describes Copy-on-Write Snapshot windows and dialog boxes in

Storage Navigator.
Note: P-VOL and S-VOLs listed in Storage Navigator may end in special
symbols. An LDEV number that ends with a pound or gate symbol (#)
indicates an external volume (for example, 00:00:01#). An LDEV number
that ends with a letter “X” indicates that a virtual volume used by Dynamic
Provisioning (for example, 00:00:01X).
□ Pair Operation window
□ Display filter dialog box
□ Detail dialog box
□ Pairsplit-S dialog box
□ History window
□ Snapshot window
□ Top window when selecting Pool
□ Top window when selecting a pool volume group under Pool
□ Create Pools wizard
□ Expand Pool wizard
□ Edit Pools wizard
□ Delete Pool wizard
Snapshot GUI reference B–1

□ Restore Pools window
□ Complete SIMs window
□ Select Pool window
□ Select Pool Volumes window
□ Pool Property window
B–2 Snapshot GUI reference

Pair Operation window
This window lets you view Snapshot and ShadowImage pair and volume
information for the selected port or host group. Only the items related to
Snapshot pairs are discussed here. See the Hitachi ShadowImage® User
Guide for information about that product.
Use this window to perform the following tasks:

• Monitoring pair status on page 6-2
• Monitoring pair, volume details on page 6-4
• Monitoring S-VOL path information on page 6-5
• Monitoring number of pairs, license information on page 6-6
Item Description
Display Filter Opens the Display Filter dialog box where you can control which
volumes display in the Pair list. See Display filter dialog box on page
B-7 for more information.
Tree Shows port and host group. When you click one of these, associated
pairs show in the pair/volume list. If you select Subsystem, no pair or
volume displays in the list.
Pair/volume Shows volume and pair information. The list can be sorted by column
list in ascending or descending order. See Volume list on page B-4.

Item Description
Icons The following are the Snapshot icons and their meanings:
: storage system
: port
: host group
: LUN or SMPL volume
: Snapshot pair
For the ShadowImage icons, see the Hitachi ShadowImage® User
Guide.
Preview Shows the operation(s) you have specified but not yet applied to the
system. You can change or delete the operations when you right-click
the item in the Preview list.
Apply Applies the operations displayed in the Preview list to the storage
system. If the specified operations are applied successfully, the
Preview list will be cleared.
If an error occurs during an operation, the failed operation will remain
in the Preview list with an error icon ( ) displayed in front. Details

of the error (error code and message) are displayed on the error
dialog box. For details about the list of the error code of Snapshot, see
Hitachi Storage Navigator Messages.
Cancel Cancels all the operations set in the Preview list.
Volume list
The main list in the Pair Operation window displays volume and pair
information. Both Snapshot and ShadowImage information is shown. You
can filter the list to show only Snapshot volumes using the Display Filter
feature.
Item Description
P-VOL P-VOL information in AAA-BB-CCC(XX:YY:ZZ) format:
• AAA : Port ID (cluster and channel number)
• BB : Group number of host group
• CCC : LU number
• XX:YY:ZZ : LDKC number:CU number:LDEV number
A device ID ending in # (e.g., 00:00:3C #), indicates the LDEV is an
external volume. For details on an external volume, see the Hitachi
Universal Volume Manager User Guide.A device ID ending in X (e.g.,
00:00:3C X) indicates the LDEV is a Dynamic Provisioning virtual
volume. For details on a virtual volume, see the Provisioning Guide for
Open Systems.
MU “Mirror unit number” of the Snapshot pair, formed with the P-VOL. The
storage system assumes the same numbers of P-VOLs as S-VOLs. For
example, when a P-VOL is paired with three S-VOLs, though just one
P-VOL exists, the system assumes that there are three P-VOLs. These
“virtual” P-VOLs are mirror units, MUs. The MU numbers identify the
virtual P-VOLs seen only by the system.
If the pair is in SMPL status, dotted lines (---) display.
Status Pair status.

Item Description
S-VOL S-VOL information in AAA-BB-CCC(XX:YY:ZZ) format:
• CCC : LU number
Only one path is listed, which is the path connected to the first port in
the tree view.
volume. For details on a virtual volume, see the Provisioning Guide for
Open Systems.
CTG The pair’s consistency group number. When the consistency group is
not specified, dotted lines (---) display.
SvolMode Displays the status of the S-VOL. When data is not written in the S-
VOL, dotted lines (---) display. When the data is written in the S-VOL,
W displays.
Copy Pace Not for Snapshot, displays dotted lines (---).
Sync. Percentage of pair synchronization, if applicable. Changes according to
the pair status.
• SMPL: --- is displayed.
• COPY, PAIR, COPY(RS), COPY(RS-R), PSUS: The consistency rate
of the P-VOL and the S-VOL is displayed as a percent (%).
• PSUE, SMPL(PD): --- is displayed.
Emulation Emulation type of the volume.
Capacity (MB) Volume storage capacity in megabytes.
CLPR (S) S-VOL cache logical partition.
Right-click Commands you can perform. Displays the menus in the following table
command when you select and right click the Snapshot pair volumes in the
menu volume list. See the following table for command descriptions.
Previous Displays the previous page of the volume list when the total number
of the volumes in the storage system is more than 1,024. If the
number of the items in the volume list is less than 1,024, this button
is grayed out.
Next Displays the next page of the volume list when the total number of the
volumes in the storage system is more than 1,024. If the number of
the items in the volume list is less than 1,024, this button is grayed
out.
Message Displays when there is no volume or pair to be displayed. If you see
the message in the Volume List, click a different icon in the Tree on
the left area of the Pair Operation window.
Preview List
The Preview List shows the operations and changes you have made from the
Pair Operation window. You can review your changes, modify the operation
or your changes, and apply them to the storage system.
The Preview List displays below the Volume List.

To modify an operation or change, right-click the row and select Delete or
Modify. To see error messages, click Error.
Field Description
• CCC : LU number
MU The MU number of the ShadowImage pair formed with the P-VOL.
S-VOL S-VOL information in AAA-BB-CCC(XX:YY:ZZ) format:
• CCC : LU number
Copy Pace Indicates the speed that data is copied according to the pair status.
Error Code If you click Apply and then the operations in the Preview list fail,
an error code indicates the cause of the error.
Menu When you select and right click items in the Preview list, the menu
displays the following commands:
• Delete: Cancels the selected operation(s) in the Preview list.
• Error Detail: Displays the error message dialog box, which
displays the error code and message. For Snapshot error
codes, see Hitachi Storage Navigator Messages.
The grayed out commands are for ShadowImage pairs. For details
about those commands, see the Hitachi ShadowImage® User
Guide.
Preview X(Y) X indicates the total number of operations displayed in the Preview
list.
Y indicates the type of operation.
Data in the status bar below the Preview List indicate the number of
changes, the type of change (the operation), and any command options.
Command menu
When you right-click a row or other item, a menu displays the following
commands you can select.
Command Function
Detail Opens the Detail dialog box, which displays detailed information for the
selected volume or pair.
Pairsplit-S Opens the Pairsplit-S dialog box, in which you delete Snapshot pairs.
S-VOL Path Opens the S-VOL Path dialog box, in which you view informaton about
the S-VOL path.
Information Opens the Information dialog box, which displays the number of pairs
or reserved volumes.

Command Function
Grayed-out Reserved for ShadowImage.
commands
Paircreate, Though the Paircreate and Pairsplit dialog boxes open, they are
Pairsplit reserved for ShadowImage. Snapshot pairs cannot be created or split
with these dialog boxes, but are performed using CCI.
Display filter dialog box

This dialog box lets you filter pair information on the Pair Operations
window.
Item Description
CLPR Displays volumes for the selected cache logical partition (CLPR). If
you select All, the volumes in all the CLPRs are displayed.
Volume Type Displays internal or external volumes.
Attribute Displays volumes according to the check boxes selected:
• Reserved: ShadowImage only.
• Pair: Displays pair volumes.
• Non-Pair: Displays volumes in SMPL status.
• Cascade (L1 / L2 radio buttons): ShadowImage only.
Pair Status box Displays volumes according to the check boxes selected:
• ShadowImage: Displays ShadowImage pairs.
• C.O.W. Snapshot: Displays Snapshot pairs.
ShadowImage Displays ShadowImage volumes and statuses.
C.O.W. Snapshot Displays Snapshot volumes and statuses.

Item Description
OK Applies the settings and closes the Display Filter dialog box.
Cancel Resets the settings and closes the Display Filter dialog box.
Detail dialog box

This dialog box lets you view detailed information regarding pairs and
volume pairs.
Item Description
P-VOL P-VOL LDKC number, CU number, and LDEV number.
Emulation P-VOL emulation type.
Capacity (MB) P-VOL capacity in megabytes (MB).
Capacity (blocks) P-VOL capacity in blocks.
Pool ID Pool ID of the pool in which the P-VOL is registered.
Amount of pool use Amount of the pool capacity used by the P-VOL.
by P-VOL (GB)
Pool usage rate by Pool usage rate of the P-VOL.
P-VOL

Item Description
Snapshot Pair • MU: Snapshot ID.
Detail list • S-VOL: LDKC number, CU number, and LDEV number.
• Status: Pair’s status.
• Date: Time when the Snapshot data was stored in the pool.
• Pool used (GB): Capacity of the pool used by the S-VOL.
• Sync.: Consistency rate of data of the P-VOL and the S-VOL.
• CLPR (S): S-VOL’s cache logical partition (CLPR).
• CTG: Pair’s consistency group number.
When the consistency group is not specified, dotted lines (--
-) display.
Refresh the window If you select the check box, the information displayed in the
after this dialog ShadowImage Pair Operation window is updated after the Detail
box is closed. check dialog box closes. If you do not select the check box, the
box information stays the same when the dialog box is closed.
Refresh Updates the information in the Detail dialog box.
Close Closes the Detail dialog box.
Pairsplit-S dialog box

This dialog box lets you delete multiple Snapshot pairs.
See the following topics for complete instructions:

• Deleting multiple pairs related to a port or host group on page 5-5
• Deleting multiple pairs related to a pool on page 5-6

Item Description
• CCC : LU number
A device ID ending in # (e.g., 00:00:3C #), indicates the LDEV
is an external volume. For details on an external volume, see the
Hitachi Universal Volume Manager User Guide.A device ID
ending in X (e.g., 00:00:3C X) indicates the LDEV is a Dynamic
Provisioning virtual volume. For details on a virtual volume, see
the Provisioning Guide for Open Systems.
MU Snapshot ID.
Status Status of the Snapshot pair.
S-VOL Information about S-VOL is displayed in AAA-BB-CCC(XX:YY:ZZ)
format:
• CCC : LU number
An LDEV number that ends with a pound or gate (#) mark
indicates that the LDEV is an external volume (e.g., 00:00:01#).
An LDEV number that ends with a letter X indicates that the
LDEV is a virtual volume used by Dynamic Provisioning (e.g.,
00:00:00X). For details about external volumes, see the Hitachi
Universal Volume Manager User Guide. For information about
Dynamic Provisioning, see the Provisioning Guide for Open
Systems.
Emulation Emulation type
Capacity (MB) Snapshot pair storage capacity.
OK Closes the Pairsplit-S dialog box and displays the list of the Snapshot
pairs in the Preview list.
Cancel Cancels the operation and closes the Pairsplit-S dialog box.
History window
This window lets you view the history of operations and associated data.
• The upper pane shows ShadowImage history.
• The lower pane shows Snapshot history.
For details about ShadowImage history, see the Hitachi ShadowImage®
User Guide.

Item Description
Previous Displays the previous page of the operation history list when the total
number of the operation history is more than 16,384. If the number
of the operation history is less than 16,384, this button is grayed out.
Next Displays the next page of the operation history list when the total
number of the operation history is more than 16,384. If the number
of the operation history is less than 16,384, this button is grayed out.
Date Displays date and time of the operation in the YYYY / MM / DD
hh:mm:ss format.
• YYYY : year
• MM : month
• DD : day
• hh : hour
• mm : minute
• ss : second
P-VOL The operation’s P-VOL, identified by LDKC:CU:LDEV.
volume. For details on a virtual volume, see the Provisioning Guide
for Open Systems.
S-VOL The operation’s S-VOL (V-VOL), identified by LDKC:CU:LDEV.
A device ID ending in V (e.g., 00:00:01 V) indicates the LDEV is a
virtual volume.
MU Snapshot ID
Pool ID ID of the related data pool.

Item Description
Code Snapshot reference code, which indicates the kind of operation that
was performed. See Reference codes on page B-12.
Message Describes the operation. Related to the reference code.
Reference codes
In the History window, the reference code and message columns provide
information about the operation, which are described here.
Code Message Description

0x2001 PAIR The pair was created.
0x2011 PSUS The pair was split.
0x2021 SMPL The pair was deleted.
0x2030 COPY(RS-R) START Pair restoration started.
0x2031 COPY(RS-R) END Pair restoration ended normally.
0x2032 COPY(RS-R) ENDED Pair restoration ended abnormally.
ABNORMAL
0x2051 COPY(RS) Snapshot data was deleted.
0x2070 PSUE(ABNORMAL END) A failure occurred and the status of the pair
changed to PSUE.
0x2040 INITIALIZE START Initialization started.
0x2041 INITIALIZE END Initialization ended normally.
0x2042 INITIALIZE ENDED Initialization ended abnormally.
ABNORMAL
Snapshot window
This window lets you to view Snapshot pool information.

Item Description
Tree The pools in the storage system display with the following icons:
• : storage system
• Pool:X : pool in normal status (X indicates pool ID)
• Pool:X : pool whose usage rate exceeds the threshold (X

indicates pool ID)
• Pool:X : blocked pool (X indicates pool ID)

Item Description
Pool/volume The content of the main list is either data pools or pair volumes. This
list depends on whether Subsystem or a Pool is selected in the tree.
If Subsystem is selected, all pools in the storage system display in
the pool/volume list with the following fields:
• Pool ID: Pool ID.
• Capacity (GB): Storage capacity of the pool.
• Used Capacity (GB): Capacity of the pool that is used by the
Snapshot pairs.
• Usage rate: Usage rate of the pool.
• Pool-VOL(s): Total number of pool-VOLs in the pool.
If a Pool is selected, the Snapshot pairs that use the pool display in
the pool/volume list, with the following fields:
• P-VOL: Port ID, group number of the host group, and LUN (LDKC
number, CU number, and LDEV number of the volume) of the P-
VOL.
For P-VOL LUs with more than one path, only one path is listed.
The path is connected to the first port within the ports configured
to a path that are shown in the tree view of the Pair Operation
Window.
• MU: Snapshot ID.
• Status: Status of the Snapshot pair.
• S-VOL: Port ID, group number of the host group, and LUN (LDKC
number, CU number, and LDEV number of the volume) of the S-
VOL.
For S-VOL LUs with more than one path, only one path is listed.
The path is connected to the first port within the ports configured
to a path that are shown in the tree view of the Pair Operation
Window. When the volume is unmounted, dotted lines (---)
display.
• Pool used (GB): Capacity of the pool that is used by the S-VOL.
• Sync.: Consistency rate of the data of the P-VOL and the S-VOL.
• CTG: Consistency group number of the Snapshot pair.
When the consistency group is not specified, dotted lines (---)
display.
Pool X is the capacity in use of pool association information.
Association Y is the maximum possible capacity of pool association information.
Inf.: X GB / Y The maximum possible capacity of pool association information is
GB calculated, based on the assumption that the remaining space of the
V-VOL management area is used as pool association information. If
the remaining space of the V-VOL management area is used for pool
management blocks, the maximum possible capacity of pool
association information is decreased due to decrease in the remaining
space of the V-VOL management area.

Item Description
Pool Mng. X indicates the capacity in use of the pool management blocks.
Block: X GB / Y Y indicates the maximum possible capacity of the pool management
GB blocks.
The maximum possible capacity of pool management blocks is
calculated, based on the assumption that the remaining space of the
V-VOL management area is used as pool management blocks. If the
remaining space of the V-VOL management area is used for pool
association information, the maximum possible capacity of pool
management blocks is decreased due to decrease in the remaining
space of the V-VOL management area.
Pool association information and a pool management block are the
elements of V-VOL management area. You need to know the capacity
of these two elements to calculate the number of Snapshot pairs you
can create.
Caution: The value displayed at the Total Capacity of the Pool
Information box and the value displayed at the Pool Mng. Capacity
: used are approximately equal, but there may be some difference.
Also note that even if the value displayed at the Total Capacity of the
Pool Information box is updated when the pool-VOLs are added to
or deleted from the pool, the value displayed at the Pool Mng.
Capacity : used will not be updated until you click Apply.
Command When you right-click a pair in the pool/volume list, a menu with the
menu Pairsplit-S command is displayed. If selected, the Pairsplit-S dialog
box opens.
Preview Displays the settings you have defined. They are not applied to the
system until Apply is clicked.
• P-VOL: Port ID, group number of the host group, and LUN of the
P-VOL.
• MU: Snapshot ID.
• S-VOL: Port ID, group number of the host group, and LUN of the
S-VOL.
• Error Code: Code for an error. If there is no error, dotted lines (--
-) display.
• Preview X(Y): Total number of operations displayed in the Preview
list(X) and type of operation(Y).
Preview list When you right-click a row in the Preview list, a menu with the
command following commands displays:
menu • Delete: Cancels the selected operation and deletes the operation
from the Preview list in the C.O.W. Snapshot window.
• Error Detail: Displays the error message dialog box, which
displays the error code and message. For the Snapshot error
codes, see the Hitachi Storage Navigator Messages.
Apply Applies the operations displayed in the Preview list to the storage
system. The Preview list is cleared when the operations complete. If
an error occurs, the failed operation remains in the Preview list.
Details of the error (error code and message) are displayed on the
error dialog box. For details about the list of the error code of
Snapshot, see the Hitachi Storage Navigator Messages.
Cancel Cancels all operations in the Preview list.

Top window when selecting Pool

Summary
Item Description
DP Shows capacities for Dynamic Provisioning pools:
• Pool Capacity (Used/Total): Pool capacity (used/total)
of Dynamic Provisioning.
• Remaining Configurable Pool Capacity: Remaining
configurable pool capacity of Dynamic Provisioning.
• HDP Licensed Capacity: License capacity of Dynamic
Provisioning.
• V-VOL Capacity (Total/Remaining) Configurable: V-
VOL capacity (total/remaining configurable) of
Dynamic Provisioning.
Caution: The value in the Total of Capacity in the Pools tab
page is almost the same as the value in Pool Capacity
(Used) of Summary, but there might be some difference.
Even if addition or deletion of pool-VOLs updates the value
in the Total of Capacity for each pool in the Pools tab page,
the value in Pool Capacity (Used) of Summary is not
updated until you click Apply.
COW snapshot Shows capacities for Copy-on-Write Snapshot pools:
• Pool Capacity (Used/Total): Pool capacity (used/total)
of Copy-on-Write Snapshot.
• Remaining Configurable Pool Capacity: Remaining
configurable pool capacity of Copy-on-Write Snapshot.
• SI/COW Snapshot Licensed Capacity: License capacity
of Copy-on-Write Snapshot.
Number of Pools Number of pools in the system.
Pool tab
Item Description
Pool Name (ID) Shows the pool name and ID. Clicking the pool name takes
you to the pool information window in the lower hierarchy.
Status Shows the following information about pool status:
Normal: The pool is in a normal status.
: The pool-VOL in the pool is blocked.
Exceeded Threshold: The used capacity of the pool

exceeds the pool threshold.
Shrinking: Reducing the pool-VOL.
Blocked: The pool is full, or an error occurred in the

pool, therefore the pool is blocked. If the pool is in both
Warning and Blocked status, only Blocked is displayed.
Number of Pool VOLs Shows the number of pool-VOLs.

Item Description
Capacity Shows the following information about pool capacity:
• Total: Total capacity of pool.
Using Option button, you can select unit of capacity.
- One block means 512 bytes and one page means 42
megabytes in pool capacity of Dynamic Provisioning or
Dynamic Tiering.
- One block means 512 bytes and one page means 256
kilobytes in pool capacity of Snapshot.
• Used: Used pool capacity.
• Used (%): Pool usage rates to pool capacity.
• User-Defined Threshold: Threshold you configure.
Subscription Shows the following information about subscription of the
pool:
• Current: Current subscription.
• Limit: Subscription limit.
For a COW snapshot pool, a hyphen (-) is displayed for
Current or Limit.
Pool Type Shows the pool type.
• For Dynamic Provisioning or Dynamic Tiering:
DP is displayed.
• For COW Snapshot:
COW Snapshot is displayed.
Tier Management Shows whether Dynamic Tiering is enabled or disabled. If
it is enabled Auto or Manual is displayed. If it is disabled,
a hyphen (-) is displayed.
For a COW Snapshot pool, a hyphen (-) is displayed.
CLPR Shows CLPR set for the pool volumes. For DP pools, a
hyphen (-) is displayed.
Shrinkable Shows whether the pool-VOL can be deleted. For a COW
Snapshot pool, a hyphen(-) is displayed because it is not
shrinkable.
Create Pools Displays the Create Pools window.
Create LDEVs Displays the Create LDEVs window.
Expand Pool Displays the Expand Pool window.
Delete Pools* Displays the Delete Pools window.
Restore Pools* Displays the Restore Pools window.
Edit Pools* Displays the Edit Pools window.
Complete SIMs* Displays the Complete SIMs window.
View Tier Properties* Displays the View Tier Properties window. This window can
be viewed only for the pools for which Dynamic Tiering is
enabled.
Export* Displays the window for outputting table information.
* Appears when you click More Actions.

Top window when selecting a pool volume group under
Pool

Summary
Item Description
Normal: The pool is in a normal status.
Warning: The pool-VOL in the pool is blocked.
Exceeded Threshold: The used capacity of the pool

exceeds the pool threshold.
Blocked: The pool is full, or an error occurred in the

pool, therefore the pool is blocked. If the pool is in both
Warning and Blocked status, only Blocked is displayed.
Pool Name (ID) Shows pool name and ID.
Top Pool VOL (Name) Shows the LDEV ID and LDEV name of the first pool
volume.
DP is displayed.
RAID Level Shows the RAID level.
If multiple RAID levels exist in a pool, this field indicates
that RAID levels are mixed.
Drive Type/RPM Shows the data drive type and RPM of the pool.
If multiple Drive Type/RPMs exist in a pool, this field
indicates that Drive Type/RPMs are mixed.
Pool Capacity (Used/Total) Shows the used and total pool capacity.
V-VOL Capacity (Used/ Shows the used and total V-VOL capacity. For a COW
Total) Snapshot pool, a hyphen (-) is displayed along with the
used and total V-VOL capacity.
Subscription (Current/Max) Shows the subscription (rate of total V-VOL capacity
associated with a pool to the pool capacity/Subscription
that is set).
For a COW Snapshot pool, a hyphen (-) is displayed for
Current or Max.
User-Defined Threshold / Shows the threshold you configure.
System Threshold
Cache Mode Shows the cache mode.
Tier Management Shows whether Dynamic Tiering is enabled or disabled. If
it is enabled, Auto or Manual is displayed. If it is disabled,
a hyphen (-) is displayed.
Cycle Time Shows the cycle of performance monitoring and tier
relocation. If Dynamic Tiering is disabled, a hyphen (-) is
displayed.
Monitoring Period Shows the time of starting and ending of performance
monitoring. If Dynamic Tiering is disabled, a hyphen (-)
is displayed.

Item Description
Number of V-VOLs Shows the number of V-VOLs associated with the pool,
and the muximum number of V-VOLs that can be
associated with the pool.
Number of Pool VOLs Shows the number of pool VOLs set for the pool, and the
maximum number of pool VOLs that can be set for the
pool.
Pool Volumes tab
Item Description
LDEV ID Shows the LDEV ID. Clicking LDEV ID opens the LDEV
Properties window.
LDEV Name Shows the LDEV name.
Normal: Normal status.
Blocked: Pool-VOL is blocked.

Parity Group ID Shows the parity group ID.
Usable Capacity Shows available capacity of page boundaries in a pool-VOL
by the specified unit. For the top pool-VOL of Dynamic
Provisioning or Dynamic Tiering, the displayed capacity
does not include the capacity of the management area.
Emulation Type Shows the emulation type.
Drive Type/RPM Shows the data drive type and RPM.
Provisioning Type Shows the provisioning type.
CLPR Shows CLPR.
Shrinkable Shows whether the pool-VOL can be deleted. For a COW
Snapshot pool, a hyphen (-) is displayed.
Expand Pool Displays the Expand Pool window.
Shrink Pool Displays the Shrink Pool window.
Stop Shrinking Pool Displays the Stop Shrinking Pool window.
Export Displays the window for outputting table information

Create Pools wizard
Create Pools window

Setting fields
The items labeled with an asterisk are required fields.
Item Description
*Pool Type Select the pool type.
Select Dynamic Provisioning.
Select COW Snapshot.
*Multi-Tier Pool If Dynamic Provisioning is selected for the pool type, you
can enable or disable Multi-Tier Pool. If it is set to enabled,
Dynamic Tiering is enabled.
*Drive Type/RPM Select the data drive type and RPM of the pool-VOL.
“Any” appears in the case of HDT.
*RAID Level Select the RAID level of the pool-VOL.
“-” appears when External Storage is selected in the Drive
Type/RPM list. “Any” appears in the case of HDT.
Select Pool VOLs Opens the Select Pool Volumes window. Selecting a pool-
VOL is mandatory.
Total Selected Pool Shows the total number of the selected pool-VOLs.
Volumes

Item Description
Total Selected Capacity Shows the total capacity of the selected pool-VOLs.
*Pool Name Set the pool name:
• Prefix: Enter the alphanumeric characters, which are
fixed characters of the head of the pool name. The
characters are case-sensitive.
• Initial Number: Enter the initial number following the
prefix name, which can be up to nine digits.
• You can enter up to 32 characters, including the initial
number.
Initial Pool ID The smallest available number is entered in the text box
as a default. However, if no available pool ID exists, no
number appears in the text box, .
No number, however, appears in the text box, if no
available pool ID exists.
Subscription Limit Set the subscription limit in the range from 0 to 65534
(%).
If this is blank, the subscription limit is set to unlimited.
When creating a COW Snapshot pool, this setting is not
necessary.
User-Defined Threshold • For Dynamic Provisioning and Dynamic Tiering:
Select the threshold from 5 to 95% in 5% increments.
The initial value is 70%.
Select the threshold from 20 to 95% in 5%
increments. The initial value is 80%.
Tier Management Select Auto or Manual of performance monitoring and tier
relocation:
• Cycle Time
Select the cycle of performance monitoring and tier
relocation.
• Monitoring Period
Enter the time zone of performance monitoring when
24 Hours is selected in the Cycle Time list.
When 24 Hours is selected in the Cycle Time list, specify
the time zone from 00:00 to 23:59 (default value), in
which performance monitoring is to be performed. Set the
end time one hour or more later than the start time.
This function can be set only when Multi-Tier Poolis
enabled.
Add button
When you click Add, the configured information is added to the right
Selected Pools table.

Selected pools table
The following table lists the details of items.
Item Description
Pool Name (ID) Shows the nickname and ID of the pool.
RAID Level Shows the RAID level of the pool.
Capacity Shows the pool capacity.
DP is displayed.
If multiple types of drives exist in a pool, this field
indicates that the drive types are mixed.
Subscription Limit (%) Shows the subscription limit of the pool.
For COW Snapshot, a hyphen (-) is displayed.
User-Defined Threshold Shows the threshold you configure.
(%)

Item Description
Multi-Tier Pool Shows the Dynamic Tiering information:
• Tier Management
Shows Auto or Manual of performance monitoring and
tier relocation.
• Cycle Time
Shows the cycle of performance monitoring and tier
relocation.
Shows the time zone of performance monitoring when
If Multi-Tier Pool is not set to enable, a hyphen (-) is
displayed.
Detail Shows the Pool Properties window when a line is selected,
and shows the error window when a line is not selected or
multiple lines are selected.
Remove Deletes the pool selected in the Selected Pools window.
Shows the error window when a line is not selected.
Confirm window

Create Pools table
Item Description
DP is displayed.
Subscription Limit (%) Shows the subscription limit of the pool.
• Tier Management
tier relocation.
• Cycle Time
relocation.
If Multi-Tier Pool is not set to enable, a hyphen (-) is
displayed.
Total Shows the total number of pools.

Expand Pool wizard
Expand Pool window
Pool Volume Selection:
Item Description
Drive Type/RPM Unavailable.
RAID Level Unavailable.
Select Pool VOLs Shows the Select Pool Volumes window.
Total Selected Pool Shows the total number of selected pool-VOLs.
Volumes
Total Selected Capacity Shows the total capacity of the selected pool-VOLs.

Confirm window
Selected table
Item Description
Selected pool volumes table
Item Description
LDEV ID Shows the LDEV ID.
Capacity Shows the pool-VOL capacity.
Total Shows the total number of pool-VOLs.

Edit Pools wizard
Edit Pools window
Setting fields
Item Description
Multi-Tier Pool Set to Enable or Disable HDT by selecting either of the
checkboxes. However, if more than one tier exists, you
cannot change Enable to Disable. You must decrease the
pool capacity to unite tiers before changing to Disable.
A pool that is comprised of external volumes or volumes
with RAID level 1 cannot be changed from Disable to
Enable.
In COW Snapshot, you cannot change the setting of this
function.

Item Description
Tier Management Set to execute performance monitoring and tier relocation
automatically or manually:
• Cycle Time
When selecting Auto from the Tier Management field,
select the cycle of performance monitoring and tier
relocation from the Cycle Time list.
When selecting 24 Hours from the Cycle Time list,
specify the starting and ending of performance
monitoring in 00:00 to 23:59 (default value).Set the
end time one hour or more later than the start time.
If the checkbox is not selected, the setting is not applied.
Subscription Limit Check subscription limit to enter the subscription limit
(%):
• If this field is blank, the subscription limit is set to be
unlimited.
• The following shows the available range:
(Total V-VOL capacity allocated to the pool/pool
capacity) ×100(%) +1 to 65534(%)
• You cannot configure the subscription limit if both of
the following conditions are satisfied:
- The subscription is unlimitedly set.
- (Total V-VOL capacity allocated to the pool/pool
capacity) ×100) exceeds 65534.
• If not checked, the subscription limit is enabled.
In COW Snapshot, you cannot change the setting of this
function.
Pool Name Check Pool Name to enter the pool name:
If the checkbox is not selected, the setting is not applied.
• Prefix: Enter the alphanumeric characters, which are
fixed characters of the head of the pool name. The
characters are case-sensitive.
• Initial Number: Enter the initial number for the pool
name.
• Prefix and Initial Number can be up to the 32
characters in total. Initial Number can be up to 9-digit.
*: When one pool is selected, the pool name appears in the
Prefix text box as the default value. When multiple pools
are selected, the numbers ranging from the specified
Initial Number to the the maximun number of the same
digits are automatically set to the pool name.
Example: If Initial Number is set to 1, a number from 1 to
9 is automatically added to each pool name. If Initial
Number is set to 08, a number from 08 to 99 is added to
each pool name. If Initial Number is set to 098, a number
from 098 to 999 is added to each pool name.
User-Defined Threshold For Dynamic Provisioning and Dynamic Tiering:
• Check User-Defined Threshold to select the threshold
between 20% and 95% in 5% increments.
For COW Snapshot:
• Check User-Defined Threshold to select the threshold
between 20% and 95% in 5% increments.

Confirm window
Selected Pools table
Item Description
RAID Level If multiple RAID levels exist in a pool, this field indicates
Pool Type Shows the pool type:
DP is displayed.
Subscription Limit (%) Shows the subscription limit.
(%)

Item Description
• Type
tier relocation.
• Cycle Time
relocation.
If Multi-Tier Pool is not enabled, a hyphen (-) is displayed.
Delete Pool wizard

Delete Pool window
Item Description

Item Description
DP is displayed.
Drive Type/RPM Shows the data drive type and RPM of the pool.
(%)
Confirm window

Item Description
In the case of LUSE, shows the LUSE capacity.
DP is displayed.
(%)
Restore Pools window

Item Description
If the pool is blocked and the pool-VOLs that belong to the
pool cannot be identified, 0 is displayed.
DP is displayed.
(%)
If the pool is blocked and the pool-VOLs that belong to the
pool cannot be identified, 0 is displayed.
Complete SIMs window

Setting fields
Item Description
Task Enter the task name.
You can enter up to 32 alphanumeric characters and
symbols in all, except for / : , ; * ? ” < > |. The characters
are case-sensitive.
“date-window name” is entered as a default.
Select Pool window
Available Pools table
Item Description
Capacity Used: Shows the used pool capacity.
Total: Shows the total pool capacity.
(%)
Tier Management Shows Auto or Manual according to the Tier Management
setting.
For pools other than Dynamic Tiering, a hyphen (-) is
displayed.

Select Pool Volumes window

Available Pool Volumes table
Item Description
Parity Group ID Shows the Array Group ID.
Provisioning Type Shows the LDEV type.
CLPR Shows CLPR.
Cache Mode Shows whether the cache mode is enabled or disabled.
For a volume other than external volumes, a hyphen (-) is
displayed.

Add button
If you select a line in the Available Pool Volumes table and then click this
button, the selected pool-VOL is added to the Selected pool volumes table.
Note: The pool-VOL that is first added to the Selected pool volumes table
will be the top pool-VOL.
Remove button
If you select a line in the Selected pool volumes table and then click this
button, the selected LDEV is removed from the Selected pool volumes table.
Note: After you remove the pool-VOL that is set as the top pool-VOL, the
pool-VOL that is now displayed at the top of the Selected pool volumes table
will be the new top pool-VOL.
The top pool-VOL is not set when the pool is expanded.
Up to 1024 volumes can be added, including volumes that already exist in
the pool.
When you add a volume to a pool for which Multi-Tier Pool is enabled,
consider the following:
• Drive Type/RPM for the volume to be added must be up to 3.
• When adding volumes to a pool, one RAID Level must be set for one
Drive Type/RPM.
A volume whose Drive Type/RPM is SAS/15k and RAID level is
5(3D+1P), and a volume whose Drive Type/RPM is SAS/15k and RAID
level is 5(7D+1P), cannot be added to the same pool.
• The top pool-VOL cannot be removed from the pool, so the tier to which
the top pool-VOL belong cannot be removed.

Selected pool volumes table
Item Description
RAID Level Show the RAID level.
Provisioning Type Shows the LDEV type.
CLPR Shows CLPR.
Cache Mode Shows whether the cache mode is enabled or disabled.
For a volume other than external volumes, a hyphen (-) is
displayed.
Location The pool-VOL that is indicated as Top will be the top pool-
VOL.

Item Description
Change Top Pool Vol If you select a line from the Selected pool volumes table
and then click this button, the selected pool-VOL will be
changed to the top pool-VOL.
When the pool is expanded, this button is disabled and you
cannot specify the top pool-VOL.
Pool Property window
Pool Properties table
Item Description
Pool Name (ID) Shows the pool name.
DP is displayed.
Capacity Shows the pool capacity by the specified unit.

Item Description
Subscription Limit Shows the subscription limit.
Top Pool VOL (Name) Shows the LDEV ID and LDEV Name of the top pool-VOL.
Pool Volumes table

The following table lists the details of items.
Item Description
Capacity Shows the pool volume capacity by the specified unit.
Provisioning Type Shows the provisioning type of the pool volumes.
CLPR Shows CLPR.

Glossary
This glossary defines the special terms used in this document. Click the
letter links below to navigate.
#
2DC
two-data-center. Refers to the local and remote sites, or data centers, in
which TrueCopy (TC) and Universal Replicator (UR) combine to form a
remote replication configuration.
In a 2DC configuration, data is copied from a TC primary volume at the
local site to the UR master journal volume at an intermediate site, then
replicated to the UR secondary volume at the remote site. Since this
configuration side-steps the TC secondary volume at the intermediate
site, the intermediate site is not considered a data center.
3DC
three-data-center. Refers to the local, intermediate, and remote sites, or
data centers, in which TrueCopy and Universal Replicator combine to
form a remote replication configuration.
In a 3DC configuration, data is copied from a local site to an
intermediate site and then to a remote site (3DC cascade configuration),
or from a local site to two separate remote sites (3DC multi-target
configuration).
A
alternate path
A secondary path (port, target ID, LUN) to a logical volume, in addition
to the primary path, that is used as a backup in case the primary path
fails.
# A B C D E F G H II
# J K L M N O P Q R S T U V W X Y Z
Glossary–1
array
Another name for a RAID storage system.
array group
See RAID group.
async
asynchronous
at-time split
Operation that allows multiple pairsplit operations to be performed at a
pre-determined time.
audit log
Files that store a history of the operations performed from Storage
Navigator and the service processor (SVP), commands that the storage
system received from hosts, and data encryption operations.
B
base emulation type
Emulation type that is set when drives are installed. Determines the
device emulation types that can be set in the RAID group.
BC
business continuity
BCM
Business Continuity Manager
blade
A computer module, generally a single circuit board, used mostly in
servers.
BLK, blk
block
bmp
bitmap
C
C/T
See consistency time (C/T).
#
# A B C D E F G H II J K L M N O P Q R S T U V W X Y Z
Glossary–2
ca
cache
cache logical partition (CLPR)

Consists of virtual cache memory that is set up to be allocated to
different hosts in contention for cache memory.
capacity
The amount of data storage space available on a physical storage device,
usually measured in bytes (MB, GB, TB, etc.).
cascade configuration
In a 3DC cascade configuration for remote replication, data is copied
from a local site to an intermediate site and then to a remote site using
TrueCopy and Universal Replicator. See also 3DC.
In a ShadowImage cascade configuration, two layers of secondary
volumes can be defined for a single primary volume. Pairs created in the
first and second layer are called cascaded pairs.
cascade function
A ShadowImage function for open systems that allows a primary volume
(P-VOL) to have up to nine secondary volumes (S-VOLs) in a layered
configuration. The first cascade layer (L1) is the original ShadowImage
pair with one P-VOL and up to three S-VOLs. The second cascade layer
(L2) contains ShadowImage pairs in which the L1 S-VOLs are
functioning as the P-VOLs of layer-2 ShadowImage pairs that can have
up to two S-VOLs for each P-VOL.
See also root volume, node volume, leaf volume, level-1 pair, and level-
2 pair.
cascaded pair
A ShadowImage pair in a cascade configuration. See cascade
configuration.
shared volume
A volume that is being used by more than one replication function. For
example, a volume that is the primary volume of a TrueCopy pair and
the primary volume of a ShadowImage pair is a shared volume.
CCI
Command Control Interface
CFL
Configuration File Loader. A Storage Navigator function for validating
and running scripted spreadsheets.
Glossary–3
CFW
cache fast write
CG
See consistency group (CTG).
CTG
CH
channel
channel path
The communication path between a channel and a control unit. A
channel path consists of the physical channel path and the logical path.
CHAP
challenge handshake authentication protocol
CL
cluster
CLI
command line interface
CLPR
cache logical partition
cluster
Multiple-storage servers working together to respond to multiple read
and write requests.
command device
A dedicated logical volume used only by Command Control Interface and
Business Continuity Manager to interface with the storage system. Can
be shared by several hosts.
configuration definition file

Defines the configuration, parameters, and options of Command Control
Interface (CCI) operations. A text file that defines the connected hosts
and the volumes and groups known to the Command Control Interface
instance.
#
Glossary–4
consistency group (CG, CTG)
A group of pairs on which copy operations are performed
simultaneously; the pairs’ status changes at the same time. See also
extended consistency group (EXCTG).
consistency time (C/T)

Shows a time stamp to indicate how close the target volume is to the
source volume. C/T also shows the time stamp of a journal group and
extended consistency group.
controller
The component in a storage system that manages all storage functions.
It is analogous to a computer and contains a processors, I/O devices,
RAM, power supplies, cooling fans, and other sub-components as
needed to support the operation of the storage system.
copy-on-write
Point-in-time snapshot copy of any data volume within a storage
system. Copy-on-write snapshots only store changed data blocks,
therefore the amount of storage capacity required for each copy is
substantially smaller than the source volume.
copy pair
A pair of volumes in which one volume contains original data and the
other volume contains the copy of the original. Copy operations can be
synchronous or asynchronous, and the volumes of the copy pair can be
located in the same storage system (local copy) or in different storage
systems (remote copy).
A copy pair can also be called a volume pair, or just pair.
COW
copy-on-write
COW Snapshot
Hitachi Copy-on-Write Snapshot
CTG
CTL
controller
CU
control unit
Glossary–5
currency of data
The synchronization of the volumes in a copy pair. When the data on the
secondary volume (S-VOL) is identical to the data on the primary
volume (P-VOL), the data on the S-VOL is current. When the data on the
S-VOL is not identical to the data on the P-VOL, the data on the S-VOL
is not current.
CYL, cyl
cylinder
cylinder bitmap
Indicates the differential data (updated by write I/Os) in a volume of a
split or suspended copy pair. The primary and secondary volumes each
have their own cylinder bitmap. When the pair is resynchronized, the
cylinder bitmaps are merged, and the differential data is copied to the
secondary volume.
D
DASD
direct-access storage device
data consistency
When the data on the secondary volume is identical to the data on the
primary volume.
data path
The physical paths used by primary storage systems to communicate
with secondary storage systems in a remote replication environment.
data pool
One or more logical volumes designated to temporarily store original
data. When a snapshot is taken of a primary volume, the data pool is
used if a data block in the primary volume is to be updated. The original
snapshot of the volume is maintained by storing the to-be-changed data
blocks in the data pool.
DB
database
DBMS
database management system
#
Glossary–6
delta resync
A disaster recovery solution in which TrueCopy and Universal Replicator
systems are configured to provide a quick recovery using only
differential data stored at an intermediate site.
device
A physical or logical unit with a specific function.
device emulation
Indicates the type of logical volume. Mainframe device emulation types
provide logical volumes of fixed size, called logical volume images
(LVIs), which contain EBCDIC data in CKD format. Typical mainframe
device emulation types include 3390-9 and 3390-M. Open-systems
device emulation types provide logical volumes of variable size, called
logical units (LUs), that contain ASCII data in FBA format. The typical
open-systems device emulation type is OPEN-V.
DEVN
device number
DFW
DASD fast write
DHCP
dynamic host configuration protocol
differential data
Changed data in the primary volume not yet reflected in the copy.
disaster recovery
A set of procedures to recover critical application data and processing
after a disaster or other failure.
disk array
Disk array, or just array, is another name for a RAID storage system.
disk controller (DKC)

The hardware component that manages front-end and back-end storage
operations. The term DKC is sometimes used to refer to the entire RAID
storage system.
DKC
disk controller. Can refer to the RAID storage system or the controller
components.
Glossary–7
DKCMAIN
disk controller main. Refers to the microcode for the RAID storage
system.
DKP
disk processor. Refers to the microprocessors on the back-end director
features of the Universal Storage Platform V.
DKU
disk unit. Refers to the cabinet (floor model) or rack-mounted hardware
component that contains data drives and no controller components.
DMP
Dynamic Multi Pathing
DRU
Hitachi Data Retention Utility
DP-VOL
Dynamic Provisioning-virtual volume. A virtual volume with no memory
space used by Dynamic Provisioning.
dynamic provisioning
An approach to managing storage. Instead of “reserving” a fixed amount
of storage, it removes capacity from the available pool when data is
actually written to disk. Also called thin provisioning.
E
EC
error code
emulation
The operation of the Hitachi RAID storage system to emulate the
characteristics of a different storage system. For device emulation the
mainframe host “sees” the logical devices on the RAID storage system
as 3390-x devices. For controller emulation the mainframe host “sees”
the control units (CUs) on the RAID storage system as 2105 or 2107
controllers.
RAID storage system system operates the same as the storage system
being emulated.
emulation group
A set of device emulation types that can be intermixed within a RAID
group and treated as a group.
#
Glossary–8
env.
environment
ERC
error reporting communications
ESCON
Enterprise System Connection
EXCTG
See extended consistency group (ECTG).
EXG
external volume group
ext.
external
extended consistency group (EXCTG)

A set of Universal Replicator software for Mainframe journal groups in
which data consistency is guaranteed. When performing copy operations
between multiple primary and secondary systems, the journal groups
must be registered in an EXCTG.
external application
A software module that is used by a storage system but runs on a
separate platform.
external port
A fibre-channel port that is configured to be connected to an external
storage system for Universal Volume Manager operations.
external volume
A logical volume whose data resides on drives that are physically located
outside the Hitachi storage system.
F
failback
The process of switching operations from the secondary path or host
back to the primary path or host, after the primary path or host has
recovered from failure. See also failover.
Glossary–9
failover
The process of switching operations from the primary path or host to a
secondary path or host when the primary path or host fails.
FBA
fixed-block architecture
FC
fibre channel; FlashCopy
FCA
fibre-channel adapter
FC-AL
fibre-channel arbitrated loop
FCIP
fibre-channel internet protocol
FCP
fibre-channel protocol
FCSP
fibre-channel security protocol
FIBARC
Fibre Connection Architecture
FICON
Fibre Connectivity
FIFO
first in, first out
free capacity
The amount of storage space (in bytes) that is available for use by the
host system(s).
FSW
fibre switch
FTP
file-transfer protocol
#
Glossary–10
FV
fixed-size volume
FWD
fast-wide differential
G
GID
group ID
GUI
graphical user interface
H
HA
high availability
HACMP
High Availability Cluster Multi-Processing
HAM
Hitachi High Availability Manager
HDLM
Hitachi Dynamic Link Manager
HDP
Hitachi Dynamic Provisioning
HDS
Hitachi Data Systems
HDT
Hitachi Dynamic Tiering
HDvM
Hitachi Device Manager
HGLAM
Hitachi Global Link Availability Manager
Glossary–11
H-LUN
host logical unit
HOMRCF
Hitachi Open Multi-RAID Coupling Feature. Another name for Hitachi
ShadowImage.
HORC
Hitachi Open Remote Copy. Another name for Hitachi TrueCopy.
HORCM
Hitachi Open Remote Copy Manager. Another name for Command
Control Interface.
host failover
The process of switching operations from one host to another host when
the primary host fails.
host group
A group of hosts of the same operating system platform.
host mode
Operational modes that provide enhanced compatibility with supported
host platforms. Used with fibre-channel ports on RAID storage systems.
host mode option

Additional options for fibre-channel ports on RAID storage systems.
Provide enhanced functionality for host software and middleware.
HRC
Hitachi Remote Copy. Another name for Hitachi TrueCopy for IBM z/OS.
HRpM
Hitachi Replication Manager
HSCS
Hitachi Storage Command Suite. This suite of products is now called the
Hitachi Command Suite.
HUR
Hitachi Universal Replicator
#
Glossary–12
HXRC
Hitachi Extended Remote Copy. Another name for Hitachi Compatible
Replication for IBM XRC.
I
iFCP
internet fibre-channel protocol
IML
initial microcode load; initial microprogram load
IMPL
initial microprogram load
initial copy
An initial copy operation is performed when a copy pair is created. Data
on the primary volume is copied to the secondary volume.
initiator port
A fibre-channel port configured to send remote I/Os to an RCU target
port on another storage system. See also RCU target port and target
port.
in-system replication
The original data volume and its copy are located in the same storage
system. ShadowImage in-system replication provides duplication of
logical volumes; Copy-on-Write Snapshot in-system replication provides
“snapshots” of logical volumes that are stored and managed as virtual
volumes (V-VOLs).
See also remote replication.
intermediate site (I-site)

A site that functions as both a TrueCopy secondary site and a Universal
Replicator primary site in a 3-data-center (3DC) cascading
configuration.
internal volume
A logical volume whose data resides on drives that are physically located
within the storage system. See also external volume.
IO, I/O
input/output
Glossary–13
IOPS
I/Os per second
IP
internet protocol
IPL
initial program load
J
JNL
journal
JNLG
journal group
journal group (JNLG)

In a Universal Replicator system, journal groups manage data
consistency between multiple primary volumes and secondary volumes.
See also consistency group (CTG).
journal volume
A volume that records and stores a log of all events that take place in
another volume. In the event of a system crash, the journal volume logs
are used to restore lost data and maintain data integrity.
In Universal Replicator, differential data is held in journal volumes on
until it is copied to the S-VOL.
JRE
Java Runtime Environment
L
L1 pair
See layer-1 (L1) pair.
L2 pair
See layer-2 (L2) pair.
LAN
local-area network
#
Glossary–14
layer-1 (L1) pair
In a ShadowImage cascade configuration, a layer-1 pair consists of a
primary volume and secondary volume in the first cascade layer. An L1
primary volume can be paired with up to three L1 secondary volumes.
See also cascade configuration.
layer-2 (L2) pair

In a ShadowImage cascade configuration, a layer-2 (L2) pair consists of
a primary volume and secondary volume in the second cascade layer. An
L2 primary volume can be paired with up to two L2 secondary volumes.
See also cascade configuration.
LBA
logical block address
LCP
local control port; link control processor
LCU
logical control unit
LDEV
logical device
LDKC
See logical disk controller (LDKC).
leaf volume
A level-2 secondary volume in a ShadowImage cascade configuration.
The primary volume of a layer-2 pair is called a node volume. See also
cascade configuration.
LED
light-emitting diode
license key
A specific set of characters that unlocks an application and allows it to
be used.
local copy
See in-system replication.
local site
See primary site.
Glossary–15
logical device (LDEV)
An individual logical data volume (on multiple drives in a RAID
configuration) in the storage system. An LDEV may or may not contain
any data and may or may not be defined to any hosts. Each LDEV has a
unique identifier or “address” within the storage system composed of the
logical disk controller (LDKC) number, control unit (CU) number, and
LDEV number. The LDEV IDs within a storage system do not change.An
LDEV formatted for use by mainframe hosts is called a logical volume
image (LVI). An LDEV formatted for use by open-system hosts is called
a logical unit (LU).
logical disk controller (LDKC)

A group of 255 control unit (CU) images in the RAID storage system that
is controlled by a virtual (logical) storage system within the single
physical storage system. For example, the Universal Storage Platform V
storage system supports two LDKCs, LDKC 00 and LDKC 01.
logical unit (LU)

A logical volume that is configured for use by open-systems hosts (for
example, OPEN-V).
logical unit (LU) path

The path between an open-systems host and a logical unit.
logical volume
See volume.
logical volume image (LVI)

A logical volume that is configured for use by mainframe hosts (for
example, 3390-9).
LU
logical unit
LUN
logical unit number
LUNM
Hitachi LUN Manager
LUSE
Hitachi LUN Expansion; Hitachi LU Size Expansion
LV
logical volume
#
Glossary–16
M
main control unit (MCU)
A storage system at a primary or main site that contains primary
volumes of TrueCopy for z/OS remote replication pairs. The MCU is
configured to send remote I/Os to one or more storage systems at the
secondary or remote site, called remote control units (RCUs), that
contain the secondary volumes of the remote replication pairs. See also
remote control unit (RCU).
main site
See primary site.
main volume (M-VOL)

A primary volume on the main storage system in a TrueCopy for z/OS
copy pair. The M-VOL contains the original data that is duplicated on the
remote volume (R-VOL). See also remote volume (R-VOL).
master journal (M-JNL)

Holds differential data on the primary Universal Replicator system until
it is copied to the restore journal (R-JNL) on the secondary system. See
also restore journal (R-JNL).
max.
maximum
MB
megabyte
Mb/sec, Mbps
megabits per second
MB/sec, MBps
megabytes per second
MCU
See main control unit (MCU).
MF, M/F
mainframe
MIH
missing interrupt handler
Glossary–17
mirror
In Universal Replicator, each pair relationship in and between journal
groups is called a “mirror”. Each pair is assigned a mirror ID when it is
created. The mirror ID identifies individual pair relationships between
journal groups.
M-JNL
main journal
modify mode
The mode of operation of Storage Navigator that allows changes to the
storage system configuration. See also view mode.
MP
microprocessor
MSCS
Microsoft Cluster Server
mto, MTO
mainframe-to-open
MU
mirror unit
multi-pathing
A performance and fault-tolerant technique that uses more than one
physical connection between the storage system and host system. Also
called multipath I/O.
M-VOL
main volume
N
node volume
A level-2 primary volume in a ShadowImage cascade configuration. The
secondary volume of a layer-2 pair is called a leaf volume. See also
NUM
number
#
Glossary–18
NVS
nonvolatile storage
O
OPEN-V
A logical unit (LU) of user-defined size that is formatted for use by open-
systems hosts.
OPEN-x
A logical unit (LU) of fixed size (for example, OPEN-3 or OPEN-9) that is
used primarily for sharing data between mainframe and open-systems
hosts using Hitachi Cross-OS File Exchange.
OS
operating system
OS/390
Operating System/390
P
pair
Two logical volumes in a replication relationship in which one volume
contains original data to be copied and the other volume contains the
copy of the original data. The copy operations can be synchronous or
asynchronous, and the pair volumes can be located in the same storage
system (in-system replication) or in different storage systems (remote
replication).
pair status
Indicates the condition of a copy pair. A pair must have a specific status
for specific operations. When an operation completes, the status of the
pair changes to the new status.
parity group
See RAID group.
path failover
The ability of a host to switch from using the primary path to a logical
volume to the secondary path to the volume when the primary path fails.
Path failover ensures continuous host access to the volume in the event
the primary path fails.
See also alternate path and failback.
Glossary–19
PG
parity group. See RAID group.
physical device
See device.
PiT
point-in-time
point-in-time (PiT) copy

A copy or snapshot of a volume or set of volumes at a specific point in
time. A point-in-time copy can be used for backup or mirroring
application to run concurrently with the system.
pool
A set of volumes that are reserved for storing Copy-on-Write Snapshot
data or Dynamic Provisioning write data.
pool volume (pool-VOL)

A logical volume that is reserved for storing snapshot data for Copy-on-
Write Snapshot operations or write data for Dynamic Provisioning.
port attribute
Indicates the type of fibre-channel port: target, RCU target, or initiator.
port block
A group of four fibre-channel ports that have the same port mode.
port mode
The operational mode of a fibre-channel port. The three port modes for
fibre-channel ports on the Hitachi RAID storage systems are standard,
high-speed, and initiator/external MIX.
PPRC
Peer-to-Peer Remote Copy
Preview list
The list of requested operations on Hitachi Storage Navigator.
primary site
The physical location of the storage system that contains the original
data to be replicated and that is connected to one or more storage
systems at the remote or secondary site via remote copy connections.
A primary site can also be called a “main site” or “local site”.
#
Glossary–20
The term “primary site” is also used for host failover operations. In that
case, the primary site is the host computer where the production
applications are running, and the secondary site is where the backup
applications run when the applications at the primary site fail, or where
the primary site itself fails.
primary volume (P-VOL)

The volume in a copy pair that contains the original data to be replicated.
The data on the P-VOL is duplicated synchronously or asynchronously on
the secondary volume(s) (S-VOL).
The following Hitachi products use the term P-VOL: Copy-on-Write
Snapshot, ShadowImage, TrueCopy, Universal Replicator, Universal
Replicator software for Mainframe, and High Availability Manager.
See also secondary volume (S-VOL).
P-site
primary site
P-VOL
See primary volume (P-VOL).
Q
quick format
The quick format feature in Virtual LVI/Virtual LUN in which the
formatting of the internal volumes is done in the background. This allows
system configuration (such as defining a path or creating a TrueCopy
pair) before the formatting is completed. To execute quick formatting,
the volumes must be in blocked status.
quick restore
A reverse resynchronization in which no data is actually copied: the
primary and secondary volumes are swapped.
quick split
A split operation in which the pair becomes split immediately before the
differential data is copied to the secondary volume (S-VOL). Any
remaining differential data is copied to the S-VOL in the background. The
benefit is that the S-VOL becomes immediately available for read and
write I/O.
R
R/W, r/w
read/write
Glossary–21
RAID
redundant array of inexpensive disks
RAID group
A redundant array of inexpensive drives (RAID) that have the same
capacity and are treated as one group for data storage and recovery. A
RAID group contains both user data and parity information, which allows
the user data to be accessed in the event that one or more of the drives
within the RAID group are not available. The RAID level of a RAID group
determines the number of data drives and parity drives and how the
data is “striped” across the drives. For RAID1, user data is duplicated
within the RAID group, so there is no parity data for RAID1 RAID groups.
A RAID group can also be called an array group or a parity group.
RAID level
The type of RAID implementation. RAID levels include RAID0, RAID1,
RAID2, RAID3, RAID4, RAID5 and RAID6.
RCP
remote control port
RCU
See remote control unit (RCU).
RD
read
RCU target port

A fibre-channel port that is configured to receive remote I/Os from an
initiator port on another storage system.
remote console PC
A previous term for the personal computer (PC) system that is LAN-
connected to a RAID storage system. The current term is Storage
Navigator PC.
remote control port (RCP)

A serial-channel (ESCON) port on a TrueCopy main control unit (MCU)
that is configured to send remote I/Os to a TrueCopy remote control unit
(RCU).
remote control unit (RCU)

A storage system at a secondary or remote site that is configured to
receive remote I/Os from one or more storage systems at the primary
or main site.
#
Glossary–22
remote copy
See remote replication.
remote copy connections

The physical paths that connect a storage system at the primary site to
a storage system at the secondary site. Also called data path.
remote replication
Data replication configuration in which the storage system that contains
the original data is at a local site and the storage system that contains
the copy of the original data is at a remote site. TrueCopy and Universal
Replicator provide remote replication. See also in-system replication.
remote site
See secondary site.
remote volume (R-VOL)

In TrueCopy for z/OS, a volume at the remote site that contains a copy
of the original data on the main volume (M-VOL) at the main site.
restore journal (R-JNL)

Holds differential data on the secondary Universal Replicator system
until it is copied to the secondary volume.
resync
“Resync” is short for resynchronize.
RF
record format
RIO
remote I/O
R-JNL
restore journal
RL
record length
RMI
Remote Method Invocation
rnd
random
Glossary–23
root volume
A level-1 primary volume in a ShadowImage cascade configuration. The
secondary volume of a layer-1 pair is called a node volume. See also
RPO
recovery point objective
R-SIM
remote service information message
R-site
remote site (used for Universal Replicator)
RTC
real-time clock
RTO
recovery time objective
R-VOL
See remote volume (R-VOL).
R/W
read/write
S
S#
serial number
S/N
serial number
s/w
software
SAID
system adapter ID
SAN
storage-area network
#
Glossary–24
SATA
serial Advanced Technology Attachment
SC
storage control
SCDS
source control dataset
SCI
state change interrupt
scripting
The use of command line scripts, or spreadsheets downloaded by
Configuration File Loader, to automate storage management operations.
SCSI
small computer system interface
secondary site
The physical location of the storage system that contains the primary
volumes of remote replication pairs at the main or primary site. The
storage system at the secondary site is connected to the storage system
at the main or primary site via remote copy connections. The secondary
site can also be called the “remote site”. See also primary site.
secondary volume (S-VOL)

The volume in a copy pair that is the copy of the original data on the
primary volume (P-VOL). The following Hitachi products use the term
“secondary volume”: ShadowImage, TrueCopy, Universal Replicator,
Universal Replicator software for Mainframe, and High Availability
Manager.
See also primary volume (P-VOL).
seq.
sequential
service information message (SIM)

SIMs are generated by a RAID storage system when it detects an error
or service requirement. SIMs are reported to hosts and displayed on
Storage Navigator.
Glossary–25
service processor (SVP)
The computer inside a RAID storage system that hosts the Storage
Navigator software and is used by service personnel for configuration
and maintenance of the storage system.
severity level
Applies to service information messages (SIMs) and Storage Navigator
error codes.
SI
Hitachi ShadowImage
SIz
Hitachi ShadowImage for Mainframe
sidefile
An area of cache memory that is used to store updated data for later
integration into the copied data.
SIM
service information message
size
Generally refers to the storage capacity of a memory module or cache.
Not usually used for storage of data on disk or flash drives.
SM
shared memory
SMTP
simple mail transfer protocol
SN
serial number; Storage Navigator
snapshot
A point-in-time virtual copy of a Copy-on-Write Snapshot primary
volume (P-VOL). The snapshot is maintained when the P-VOL is updated
by storing pre-updated data (snapshot data) in a data pool.
SNMP
simple network management protocol
#
Glossary–26
SOM
system option mode
source volume (S-VOL)

The volume in a copy pair containing the original data that is duplicated
on the target volume (T-VOL). The following Hitachi products use the
term source volume: ShadowImage for Mainframe, Dataset Replication,
IBM FlashCopy.
space
Generally refers to the data storage capacity of a disk drive or flash
drive.
SRM
Storage Replication Manager
SS
snapshot
SSB
sense byte
SSID
storage subsystem ID. SSIDs are used for reporting information from
the CU to the mainframe operating system. Each group of 64 or 256
volumes requires one SSID, so there are one or four SSIDs per CU
image. The user-specified SSIDs are assigned during storage system
installation and must be unique to all connected host operating
environments.
SSL
secure socket layer
steady split
In ShadowImage, a typical pair split operation in which any remaining
differential data from the P-VOL is copied to the S-VOL and then the pair
is split.
S-VOL
See secondary volume (S-VOL) or source volume (S-VOL).
SVP
See service processor (SVP).
Glossary–27
sync
synchronous
system option mode (SOM)

Additional operational parameters for the RAID storage systems that
enable the storage system to be tailored to unique customer operating
requirements. SOMs are set on the service processor.
T
target port
A fibre-channel port that is configured to receive and process host I/Os.
target volume (T-VOL)

The volume in a mainframe copy pair that is the copy of the original data
on the source volume (S-VOL). The following Hitachi products use the
term T-VOL: ShadowImage for Mainframe, Dataset Replication, IBM
FlashCopy.
See also source volume (S-VOL).
TB
terabyte
TC
Hitachi TrueCopy
TCz
Hitachi TrueCopy for Mainframe
TDEVN
target device number
TGT
target; target port
THD
threshold
TID
target ID
total capacity
The aggregate amount of storage space in a data storage system.
#
Glossary–28
T-VOL
See target volume (T-VOL).
U
update copy
An operation that copies differential data on the primary volume of a
copy pair to the secondary volume. Update copy operations are
performed in response to write I/Os on the primary volume after the
initial copy operation is completed.
UR
Hitachi Universal Replicator
URz
Hitachi Universal Replicator for for Mainframe
USP
Hitachi TagmaStore® Universal Storage Platform
USP V
Hitachi Universal Storage Platform V
USP VM
Hitachi Universal Storage Platform VM
UT
Universal Time
UTC
Universal Time-coordinated
V
V
version; variable length and de-blocking (mainframe record format)
VB
variable length and blocking (mainframe record format)
view mode
The mode of operation of Storage Navigator that allows viewing only of
the storage system configuration. The two Storage Navigator modes are
view mode and modify mode.
Glossary–29
virtual device (VDEV)
A group of logical devices (LDEVs) in a RAID group. A VDEV typically
consists of some fixed volumes (FVs) and some free space. The number
of fixed volumes is determined by the RAID level and device emulation
type.
Virtual LVI/LUN volume

A custom-size volume whose size is defined by the user using Virtual
LVI/Virtual LUN. Also called a custom volume (CV).
virtual volume (V-VOL)

The secondary volume in a Copy-on-Write Snapshot pair. When in PAIR
status, the V-VOL is an up-to-date virtual copy of the primary volume
(P-VOL). When in SPLIT status, the V-VOL points to data in the P-VOL
and to replaced data in the pool, maintaining the point-in-time copy of
the P-VOL at the time of the split operation.
When a V-VOL is used with Dynamic Provisioning, it is called a DP-VOL.
VLL
Hitachi Virtual LVI/LUN
VLVI
Hitachi Virtual LVI
VM
volume migration; volume manager
VOL, vol
volume
VOLID
volume ID
volser
volume serial number
volume
A logical device (LDEV), or a set of concatenated LDEVs in the case of
LUSE, that has been defined to one or more hosts as a single data
storage unit. A mainframe volume is called a logical volume image (LVI),
and an open-systems volume is called a logical unit. (LU).
volume pair
See copy pair.
#
Glossary–30
V-VOL
virtual volume
V-VOL management area

Contains the pool management block and pool association information
for Copy-on-Write Snapshot operations. The V-VOL management area is
created automatically when additional shared memory is installed and is
required for Copy-on-Write Snapshot operations.
Glossary–31
#
Glossary–32
Index
A Information dialog box 6–7

interfaces;Storage Navigator;CCI 1–5
access attribute;Data Retention Utility 3–2
additional shared memory 2–6
L
B license info for pairs 6–6
blocked pool 7–2
blocked pool, recovering 7–5
M
blocked volume 7–3 managing pools and V-VOLs 6–10
menu commands
C Snapshot window B–15
monitoring pool information 6–9
CCI
command device;command device 4–5
troubleshooting with 7–5
O
changing a V-VOL name 6–14 operations, pair;pair operations;Snapshot
configuration workflow 4–2 pair operations 5–2
consistency group requirements 2–3 overview;Snapshot
Copy Threshold option 6–11 overview 1–2
creating a pair 5–2
creating a V-VOL;V-VOL P
creating 4–3 pair details 6–4
creating multiple pairs 5–3 pair operations history, monitoring;history of pair
operations, monitoring 6–8
D pair restore problem 7–4
deleting a pair or pairs 5–5 pair status
deleting V-VOLs;V-VOLs and pair operations 6–3
deleting 6–14 definitions 6–3
differential tables, calculating maximum 2–6 monitoring 6–2
Dynamic Provisioning 3–6 pair tables 2–10
pair volumes, sharing;interoperability 3–2
E pairs
description 1–2
external volumes, planning 2–11
maximum number 2–6
planning how many needed;maximum pairs,
H calculating 2–6
History window B–10 Pairsplit-S dialog box 5–6
host access problem 7–3 pool threshold exceeded 7–2
HP-UX server restriction 2–3 pools
changing the pool name 6–13
I changing the usage threshold 6–12
creating;creating pools 4–2
increasing pool capacity 6–11
deleting;deleting a pool 6–13
Index-1
description 1–4
managing 6–11
maximum number 2–2
monitoring 6–9
recovering;recovering a pool 6–12
requirements, restrictions 2–3
sizing;V-VOL:sizing 2–4
powering off the system;Snapshot
powering off the system 6–15
Preview list B–5
R
RAID levels supported 2–2
required shared memory;shared memory
requirement 2–2
requirements;Snapshot
requirements 2–2
restoring a pair 5–4
resynchronizing a pair 5–4
S
S-VOL Path dialog box 6–6
shared memory, V-VOL management area 2–7
SIMs for pool problems 7–5
Snapshot
installing, uninstalling 4–2
splitting pairs 5–3
T
Task Name field, valid characters and symbols 4–
2
V
V-VOL
and S-VOL;S-VOL 1–2
V-VOLs
managing 6–14
Volume Migration 3–3
Index-2
1
Hitachi Data Systems
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 Americas
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
MK-90RD7013-00

Copy On WriteSnapshotUserGuide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Copy On WriteSnapshotUserGuide

Uploaded by

Copyright:

Available Formats

Hitachi Virtual Storage Platform

Hitachi Copy-on-Write Snapshot User Guide

ShadowImage and TrueCopy are registered trademarks of Hitachi Data Systems.

2 Planning and design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

3 Sharing Snapshot volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

4 Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

5 Pair operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

6 Monitoring and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

A CCI command reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

B Snapshot GUI reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

This document provides instructions for performing Copy-on-Write

□ Document revision level

□ Source documents for this revision

□ Changes in this revision

□ Convention for storage capacity values

□ Accessing product documentation

Document revision level

Source documents for this revision

Changes in this revision

This document uses the following icons to draw attention to information:

Icon Meaning Description

Note Calls attention to important and/or additional information.

Caution Warns users of adverse conditions and consequences, such

WARNING Warns users of severe conditions and consequences, such as

Convention for storage capacity values

Physical capacity unit Value

Logical capacity unit Value

Accessing product documentation

With Hitachi Copy-on-Write Snapshot software, you create virtual copies of

□ Copy-on-Write Snapshot software

□ How Snapshot works

□ Licenses and capacity

□ Interfaces for performing Snapshot operations

How Snapshot works

Volume pairs — P-VOLs and V-VOLs

Licenses and capacity

Interfaces for performing Snapshot operations

Command Control Interface (CCI)

This topic describes requirements for setting up and using Copy-on-Write

□ Data pool requirements and restrictions

□ Planning for external volumes

Planning and design 2–1

2–2 Planning and design

Data pool requirements and restrictions

Planning and design 2–3

Planning V-VOLs, data pools

2–4 Planning and design

Sizing the data pool

Figure 2-2 Basic factors for data pool sizing

Planning and design 2–5

Calculating max. pairs based on differential tables

2–6 Planning and design

In this example, the maximum number allowed for Snapshot based on

Calculating max. pairs based on V-VOL management area shared

Table 2-1 Shared memory capacity for V-VOL management area

Shared memory Shared memory capacity

Planning and design 2–7

1. Calculate total capacity of all pools (P), using the following

where Y = Total capacity of pool-VOLs (in kilobytes).

2. Calculate shared memory capacity for the pool management

2–8 Planning and design

3. Calculate shared memory capacity for pool association

4. Calculate the total capacity of P-VOLs, using the following