hitachi virtual storage platform - hitachi data systems ibm, lotus, mvs, os/390, ... manager, pprc...

Hitachi Virtual Storage PlatformHitachi ShadowImage® for Mainframe User Guide

MK-90RD7023-14

Document Organization

Product Version

Getting Help

Contents

© 2010 - 2016 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 retrievalsystem for any purpose without the express written permission of Hitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time without notice andassumes no responsibility for its use. This document contains the most current information availableat the time of publication. When new or revised information becomes available, this entiredocument will be updated and distributed to all registered users.

Some of the features described in this document might not be currently available. Refer to the mostrecent product announcement for information about feature and product availability, or contactHitachi Data Systems Corporation at https://portal.hds.com.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions ofthe applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products isgoverned by the terms of your agreements with Hitachi Data Systems Corporation.

Notice on Export Controls. The technical data and technology inherent in this Document may besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility toobtain licenses to export, re-export, or import the Document and any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. HitachiData Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States andother countries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft,Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform areregistered trademarks of Hitachi Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON,FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA,z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of InternationalBusiness Machines Corporation.

All other trademarks, service marks, and company names in this document or website areproperties of their respective owners.

Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

iiHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

https://portal.hds.com

Contents

Preface.................................................................................................. ixIntended audience..................................................................................................... xProduct version..........................................................................................................xDocument revision level..............................................................................................xChanges in this revision............................................................................................. xiReferenced documents.............................................................................................. xiDocument organization..............................................................................................xiDocument conventions..............................................................................................xiiConvention for storage capacity values......................................................................xiiiAccessing product documentation.............................................................................xivGetting help............................................................................................................ xivComments.............................................................................................................. xiv

1 ShadowImage for Mainframe overview...................................................1-1How ShadowImage for Mainframe works..................................................................1-2Hardware and software components........................................................................ 1-2

Volume pairs (primary volumes and secondary volumes)..................................... 1-3Storage Navigator GUI...................................................................................... 1-3Command Control Interface, PPRC, Business Continuity Manager and consistencygroups.............................................................................................................1-4

Initial and update copy operations........................................................................... 1-4Initial copy.......................................................................................................1-4Update copy.....................................................................................................1-5

2 Requirements and planning................................................................... 2-1System requirements.............................................................................................. 2-2Supported emulation types for pair volumes............................................................. 2-3License capacity requirements................................................................................. 2-5Planning pair volumes............................................................................................. 2-5

Planning number of pairs.................................................................................. 2-6Calculating the number of differential tables and pair tables....................... 2-7Calculating maximum number of pairs...................................................... 2-8

Planning for performance........................................................................................ 2-9Consistency group pair-split................................................................................... 2-10

Consistency group pair-split for shared volumes................................................2-11

iiiHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Requirements, restrictions, and recommendations for shared volumes...... 2-12Consistency group pair-split and supported pair statuses..........................2-14

Preparing for Business Continuity Manager, PPRC use..............................................2-15Command device............................................................................................ 2-15

3 Sharing ShadowImage for Mainframe volumes........................................3-1Cache Residency Manager....................................................................................... 3-2Compatible FlashCopy®..........................................................................................3-2Compatible FlashCopy® SE..................................................................................... 3-2Compatible XRC......................................................................................................3-2Concurrent Copy.....................................................................................................3-3Dynamic Provisioning for Mainframe and Dynamic Tiering for Mainframe.................... 3-3Resource Partition Manager..................................................................................... 3-3TrueCopy for Mainframe..........................................................................................3-3Universal Replicator for Mainframe...........................................................................3-4

Sharing volumes in 3-URz data center configurations.......................................... 3-5Sharing volumes in a 3-URz DC multi-target configuration..........................3-5Sharing volumes in a 3-URz DC cascade configuration............................... 3-7

Sharing volumes in 3-URz/TCz data center configurations....................................3-8Sharing volumes in 3-URz/TCz DC multi-target and delta resync configurations..............................................................................................................3-9Sharing volumes in a 3-TCz/URz DC cascade configuration....................... 3-10

Universal Volume Manager.................................................................................... 3-11Virtual LVI............................................................................................................ 3-11Volume Migration..................................................................................................3-11Volume Retention Manager....................................................................................3-12

Access attributes and ShadowImage for Mainframe operations.......................... 3-12ShadowImage for Mainframe pair statuses and access attribute setting.............. 3-13

4 Performing configuration operations.......................................................4-1Configuration workflow .......................................................................................... 4-2Setting up primary and secondary volumes...............................................................4-2Reserving secondary volumes.................................................................................. 4-2Reserving a consistency group.................................................................................4-3System options that affect performance................................................................... 4-4

Setting performance options..............................................................................4-5

5 Performing pair operations.................................................................... 5-1Pair operations workflow......................................................................................... 5-2Check pair status.................................................................................................... 5-2Pair creation...........................................................................................................5-2

Prerequisite information for creating pairs.......................................................... 5-3SIz pair configuration in Create Pairs wizard....................................................... 5-3Creating pairs...................................................................................................5-4

Suspending pair creation......................................................................................... 5-8Pair split.................................................................................................................5-8

Types of split operations................................................................................... 5-9Prerequisite information for splitting pairs...........................................................5-9Split/SUSPOP, performance, and SOM 459......................................................... 5-9Splitting pairs................................................................................................. 5-10

ivHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Splitting pairs in a consistency group................................................................5-11Pair resynchronization........................................................................................... 5-11

Types of resync operations..............................................................................5-12Prerequisite information for resynchronizing..................................................... 5-13Resynchronizing pairs......................................................................................5-14

Pair deletion......................................................................................................... 5-15Prerequisite information for deleting pairs.........................................................5-15Deleting pairs................................................................................................. 5-15

6 Monitoring and maintaining the system.................................................. 6-1Monitoring the system ............................................................................................6-2

Monitoring pair activity, status ..........................................................................6-2Pair status definitions.............................................................................. 6-2CCI pair status names............................................................................. 6-4Status, pair operations permitted ............................................................ 6-5Status of unaffected S-VOLs, operations permitted ................................... 6-5

Monitoring pair, volume details..........................................................................6-6Monitoring synchronous rates............................................................................6-6Monitoring consistency groups...........................................................................6-7Monitoring reserve volumes...............................................................................6-7Monitoring a pair’s operation history ................................................................. 6-7

Maintaining the system........................................................................................... 6-9Removing reserve attribute from a volume......................................................... 6-9Releasing a reserved consistency group............................................................. 6-9Pair operations during system, device maintenance.............................................6-9

7 Troubleshooting....................................................................................7-1ShadowImage for Mainframe Troubleshooting.......................................................... 7-2

Operation and display troubleshooting............................................................... 7-2Troubleshooting pinned tracks...........................................................................7-2Troubleshooting extended copy times................................................................ 7-2

Service Information Messages (SIMs).......................................................................7-3Troubleshooting with CCI........................................................................................ 7-4

Troubleshooting consistency group pair-split.....................................................7-13Calling the Hitachi Data Systems customer support..................................................7-14

A Pair operations using PPRC................................................................... A-1Overview of PPRC commands supported by ShadowImage for Mainframe...................A-2PPRC command requirements..................................................................................A-2Preparing the system with PSF and DEVSERV........................................................... A-3Pair operations using PPRC commands when S-VOL is online.....................................A-4Adding pairs with CESTPAIR and PPRCOPY ESTPAIR................................................. A-4

CESTPAIR........................................................................................................A-4ESTPAIR..........................................................................................................A-5

Splitting pairs with CSUSPEND and PPRCOPY SUSPEND.............................................A-7CSUSPEND.......................................................................................................A-7SUSPEND.........................................................................................................A-8

Resynchronizing pairs with CESTPAIR and PPRCOPY ESTPAIR....................................A-8CESTPAIR (resynchronizing pairs.......................................................................A-9ESTPAIR (resynchronizing pairs)......................................................................A-10

vHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Deleting pairs with CDELPAIR, DELPAIR................................................................. A-12CDELPAIR...................................................................................................... A-12

DELPAIR...............................................................................................A-13Consistency group pair operations with PPRC..........................................................A-13

Setting up pairs in consistency groups..............................................................A-14Splitting pairs in consistency groups.................................................................A-14Resynchronizing pairs in consistency groups.....................................................A-14Deleting pairs in consistency groups.................................................................A-14

Showing pair information with CQUERY TSO, QUERY ICKDSF...................................A-14CQUERY.........................................................................................................A-15PPRCOPY QUERY............................................................................................A-16Output descriptions.........................................................................................A-16

B Interface support for SIz operations and options.....................................B-1Operations supported by Storage Navigator, CCI, Business Continuity Manager, andPPRC..................................................................................................................... B-2Consistency group operations supported by Storage Navigator, CCI, Business ContinuityManager, PPRC.......................................................................................................B-3

C ShadowImage for Mainframe GUI reference...........................................C-1Replications window............................................................................................... C-3Local Replications window.......................................................................................C-4View Pair Properties window..................................................................................C-11View Pair Synchronous Rate window...................................................................... C-13View Histories window...........................................................................................C-15Consistency Group Properties window.................................................................... C-16Create Pairs wizard............................................................................................... C-18

Select Pair Configuration window.....................................................................C-19Select Primary Volumes window.......................................................................C-20Select Secondary Volumes window...................................................................C-23Confirm window............................................................................................. C-26

Split Pairs wizard.................................................................................................. C-27Split Pairs window.......................................................................................... C-27Confirm window............................................................................................. C-30

Resync Pairs wizard.............................................................................................. C-31Resync Pairs window...................................................................................... C-31Confirm window............................................................................................. C-34

Suspend Pairs window...........................................................................................C-35Delete Pairs window..............................................................................................C-37Edit Mirror Units dialog box....................................................................................C-38Change Options dialog box....................................................................................C-38Add Reserve Volumes Wizard.................................................................................C-39

Add Reserve Volumes window......................................................................... C-39Confirm window............................................................................................. C-41

Remove Reserve Volumes window......................................................................... C-41Reserve Consistency Groups wizard........................................................................C-42

Reserve Mainframe CTGs window.................................................................... C-42Confirm window............................................................................................. C-43

Release Reserve Mainframe CTGs window.............................................................. C-44Edit Local Replica Option wizard.............................................................................C-44

Edit Local Replica Option window.....................................................................C-45

viHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Confirm window............................................................................................. C-46

D Configuration operations (secondary window)........................................D-1Configuration workflow...........................................................................................D-2Setting up source and target volumes......................................................................D-2Reserving T-VOLs...................................................................................................D-2Reserving a consistency group................................................................................ D-3Setting performance options................................................................................... D-4

E Pair operations (secondary window).......................................................E-1Pair operations workflow......................................................................................... E-2Check pair status.................................................................................................... E-2Creating pairs.........................................................................................................E-2Splitting pairs, creating and splitting pairs.................................................................E-4

Splitting pairs in a consistency group................................................................. E-6Suspending pair creation......................................................................................... E-7Resynchronizing pairs............................................................................................. E-9Deleting pairs....................................................................................................... E-12

F Monitoring and maintaining the system (secondary window)....................F-1Monitoring the system (secondary window).............................................................. F-2

Monitoring pair activity, status (secondary window)............................................ F-2Pair status definitions (secondary window)................................................F-2

Reviewing pair, volume details...........................................................................F-3Reviewing pair, license information ................................................................... F-4Reviewing a pair’s operation history .................................................................. F-6Reviewing pair details for a consistency group.................................................... F-8

Maintaining the system (secondary window)............................................................. F-9Removing reserve attribute from a volume ........................................................ F-9

G ShadowImage for Mainframe GUI reference (secondary window)............ G-1Pair Operation window............................................................................................G-2

Main components ............................................................................................G-3Volume list.......................................................................................................G-3Preview list......................................................................................................G-5Pair Operation command menu......................................................................... G-5Display Filter dialog box ...................................................................................G-6

History window...................................................................................................... G-7Option window.......................................................................................................G-8CTG window ......................................................................................................... G-9

CTG command menu .....................................................................................G-11

Glossary

Index

viiHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

viiiHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Preface

This document provides information for setting up and operating HitachiShadowImage® for Mainframe on the Hitachi Virtual Storage Platform (VSP)storage system.

Please read this document carefully to understand how to use this product,and maintain a copy for reference purposes.

This preface includes the following information:

□ Intended audience

□ Product version

□ Document revision level

□ Changes in this revision

□ Referenced documents

□ Document organization

□ Document conventions

□ Convention for storage capacity values

□ Accessing product documentation

□ Getting help

□ Comments

Preface ixHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Intended audienceThis document is intended for system administrators, HDS representatives,and authorized service providers who are involved in installing, configuring,and operating the Hitachi Virtual Storage Platform storage system.

This document assumes the following:

• The user has a background in data processing and understands RAIDstorage systems and their basic functions.

• The user is familiar with the Hitachi Virtual Storage Platform storagesystem and has read the Hitachi Virtual Storage Platform User andReference Guide.

• The user is familiar with the Storage Navigator software for VSP and hasread the Hitachi Storage Navigator User Guide.

Product versionThis document revision applies to Hitachi Virtual Storage Platform microcode70-06-2x or later.

Document revision levelRevision Date Description

MK-90RD7023-00 October 2010 Initial release

MK-90RD7023-01 December 2010 Supersedes and replaces MK-90RD7023-00.

MK-90RD7023-02 January 2011 Supersedes and replaces MK-90RD7023-01.

MK-90RD7023-03 April 2011 Supersedes and replaces MK-90RD7023-02.

MK-90RD7023-04 August 2011 Supersedes and replaces MK-90RD7023-03.

MK-90RD7023-05 November 2011 Supersedes and replaces MK-90RD7023-04.

MK-90RD7023-06 March 2012 Supersedes and replaces MK-90RD7023-05.

MK-90RD7023-07 June 2012 Supersedes and replaces MK-90RD7023-06.

MK-90RD7023-08 November 2012 Supersedes and replaces MK-90RD7023-07.

MK-90RD7023-09 January 2013 Supersedes and replaces MK-90RD7023-08.

MK-90RD7023-10 July 2013 Supersedes and replaces MK-90RD7023-09

MK-90RD7023-11 March 2014 Supersedes and replaces MK-90RD7023-10

MK-90RD7023-12 April 2014 Supersedes and replaces MK-90RD7023-11

MK-90RD7023-13 September 2014 Supersedes and replaces MK-90RD7023-12

MK-90RD7023-14 March 2016 Supersedes and replaces MK-90RD7023-13

x PrefaceHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Changes in this revision• Updated System requirements on page 2-2.• Updated prerequisites in Pair creation on page 5-2.

Referenced documentsHitachi Virtual Storage Platform documentation:

• Command Control Interface User and Reference Guide, MK-90RD7010• Hitachi Copy-on-Write Snapshot User Guide, MK-90RD7013• Hitachi Compatible FlashCopy® V2 User Guide, MK-90RD7017• Hitachi Virtual Storage Platform Performance Guide, MK-90RD7020• Hitachi Virtual Storage Platform Provisioning Guide for Mainframe

Systems, MK-90RD7021• Hitachi TrueCopy® for Mainframe User Guide, MK-90RD7030• Hitachi Universal Replicator for Mainframe User Guide, MK-90RD7031• Hitachi Thin Image User Guide, MK-90RD7179• Business Continuity Manager User Guide, MK-94RD247

Document organizationThe following table provides an overview of the contents and organization ofthis document. Click the chapter title in the left column to go to that chapter.The first page of each chapter provides links to the topics in that chapter.

Chapter/AppendixTitle Description

Chapter 1, ShadowImage forMainframe overview on page1-1

Provides an overview of Hitachi ShadowImage forMainframe.

Chapter 2, Requirements andplanning on page 2-1

Describes system requirements and recommendationsfor planning a ShadowImage for Mainframe system.

Chapter 3, SharingShadowImage for Mainframevolumes on page 3-1

Discusses requirements, recommendations, andrestrictions for using ShadowImage for Mainframe withother Hitachi software.

Chapter 4, Performingconfiguration operations onpage 4-1

Provides information and instructions for configuring aShadowImage for Mainframe system.

Chapter 5, Performing pairoperations on page 5-1

Provides instructions for performing ShadowImage forMainframe pair operations.

Chapter 6, Monitoring andmaintaining the system on page6-1

Provides information and instructions for checkingShadowImage for Mainframe’s operational status.

Preface xiHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Chapter/AppendixTitle Description

Chapter 7, Troubleshooting onpage 7-1

Provides information and instructions fortroubleshooting ShadowImage for Mainframe.

Appendix A, Pair operationsusing PPRC on page A-1

Provides PPRC requirements, commands, andexamples.

Appendix B, Interface supportfor SIz operations and optionson page B-1

Lists operations and the user interfaces that supportthem.

Appendix C, ShadowImage forMainframe GUI reference onpage C-1

Describes the ShadowImage for Mainframe windowsand dialog boxes in Storage Navigator.

Appendix D, Configurationoperations (secondary window)on page D-1

Provides information and instructions for configuring aShadowImage for Mainframe system using the previousStorage Navigator GUI, which is shown in a secondarywindow.

Appendix E, Pair operations(secondary window) on pageE-1

Provides information and instructions for performingShadowImage for Mainframe operations using theprevious Storage Navigator GUI, which is shown in asecondary window.

Appendix F, Monitoring andmaintaining the system(secondary window) on pageF-1

Provides information and instructions for checkingShadowImage for Mainframe’s operational status usingthe previous Storage Navigator GUI, which is shown ina secondary window.

Appendix G, ShadowImage forMainframe GUI reference(secondary window) on pageG-1

Describes the ShadowImage for Mainframe windowsand dialog boxes in Storage Navigator as seen in theprevious Storage Navigator GUI, which is shown in asecondary window.

Document conventionsThis document uses the following typographic conventions:

Convention Description

Bold Indicates text on a window, other than the window title,including menus, menu options, buttons, fields, and labels.Example: Click OK.

Italic Indicates a variable, which is a placeholder for actual textprovided by the user or system. Example: copy source-filetarget-fileNote: Angled brackets (< >) are also used to indicate variables.

screen/code Indicates text that is shown on screen or entered by the user.Example: # pairdisplay -g oradb

< > angled brackets Indicates a variable, which is a placeholder for actual textprovided by the user or system. Example: # pairdisplay -g<group>

xii PrefaceHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Convention Description

Note: Italic font is also used to indicate variables.

[ ] square brackets Indicates optional values. Example: [ a | b ] indicates that youcan choose a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b }indicates that you must choose either a or b.

| vertical bar Indicates that you have a choice between two or more optionsor arguments. Examples:[ a | b ] indicates that you can choose a, b, or nothing.{ a | b } indicates that you must choose either a or b.

Underline Indicates the default value. Example: [ a | b ]

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

Icon Meaning Description

Tip Provides helpful information, guidelines, or suggestions forperforming tasks more effectively.

Note Calls attention to important and/or additional information.

Caution Warns the user of adverse conditions and/or consequences,such as disruptive operations.

WARNING Warns the user of severe conditions and/or consequences,such as destructive operations.

Convention for storage capacity valuesPhysical storage capacity values, such as disk drive capacity, are calculatedbased 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

Preface xiiiHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Logical storage capacity values, such as logical device capacity, are calculatedbased 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

1 block 512 bytes

Accessing product documentationThe Hitachi Virtual Storage Platform user documentation is available on theHDS Support Portal: https://portal.hds.com. Please check this site for themost current documentation, including important updates that may havebeen made after the release of the product.

Getting helpThe HDS customer support staff is available 24 hours a day, seven days aweek. If you need technical support, log on to the HDS Support Portal forcontact information: https://portal.hds.com

CommentsPlease send us your comments on this document: [email protected] the document title, number, and revision, and refer to specificsections and paragraphs whenever possible. All comments become theproperty of HDS.

Thank you!

xiv PrefaceHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

https://hdssupport.hds.com


mailto:[email protected]

1ShadowImage for Mainframe overview

ShadowImage for Mainframe (SIz) uses local mirroring technology to createand maintain a full copy of any volume in the storage system.

With SIz software you can create one or more copies of a data volume withinthe same storage system. You can use SIz copies as backups, with secondaryhost applications, for data mining, for testing, and other uses — whilebusiness operations continue without stopping host application I/O to theproduction volume.

This guide provides instructions for planning, configuring, operating,maintaining, and troubleshooting an SIz system.

□ How ShadowImage for Mainframe works

□ Hardware and software components

□ Initial and update copy operations

ShadowImage for Mainframe overview 1-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

How ShadowImage for Mainframe worksA pair is created when you:

• Select a volume that you want to duplicate. This becomes the P-VOLvolume (P-VOL).

• Identify another volume to contain the copy. This becomes the secondaryvolume (S-VOL).

• Associate the P-VOL and S-VOLs.• Perform the initial copy.

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

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

• S-VOL data is consistent and usable. It is available for read/write accessby secondary host applications.

• Changes to the P-VOL and S-VOLs are managed by differential bitmaps.• You can pair the volumes again by resynchronizing the update data from

P-VOL-to-S-VOL, or from S-VOL-to-P-VOL, as circumstance dictates.

Note: In Storage Navigator (SN), the source volume is called “P-VOL” andthe destination volume is called “S-VOL”.

Hardware and software componentsA typical configuration consists of a Hitachi Virtual Storage Platform storagesystem, a host connected to the storage system, SIz software, a P-VOL, a S-VOL or volumes, and interface tools for operating SIz.

Interface tools include the SN graphical user interface (GUI) and VOS3DMFVSS, Business Continuity Manager (BCM), IBM PPRC host softwarefunctions, IBM DFSMSdss host software functions, and Command ControlInterface software (CCI).

The following shows a typical configuration.

1-2 ShadowImage for Mainframe overviewHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Volume pairs (primary volumes and secondary volumes)A pair consists of the P-VOL and secondary data volume. Each P-VOL can bepaired with up to three S-VOLs. Thus, you can create three pairs using one P-VOL.

During most operations, the P-VOL remains available to the host for I/Ooperations. Updating the P-VOL regularly copies the new data, the differentialdata, to the S-VOL. Because S-VOLs are updated asynchronously, the P-VOLand S-VOLs may not be identical. S-VOLs become available for host accessonly after you split or delete the pair, and all updates to the S-VOL completeonly when the pair is split. If the pair is deleted, pending updates to the S-VOL are not completed.

Storage Navigator GUIWith the SN GUI, you:

• Enable the SIz license key.• Configure the storage system.• Perform copy operations.• Perform monitoring, maintenance, and troubleshooting.

You perform SIz operations using the new version of the SN GUI. You arealso able to use the previous version, if you choose to do so. Proceduresdescribing operations in the previous version are found in the appendixes.


The SN GUI communicates with the storage system’s service processor (SVP)over defined TCP/IP connections. SN is LAN-attached to the storage system.

Command Control Interface, PPRC, Business Continuity Manager andconsistency groups

With Command Control Interface (CCI), PPRC, and BCM you use a commandline interface for running most of the same operations as are performed withSN. Pair commands are issued directly from the host. Commands can also beautomated using scripts.

Using CCI, PPRC, or BCM, you can specify multiple pairs as a consistency orcopy group. With a consistency (or copy) group, you perform tasks onmultiple pairs at the same time. This also changes the pair status for all thepairs in a group.

Initial and update copy operationsCreating a pair causes the storage system to create an initial copy. Thestorage system asynchronously copies updates received by the P-VOL to theS-VOL.

Initial copyCreating a pair causes the storage system to start the initial copy and copiesall the data in the P-VOL to the S-VOL. Before the pair is created, the pair’sstatus is “SMPL”. While the initial copy is in progress, the status is“PENDING”. When the initial copy is complete, the volumes are paired(“DUPLEX” status).


An P-VOL continues receiving updates from the host during the initial copy.When the initial copy is completed, update copy operations start.

Update copyI/O sent to the P-VOL that is paired (“DUPLEX” status) is marked asdifferential data and stored in bitmaps for transfer to the S-VOL. Update copyoperations are performed periodically by the storage system. The timing ofthe update copy operation is based on the amount of differential data thataccumulates and the elapsed time since the previous update.


Though the volumes are paired (“DUPLEX” status), data in the P-VOL and S-VOLs may not be the same because update copying occurs asynchronously,and therefore later data exists in the P-VOL. You can ensure that P-VOL andS-VOLs data are the same at a certain point in time, by splitting pair.

Also, data in the P-VOL and the data in the S-VOL may not be the same if acopy operation is completed without host I/O. As mentioned above, the P-VOL and S-VOLs can be made the same by splitting the pair.


2Requirements and planning

This chapter describes system requirements and recommendations forplanning an SIz system.

□ System requirements

□ Supported emulation types for pair volumes

□ License capacity requirements

□ Planning pair volumes

□ Planning for performance

□ Consistency group pair-split

□ Preparing for Business Continuity Manager, PPRC use

Requirements and planning 2-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

System requirementsThe following table shows minimum requirements for SIz.

Item Requirement

SIz license capacity Based on purchased capacity. For more information, see Licensecapacity requirements on page 2-5.

License key Must be installed.For more information about installation, see the Hitachi StorageNavigator User Guide.

RAID level RAID 1, RAID 5, RAID 6

SN If you are using the previous version of SN, which is shown in asecondary window, you must be in Modify mode to perform pairoperations.

BCM/IBM PPRC BCM and PPRC are independent functions. Use one or the other.BCM requires a command device. For more information aboutPPRC, see Preparing for Business Continuity Manager, PPRC use onpage 2-15, Appendix A, Pair operations using PPRC on pageA-1, the Business Continuity Manager User Guide, and other IBMdocumentation regarding PPRC.

CCI Requires a command device when used in In-Band mode, thoughnot for Out-of-Band mode.For more information, see the Command Control Interface Userand Reference Guide.

Pair volumes • Number of P-VOLs per S-VOL: one• Number of S-VOLs per P-VOL: one to three• Volume capacity:

The P-VOL and S-VOLs must be the same size in blocks. If thecapacity is displayed in gigabytes, a small difference betweenP-VOL and S-VOL capacity might not be displayed.To view the capacity in blocks, click Options > Capacity Unit> Cyl in the Logical Devices window, or for a secondarywindow, look at the Capacity (Cyl) area of the Detailwindow.

• Supported emulation types—See Supported emulation typesfor pair volumes on page 2-3.

• Supported volume types: - Internal system volumes.- External volumes. Universal Volume Manager (UVM) licenserequired.- Custom-sized volumes. Virtual LVI required. Pair volumesmust have same capacity and emulation type.

• MU number (mirror unit number): Use 0, 1, or 2. Specifiedwhen using SN and CCI, though not when using PPRC or BCM.

• Sharing volumes with other software products is supported.See Chapter 3, Sharing ShadowImage for Mainframe volumeson page 3-1.

• The following cannot be used as pair volumes:- Universal Replicator for Mainframe (URz) journal volumes.

2-2 Requirements and planningHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Item Requirement

- Command devices for BCM.• TSE volumes• Volumes with emulation type 3390-V.

Maximum numberof pairs

Per storage system: 16,384 pairs (when one S-VOL per P-VOL).Actual number is based on amount of additional shared memory.See Planning number of pairs on page 2-6 for furtherinformation.

Consistency groups • You can configure up to 256 consistency groups in a storagesystem, including SI, SIz, Thin Image (HTI), and Copy-on-Write Snapshot (SS) consistency groups.Note: SI, SIz, HTI, and SS pairs cannot co-exist in the sameconsistency group.

• You can define up to 8,192 SIz pairs in a consistency group.• A number (0–FF) is assigned to each consistency group. You

specify a consistency group number when you create pairs. Ifyou do not specify a number, the storage system automaticallyassigns it.- Consistency group numbers 00 to 7F (or 0 to 127) that youcan use for SI, SIz, HTI, and SS. Consistency group numbers80 to FF (or 128 to 255) are exclusively used for HTI and SS.- PPRC/BCM consistency group numbers need to be reservedbefore creating a pair.- If you are using CCI, you do not need not to reserveconsistency group numbers.

• You cannot use consistency groups reserved for PPRC/BCM inCCI. Conversely, you cannot use consistency groups createdusing CCI with BCM/PPRC.

Supported emulation types for pair volumesThe emulation type of the P-VOL and S-VOLs must be the same. However,you can create a pair from an intermediate volume and a normal volume ifthe two volumes are of the same type (such as 3390-3 and 3390-3A/3390-3B).

The following table shows the combinations that you can use to create SIzpairs.

P-VOL S-VOL

3380-3 • 3380-3• 3380-3A• 3380-3B• 3380-3C

3380-3A • 3380-3• 3380-3A


P-VOL S-VOL

3380-3B • 3380-3• 3380-3B

3380-3C • 3380-3• 3380-3C

3390-1 3390-1

3390-2 3390-2

3390-3/3R • 3390-3/3R• 3390-3A• 3390-3B• 3390-3C

3390-3A • 3390-3/3R• 3390-3A

3390-3B • 3390-3/3R• 3390-3B

3390-3C • 3390-3/3R• 3390-3C

3390-9 • 3390-9• 3390-9A• 3390-9B• 3390-9C

3390-9A • 3390-9• 3390-9A

3390-9B • 3390-9• 3390-9B

3390-9C • 3390-9• 3390-9C

3390-L • 3390-L• 3390-LA• 3390-LB• 3390-LC

3390-LA • 3390-L• 3390-LA

3390-LB • 3390-L• 3390-LB

3390-LC • 3390-L• 3390-LC

3390-M • 3390-M• 3390-MA


P-VOL S-VOL

• 3390-MB• 3390-MC

3390-MA • 3390-M• 3390-MA

3390-MB • 3390-M• 3390-MB

3390-MC • 3390-M• 3390-MA

3390-A 3390-A

3390-V None supported

Note: Combinations not listed are not supported.

License capacity requirementsThe total capacity of pair volumes must be less than the maximum volumecapacity licensed to you. After operations begin, you should be aware ofcapacity requirements in order to keep volumes’ total size within purchasedcapacity.

• P-VOLs, S-VOLs, and volumes are reserved for use as S-VOLs must havelicensed capacity.

• If you are using a volume for multiple purposes, the capacity of thevolume is counted only once. You do not need to multiply the capacity bythe number of purposes for which it is used.

When your SIz volumes exceed license capacity, you are allowed to use thevolumes for additional 30 days. After that, you cannot perform SIz operationsexcept to delete pairs.

For more information, see the Hitachi Storage Navigator User Guide.

Planning pair volumesYou must create volumes for P-VOLs and S-VOLs prior to creating pairs. Formore information about the system requirements for pair volumes, seeSystem requirements on page 2-2. Also, you can use the following options:

• Before creating a pair, you can reserve a volume as an S-VOL. Thisensures that an I/O does not occur in the reserved volume beforecreating the pair. You can only use reserved volumes as S-VOLs. (WithTSO or ICKDSF commands, T-VOLs are required to be offline to the host;therefore, you do not need to reserve them.)

• If you use BCM, you can place a group of pairs in a consistency group.Using the consistency group, you can perform pair operations on all the


pairs in the group at the same time, including consistency group pair-splitoperations at specified times (ATTIME Suspend).For more information about setting up consistency groups and performingpair operations, see the Business Continuity Manager User Guide.If you use PPRC, you can split the pairs in a consistency group, but not ata specific time.

Planning number of pairsYou can calculate the number of system resources required for an SIz pair.With this information you can calculate the maximum number of pairsallowed on your system.

Differential tables (tables managing differential bitmaps) and pair tables arerequired to create pairs. You must supply an adequate number of tables tohandle all the pairs you plan to create.

The number of differential and pair tables that are present in the systemdepends on additional shared memory that is installed. Therefore, you mustensure that you have sufficient additional shared memory to handle thenumber of pairs.

Number of differential tables, pair tables, and volumes peradditional shared memory

The following table shows the number of differential and pair tables and thenumber of volumes allowed per additional shared memory. The maximumnumber of pairs is half the number of volumes shown, when P-VOLs and S-VOLs are in a one-to-one relationship.

For example, if additional shared memory is not installed, since the numberof volumes is 16,384, then the number of pairs you can create is 8,192. Thisexample assumes one S-VOL per P-VOL. If there are more S-VOLs than P-VOLs, then the number of allowed pairs decreases.

However, for Extension 1 and Extension 2, the maximum number of pairs is16,384, regardless of the total number of system volumes.

Additional shared memory Number of diff.tables

Number of pairtables

Number ofsystem volumes

Base (No additional sharedmemory)

26,176 8,192 16,384

Extension 1 104,768 16,384 65,536

Extension 2 209,600 16,384 65,536

You can determine the maximum number of pairs that can be created onyour system by calculating the number of differential and pair tables yoursystem needs to create SIz pairs. This number must be equal to or less thanthe difference of the total number of differential and pair tables in the storagesystem, minus the number of tables being used by the other products (forexample, Hitachi Compatible FlashCopy®).


The following software products also use differential tables:

• SI• Compatible FlashCopy®• Compatible FlashCopy® SE• Volume Migration• SS

The following software products also use pair tables:

• SI• Volume Migration (using migration plans)

Note: You can use CCI’s inqraid command to query the number of thedifferential tables required when you create SI pairs, though not for creatingSIz pairs. For SI, you can also query the number of differential tables notused in the storage system with this command.For more information about the inqraid command, see the Command ControlInterface User and Reference Guide.

Calculating the number of differential tables and pair tables

Calculations in the following sections assume that you are only using SIz inthe system.

The emulation type of your volumes affects the number of differential andpair tables.

To calculate the number differential and pair tables for mainframe

Total number of the differential tables per pair = ((the numberof cylinders in a volume) + (number of the control cylinders*) ×15 ÷ (20,448**)* See the following table.

** Number of the slots that can be managed by a differential table.

Round up the total number to the nearest whole number. For example, if theemulation type is 3390-3 and if the number of the cylinders of the volume is3390, then the total number of the differential tables is calculated as follows:((3,339 +6) x 15) ÷ 20,448 = 2.4537. Rounding up 2.4537 to the nearestwhole number changes it to 3. In this example, the total number of thedifferential tables for one pair is 3. Because one pair table is used for up to 36differential tables, the total number of the pair tables for a pair in thisexample is 1.

The following table shows control cylinders per emulation type.

Emulation Type Number of Control Cylinders

3380-3, 3380-3A, 3380-3B, 3380-3C 7

3390-1 5


Emulation Type Number of Control Cylinders

3390-2, 3390-3, 3390-3A, 3390-3B, 3390-3C,3390-3R

6

3390-9, 3390-9A, 3390-9B, 3390-9C 25

3390-L, 3390-LA, 3390-LB, 3390-LC 23

3390-A, 3390-M, 3390-MA, 3390-MB, 3390-MC 53

Note: You cannot perform VLL operations on OPEN-L volumes.

Having determined the number of differential and pair tables required perpair on your storage system, you can now calculate the maximum number ofpairs.

Calculating maximum number of pairs

With the calculation for the number of differential and pair tables done in theprevious topic, you can determine the maximum number of pairs yourstorage system can support.

To calculate the maximum number of pairs allowed on your system

Use the following formula:Σ(α) ≤ (β)and Σ(γ) ≤ (δ)where:

• Σ(α) is the total number of differential tables per pair (per previouscalculation).

• (β) is the number of differential tables available in the system (seeNumber of differential tables, pair tables, and volumes per additionalshared memory on page 2-6).

• Σ(γ) is the total number of pair tables per pair (per previous calculation).• δ is the number of pair tables available in the system (see Number of

differential tables, pair tables, and volumes per additional shared memoryon page 2-6).(β) and (δ) will differ according to the installed additional shared memoryfor differential tables.

For example, if you are to create 10 pairs of 3390-3 volumes and 20 pairs of3390-L volumes in a storage system that has 26,176 differential tables, thefollowing equation would be used to calculate Σ(α) and Σ(γ):

Σ(α): (3 x 10) + (24 x 20) = 510

Σ(γ): (1 x 10) + (1 x 20) = 30

Since 510 is smaller than 26,176, and 30 is smaller than 8,192, it meets theequation, Σ(α) ≤ (β) and Σ(γ) ≤ (δ), thus insuring that 10 pairs of 3390-3volumes and 20 pairs of 3390-L volumes can be created.


Planning for performancePair operations affect I/O performance on the storage system. The followinginformation is provided to help calibrate your system:

• Performance versus number of pairs. Compare the importance ofperformance with the number of pairs and copy pace (rate at which datais copied).

¢ Assigning multiple S-VOLs to a P-VOL uses more system resourcesand lowers performance.

¢ The slower the copy pace, the less impact on I/O performance; a fastpace has a greater impact on performance. (You assign copy pacewhile creating, splitting, and resynchronizing pairs.)

• Load sharing on parity groups.

¢ A parity group should contain an even distribution of P-VOLs and S-VOLs, rather than a concentration of one or the other.

¢ If you plan to perform multiple pair operations simultaneously, placethe pairs in different parity groups.

¢ For copy pace, specify Slower when you create, split, orresynchronize.

¢ If you plan to perform a copy operation on multiple pairs on the sameparity group, perform the operation on one pair at a time.

¢ If the system is overloaded, increase parity groups, cache, channeladapters (CHAs), and/or disk adapters (DKAs). Assign S-VOLs tonewly installed parity groups.

• Preparing for resynchronization by Quick Restore. During a quick restoreoperation, in which the contents of the P-VOL and S-VOLs are swapped,the RAID levels, HDD types, and Cache Residency Manager settings of thetwo volumes are also exchanged. To avoid performance impact, considerthe following:

¢ Both pair volumes should have the same RAID level and HDD typebefore performing the quick restore operation. You can resume theoriginal RAID levels after the quick restore by again splitting the pairand performing the quick restore.

¢ Set the same Cache Residency Manager settings (locations) for the P-VOL and S-VOLs before the quick restore operation.Alternatively, you can release Cache Residency Manager settingsbefore the quick restore operation, then reset them when theoperation is completed.For more information about settings, see the Hitachi Virtual StoragePlatform Performance Guide.

Caution: Do not perform the Quick Restore when the P-VOL and S-VOLs arein different CLPRs, otherwise the two volumes will be reversed when theoperation completes.


Consistency group pair-splitWith a consistency group, you perform tasks and change the pair status on agroup of pairs. This allows you to copy data from the S-VOLs in theconsistency group to the T-VOLs simultaneously. The T-VOLs will contain thesame data as the S-VOLs when the operation is performed.

With ATTIME Suspend (sometimes referred to as ATTIME Split), you candefine a specific time to split pairs in a consistency group.

The following is a list of requirements and restrictions:

• BCM is required to run this and all operations on the pairs in theconsistency group. If you have performed pair operations using the SNafter creating pairs using BCM, you cannot use consistency group pair-split.With PPRC, you can split the pairs in a consistency group but not at aspecified time. For more information about splitting pairs, see Appendix A,Pair operations using PPRC on page A-1.

• Pairs in the BCM copy group must be in an SIz consistency group.• Before using consistency group pair-split a second time, verify that the

status of all the pairs in the same consistency group is changed to thestatus specified by the YKEWAIT command.For detailed information about monitoring status changes for copy pairs ina specified copy group using the YKEWAIT command, see the BusinessContinuity Manager User’s Guide.


• You can use consistency group pair-split when SIz P-VOLs are shared withURz or TCz S-VOLs. For more information, see Consistency group pair-split for shared volumes on page 2-11.

Consistency group pair-split for shared volumesIf you share SIz S-VOLs in a storage system with TCz or URz S-VOLs, you canuse consistency group pair-split to keep the SIz T-VOLs consistent. Thefollowing illustrations show consistency group pair-split with TCz and withURz.


The following takes place when you use consistency group pair-split withshared URz volumes:

1. URz restore journal data created before the split time is restored to URzS-VOLs (SIz P-VOLs).

2. Restore journal operations are suspended when URz detects restorejournal data with a time stamp later than the split time. After the URzsuspension, the SIz split operations run.

3. When SIz split operations are completed, URz resumes the suspendedrestore journal operations.

Requirements, restrictions, and recommendations for shared volumes

The following is a list of the requirements, restrictions, and recommendationsfor using consistency group pair-split with shared TCz or URz volumes:

• BCM is required.• You must share the SIz P-VOLs with the URz or TCz S-VOLs.• The SIz pairs must be registered in the same SIz consistency group to

ensure consistent backup operations.• If you are sharing SIz P-VOLs in a storage system with URz or TCz S-

VOLs, to prevent the consistency group pair-split from ending abnormally,


ensure the status of all URz or TCz pairs in the consistency group is thesame, “DUPLEX” or “Split/SUSPOP”.

• You can perform one split operation per SIz consistency group.• The specified split time remains enabled even after the split operation on

SIz pairs is completed. Therefore, delete the registered split time beforespecifying a new split time.

• You can reset the specified split time by running PS OFF of RCU.• If you use consistency group pair-split when URz and TCz volumes are in

the following configurations, enable the time stamp transferring option ofall the TCz pairs in the journal to insure data consistency in the SIzconsistency group:

¢ 3DC Cascade configuration¢ 3DC multi-target configuration that has been switched to a cascade

configuration during disaster recovery• You cannot add pairs, resume pairs, or suspend pairs from BCM when a

split time is set for an SIz consistency group, unless you first delete thesplit time.

• URz pairs must belong to the same journal group. If multiple journalgroups are registered in one SIz consistency group, consistent backupcannot be ensured on SIz S-VOLs.

• With URz, if a pair is suspended due to a failure, URz journal data createdbefore the split time may not be restored to the URz/SIz volume after thesplit operation is completed. This is because the split time and the actualstarting time of the operation are not necessarily the same in thiscircumstance. The starting time delays according to the amount of journaldata in the journal volume at the split time. For example, if the journalvolume contains data that needs one hour to be restored, the startingtime of the split operation delays for an hour.

• With URz, three split operations can be performed per URz journal(equivalent to three SIz consistency groups).

• With URz, you can select the Quick Split or Steady Split for the SIzconsistency group pair-split operation.

• With URz, if you specify a split time, you cannot restore the URz pair.To run the Reverse Resync, delete the split times of the SIz pair whose S-VOL is related to the restore journal.For more information about the Reverse Resync, see the CommandControl Interface User and Reference Guide and Business ContinuityManager User Guide.

• With URz, if a restore journal has a timeout period that ends after thesplit time, journal data may not be detected. In this case, the SIz splitoperation runs after the timeout period.You set the timeout value according to your requirements. The defaultvalue is 6 hours.For more information, see the Business Continuity Manager User Guide.


• With URz, you can delete pairs when split time is set for an SIzconsistency group. The specified split time is deleted when you delete thefollowing pairs:

¢ All SIz pairs belonging to the SIz consistency group.¢ All URz pairs belonging to the URz restore journal.

Consistency group pair-split and supported pair statuses

The pair status for all of the SIz pairs in the consistency group determines ifyou can perform a consistency group pair-split. If all of the SIz pairs in theconsistency group are paired (“DUPLEX” status), you can perform aconsistency group pair-split.

The following table shows when you can perform a consistency group pair-split based on the SIz pairs in the consistency group that are not paired (astatus other than “DUPLEX”), and the resulting pair status after you performa consistency group pair-split.

The status of thepairs in the

consistency groupthat have a statusother than DUPLEX

Can you perform a consistencygroup pair-split?

Status after youperform a consistency

group pair-split

PENDING YES Split/SUSPOP

SP-Pend/TRANS YES2 Split/SUSPOP

V-Split/SUSPVS YES2 Split/SUSPOP

Split/SUSPOP YES2 Split/SUSPOP

Resync/PENDING NOThe command ends abnormally andshows the following information:[EX_CMDRJE] An order to thecontrol/command device wasrejected1

The pair statuses remainthe same.

Resync-R/REVRSY NOThe command ends abnormally andshows the following information:[EX_CMDRJE] An order to thecontrol/command device wasrejected1


Suspend/SUSPER NOThe command ends abnormally andshows the following information:[EX_CMDRJE] An order to thecontrol/command device wasrejected


Notes:


The status of thepairs in the

consistency groupthat have a statusother than DUPLEX

Can you perform a consistencygroup pair-split?

Status after youperform a consistency

group pair-split

1. If you share the URz S-VOL and the SIz P-VOL, the command may end normallyafter you perform a consistency group pair-split. Ensure the status of the pairswithin the consistency group have changed to “Split/SUSPOP” (use the pairdisplaycommand).

2. Consistency is guaranteed only for SIz pairs in “DUPLEX” or “PENDING” status.

The following are examples of when you can perform a consistency grouppair-split based on status of the SIz pairs in the consistency group:

• Example 1The are six SIz pairs in a consistency group. Two of the pairs are paired(“DUPLEX” status), two are in “PENDING” status, and two are in “Split/SUSPOP” status. In this case, you can perform a consistency group pair-split, and doing so changes the status of all of the pairs in the consistencygroup to “Split/SUSPOP”.

• Example 2There are two SIz pairs in a consistency group and one is paired(“DUPLEX” status) and the other is in the process of being resynchronized(“Resync/PENDING” status). In this case, you cannot perform aconsistency group pair-split.

• Example 3The are six SIz pairs in a consistency group. Two of the pairs are paired(“DUPLEX” status), two are in the process of Quick Split (“V-Split/SUSPVS” status), and two are in “Suspend/SUSPER” status. In this case,the consistency group pair-split ends abnormally and the status of all ofthe pairs in the consistency group remains the same.

Preparing for Business Continuity Manager, PPRC useYou can use BCM and PPRC to perform the same SIz pair operations.However, they are independent functions. Use one or the other.

Command deviceAssign a volume as the command device for BCM.

For more information about setting up the command device, see the BusinessContinuity Manager User Guide.

On open systems, separate the BCM command device from the commanddevice used by Command Control Interface (CCI).

The storage system uses the Missing Interrupt Handler (MIH) values as I/Omonitor time for volumes used as command devices. From the host, set aminimum MIH value of 45 (seconds).


3Sharing ShadowImage for Mainframe

volumes

You can share SIz volumes with other Hitachi software product volumes. Thistopic discusses requirements, recommendations, and restrictions for sharingvolumes.

□ Cache Residency Manager

□ Compatible FlashCopy®

□ Compatible FlashCopy® SE

□ Compatible XRC

□ Concurrent Copy

□ Dynamic Provisioning for Mainframe and Dynamic Tiering for Mainframe

□ Resource Partition Manager

□ TrueCopy for Mainframe

□ Universal Replicator for Mainframe

□ Universal Volume Manager

□ Virtual LVI

□ Volume Migration

□ Volume Retention Manager

Sharing ShadowImage for Mainframe volumes 3-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Cache Residency ManagerYou can use volumes with Cache Residency Manager settings as SIz P-VOLsand S-VOLs.

Note: For important information about the operation and volumes with CacheResidency Manager settings, see the bullet on Quick Restore in Planning forperformance on page 2-9.

Compatible FlashCopy®You can share an SIz S-VOL with a Compatible FlashCopy® S-VOL. This isthe only configuration possible with Compatible FlashCopy®.

• You can perform the following SIz operations: Add pair, Split pair,Suspend Pair, Resynchronize Pair, Delete Pair

• You cannot perform the following SIz operations: Reverse Resync, QuickRestore

• Establishing and deleting Compatible FlashCopy® relationships are theonly operations allowed on volumes shared with SIz. The SIz pair cannotbe in Resync-R/REVRSY.

• If you are sharing volumes, you can create the number of pairs supportedby each software application:

¢ SIz: 3¢ Compatible FlashCopy®: 16

For more information, see the Hitachi Compatible FlashCopy® User Guide.

Compatible FlashCopy® SEFor information, see the topic on interoperability in the Hitachi CompatibleFlashCopy® User Guide.

Compatible XRCIf an SIz S-VOL and a Compatible XRC source volume (original data) sharethe same volume, you cannot perform the Reverse Copy or Quick Restoreoperation.

Caution: Do not use Compatible XRC T-VOLs (copied data) for SIz volumes.

3-2 Sharing ShadowImage for Mainframe volumesHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Concurrent CopyIf SIz S-VOLs and Concurrent Copy source volume (original data) share thesame volumes, you cannot perform the Reverse Copy or Quick Restoreoperation for those volumes.

Note: Do not use Concurrent Copy T-VOLs (copied data) for SIz volumes.

Dynamic Provisioning for Mainframe and Dynamic Tieringfor Mainframe

You can share Hitachi Dynamic Provisioning for Mainframe (HDPz) and HitachiDynamic Tiering for Mainframe software (HDTz) volumes with SIz P-VOLs andS-VOLs. HDPz and HDTz volumes with SIz reserved volumes. The followingrestrictions apply:

• You should share HDPz and HDTz volumes with both the SIz P-VOL and S-VOLs, rather than one or the other.

• If you share an HDPz or HDTz volume with only the P-VOL, or only the S-VOL, you cannot perform the Quick Restore operation.To perform the Quick Restore, both P-VOL and S-VOLs must be sharedwith HDPz or HDTz volumes.

• You cannot perform SIz pair operations while increasing HDPz or HDTzvolume capacity.

Resource Partition ManagerYou can specify volumes in a Resource Partition Manager resource group asSIz P-VOLs and S-VOLs. However, ensure the resource group is assigned toone of your user groups. The resource group must be assigned to a usergroup for which your user account has privileges.

Note: For mainframe systems, you can only access one resource group froma host. Therefore, ensure that the resource group volumes you use as P-VOLsand S-VOLs are in the group that can be accessed by the host.

For more information about Resource Partition Manager, see the ProvisioningGuide for Mainframe Systems

TrueCopy for MainframeYou can share TCz volumes with SIz volumes.

• You can share SIz P-VOLs and S-VOLs with TCz P-VOLs and S-VOLs.However, you cannot share an SIz S-VOL with a TCz S-VOL.

• When you share an SIz P-VOL with a TCz S-VOL, the write operation onthe TCz P-VOL takes more time. This is especially true when the SIz pair


is in the V-Split status because of the copying time needed for the SIzpair.

Note: When using PPRC, the “Split” status cannot be distinguished fromthe “V-Split” status. Complete the following:

• Using the CSUSPEND command, specify MFS00 for the PRIMparameter to perform the Steady Split operation. In this case the pairstatus will not be V-Split.

• Use SN to check whether the pair status is “Split” or “V-Split”.• You can perform the Quick Restore operation on an SIz pair when the TCz

pair is suspended.• The SIz P-VOL can be shared with TCz volumes in a 3 data center

configuration. For more information, see Sharing volumes in a 3-TCz/URzDC cascade configuration on page 3-10.

• If the SIz P-VOL’s emulation type is 3390 and the SIz S-VOL and TCz M-VOL are shared, you cannot use the SIz P-VOL to create another SIz pair.

• You can use the consistency group pair-split operation on SIz pairs whosevolumes are shared with TCz S-VOLs. For more information, seeConsistency group pair-split for shared volumes on page 2-11.

For more information about sharing SIz and TCz volumes, see the section onsharing volumes with SIz in the Hitachi TrueCopy® for Mainframe UserGuide.

Universal Replicator for MainframeYou can share URz volumes with SIz volumes.

• You can share SIz P-VOLs with URz P-VOLs and S-VOLs.• You cannot share SIz S-VOLs with URz S-VOLs.• You cannot share SIz pair volumes with URz journal volumes.• You cannot perform the Quick Restore operation on the SIz pair when the

URz pair is suspended.• You can use PPRC to query pair status for SIz and URz shared volumes.

The storage system reports the SIz status. Use BCM to obtain URz’s pairstatus.

• You can share SI volumes with UR volumes in a 3 UR data centerconfiguration. For more information, see Sharing volumes in 3-URz datacenter configurations on page 3-5.

• You can share the SIz P-VOL with URz and TCz volumes in a 3 URz/TCzdata center configuration. For more information, see Sharing volumes in a3-TCz/URz DC cascade configuration on page 3-10.

• You can use the consistency group pair-split operation on SIz pairs whosevolumes are shared with URz S-VOLs. For more information, seeConsistency group pair-split for shared volumes on page 2-11.


For more information about sharing SIz and URz volumes, see the relatedappendix in the Hitachi Universal Replicator for Mainframe User Guide.

Sharing volumes in 3-URz data center configurationsYou can share SIz pair volumes with URz volumes in the following 3-URz datacenter (3DC) configurations:

• Multi-target• Delta-resync• Cascade

These sections describe the configurations and supported SIz operations.

For more information about these configurations, see the Hitachi UniversalReplicator for Mainframe User Guide.

Sharing volumes in a 3-URz DC multi-target configuration

You can share SIz volumes with URz volumes in 3 DC multi-targetconfigurations. You can share the SIz P-VOL and S-VOLs with URz volumes,as shown in the following figure.

Figure 3-1 SIz volumes in a 3-URz DC multi-target configuration

In these configurations, SIz pair operations are dependent on the pair statusof the URz local-intermediate pair and the local-remote pair.

The following table shows the supported SIz operations when the P-VOL isshared with URz P-VOL.


URz local-intermed.pair status

URz intermed.-remote pair

status

SIz operations

Create, Split, Suspend, Delete,Resync--Normal Copy, Quick Resync

Resync --Reverse

Copy,

Resync --Quick

Restore

DUPLEX,PENDING*,and Suspend/SSWS

DUPLEX orPENDING

YES NO NO

DUPLEX orPENDING

Suspend/SSWS YES NO NO

Suspend/SSWS

Suspend/SSWS YES YES NO

* You cannot perform SIz operations if the status for both URz pairs is “PENDING”.

The following table shows the supported SIz operations when the S-VOL isshared with URz P-VOL.


URzintermed.-remote pair

status

SIz operations

Create Split Suspend,Delete

Resync

Normal Copy,Quick Resync,Reverse Copy

QuickRestore

DUPLEX,PENDING*, orSuspend/SSWS

DUPLEX orPENDING*

NO NO YES NO NO

DUPLEX orPENDING

Suspend/SSWS

NO NO YES NO NO

Suspend/SSWS

Suspend/SSWS

NO YES YES YES NO


The following table shows the supported SIz operations when the P-VOL isshared with URz S-VOL (intermediate or remote site).

URz* pairstatus

SIz operations


Resync -- ReverseCopy, Quick

Restore

DUPLEX orPENDING

YES NO

Suspend/SSWS YES YES

* Note:• If the SIz P-VOL is shared with the intermediate site’s URz S-VOL, then check URz status for the

local-intermediate pair.


URz* pairstatus

SIz operations



Restore

• If the SIz P-VOL is shared with the remote site’s URz S-VOL, then check URz status for the local-remote pair.

Sharing volumes in a 3-URz DC cascade configuration

You can share SIz volumes with URz volumes in 3 DC cascade configurations.You can share SIz P-VOL and S-VOLs with URz volumes, as shown in thefollowing figure.

Figure 3-2 SIz volumes in a 3-URz DC cascade configuration

When associated with these configurations, SIz pair operations are dependenton the pair status of the URz local-intermediate pair and the local-remotepair.

The following table shows the SIz operations that you can perform when theP-VOL is shared with URz P-VOL at local site.

URz local-intermed. pair

status

SIz operations


Resync--Reverse Copy andQuick Restore

DUPLEX orPENDING

YES NO


The following table shows the SIz operations that you can perform when theS-VOL is shared with URz P-VOL at local site.


URz local-intermed. pair statusSIz operations

Paircreate Pair split Suspend,

Delete Resync - all types

DUPLEX NO NO YES NO

PENDING NO NO YES NO

Suspend/SSWS NO YES YES YES

The following table shows the SIz operations that you can perform when theP-VOL is shared with URz S-VOL/P-VOL at intermediate site.


URzintermed.-remote pair

status

SIz operations


Resync --Reverse

Copy,

Resync --Quick

Restore

DUPLEX,PENDING*,and Suspend/SSWS

DUPLEX orPENDING

YES NO NO

DUPLEX orPENDING

Suspend/SSWS YES NO NO

Suspend/SSWS

Suspend/SSWS YES YES NO


The following table shows the SIz operations that you can perform when theP-VOL is shared with URz S-VOL at remote site.

URz intermed.-remote pair

status

SIz operations



Restore

DUPLEX orPENDING

YES NO


Sharing volumes in 3-URz/TCz data center configurationsYou can share SIz pair volumes with URz and TCz volumes in the following 3-URz/TCz DC configurations:

• Multi-target• Cascade

These sections describe the configurations and supported SIz operations.


For more information about these configurations, see the Hitachi UniversalReplicator for Mainframe User Guide.

Sharing volumes in 3-URz/TCz DC multi-target and delta resync configurations

You can share SIz P-VOL with TCz and URz volumes at the intermediate andremote sites in 3DC multi-target and delta resync configurations, as shown inthe following figure.

Note: TCz volume designations are main volume, M-VOL, and target volume,T-VOL.

The SIz operations that you can perform depend on the pair status of theother pairs.

The following table shows supported SIz operations at the intermediate site.

TCz local-intermed.

pairstatus

URz deltaresync pair

status

SIz operations

Create, Split, Suspend, Delete,Resync--Normal Copy, Quick

Resync

Resync --Reverse

Copy,

Resync-- QuickRestore

DUPLEX orPENDING

HOLD YES NO NO

DUPLEX orPENDING

HLDE YES NO NO

Suspend/SSWS

HOLD YES YES NO

Suspend/SSWS

HLDE YES YES NO

The following table shows supported SI operations at the remote site.


URz local-remote

pairstatus

URz deltaresync pair

status

SI operations

Create, Split, Suspend, Delete,Resync--Normal Copy, Quick

Resync

Resync --Reverse

Copy,

Resync-- QuickRestore

DUPLEX orPENDING

HOLD YES NO NO

Suspend/SSWS

HOLD YES YES NO

Sharing volumes in a 3-TCz/URz DC cascade configuration

You can share SIz P-VOL with TCz and URz pairs at the intermediate site in3DC cascade configurations, as shown in the following figure.

Figure 3-3 URz, TCz, and SIz Shared Volume Configuration 1


Figure 3-4 URz, TCz, and SIz Shared Volume Configuration 2

You can perform all SIz operations, with the following exceptions, in theintermediate site, irrespective of TCz pair status. The URz delta resync pair’sstatus must be HOLD or HLDE:

• You can perform Reverse Copy only when the TCz and URz pair status isSuspended.

• You cannot perform the Quick Restore.

Universal Volume ManagerIf you use SIz with UVM, you can create pairs to use the external volumes.

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

Virtual LVIYou can assign Virtual LVI volumes to SIz pairs, provided that the T-VOL hasthe same capacity as the S-VOL.

Volume MigrationYou can assign the following SIz volumes to Volume Migration migrationvolumes:

• L1 P-VOL with up to two S-VOLs.• L2 P-VOL with one S-VOL.


• Reserved volumes.

To assign or reserve SIz volumes to Volume Migration migration volumes,complete the following:

1. Delete the SIz pairs.2. Unreserve the reserved SIz S-VOLs.3. Assign the SIz volumes to Volume Migration migration volumes.

You cannot use SIz volumes for destination volumes.

You cannot use migration, destination, and reserved volumes of VolumeMigration for SIz pair operations. To perform SIz operations, you must firstrelease the Volume Migration volumes.

You can assign SIz volumes as Volume Migration volumes, with the followingrestrictions:

• If the SIz S-VOL is paired with three T-VOLs, you must delete the pairbefore migrating the volumes with Volume Migration.

• If you want to assign SIz volumes as destination volumes of a migrationusing Volume Migration, or reserve SIz volumes for Volume Migration,you must delete the SIz volumes or un-reserve them before using VolumeMigration.

• If you assign a SIz S-VOL that is paired with three T-VOLs as a migrationvolume, or assign SIz volumes to volumes other than Volume Migrationmigration volumes, the command is rejected.

• If you split a SIz pair in which the volumes are assigned as migrationvolumes, migration of those volumes is canceled.

Volume Retention Manager

Access attributes and ShadowImage for Mainframe operationsYou can create SIz pairs using volumes for which you set access attributeswith Volume Retention Manager. However, depending on the access attribute,you cannot perform SIz pair operations and reserve attribute changeoperations.

You can also set access attributes for SIz P-VOLs, S-VOLs, and reservevolumes. See the following tables for SIz pair operations and reserveattribute change operations after access attribute setting as well.

Note: The Volume Retention Manager access attributes of volumes do notchange as a result of SIz operations. Even though the Quick Restoreoperation reverses the P-VOL and S-VOL, the access attributes of the P-VOLand S-VOL are not reversed.

The following table shows the SIz pair operations you can perform forvolumes for which access attributes are set with Volume Retention Manager.


Volume access attributes specifiedfor the SIz pair SIz operations

P-VOL S-VOLCreate, Split,

Suspend, Resync(forward)

Resync(reverse) Delete

Read/Write

Read/Write or Read Only YES YES YES

Protect NO NO YES

ReadOnly

Read/Write or Read Only YES YES YES

Protect NO NO YES

Protect Read/Write, Read Only, orProtect

NO NO YES

The following table shows the SIz reserve attribute change operations youcan perform for volumes for which access attributes are set with VolumeRetention Manager.

Volume accessattributes specified by

SIz

SIz reserve attribute change operation

Setting reserve attribute Removing reserve attribute

Read/Write or Read Only YES YES

Protect NO YES

ShadowImage for Mainframe pair statuses and access attributesetting

You can use Volume Retention Manager to set access attributes to SIz P-VOLsand S-VOLs.

For SIz reserve volumes, you can set all of the following Volume RetentionManager access attributes:

• Read/Write• Read Only• Protect

Caution: For 3390-A volumes, an attempt to set the Read Only attribute orProtect attribute on a P-VOL or S-VOL may result in termination of copyprocessing or pair suspension.


4Performing configuration operations

This chapter provides instructions for configuring SIz.

□ Configuration workflow

□ Setting up primary and secondary volumes

□ Reserving secondary volumes

□ Reserving a consistency group

□ System options that affect performance

Performing configuration operations 4-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Configuration workflow Setup for SIz consists of the following operations. You must have StorageAdministrator (Local Copy) role to perform SIz operations.

• Setting up primary and secondary volumes on page 4-2.• Reserving secondary volumes on page 4-2. (Optional.)• Reserving a consistency group on page 4-3. (Optional.)• System options that affect performance on page 4-4. (Optional.)

Setting up primary and secondary volumesThe P-VOL and S-VOLs must be set up prior to making copies. Ensure thatthe volumes you plan to use meet the requirements for pair volumes inPlanning pair volumes on page 2-5.

Reserving secondary volumesThis is an optional feature that allows you to reserve SMPL volumes for use asS-VOLs. The storage system rejects write I/Os to reserved volumes (exceptin “Split/SUSPOP” status).

Prerequisite information

Volumes must be:

• In SMPL status• Unreserved and unpaired

1. In the tree, click Replications > Local Replications, then click theReserve Volumes tab.

2. In the Reserve Volumes tab, click Add Reserve Volumes.3. In the Add Reserve Volumes window/Available LDEVs table, select

the LDEV you want for a reserved volume and click Add. This actionmoves the LDEV to the Selected LDEVs table.

4-2 Performing configuration operationsHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

4. Click Finish.5. In the Confirm window, enter a Task Name then click Apply.

Related information

• Removing reserve attribute from a volume on page 6-9

Reserving a consistency groupA consistency group number is required when assigning pairs to a consistencygroup. Once you have assigned pairs to a consistency group, you can performpair operations on the pairs in the group, including consistency group pair-split.


• The consistency group must be created before reserving it, using BCM.

1. In the tree, click Replications > Local Replications, then click theConsistency Group tab.

2. In the Consistency Group window, click Reserve Maintenance CTGs.3. In the Reserve Maintenance CTGs window’s Available Consistency

Groups table, select the consistency group you want to reserve and clickAdd. This action moves the consistency group to the SelectedConsistency Groups table.



Related information

• Releasing a reserved consistency group on page 6-9

System options that affect performanceYou can enable and disable the following options that affect performance. (Togo directly to the procedure, see Setting performance options on page4-5).

• Swap&Freeze. Alters the behavior of the quick restore operation. WithSwap&Freeze, update copy operations are suppressed when the quickrestore is completed and the pair is in “DUPLEX” status. Differential datais not copied to the new S-VOL. Use the Swap&Freeze option when youwant to keep S-VOLs unchanged after the quick restore operation.

• Host I/O Performance. Increases I/O performance while suppressingcopy processing. However, be aware that enabling this option results in alonger copy time, slowing copy processing.

• Copy Threshold. Temporarily stops copy operations when the workloadon the storage system is heavy. This is done to minimize degradation tohost I/O performance during peak periods. The option performs onlywhen workload is heavy; the Host I/O Performance option suppressescopy operations at all times regardless of workload level.When the Copy Threshold Option is enabled, it is effective for all of thefollowing software:

¢ SI¢ SIz¢ Compatible FlashCopy®¢ HTI¢ SS¢ Volume Migration

Note: Your service representative must enable the Copy Thresholdoption.

• Copy Pace options. Reduce the effect on host I/O performance bysuppressing copy processing in “DUPLEX” status. The system uses thisoption when pairs are in “DUPLEX” status only. This option does not havean effect if the pair is in other statuses.You can choose from three levels of processing-suppression/performance-improvement:

¢ Copy Pace Ext. None (usable since program version 70-03-01-xx/xx). This is the most effective option—stops copy processing.

Note: With this option, synchronization when a pair is split tends tobe slower, which prolongs the time that the pair is in process of QuickSplit (“V-Split/SUSPVS” status) or in the process of Steady Split (“SP-


Pend/TRANS” status). If this poses a problem, complete one of thefollowing:

• Minimize the time that the pair is in “DUPLEX” status so thatsynchronization at the pair split does not require so much time.

• Use one of the other Copy Pace options.¢ Copy Pace Ext. Slower2—2nd most effective¢ Copy Pace Ext. Slower1—3rd most effective

Setting performance options1. In the tree, click Replications > Local Replications.2. In the Local Replications window, click Edit Local Replica Options.3. In the Edit Local Replica Options window, for System Type, select

Mainframe.

4. In the System Options list, select the option you want and click Enable.You may need to scroll down to the option you want. Copy Thresholdmust be enabled by your service representative.



5Performing pair operations

This chapter provides instructions for performing SIz pair operations usingSN. Also included is an operation for splitting pairs by consistency group,using CCI.

□ Pair operations workflow

□ Check pair status

□ Pair creation

□ Suspending pair creation

□ Pair split

□ Pair resynchronization

□ Pair deletion

Performing pair operations 5-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Pair operations workflowA typical workflow for performing pair operations consists of the following.You must have Storage Administrator (Local Copy) role to perform SIzoperations.

• Check pair status on page 5-2. Each operation requires a pair to have aspecific status. You also check pair status to ensure that an operationcompleted successfully.

• Pair creation on page 5-2, in which the S-VOL becomes a duplicate ofthe P-VOL. You can create a pair and immediately split it so that you canaccess the S-VOL.

• Suspending pair creation on page 5-8.• Pair split on page 5-8, which separates the P-VOL and S-VOLs and

allows use of S-VOL data by secondary applications.• Splitting pairs in a consistency group on page 5-11, which allows you to

split pairs in a consistency group at a specified time.• Pair resynchronization on page 5-11, in which the S-VOL is again

updated from the P-VOL.• Pair deletion on page 5-15 in which the pair relationship between the

pair volumes is ended, though the data remains.

Check pair statusEvery pair operation requires the pair to have a specific status. When youwant to perform a pair operation, check pair status to ensure that you canproceed successfully.

• For pair status definitions and instructions for finding pair status, seeMonitoring the system on page 6-2.

• For the operations allowed for specific pair statuses, see Status, pairoperations permitted on page 6-5.

Pair creationWhen you create the initial copy, data in the P-VOL is copied to the S-VOL.During the operation, the P-VOL can receive updates from the host. After theinitial copy is completed, the updated data in the P-VOL—differential data—iscopied to the S-VOL periodically (update copy).

You can create the pair and immediately split it so that you can have instantaccess to the S-VOL. Instructions are included in the procedure.

Related information

• Prerequisite information for creating pairs on page 5-3• Creating pairs on page 5-4

5-2 Performing pair operationsHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Prerequisite information for creating pairs• Make sure that your volumes are set up for pairing. For more information,

see Planning pair volumes on page 2-5.• Volumes should be in SIMPLEX status.• If the P-VOL is already paired with other S-VOLs, before creating the new

pair, check the permitted status of existing S-VOLs. For more information,see Status of unaffected S-VOLs, operations permitted on page 6-5.

• Because pair creation affects performance on the host, observe thefollowing:

¢ Create a pair when I/O load is light.¢ Limit the number of pairs that you create simultaneously.

• When you create a pair, the S-VOL’s LDEV is allocated to the sameprocessor blade to which the P-VOL’s LDEV is allocated.

• The paircreate operation overwrites all existing data on the S-VOL. Theuser is responsible for backing up data on the S-VOLs before creatingpairs.

• If you use BEDs supporting encryption, you can create an SIz pair byusing an encrypted volume and a non-encrypted volume. For example,you can create the pair specifying an encrypted volume as the P-VOL anda non-encrypted volume as the S-VOL. In this case, data in the encryptedP-VOL becomes non-encrypted data in the S-VOL.

• In the Create Pairs wizard, specify pair configuration settings thatrequire additional explanation.For more information on setting up pair configurations, see SIz pairconfiguration in Create Pairs wizard on page 5-3.

• The P-VOL and S-VOLs must be the same size in blocks. If the capacity isdisplayed in gigabytes, a small difference between P-VOL and S-VOLcapacity might not be displayed.To view the capacity in blocks, click Options > Capacity Unit > Cyl inthe Logical Devices window, or for a secondary window, look at theCapacity (Cyl) area of the Detail window.

SIz pair configuration in Create Pairs wizardSIz pair configuration uses the following process:

1. In the Create Pairs wizard, you will enter the number of S-VOLs that youwant to pair. You will set this number according to the pair with thehighest number of S-VOLs.

2. If you are creating pairs with different numbers of S-VOLs, you willspecify the highest number, even when some pairs will not have thatmany S-VOLs.

3. You will remove volumes later in the Create Pairs wizard (see Example 3on page 5-4).


Example 1

When you create a pair using one P-VOL and one S-VOL, the Number ofSecondary Volumes is set to 1.

When using one P-VOL and three S-VOLs (the maximum), the Number ofSecondary Volumes is set to 3.

Example 2

You may want to add a new S-VOL to an existing pair, as shown in thefollowing figure. In this case, the Number of Secondary Volumes is set to2.

Example 3

If you wanted to create one pair with two S-VOLs, and another pair with oneS-VOL at the same time, set the Number of Secondary Volumes at 2. Inthis case, the system operates on the assumption that you are creating twopairs, each having two S-VOLs.

Use the following workflow:

1. In the Pair Configuration window, set Number of SecondaryVolumes at 2.

2. In the Select Primary Volume window, select two LDEVs as P-VOLs.3. In the Select Secondary Volumes window, select 3 LDEVs from the

Available LDEVs table as the S-VOL.4. In the Selected Pairs table, delete the unwanted row by selecting it and

clicking Remove.

Creating pairs1. In the tree, click Replications > Local Replications.


2. In the Pairs tab, click Create Pairs.3. In the Select Pair Configuration window of the Create Pairs wizard,

select the Copy Type, ShadowImage for Mainframe.

4. Select the Emulation Type.5. In Number of Secondary Volumes, enter the number of S-VOLs

according to the P-VOL with the highest number of S-VOLs that you aresetting up during this procedure.For more information, see SIz pair configuration in Create Pairs wizard onpage 5-3.

6. Select an Initial MU Number.7. In Split Type, you have the option of splitting the pair once it is created.

Select one of the following:

¢ Non Split: Does not split the new pair.¢ Quick Split: The new pair is split prior to data copy so that the S-VOL

is immediately available for read and write I/O. Any remainingdifferential data is copied to the S-VOL in the background.

¢ Steady Split: Splits the new pair after all differential data is copied tothe S-VOL.

8. In Copy Pace, select the pace at which data is to be copied, Slower,Medium, or Faster. Processing speed and system performance areaffected by the pace you select; you see slower speed and betterperformance with Slower, faster speed but more impact to performancewith Faster.

9. Click Next.10. In the Select Primary Volumes window, in the Available LDEVs table,

select an LDEV to be a P-VOL, then click Add. The LDEV is moved to theSelected LDEVs table. You can make multiple selections.


11. Click Next.12. In the Select Secondary Volumes window, assign LDEVs as S-VOL to

the P-VOL LDEV (or LDEVs) selected in the Select Primary Volumeswindow.Complete the following:

¢ If you specified a P-VOL, select a secondary LDEV ID in theAvailable LDEVs table, and click Set. Repeat this step to assignadditional S-VOLs.

¢ If you specified more than one P-VOL, select an LDEV ID in theAvailable LDEVs table, then select a P-VOL LDEV ID in theSelected Pairs table, and click Set.Repeat this step as many times as needed to make all your pairings.By not selecting a P-VOL in the Selected Pairs table, the S-VOL youselect and set is assigned to P-VOLs in order from the first line of thetable.


¢ To sort the Available LDEVs and Selected Pairs tables according tothe capacity, click Capacity near the top of the window.

¢ The remaining number you have to select refers to the P-VOLsthat do not have an assigned S-VOL, as seen in the Selected Pairstable.

¢ Sort in the middle-left allows you to sort the Selected Pairs table.¢ Change Options in the middle-right allows you to change Split Type

and Copy Pace (applies to all new pairs).¢ To change MU numbers, complete the following:

a. Select the desired primary/secondary line in the Selected Pairstable.b. Click Edit Mirror Unit near the bottom-right after specifying S-VOL.

¢ To remove a line from the Selected Pairs table, select the line andclick Remove. For more information on removing rows to alter pairconfiguration, see Example 3 on page 5-4.

13. Click Finish.14. In the Confirm window, type a Task Name then click Apply.

After creating the pair, if you do not see the number of pairs and otherinformation you expect to see in the Summary tab of the LocalReplications window, the system is working and requires more time. Wait alittle longer, then click File/Refresh.


Suspending pair creationYou can suspend a pair create operation (initial copy). When this is done, pairstatus changes to “Suspend/SUSPER”. The S-VOL continues accepting writeI/O operations from the P-VOL and marks the entire P-VOL track as differencedata. Resynchronizing a suspended pair change the pair status to “Resync/PENDING” and copies the entire P-VOL to the S-VOL. Resynchronizing asuspended pair takes the same time as the initial copy operation.

The storage system automatically suspends a pair when it detects an errorcondition related to an update copy operation, or when it cannot keep thepair mirrored.

1. In the tree, click Replications > Local Replications.2. In the Pairs tab, select the pair you want to suspend, and click More

Actions > Suspend Pairs.3. In the Suspend Pairs window, type a Task Name and click Apply.

Pair splitHost updates to the P-VOL and periodic copying to the S-VOL continue untilthe pair is split. After the pair is split, updates continue to the P-VOL but arenot copied to the S-VOL; data in the S-VOL is ensured at the time of the split.Update data that accrues during the split is stored in differential bitmaps untilit is copied to the S-VOL during resynchronization.

The P-VOL and S-VOL are synchronized when the pair status changes from“V-Split/SUSPVS” or “SP-Pend/TRANS” to “Split/SUSPOP”.

Related information

• Types of split operations on page 5-9


• Prerequisite information for splitting pairs on page 5-9• Splitting pairs on page 5-10• Splitting pairs in a consistency group on page 5-11

Types of split operationsThe following options are available when splitting a pair:

• Non split, which does not split the pair.• Steady split, which copies all differential data to the S-VOL and then

splits the pair.• Quick split, in which the pair is immediately split, so that the S-VOL is

immediately available for read and write I/O. Remaining differential datais copied to the S-VOL in the background.

• Consistency group pair-split, in which all pairs in a consistency groupare split simultaneously. You can use this method with CCI, BCM, orPPRC. For more information, see Appendix A, Pair operations using PPRCon page A-1.If you are using BCM, ATTIME Suspend allows you to perform aconsistency group pair-split at a specified time. The split time indicatesthe time when you want to mirror P-VOL data in the S-VOL.For split operations with BCM, both Quick Split and Steady Split areavailable.

Prerequisite information for splitting pairs• Pair status must be one of the following:

¢ “DUPLEX”, or “PENDING”, when splitting an existing pair.¢ “SIMPLEX”, when creating and immediately splitting a pair.

• The P-VOL and S-VOL are synchronized when pair status changes from“SP-Pend/TRANS” or “V-Split/SUSPVS” to “Split/SUSPOP”.

• To ensure that the data in the P-VOL matches data in the S-VOL after thepair split, stop write operations from the host server to the P-VOL beforerunning the operation.

• For a split operation to complete faster on an existing pair, stop hostaccess to the P-VOL before starting the split.

Related information

• Split/SUSPOP, performance, and SOM 459 on page 5-9

Split/SUSPOP, performance, and SOM 459Performance can be affected for pairs that are in “V-Split/SUSPVS” or “SP-Pend/TRANS” status depending on the following:

• Whether system option mode 459 is enabled.


• Whether the S-VOL is an external or internal volume.• Whether the S-VOL is a volume in a Hitachi Dynamic Provisioning pool.

The following table shows the affects of these conditions.

System option mode459 S-VOL* V-Split/SUSPVS or SP-Pend/TRANS

status

OFF Internal volume Pair status changes to “V-Split/SUSPVS”after differential data is copied to thecache in the storage systemExternal volume

ON Internal volume

External volume Pair status changes to “Split/SUSPOP”after differential data is copied to thecache in the storage system anddestage to the external storage systemhas completed.

* This function does not work if the S-VOL’s emulation type is 3390-A.

Splitting pairs1. In the tree, click Replications > Local Replications.2. In the Pairs tab, select the pair you want to split, then click Split Pairs.3. In the Split Pairs window, select a Split Type.

Values: Quick Split or Steady SplitFor more information, see Types of split operations on page 5-9.

4. In Copy Pace, select the pace at which data is to be copied.Values: Slower, Medium, or Faster.


Processing speed and system performance are affected by the pace youselect; you see slower speed and better performance with Slower, fasterspeed but more impact to performance with Faster.

5. Click Finish.6. In the Confirm window, type a Task Name then click Apply.

Splitting pairs in a consistency groupUse consistency group pair-split to simultaneously split all the pairs in aconsistency group.

If you use BCM, you can split the pairs at a specified time. With PPRC, youcan split the pairs in a consistency group, but without a specified time. Formore information, see the instructions in Appendix A, Pair operations usingPPRC on page A-1.


For requirements and restrictions, see Consistency group pair-split on page2-10.

For more information about splitting pairs, see Splitting pairs in a consistencygroup on page E-6. For more information about troubleshootingconsistency group pair-split and the consistency group pair-split option, seeTroubleshooting consistency group pair-split on page 7-13.

1. Define a consistency group for the SIz pairs that you are splitting.

a. Specify the consistency group as a BCM copy group and select a splittype: Quick Split or Steady Split.

b. If you register the split time, the split type changes to Quick Split.For more information about splitting pairs and the split type, see Splittingpairs, creating and splitting pairs on page E-4.

2. Specify the consistency group pair-split option, then create the pairs.3. Ensure that all SIz pairs in the consistency group are in “DUPLEX” or

“PENDING” status.4. Split the pairs in the consistency group.

The pairs are split simultaneously.

Note: You cannot maintain SIz S-VOL consistency if you are sharing an SIzP-VOL with URz S-VOLs and you have included SIz pairs in a status otherthan “DUPLEX” or “PENDING” in the consistency group.

Pair resynchronizationYou resynchronize a pair that is split or suspended by the system.Resynchronizing updates the S-VOL so that it is again paired with the P-VOL.


Caution: Resynchronizing the pair does not guarantee that P-VOL data is thesame as S-VOL data. Data in the two volumes is the same only if the P-VOL isoffline and the pair has been split (“Split/SUSPOP” status).

Related information

• Types of resync operations on page 5-12• Prerequisite information for resynchronizing on page 5-13• Resynchronizing pairs on page 5-14

Types of resync operationsYou can resynchronize pairs from P-VOL to S-VOL and from S-VOL to P-VOL.The types of resync operation follow, with requirements and restrictions:

• Normal Copy. Forward full resync, from P-VOL to S-VOL.

¢ The P-VOL is accessible to hosts for both read and write operations.¢ The S-VOL is inaccessible to hosts.¢ After performing a Quick Split, wait 20 seconds before a Normal Copy

resynchronization, otherwise the operation might end abnormally.• Quick Resync. Forward resync from P-VOL to S-VOL but does not data

copy. The status changes to “DUPLEX” but does not resynchronize thedata to the S-VOL.

¢ Differential data is copied to the S-VOL during update copying.¢ The P-VOL is accessible to hosts for read and write operations. The S-

VOL is inaccessible to all hosts.¢ Data in the P-VOL and S-VOL might not be the same after a Quick

Resync even when there a host I/O is not present during theoperation. Split the pair to ensure that data is the same.

¢ After performing a Quick Split, wait 20 seconds before a Quick Resyncresynchronization, otherwise the operation might end abnormally.

• Reverse Copy. Reverse full resync from S-VOL to P-VOL.

¢ The P-VOL is inaccessible to hosts.¢ All differential data is updated to the P-VOL.¢ Pairs sharing the same P-VOL must be in “Split/SUSPOP” or “Suspend/

SUSPER” status.¢ If the pair shares a volume with TCz or URz, you must suspend the

TCz or URz pair to perform the Reverse Copy or Quick Restoreoperation.

¢ You cannot create a TCz or URz pair with a volume shared by SIzduring the Reverse Copy or Quick Restore operation.

¢ When the Reverse Copy or Quick Restore is in progress, you cannotcreate, split, or resync any pair sharing the same P-VOL. However,the pairs can be deleted or suspended.

¢ Reverse Copy cannot be used for the following:


- SI L2 pair- ShadowImage for Mainframe (SIz) pair when the P-VOL is sharedwith an FCv2/FCSE volume

• Quick Restore, P-VOL and S-VOL are swapped. NO data is copied, andthe pair is placed in “DUPLEX” status. Differential data is copied to the S-VOL during update copy operations.

¢ Differential data is copied during update copying.¢ The P-VOL and S-VOL are inaccessible during this operation. When the

operation completes, the P-VOL is accessible.¢ Pairs sharing the same P-VOL must be in “Split/SUSPOP” or “Suspend/

SUSPER” status.¢ When there is a small amount of differential data between P-VOL and

S-VOL, the Reverse Copy operation may complete faster than theQuick Restore operation.

¢ Performing LDEV maintenance during the Quick Restore processincreases the time for the operation to complete.

¢ If the pair shares a volume with TCz or URz, you must suspend theTCz or URz pair to perform the Reverse Copy or Quick Restoreoperation.

¢ You cannot create a TCz or URz pair with a volume shared by SIzduring the Reverse Copy or Quick Restore operation.

¢ When the Reverse Copy or Quick Restore operation is in progress, youcannot create, split, or resync any pair sharing the same P-VOL.However, the pairs can be deleted or suspended.

¢ Quick Restore cannot be used for the following:- When a quick format is being performed on either pair volume- A pair in which one volume is a DP-VOL, though not both- On a Cross OS File Exchange pair- A SIz pair whose P-VOL is shared with an FCv2/FCSE volume

Prerequisite information for resynchronizing• For Normal Copy and Quick Resync, the S-VOL must be offline.• For Reverse Copy and Quick Restore, the P-VOL must be offline.• For Reverse Copy or Quick Restore, the pair must be in “Split/SUSPOP”

status.• The pairresync normally takes less time when the pair is in “Split/

SUSPOP” status than when it is in “Suspend/SUSPER”. This is because theamount of differential data accumulated for a split pair is usually muchless than the total amount of data in the P-VOL, which must be copied infull when the pair was suspended by the storage system.

• To keep the P-VOL and S-VOL unsynchronized when performing a QuickRestore, enable the Swap&Freeze option prior to performing theoperation. Update copy operations are then suppressed when the QuickRestore is completed, and the pair is in “DUPLEX” status.


• If a pair consists of encrypted volumes and a non-encrypted volume, andthe Quick Restore is run, the P-VOL and S-VOL encryption statuses arereversed.

• With a Quick Restore, SN can show outdated information. Click RefreshView to ensure the most up-to-date information.

Resynchronizing pairs1. In the tree, click Replications > Local Replications.2. In the Pairs tab, select the pair you want to resynchronize, then click

Resync Pairs.3. In the Resync Pairs window, select a Resync Type.

For more information, see Types of resync operations on page 5-12.

4. Select a Copy Pace, which is the rate that data is to be copied.Values: Slower, Medium, or Faster.Processing speed and system performance are affected by the pace youselect; you see slower speed and better performance with Slower, fasterspeed but more impact to performance with Faster.

5. Click Finish.6. In the Confirm window, type a Task Name and click Apply.

Note: The following concerns possible post-resync conditions:

• Make sure that pair status changes to “DUPLEX” before attempting anyother operation. If you perform the TrueCopy for Mainframe resume pairoperation before SIz status changes to “DUPLEX”, the TCz command isrejected.


• If the reverse or quick restore operation ends abnormally, the pair statuschanges to “Suspend/SUSPER”. In this case, the P-VOL is read/write-enabled for all hosts, but the data is not guaranteed. The S-VOL remainswrite-disabled and data is not guaranteed. The status of other pairssharing the same P-VOL does not change.

Pair deletionYou can delete a pair when you do not need it. When you delete a pair, the P-VOL and S-VOL return to their SIMPLEX state, though their data remainsintact. After deletion, both volumes are available for use in another pair.

Note: If the pair status changes to “SIMPLEX”, the status is not shown in SN.

Related information

• Prerequisite information for deleting pairs on page 5-15• Deleting pairs on page 5-15

Prerequisite information for deleting pairs• The P-VOL and S-VOL must be synchronized. Before deleting, wait until

all write I/O operations to the P-VOL are completed, set the P-VOL offline,then split the pair.

• Pair deletion cannot be performed when the pair status is “V-Split/SUSPVS”.

• When a pair is created, the processor blade allocated to the P-VOL's LDEVis also allocated to the S-VOL's LDEV. When a pair is deleted, theprocessor blade that was originally allocated to the S-VOL's LDEV isallocated to it again. If the original processor blade was removed, anotherprocessor blade is allocated.

• Deleting a pair first changes the status of the volumes to “Deleting/TRANS” then to “SIMPLEX”. “SIMPLEX” status is not shown in SN.

• After deleting a pair, wait 10 seconds—until volume status changes from“Deleting/TRANS” to “SIMPLEX”—before performing tasks such as a pairoperation or event waiting. If you do not wait 10 seconds, the operationmight end abnormally.

Deleting pairs1. In the tree, click Replications > Local Replications.2. In the Pairs tab, select the pair you want to delete, and click More

Actions > Delete Pairs.3. In the Delete Pairs window, type a Task Name and click Apply.


After performing the pairdelete operation, if you do not see the number ofpairs and other information you expect to see in the Summary tab of theLocal Replications window, the system is working and requires more time.Wait a little longer, then click File/Refresh.


6Monitoring and maintaining the system

This chapter provides information and instructions for monitoring andmaintaining the SIz system.

□ Monitoring the system

□ Maintaining the system

Monitoring and maintaining the system 6-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Monitoring the systemMonitoring helps you keep track of pairs and volumes and their current andpast conditions. Monitoring should be an ongoing activity. This topic providesinformation for the following:

• Monitoring pair activity, status on page 6-2. Status definitions andpermitted operations for each status are included.

• Monitoring pair, volume details on page 6-6.• Monitoring synchronous rates on page 6-6.• Monitoring consistency groups on page 6-7.• Monitoring reserve volumes on page 6-7.• Monitoring a pair’s operation history on page 6-7.

Monitoring pair activity, statusMonitoring the SIz system is necessary to maintain your pairs.

Each operation requires a specific status or statuses. When you want toperform a pair command, first check the pair’s status.

Pair-status changes when an operation is performed. Check status to see thatpairs are operating correctly and that status is changing to the appropriatestate during and after the operation.

Monitoring should be repeated frequently. Email notifications of problems inpair operations can be set up using SN.

1. In the tree, click Replications > Local Replications.2. In the Pairs tab, locate the pair whose status you want to review.3. Review pair status in the Status column.

You can view license information in the Summary section.

You can view more details for a selected pair by clicking More Actions >View Pair Properties. For more information about the fields, see Monitoringpair, volume details on page 6-6.

Related information

• Pair status definitions on page 6-2• CCI pair status names on page 6-4• Status, pair operations permitted on page 6-5• Status of unaffected S-VOLs, operations permitted on page 6-5

Pair status definitions

Pair status descriptions are provided in the following table. Click RefreshView for the most current data. The SN status names shown here are alsoused in BCM.

6-2 Monitoring and maintaining the systemHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Status Description Host status P-VOL access S-VOL access

SIMPLEX The volume is not assigned to apair. The storage system acceptsread/write for volumes that are notreserved.Note: If the volume is in“SIMPLEX” status, the status is notshown in SN.

P-VOL =SIMPLEXS-VOL =SIMPLEX

N/A N/A

Deleting/TRANS

The pair is being deleted. Pairoperations are not allowed in thisstatus. Upon deletion, the statuschanges to “SIMPLEX”.

P-VOL =SIMPLEXS-VOL =SIMPLEX

Read/writedisabled1

Read/writedisabled

PENDING The pair create operation hasbegun, the initial copy is inprogress.2 The storage systemcontinues to accept read/write tothe P-VOL, but stops writeoperations to the S-VOL. No updatecopy operations are performed.

P-VOL = PPRI-PNDGS-VOL = PSEC-PNDG

Read/write-enabled

Read/writedisabled

DUPLEX The initial copy operation iscomplete, the volumes are paired.The storage system begins updatecopy operations from the P-VOL tothe S-VOL as needed. The P-VOLand S-VOL in “DUPLEX” status maynot be identical.

P-VOL =PPRIMARYS-VOL =PSECONDRY

Read/write-enabled

Read/write-disabled

SP-Pend/TRANS

The pair is in the process of SteadySplit. Any remaining differentialdata is copied to the S-VOL.2 Whenthese updates are complete, thepair is split. The split S-VOL isidentical to the P-VOL at the time ofthe split.


Read/write-enabled

Read/write-disabled

V-Split/SUSPVS

The pair is in the process of QuickSplit.2 P-VOL differential data isonly copied to the S-VOL in thebackground. Pairs cannot bedeleted.

P-VOL = PPRI-PNDGS-VOL =SIMPLEX

Read/write-enabled

Read andwrite.

Split/SUSPOP The pair is split. The storagesystem stops performing updatecopy operations from the P-VOL tothe S-VOL. Write I/Os are acceptedfor S-VOL. The storage systemkeeps track of updates to split P-VOL and S-VOL, so that the paircan be resynchronized quickly.

P-VOL = PPRI-PNDGS-VOL =SIMPLEX

Read/write-enabled

Read andwrite.

Resync/PENDING

The pairresync operation hasbegun.2 The storage system doesnot accept write I/Os for S-VOL.When a split pair is resynchronizedin normal mode, the storagesystem copies only P-VOL


Read/write-enabled

Read/write-disabled


Status Description Host status P-VOL access S-VOL access

differential data to the S-VOL.When a suspended pair isresynchronized, the storage systemcopies the entire P-VOL to the S-VOL. No update copy operations areperformed during the pairresyncoperation.

Resync-R/REVRSY

The reverse pairresync operationhas begun.2 The storage systemcopies only S-VOL differential datato the P-VOL. No update copyoperations are performed duringthe reverse or quick restorepairresync operation. Write I/Ooperations to S-VOL are rejected.


Read/write-disabled

Read/write-disabled

Suspend/SUSPER

The pair is suspended by thestorage system. The systemcontinues accepting host updates tothe P-VOL. Update copy operationsare stopped to the S-VOL. Thesystem marks the entire P-VOLtrack map as differential data,meaning that the entire P-VOL iscopied to the S-VOL when thesuspended pair is resynchronized.


Read/write-enabled

Read/write-disabled

1. Read/write enabled if status before transition to Deleting/TRANS is Read/write.2. Starting time of the copy depends on the numbers of pairs and the storage system environment.

Caution: When you execute DEVSERVE to a read/write disabled volume,“INTERVENTION REQUIRED” is returned. However, if you have created pairswith the volumes online, and then execute DEVSERVE to a read/writedisabled volume, a normal value is returned.

CCI pair status names

Some CCI pair status names are different than the SN status names. Thefollowing shows the corresponding names.

SN pair status name CCI pair status name

SIMPLEX SMPL

PENDING COPY

DUPLEX DUPLEX

SP-Pend/TRANS COPY

V-Split/SUSPVS Split/SUSPOP

Split/SUSPOP Primary volume: Split/SUSPOPSecondary volume: SSUS

Resync/PENDING COPY


SN pair status name CCI pair status name

Resync-R/REVRSY RCPY

Suspend/SUSPER Suspend/SUSPER

Status, pair operations permitted

A pair’s status shows whether a desired operation can be performed. Eachoperation requires a specific status, or is permitted for multiple possiblestatuses.

Supported operations and statuses are shown in the following table.

Oper.

Pair status

SIMPLEX Pend. DUPLE

X

SP-Pend /TRANS

V-Split/SUSPVS

Split/SUSPOP

Resync/PENDIN

G

Resync-R/

REVRSY

Suspd./SUSPER

CreatePair

YES NO NO NO NO NO NO NO NO

Split Pair NO YES YES NO NO NO NO NO NO

SuspendPair

NO YES YES YES YES YES YES YES NO

ResyncPair(forward)

NO NO NO1,2 NO YES YES NO1,2,3 NO YES

ResyncPair(reverse)

NO NO NO2 NO NO YES NO NO2 NO

DeletePair

NO YES YES YES NO YES YES YES YES

1. With BCM, the command terminates normally but pair status does not change because resyncprocessing is not performed.

2. If you use the PPRC TSO command, the command terminates normally but pair status does notchange because resync processing is not performed. However, if you specify YES in the MSGREQparameter, the command terminates abnormally with CC=8.If you use the ICKDSF PPRCOPY command, the command terminates abnormally with CC = 12.

3. If the pair status changes from “Suspend/SUSPER” to “Resync/PENDING”, the PPRC TSO commandends abnormally with CC=8.

Related information

• Status of unaffected S-VOLs, operations permitted on page 6-5

Status of unaffected S-VOLs, operations permitted

The pair operations you can perform depend on the pair’s status, but also onthe status of unaffected S-VOLs. The following table shows which operations


can be performed, given the status of S-VOLs related to the P-VOL in otherpairs.

Status ofunaffected

S-VOLs

Pair operation

Create pairs Split pairsResyncpairs

(forward)

Resyncpairs

(reverse)

Suspendpairs Delete pairs

Deleting/TRANS

NO NO NO NO NO NO

PENDING YES YES YES NO YES YES

DUPLEX YES YES YES NO YES YES

SP-Pend/TRANS

YES YES YES NO YES YES

V-Split/SUSPVS

YES YES YES NO YES NO

Split/SUSPOP YES YES YES YES YES YES

Resync/PENDING

YES YES YES NO YES YES

Resync-R/REVRSY

NO NO NO NO YES YES

Suspend/SUSPER

YES YES YES YES YES YES

Monitoring pair, volume detailsYou can review the data related to pairs and their volumes. This includesvolume capacity, pair status, P-VOL and S-VOL, identifiers, and several otherdetails.

1. Select the pair in Local Replications then click More Actions > ViewPair Properties

Related information

• View Pair Properties window on page C-11

Monitoring synchronous ratesYou can check on the percentage of synchronized data between the P-VOLand S-VOL.

1. Select the pair in Local Replications then click More Actions > ViewPair Synchronous Rate.

Clicking Refresh View shows the latest synchronous rate. If you close thewindow, information in the Local Replications window may not be thelatest. Click Refresh View again.


Related information

• View Pair Synchronous Rate window on page C-13

Monitoring consistency groupsYou can check the number of consistency groups and the details andindividual properties for consistency groups.

• View the number of consistency groups in the Summary section of theLocal Replications window.

• View a list of consistency groups with status and number of pairs on theConsistency Groups tab in the Local Replications window.

• View a consistency group’s properties by clicking the CTG ID link on theConsistency Groups tab in the Local Replications window.

Related information

• Local Replications window on page C-4

Monitoring reserve volumesYou can see the number of reserve volumes and a list of the individualreserve volumes and their details.

• View the number of reserve volumes in the Summary section of theLocal Replications window.

• View a list of reserve volumes and their details on the Reserve Volumestab in the Local Replications window.

Related information

• Local Replications window on page C-4

Monitoring a pair’s operation history You can review the operations that have been performed on a pair using theView History window.


If you use 1,000 or more pairs concurrently, some operation history mightnot be recorded.

1. In the tree, click Replications > Local Replications.2. Click View Histories.3. In the View Histories window, select SIz from the Copy Type list.


4. The Description column shows the operation that was run.The following table shows a list of the codes.

Code Description Explanation

4710 DUPLEX START Initial copy began.

4720 DUPLEX END Initial copy completed and pair statuschanged to “SIMPLEX”.

4730 Split/SUSPOP START Pair split operation began.

4740 Split/SUSPOP END Pair split completed and pair statuschanged to “Split/SUSPOP”.

4750 SP-Pend/TRANS STARTResync-R/REVRSY START

Pair resync operation began.

4760 SP-Pend/TRANS ENDResync-R/REVRSY END

Pair resync operation completed and pairstatus changed to “DUPLEX”.

4780 Deleting/TRANS DELETE The pair was deleted and status changed to“SIMPLEX”.

4790 Suspend/SUSPER SUSPEND The pair was suspended and pair status haschanged to “Suspend/SUSPER”.

47D0 COPY ABNORMAL END The copy has terminated abnormally forreasons other than above.

47E9 INITIALIZE START Initialization processing has begun.

47EA INITIALIZE END Initialization processing has terminatednormally.

47EB INITIALIZE ENDEDABNORMAL

Initialization processing has terminatedabnormally.


Related information

• View Histories window on page C-15

Maintaining the systemSome maintenance tasks are a response to behavior discovered duringsystem monitoring. Other tasks are done to keep the system in tune withyour changing requirements.

Related information

• Removing reserve attribute from a volume on page 6-9• Releasing a reserved consistency group on page 6-9• Pair operations during system, device maintenance on page 6-9e

Removing reserve attribute from a volumeYou can remove the reserve attribute from a volume.


• The volume is not assigned to a pair (“SIMPLEX” status).

1. In the tree, click Replications > Local Replications.2. Click Reserve Volumes tab.3. In the Remove Reserve Volumes window, select the volume and click

Remove Reserve Volumes.4. Enter a Task Name and click Apply.

Releasing a reserved consistency group1. In the tree, click Replications > Local Replications, then click the

Consistency Group tab.2. In the Consistency Group window, select the consistency group and

click Release Reserved Consistency Group.3. In the Release Reserved Consistency Group window, enter a Task

Name, then click Apply.

Pair operations during system, device maintenanceThe following recommendations are provided for performing pair operationswhen maintenance on VSP and related devices is underway. Review thefollowing to check whether pairs and pair operations are affected whenmaintenance is performed on physical and logical devices.

• If VSP cache maintenance is performed during a period of high I/O usage,one or more pairs may suspend. Reduce the I/O load before performingcache maintenance.


• Physical devices that contain LDEVs used by SIz can be maintainedindependently of pair operations and pair status. Maintenance does notaffect SIz.

• If a physical device failure occurs, pair status is not affected because ofthe RAID architecture.

• If a physical device failure requires the storage system to utilize dynamicsparing or automatic correction copy, pair status is not be affected.

• If an LDEV failure occurs, the storage system suspends the pair.• Maintenance is restricted for LDEVs used by a pair. However, the format

operation is allowed even when pair is suspended (“Suspend/SUSPER”status).

• Maintenance is also restricted for LDEVs in which the Reserve attribute isset for a volume.To maintain these LDEVs, suspend or delete the pair, and/or remove thereserve attribute.


7Troubleshooting

This topic provides SIz troubleshooting information.

□ ShadowImage for Mainframe Troubleshooting

□ Service Information Messages (SIMs)

□ Troubleshooting with CCI

□ Calling the Hitachi Data Systems customer support

Troubleshooting 7-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

ShadowImage for Mainframe TroubleshootingThis topic provides instructions for troubleshooting in SIz.

Operation and display troubleshootingThe following table provides operation and display troubleshootinginformation for SIz pairs.

Error Corrective action

SN hangs, or SIz operations donot function properly.

• Make sure all SIz requirements and restrictions aremet.

• Make sure the storage system is powered on andfully functional.

• Check all input values and parameters to make surethat you entered the correct information in the SIzwindows (such as P-VOL and S-VOL IDs).

The volume pairs are notshowing correctly.

Make sure the correct volumes are selected.

An SIz error message isdisplayed in SN during anoperation.

Click Tasks in the Storage Systems tree and select thefailed task to check the message.If you are using the previous SN GUI, which is shown ina secondary window, complete the following:1. Select the failed volume in the Preview list in the

Pair Operation window.2. Right-click to show the menu.3. Click Error Detail.For the list of error codes and corrective actions, seeHitachi Storage Navigator Messages.

Troubleshooting pinned tracksIf a pinned track occurs on an SIz P-VOL or S-VOL, the storage systemsuspends the pair. Contact your HDS representative for assistance inrecovering pinned tracks.

Troubleshooting extended copy timesThe following table describes the causes for bottlenecks that result in longcopy time.

Cause Response

A processor whose MP usage rate exceeds80% exists within the processor blade towhich the P-VOL and S-VOL are allocated.

Reexamine the configuration. Forinformation about checking the MP usagerate, see the Hitachi Virtual StoragePlatform Performance Guide.

7-2 TroubleshootingHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Cause Response

The Host I/O Performance option isenabled.

Disable the option. For more informationabout disabling, see System options thataffect performance on page 4-4.

The S-VOL’s HDD or external storageperformance is lower than the P-VOL’s.

Make sure the configuration of the S-VOL’sHDD or external storage is the same as theP-VOL’s.

The S-VOL’s HDD or external storage hasan error.

Check the error and make the necessarycorrection.

The P-VOL’s HDD or external storage hasan error.

Check the error and make the necessarycorrection.

Service Information Messages (SIMs)The Virtual Storage Platform storage system generates a service informationmessage (SIM) to notify users of events that have occurred in the storagesystem. SIMs can be generated by the storage system’s channel and storagepath microprocessors or the service processor (SVP). The SVP reports allSIMs related to SIz operations. The SIMs reported to the zSeries and S/390host are logged in the SYS1.LOGREC dataset of the host operating system.

SIMs are classified according to the following severities: service, moderate,serious, or acute. The larger the SIM number, the more important themessage.

All SIMs are recorded on the Virtual Storage Platform SVP and displayed inthe SN Status window.

The following figure shows a typical 32 byte SIM from the Virtual StoragePlatform. SIMs are displayed on the host console by reference code (RC) andseverity. The six digit RC (composed of bytes 22, 23, and 13) identifies thepossible error and determines the severity. The SIM type (byte 28) indicatesthe component which experienced the error.

Figure 7-1 SIM example

The following table describes the DKC SIM (byte 28 = F1) related to SIzoperations.


Reference code Importancelevel Description

SSB22 SSB23

47 Dx Moderate Copying ends abnormally and pair status changesto Suspend.• “x” indicates the last digit of the T-VOL’s CU

number (0x0 to 0xF).• “SSB13” indicates the T-VOL’s LDEV number.

47 E7 Moderate Pair status changes to Suspend.

Troubleshooting with CCIThis topic provides troubleshooting information for operations performedusing CCI. The following describes CCI error codes and instructions for usingthem. Also, see Troubleshooting consistency group pair-split on page 7-13.

When using CCI, you can identify the cause of an error by referring to eitherof the following:

• The log displayed in the CCI window.• The error code in the CCI operation log file. The default location for this

file is:/HORCM/log*/curlog/horcmlog_HOST/horcm.logwhere * = instance number, and, HOST = host name

1. Do one of the following:

¢ If you are using the CCI-window log, locate the error code you areinvestigating. An example error code in the CCI-window log is:It was rejected due to SKEY=0x05,ASC=0x20,SSB=0xB9E1,0xB901 on Serial#(64015)

¢ If using the operation log file, locate the error code you areinvestigating. An example error code in the log file is:11:06:03-37897-10413- SSB = 0xb9a0,2089

2. Locate the SSB1 and SSB2 codes. In both examples above, these codesappear to the right of the equal symbol (=).

¢ The SSB1 code consists of the alpha-numeric characters which arethe last four digits on the left of the comma (,). Examples:B9E1 in the CCI-window logb9a0 in the operation log file

¢ The SSB2 code consists of the alphanumeric characters which arelast four digits on the right of the comma (,). Examples:0xB901 in the CCI-window log2089 in the operation log file

3. In the following table, locate the description of the SSB1/SSB2 error codecombination.


For errors not described in the table, call the Support Center.

Note: (For SIz) Some related software names in the following table refer tothe mainframe version. For example, it may be inferred that UniversalReplicator or UR can be replaced with Universal Replicator for Mainframe orURz.

The following table describes CCI error codes.

SSB2code Description

- Error occurred in SIz pair operation.

200D The pair operation was rejected because the Dynamic Provisioning orDynamic Tiering V-VOL you specified was not associated with a pool.

201B The consistency group pair-split was rejected because the UR pair was notin “DUPLEX” status, split (“Split/SUSPOP” status), or suspended (“Suspend/SUSPER” status). The UR S-VOL was the SIz P-VOL included in theconsistency group on which the consistency group pair-split was performed.

2026 The quick restore operation was rejected because the cache mode of the P-VOL you specified was different from the cache mode of the external S-VOL.

2036 The pair operation was rejected because the volume you specified as a P-VOL was a quorum disk.

2037 The pair operation was rejected because the volume you specified as an S-VOL was a quorum disk.

2043 The volume you specified as a P-VOL was a volume using two mirrorsincluded in the 3-URz DC multi-targetor cascade configuration. Theoperation was rejected because the volume was used as an URz pairvolume.

2044 The volume you specified as an S-VOL was a volume using two mirrorsincluded in the 3-URz DC multi-targetor cascade configuration. Theoperation was rejected because the volume was used as an URz pairvolume.

2047 The pair operation was rejected because the current microcode version doesnot support the P-VOL capacity you specified.

2048 The pair operation was rejected because the current microcode version doesnot support the S-VOL capacity you specified.

205B The pair operation was rejected for one of the following reasons:• An MU number already in use was specified.• MU number 0 was assigned to an L2 pair.

2060 The volume you specified as a P-VOL was a volume of a UR pair. The pairoperation was rejected because the status of the UR pair was invalid.

2061 The volume you specified as an S-VOL was a volume of a UR pair. The pairoperation was rejected because the status of the UR pair was invalid.

2067 The volumes you specified for the pair were shared by TC and UR. The quickrestore or reverse copy operation was rejected because the TC or UR pairwas not split (“Split/SUSPOP” status).

2068 The pair operation was rejected because the P-VOL or S-VOL you specifiedwas being shredded.



2072 The pair operation was rejected for one of the following reasons:• The P-VOL was also an HTI or SS pool volume.• The P-VOL was also an HTI or SS secondary volume, or V-VOL.• The P-VOL was also an HTI or SS P-VOL, and one of the following

conditions was also true.- While the HTI or SS pair was restored, the create, split, or resync pairoperation was performed on the SIz pair.- The SIz quick restore operation was performed.- A consistency group was defined for SIz.- After the MU number used by an HTI or SS pair was specified, thecreate, split, or resync pair operation was performed on the SIz pair.

2073 The pair operation was rejected for one of the following reasons:• The S-VOL was also an HTI or SS pool volume.• The S-VOL was also an HTI or SS secondary volume, or V-VOL.• The S-VOL was an HTI or SS S-VOL pair, and one of the following

conditions was also true.- The HTI or SS pair was being restored.- The SIz quick restore operation was performed.- A create pair operation was performed on the SIz pair.

2078 Because the P-VOL you specified was also a UR P-VOL for delta resync, oneof the following errors occurred:• The reverse copy operation was rejected because the UR pair was not

split (“Split/SUSPOP” status).• The quick restore operation was rejected.

2079 The pair operation was rejected because the P-VOL you specified was also aUR P-VOL for delta resync.

2086 The pair operation was rejected because the initialization process was beingperformed.

2089 The quick restore operation was rejected because the volume you specifiedas a P-VOL was undergoing quick format

208A The quick restore operation was rejected because the volume you specifiedas an S-VOL was undergoing quick format.

208C The pair operation was rejected because the volume you specified as the S-VOL was a Mainframe Fibre Data Migration volume.

2093 The volume you specified as a P-VOL was a TC S-VOL. The split operationwas rejected because the status of the TC pair was not Suspend.

2094 The volume you specified as a P-VOL was a TC S-VOL. The Split operationwas rejected because the consistency time of the consistency group is notequal to the consistency time of the TC pair.

2097 The quick restore operation was rejected because of one of the following:• The P-VOL was also a Dynamic Provisioning V-VOL, but the S-VOL was

a normal volume.



• The P-VOL was a normal volume, but the S-VOL also a DynamicProvisioning V-VOL.

209B The quick restore operation was rejected because the emulation type of onlyone of the volumes in the pair was OPEN-0V.

209C The quick restore operation was rejected because the updated informationabout storage system configuration was being backed up.

209E The pair operation was rejected because the volume you specified as the P-VOL was a FICON® Data Migration volume.

20A0 The pairs you specified contain the TC asynchronous volumes. The quickrestore operation was rejected because the CLPRs of the P-VOL and S-VOLfor the pair you specified were different.

20A2 The create pair operation was rejected because the P-VOL was a DynamicProvisioning or Dynamic Tiering V-VOL whose capacity was increasing.

20A3 The create pair operation was rejected because the S-VOL was a DynamicProvisioning or Dynamic Tiering V-VOL whose capacity was increasing.

20A9 The pair operation was rejected because the consistency group number youspecified was being used by HTI or SS.

20AA The pair operation was rejected because the volume you specified as the P-VOL was a Dynamic Provisioning or Dynamic Tiering V-VOL and its zeropages were being reclaimed.

20AB The pair operation was rejected because the volume you specified as the S-VOL was a Dynamic Provisioning or Dynamic Tiering V-VOL and its zeropages were being reclaimed.

20B0 The pair operation was rejected because the volume you specified as the P-VOL was a Dynamic Provisioning or Dynamic Tiering V-VOL and its capacitywas increasing.

20B1 The pair operation was rejected because the volume you specified as the S-VOL was a Dynamic Provisioning or Dynamic Tiering V-VOL and its capacitywas increasing.

20B4 The pair operation was rejected because the volume you specified as the P-VOL was a Dynamic Provisioning or Dynamic Tiering V-VOL, which was notassociated with a pool.

20B5 The pair operation was rejected because the volume you specified as the S-VOL was a Dynamic Provisioning or Dynamic Tiering V-VOL, which was notassociated with a pool.

20B7 The pair operation was rejected because you did not define an LU path tothe volume you specified as the P-VOL.

20B8 The pair operation was rejected because you did not define an LU path tothe volume you specified as S-VOL.

20BD The pair operation was rejected because the emulation type of the volumeyou specified as the P-VOL is 3390-V.

20BE The pair operation was rejected because the emulation type of the volumeyou specified as the S-VOL is 3390-V.



20C9 The emulation type of the P-VOL was 3390-A, and the pair operation wasrejected for one of the following reasons:• Mainframe Fibre CHA was not mounted• Mainframe Fibre CHA was all blocked

20CA The emulation type of the S-VOL was 3390-A, and the pair operation wasrejected for one of the following reasons:• Mainframe Fibre CHA was not mounted• Mainframe Fibre CHA was all blocked

20D0 The P-VOL rejected the paircreate operation because the DP pool isinitializing in the Dynamic Provisioning or Dynamic Tiering V-VOL.

20D1 The S-VOL rejected the paircreate operation because the DP pool isinitializing in the Dynamic Provisioning or Dynamic Tiering V-VOL.

20D6 The pair operation was rejected because the P-VOL is used by CompatibleFlashCopy® SE or is a TSE volume.

20D7 The pair operation was rejected because the S-VOL is a TSE volume.

20DC The CTG ID you specified is being used by SI and therefore cannot be usedby SIz.

20DE The pair operation was rejected because the volume you specified as the P-VOL is an external volume that is mapped for online data migration.

20DF The pair operation was rejected because the volume you specified as the S-VOL is an external volume that is mapped for online data migration.

22F6 The pair operation was rejected because the volume you specified as the P-VOL was a Compatible FlashCopy® S-VOL.

22F7 The pair operation was rejected because the volume you specified as the S-VOL was a Compatible FlashCopy® P-VOL or S-VOL.

22F9 The Quick Restore or the Reverse Copy operation was rejected because thevolume you specified as the S-VOL was a Compatible FlashCopy® P-VOL orS-VOL.

2301 The pair operation was rejected because shared memory is not allocated orSIz is not installed.

2302 The pair operation was rejected because the volume you specified as the P-VOL or S-VOL was not the top volume of the LUSE volume.

2306 The pair operation was rejected because the LBA size of the P-VOL youspecified was not the same as the size of the S-VOL you specified.

2309 The create pair operation was rejected because the number of pairsexceeded the maximum number of pairs.

230A The create pair operation was rejected because the volume you specified asthe S-VOL was the P-VOL of the SIz pair whose MU number is 0.

230B The pair operation was rejected because the pair was being suspended ordeleted.

2310 One of the following occurred:



• The create pair operation was rejected because the consistency groupnumber you specified had already been used for L1 pair.

• The create pair operation was rejected because the consistency groupnumber you specified had already been used for L2 pair.

• The create pair operation was rejected because the volume specified asthe P-VOL was the S-VOL of the pair which was being Quick Split.

• The quick restore operation was rejected because the VLL setting of theP-VOL was different from that of the S-VOL.

• The pair operation was rejected because the P-VOL and S-VOLs youspecified were a Compatible FlashCopy® pair.

• The quick restore or reverse copy operation was rejected because thepair of the P-VOL and S-VOLs you specified are suspended (“Suspend/SUSPER” status).

• The quick restore or reverse copy operation was rejected because theP-VOL and the S-VOL you specified was the L2 pair.

• The consistency group pair-split was rejected because some of the pairsin the consistency group were being resynchronized, split, or werealready suspended.

• The pair operation was rejected because the pair status of the P-VOL,the S-VOL, or both showed that the pair could not receive the issuedcommand.

2312 The pair operation was rejected because the volume you specified as the S-VOL was online to the host.

2314 The create pair operation was rejected because the volume you specified asthe S-VOL was the S-VOL of another pair that was split (“Split/SUSPOP”status).

231F The quick restore or reverse copy operation was rejected because the P-VOLof the pair you specified was online to the host.

2322 The pair operation was rejected because the necessary shared memory wasnot installed, or initialization was not completed.

2324 The pair operation was rejected because the number of slots of the volumeyou specified as the P-VOL exceeded the upper limit.

2325 The pair operation was rejected because the number of slots of the volumeyou specified as the S-VOL exceeded the upper limit.

2326 The create pair operation was rejected because the volume you specified asthe P-VOL had already had three S-VOLs.

2327 The create pair operation was rejected because the node volume specifiedas the P-VOL had already had two S-VOLs.

2328 The pair operation was rejected because the pair configuration exceeded thenumber of the layers of the cascade configuration.

2329 The pair operation was rejected because the volume you specified as the S-VOL was the S-VOL of an existing pair.

232A The create pair operation was rejected because pairs that would exceed thelicense capacity were going to be created.



232F The pair operation was rejected because the volume you specified as the P-VOL was allocated as the destination of the Volume Migration.

2331 The pair operation was rejected due to one of the following causes.• The volume you specified as the P-VOL was a reserved volume.• The volume you specified as the P-VOL was the volume for Volume

Migration.• The capacity of the P-VOL and the S-VOL you specified was not the

same.

2332 The create pair operation was rejected because the volume you specified asthe P-VOL had already had three S-VOLs.

2333 The pair operation was rejected because the volume you specified as the P-VOL was not the P-VOL of the existing pair.

2334 One of the following occurred:• The pair operation was rejected because the volume you specified as

the P-VOL had an emulation type that could not be handled by CCI.• The consistency group pair-split was rejected because the volume you

specified as the P-VOL was an intermediate volume.

2335 The pair operation was rejected because the volume you specified as the S-VOL had an emulation type that could not be handled by CCI.

2336 The pair operation was rejected because the emulation type for the P-VOLyou specified was different from the emulation type of the S-VOL.

2337 The pair operation was rejected because the volume you specified as the P-VOL had already been an S-VOL.

233A The pairresync was rejected because the volume you specified as the P-VOLwas not a SIz P-VOL.

233B The pair operation was rejected because the volume you specified as the S-VOL was a root volume.

233C The pair operation was rejected because the volume you specified as the S-VOL was a node volume, and the volume you specified as the P-VOL was notthe P-VOL for the S-VOL you specified.

233D The pairsplit was rejected because the P-VOL and S-VOLs you specified werea L2 pair, and the L1 pair was not split (“Split/SUSPOP” status).

233E The pair task was rejected because the volume you specified as the P-VOLwas being used as a P-VOL in another SIz pair in which the S-VOL is alsoused as a TCz M-VOL.

233F The pair operation was rejected because the volume you specified as the S-VOL was the TC P-VOL, and the pair was not split (“Split/SUSPOP” status) orsuspended (“Suspend/SUSPER” status).

2342 The pair operation was rejected because the volume you specified as the S-VOL was the destination of the Volume Migration.

2343 The create pair operation was rejected because the volume you specified asthe S-VOL had already been an S-VOL.



2344 The pair operation was rejected because the volume you specified as the S-VOL for SIz pair operations was not an S-VOL.

2346 The volume you specified as an S-VOL was a TC P-VOL. The pair operationwas rejected because the status of the TC pair was invalid.

2347 The volume you specified as an S-VOL was a TC S-VOL. The pair operationwas rejected because the status of the TC pair was invalid.

234A The pair creation for the cascade configuration was rejected because thevolume you specified as the S-VOL was an intermediate volume.

234B The pair operation was rejected because the volume you specified as the S-VOL was the volume of the Volume Migration.

2350 The pair operation was rejected because the P-VOL and the S-VOL youspecified for SIz pair operations was not a pair.

2351 The pair operation was rejected because the volume you specified as the P-VOL and the volume you specified as the S-VOL was the same one.

2352 The Quick Restore operation or the Reverse Copy operation was rejectedbecause the P-VOL and S-VOLs you specified was online to the host.

2353 The deletion operation was rejected because the P-VOL and S-VOLs youspecified was being Quick Split.

2354 The pairresync operation was rejected because the P-VOL and S-VOLs wasbeing split by using Steady Split.

2357 The pair creation was rejected because the volume you specified as the S-VOL was the P-VOL of the splitting pair, or the P-VOL of the pair where theReverse Copy operation or Quick Restore operation is being performed.

2358 The pairresync operation was rejected because the volume you specified asthe S-VOL was the P-VOL of the splitting pair.

235B The volume you specified as a P-VOL was a TC P-VOL. The reverse copy orthe quick restore operation was rejected because the TC pair was notsuspended (“Suspend/SUSPER” status) or split (“Split/SUSPOP” status).

235C The volume you specified as a P-VOL was a TC S-VOL. Because the TC pairwas not suspended (“Suspend/SUSPER” status) or split (“Split/SUSPOP”status), the reverse copy or the Quick Restore operation was rejected.

235D The volume you specified as an S-VOL was a TC P-VOL. The reverse copy orthe quick restore operation was rejected because the TC pair was notsuspended (“Suspend/SUSPER” status) or split (“Split/SUSPOP” status).

236C The reverse copy or the quick restore operation was rejected because thevolume you specified as the P-VOL has the S-VOL Disable attribute assignedby the Data Retention Utility.

236D The pair operation was rejected because the volume you specified as the S-VOL has the S-VOL Disable attribute assigned by the Data Retention Utility,the pair operation was rejected.

2370 The pair operation was rejected because the volume you specified as the P-VOL was not mounted, the pair operation was rejected.



2371 The pair operation was rejected because the volume you specified as the P-VOL was blocked or a system disk.

2372 The pair operation was rejected because the volume you specified as the P-VOL was being formatted.

2373 The pair operation was rejected because the volume you specified as the P-VOL was a command device.

2380 The pair operation was rejected for one of the following reasons:• The volume you specified as the S-VOL was not mounted.• The MU number was 3 or more.

2381 The pair operation was rejected because the volume you specified as the S-VOL was blocked or a system disk.

2382 The pair operation was rejected because the volume you specified as the S-VOL was being formatted.

2383 The pair operation was rejected because the volume you specified as the S-VOL was a command device.

2385 The pair operation was rejected because the volume you specified as the P-VOL was a reserved volume for Volume Migration.

2386 The pair operation was rejected because the volume you specified as the S-VOL was a reserved volume for Volume Migration.

2387 The create pair operation was rejected because the volume you specified asthe P-VOL was the volume for Volume Migration.

2394 The registering of the pair in the consistency group was rejected becausethe number of the pairs in a consistency group exceeded the definablemaximum number of pairs.

2395 The pair operation was rejected because the pair sharing the volume youspecified as the P-VOL was undergoing the reverse copy operation or theQuick Restore operation.

2396 The pair operation was rejected because the L1 pair sharing the P-VOL youspecified as the root volume was undergoing the reverse copy operation orthe Quick Restore operation.

2397 The pair operation was rejected because the L2 pair sharing the P-VOL or S-VOL you specified as the node volume was undergoing the reverse copyoperation or the Quick Restore operation.

2398 The quick restore or reverse copy operation was rejected because the pairyou specified was not suspended (“Suspend/SUSPER” status) or split (“Split/SUSPOP” status).

2399 The quick restore or reverse copy operation was rejected because some ofthe pairs sharing the volume you specified as the P-VOL were not suspended(“Suspend/SUSPER” status) or split (“Split/SUSPOP” status).

239D The Add Pair operation was rejected because the Protect attribute was setfor the volume you specified as the P-VOL.

239E The Add Pair operation was rejected because the Protect attribute was setfor the volume you specified as the S-VOL.



23A8 The quick restore or reverse copy operation was rejected because thevolume you specified as the volume was specified as the P-VOL for XRC.

23A9 The quick restore or reverse copy operation was rejected because thevolume you specified as the volume was specified as the P-VOL for CC.

23AA The pair operation was rejected because the volume you specified as the S-VOL was specified as the P-VOL for XRC.

23AB The pair operation was rejected because the volume you specified as the S-VOL was specified as the P-VOL for CC.

23AF Registering the pair in the consistency group from CCI was rejected becausethe consistency group number you specified was reserved by PPRC/BCM.

23BB The create pair was rejected because the volume you specified as the S-VOLcould not be used as the S-VOL because of Volume Security settings.

23EF The pair deletion was rejected because the source and target volumes werebeing Quick Split.

23F5 The pair operation was rejected because the split time for the consistencygroup was set.

23F1 The Add Pair operation was rejected because the CTGID you specified wasnot supported.

9100 You cannot execute the command because the system could notauthenticate the user.

B911 The pair operation was rejected because the volume you specified did notexist.

B912 The pair operation was rejected because the S-VOL specified at the pairoperation did not exist.

B913 The pair operation was rejected because the mirror ID was invalid.

Troubleshooting consistency group pair-splitIf the consistency group pair-split fails, note the following:

• The pairs in the consistency group are suspended (“Suspend/SUSPER”status).

• When the host server is down or has failed, you can define a consistencygroup that does not have SIz pairs. Running the paircreate commandwith the consistency group split option under such a condition can causethe paircreate command to be rejected.In this case, complete the following:

a. Locate a consistency group number that is not used by any pairs inthe Pair Operation window by sorting the CTG column.

b. Specify that consistency group number explicitly, and run thepaircreate command with the consistency group split option usingCCI on the host server.


• If you use an URz S-VOL as an SIz P-VOL and you cannot change thestatus of some pairs included in the consistency group, some pairs remainunsplit in the consistency group after you run the pairsplit command inCCI. Consistency is not guaranteed.The following are possible reasons why the pair status cannot bechanged:

¢ The UR pair belongs to a consistency group, and the P-VOL and S-VOLhave the same contents. The journal volumes for this pair are full.

¢ The SIz license is invalid.¢ The SIz pair volumes are blocked.¢ The SIz pair is in a status that does not allow the pairsplit operation.

For more information, see Monitoring pair activity, status on page 6-2.¢ An SIz pair volume is also used in a TC (TC) or UR pair. The TC or UR

pair is in a status that does not allow the pairsplit operation.

After these factors are removed, perform the pairresync operation, and runthe pairsplit command.

Calling the Hitachi Data Systems customer supportIf you need to call the Hitachi Data Systems customer support, provide asmuch information about the problem as possible, including the following:

• The circumstances surrounding the error or failure.• The content of any error message(s) displayed on the host system(s).• The content of any error message(s) displayed on SN.• The SN configuration information (use the FD Dump Tool).• The service information messages (SIMs), including reference codes and

severity levels, displayed by SN.

The HDS customer support staff is available 24 hours a day, seven days aweek. If you need technical support, log on to the HDS Support Portal forcontact information: https://hdssupport.hds.com



APair operations using PPRC

You can perform SIz pair operations using TSO PPRC and ICKDSF PPRCOPYcommands.

PPRC requirements, commands, and examples are provided in this topic.However, all instructions for using the PPRC TSO and ICKDSF commands arenot provided. For more information, see the IBM user documentation.

□ Overview of PPRC commands supported by ShadowImage for Mainframe

□ PPRC command requirements

□ Preparing the system with PSF and DEVSERV

□ Pair operations using PPRC commands when S-VOL is online

□ Adding pairs with CESTPAIR and PPRCOPY ESTPAIR

□ Splitting pairs with CSUSPEND and PPRCOPY SUSPEND

□ Resynchronizing pairs with CESTPAIR and PPRCOPY ESTPAIR

□ Deleting pairs with CDELPAIR, DELPAIR

□ Consistency group pair operations with PPRC

□ Showing pair information with CQUERY TSO, QUERY ICKDSF

Pair operations using PPRC A-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Overview of PPRC commands supported by ShadowImagefor Mainframe

You can perform most SIz pair operations using PPRC, including thefollowing:

• Add pairs.• Add and split pairs.• Split pairs, specifying Steady Split or Quick Split.• Resynchronize pairs, normal and reverse, quick resync/quick restore

operations.• Delete pairs.• Show pair status and other information.

The following table shows the PPRC commands supported by SIz.

TSO command ICKDSF Description

CESTPAIR PPRCOPY ESTPAIR Adds a pair, starts initial copy operation,and changes status to “DUPLEX”.

CESTPAIR PPRCOPY ESTPAIR Adds and simultaneously splits a pair.

CSUSPEND PPRCOPY SUSPEND Splits a pair, starts Quick Split operation.

CSUSPEND PPRCOPY SUSPEND Splits a pair, starts Steady Split operation.

CESTPAIR PPRCOPY ESTPAIR Resynchronizes a pair, starts normalresync.

CESTPAIR PPRCOPY ESTPAIR Resynchronizes a pair, starts quick resync.

CESTPAIR PPRCOPY ESTPAIR Resynchronizes a pair, starts reverse copy.

CESTPAIR PPRCOPY ESTPAIR Resynchronizes a pair and starts QuickRestore.

CDELPAIR PPRCOPY DELPAIR Deletes a pair and changes the status to“SIMPLEX”.

CQUERY PPRCOPY QUERY Shows detailed pair status information.

You can perform certain operations with SN that you cannot perform withPPRC, including the following:

• Set or reset the S-VOL reserve attribute.• Suspend pairs.

PPRC command requirementsThe following requirements must be met:

• SIz must be installed and enabled on the Virtual Storage Platform storagesystem

A-2 Pair operations using PPRCHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

• The serial numbers of the P-VOL and the S-VOL must be definedaccording to one of the following:

¢ Use the same serial number for both the P-VOL and S-VOL.¢ Use the serial number for the S-VOL, and enter an additional

parameter instead of the serial number for the P-VOL.

Because SIz and TCz support PPRC, a failure to meet these requirementscould result in a PPRC command executed on a TCz pairs instead.

Preparing the system with PSF and DEVSERVPerform Storage System Function (PSF) commands enable PPRC commandsand user requests in the storage system.

The following table shows how PSF commands interact with SIz pair.

Item Interaction

Device pair status See the following table.

Rate of synchronization Not available for SIz because the differential bitmapformat is different than TCz’s.

Primary volume with 2 or moreS-VOLs

Shows information for the pair whose S-VOL has thelowest LDEV ID.

Path status Active.

Path number If the volume does not also belong to a TCz pair, 1 isshown with TCz information.

The following table shows PSF and DEVSERV results.

Pair statusPSF Read Subsystem Data DEVSERV Sense Subsystem

Status

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

PENDING PPRI-PNDG PSEC-PNDG PPRI-PNDG PSEC-PNDG

DUPLEX PPRIMARY PSECONDRY PPRIMARY PSECONDRY

SP-Pend/TRANS PPRI-PNDG PSEC-PNDG PPRI-PNDG PSEC-PNDG

V-Split/SUSPVS PPRI-SUSP PSEC-SUSP PPRI-SUSP SIMPLEX

Split/SUSPOP PPRI-SUSP PSEC-SUSP PPRI-SUSP SIMPLEX

Suspend/SUSPER

PPRI-SUSP PSEC-SUSP PPRI-SUSP PSEC-SUSP

Resync/PENDING

PPRI-PNDG PSEC-PNDG PPRI-PNDG PSEC-PNDG

Note: PPRIMARY and PSECONDRY indicate that the volume is in the “DUPLEX” status.


DEVSERV command example

Pair operations using PPRC commands when S-VOL is onlinePair split and pair deletion operations can be done using PPRC commandswhen an S-VOL is online, but whether you can perform pair creation and pairresync operations depends on the ONLINSEC parameter.

The following table shows whether pair creation and resync operations arepossible using PPRC commands when an S-VOL is online.

Pair operationONLINSEC parameter

YES NO Not specified

Pair create Yes No No

Pair resync Yes No No

Adding pairs with CESTPAIR and PPRCOPY ESTPAIRAdd pairs using the CESTPAIR and PPRCOPY ESTPAIR commands.

• The commands are issued to the P-VOL.• The S-VOL must be offline.

Parameters and examples are provided in the following topics.

CESTPAIRThe following table describes the CESTPAIR command parameters used tocreate pairs.

Parameter Value Description

DEVN Device number NA

PRIM Primary volume: SSID, serialnumber, channel connectionaddress, and CU number.To request the Add and Splitoperation, set MSF00 instead of aserial number. This parameter isvalid for MODE(COPY) orMODE(NOCOPY) only.

These parameters must be used forsuccessful execution of the command.



To create pairs in a consistencygroup, set MAnn0 instead of aserial number. nn is a CTG ID.

SEC Secondary volume: SSID, serialnumber, channel connectionaddress, and CU number.

NA

MODE COPY The storage system recognizes onlyCOPY for the MODE parameter, evenif NOCOPY is specified.NOCOPY2

PACE Any number Copy speed is medium, regardlesswhat is specified for the PACEparameter.

CRIT Not applicable Not used by SIz.

MSGREQ YES2 MSGREQ function is applicable.Note: You cannot use the MSGREQfunction when the Add and Splitoperation is required. Specifying YESfor this parameter when the Add andSplit operation is required rejects thecommand and the command endsabnormally by reporting CC = 8.

NO MSGREQ function is not applicable.

ONLINSEC1 YES Pair create operation is performedwhether the S-VOL is online or not.

NO Pair create operation is not performedif the S-VOL is online.

1. When you do not specify the parameter, the result is the same as when you specifyNO for this parameter.2. If NOCOPY is specified for the MODE parameter and YES for the MSGREQ parameter,the CESTPAIR command ends before the copy operation is completed.

CESTPAIR example

ESTPAIRThe following table describes the PPRCOPY ESTPAIR command parametersused to create pairs.

Parameters Value Description

DDNAME,SYSNAME, orUNITADDRESS

DDNAME = dname = JCL statementidentifying the volume.

Only one of the three parametersshould be specified. The italicterm is the arbitrary name. Forexample, dname is the arbitrary



SYSNAME = sysxxx = SYSNAME inthe ASSGN system controlstatement.UNITADDRESS = ccuu = devicenumber.

unique name of the JCL statementwhich identifies the volume.

PRI Primary volume: SSID, serialnumber, channel connectionaddress.To request the Add and Splitoperation, set MSF00 instead of aserial number. This parameter isvalid for MODE(COPY) orMODE(NOCOPY) only.To create pairs in a consistencygroup, set MAnn0 instead of aserial number. nn is a CTG ID.

These parameters must be usedfor successful execution of thecommand.

SEC Secondary volume: SSID, serialnumber, channel connectionaddress.

NA

MODE COPY The system recognizes only COPYfor the MODE parameter, even ifNOCOPY is specified.NOCOPY

PACE 1-255 Copy speed is medium, regardlesswhat is specified for the PACEparameter.


MSGREQ YES Do not specify this parameterwhen MODE(RESYNC) is set,otherwise it ends abnormallyreporting CC = 12.

NO MSGREQ function is notapplicable.

LSS P-VOL or S-VOL CU number. NA

ONLINSEC* YES Pair create operation is performedwhether the S-VOL is online ornot.

NO Pair create operation is notperformed if the S-VOL is online.

* When you do not specify the parameter, the result is the same as when you specify NOfor this parameter.


ESTPAIR example

Splitting pairs with CSUSPEND and PPRCOPY SUSPENDSplit pairs using the CSUSPEND and PPRCOPY SUSPEND commands.

• The commands are issued to the P-VOL.• The pair must be in “DUPLEX” status.

Parameters and examples are provided in the following topic.

CSUSPENDThe following table describes the CSUSPEND command parameters used tosplit pairs.



PRIM Primary volume: SSID, serialnumber, channel connectionaddress, and CU number.You can set MPS00 or MAnn0instead of a serial number. nn is aCTG ID.

MPS00 is used for a Steady Splitrequest.MAnn0 is used for a Quick Splitrequest on all pairs in a consistencygroup.Setting parameters other than theserial number, MPS00 or MAnn0,rejects the command.


NA

PRIMARY Not Applicable Not used by SIz.

* If you perform a Quick Split on all pairs in a consistency group, confirm that the statusof the pairs is “DUPLEX”. If there are pairs in “PENDING” status, the Quick Splitsometimes ends abnormally (CC = 12). If this occurs, wait until the copy operation forthe pair ends.

CSUSPEND example


SUSPENDThe following table describes the SUSPEND command parameters used tosplit pairs.



DDNAME = dname = JCL statementidentifying the volume.SYSNAME = sysxxx = SYSNAME inthe ASSGN system controlstatement.UNITADDRESS = ccuu = devicenumber.

Only one of the three parametersshould be specified. The italicterm is the arbitrary name. Forexample, dname is the arbitraryunique name of the JCL statementwhich identifies the volume.

PRI Primary volume: SSID, serialnumber, channel connectionaddress.You can specify MPS00 or MAnn0instead of a serial number. nn is aCTG ID.

MPS00 is used for a Steady Splitrequest.MAnn0 is used for a Quick Splitrequest on all pairs in aconsistency group.*Setting parameters other than theserial number, MPS00 or MAnn0,rejects the command.


NA

PRIMA Not Applicable Not used by SIz.


* If you perform a Quick Split request on all pairs in a consistency group, confirm thatthe status of all pairs is “DUPLEX”. If there are pairs in “PENDING” status, the Quick Splitoperation sometimes ends abnormally (CC = 12). If this occurs, wait until the copyoperation for the pair ends.

SUSPEND example

Resynchronizing pairs with CESTPAIR and PPRCOPYESTPAIR

Resynchronize pairs using the CESTPAIR and PPRCOPY ESTPAIR commands.

• The commands are issued to the P-VOL.


• The pair must be suspended (“Suspend/SUSPER” status) or split (“Split/SUSPOP” status).

Parameters and examples are provided in the following.

CESTPAIR (resynchronizing pairsThe following table describes the CESTPAIR command parameters used toresynchronize pairs.



PRIM Primary volume: SSID, serialnumber, channel connectionaddress, and CU number.You can set an additionalparameter corresponding to eachrequest instead of a serialnumber. If you do not set anadditional parameter, the requesttriggers a normal copy.For a Quick Resync, set MRF00.This parameter is valid forMODE(RESYNC) only.For a Quick Restore, set MRQ00.This parameter is valid forMODE(RESYNC) only.For a Reverse Copy set MRR00.This parameter is valid forMODE(RESYNC) only.To resync all pairs in aconsistency group, set MAnn0instead of a serial number. nn is aCTG ID. The request triggers anormal resync operations.



NA

MODE RESYNC Re-establish a split or suspendedvolume pair. This parameter isrequired.

PACE Any number Copy speed is medium, regardlesswhat is specified for the PACEparameter.


MSGREQ YES MSGREQ function is applicable.For a Resync request on all pairs in aconsistency group, do not use theMSGREQ function. Using the MSGREQfunction ends the job abnormally and"CC = 8" is reported.



NO MSGREQ function is not applicable.

ONLINSEC* YES You can Normal Copy whether the S-VOL is online or not.You can Reverse Copy whether the P-VOL and S-VOL are online or not.

NO You cannot Normal Copy when the S-VOL is online.You cannot Reverse Copy when theP-VOL and S-VOL are online.


CESTPAIR with MODE(RESYNC) example

ESTPAIR (resynchronizing pairs)The following table describes the PPRCOPY ESTPAIR command parametersused to resynchronize pairs.





PRI Primary volume: SSID, serialnumber, channel connectionaddress.You can set an additional parametercorresponding to each requestinstead of a serial number. If youdo not set an additional parameter,the request triggers a normal copy.For a Quick Resync, set MRF00. Thisparameter is valid forMODE(RESYNC) only.For a Quick Restore, set MRQ00.This parameter is valid forMODE(RESYNC) only.For a Reverse Copy set MRR00. Thisparameter is valid forMODE(RESYNC) only.

These parameters must be usedfor successful execution of thecommand.Caution: When a Quick Restoreor a Reverse Copy operation isrequired and if you specify NO forthe ONLINSEC parameter, the jobends abnormally by reporting CC= 12. Specifying YES for theONLINSEC ends the job normally.Note: The copying operation isperformed without any onlinecheck.



To resync all pairs in a consistencygroup, set MAnn0 instead of a serialnumber. nn is a CTG ID. Therequest triggers a normal resyncoperations.


NA

MODE RESYNC Re-establish a split or suspendedpair.

PACE 1-255 Copy speed is medium, regardlesswhat is specified for the PACEparameter.


MSGREQ YES Do not specify this parameterwhen MODE(RESYNC) is set,otherwise it ends abnormally (CC= 12).

NO


ONLINSEC* YES Forward pair resynchronizationcan be performed whether the S-VOL is online or not.Backward pair resynchronizationcan be performed whether the P-VOL and S-VOL are online or not.

NO Forward pair resynchronization isnot performed when the S-VOL isonline.Backward pair resynchronizationis not performed when the P-VOLand S-VOL are online. TheICKDSF job ends abnormally (CC= 12).Although errors do not occurwhen you specify YES for thisparameter, the copying operationis performed without any onlinecheck.



ESTPAIR with MODE(RESYNC) example

Deleting pairs with CDELPAIR, DELPAIRDelete pairs using the CDELPAIR and PPRCOPY DELPAIR commands.

• The commands are issued to the P-VOL.• If the pair is split, the S-VOL can be accessed by the host.• If the pair is in any other status than “Split/SUSPOP”, non-reserved S-

VOL can be accessed by the host. You cannot access reserved volume’sthat are not assigned to a pair (“SIMPLEX” status).

Note: When splitting “DUPLEX” pairs, the P-VOL and its associated S-VOLsare usually not identical since update copy operations are asynchronous. Thismeans that the data integrity of the S-VOL cannot be guaranteed. To ensuredata integrity of the S-VOL, split the pair before deleting.

Parameters and examples are provided in the following topics.

CDELPAIRThe following table describes the CDELPAIR command parameters used todelete pairs.



PRIM Primary volume: SSID, serialnumber, channel connectionaddress, and CU number.To delete all pairs in a consistencygroup, MAnn0 must be set. nn isthe CTG ID.



NA


CDELPAIR example

DELPAIR

The following table describes the PPRCOPY DELPAIR command parametersused to delete pairs.





PRI Primary volume: SSID, serialnumber, channel connectionaddress.To delete all pairs in a consistencygroup, MAnn0 must be set. nn isthe CTG ID.

These parameters must be usedfor successful execution of thecommand.


NA


DELPAIR example

Consistency group pair operations with PPRCWith PPRC, you can split, resynchronize, and delete the pairs in a consistencygroup at the same time. This topic provides instructions for creatingconsistency groups and perform the pair operations.


Setting up pairs in consistency groups1. In SN, reserve a consistency group using the instructions in Reserving a

consistency group on page 4-32. Using PPRC, create the pairs by running the CESTPAIR or PPRCOPY

ESTPAIR command.3. In SN, in the CTG window, make sure that the pairs exist in the

consistency group as expected.

Splitting pairs in consistency groups1. Run the CSUSPEND or the PPRCOPY SUSPEND command. The command

splits all the pairs in the consistency group.

Note: Running the command on a split pair does not generate errors.

2. Run the CQUERY or PPRCOPY QUERY command to check pair status. Thestatus should be “Split/SUSPOP”.Hosts can now access the data in S-VOL.

Resynchronizing pairs in consistency groups1. Resynchronize pairs by running the CESTPAIR or PPRCOPY ESTPAIR

command. The command resynchronizes all the pairs in the consistencygroup. Running the command on a pair which has not been split does notgenerate errors.

2. Run the CQUERY command or the PPRCOPY QUERY command to make surethat the pair status is “PENDING” or “DUPLEX”.

Deleting pairs in consistency groups1. Delete pairs by using the CDELPAIR or PPRCOPY DELPAIR command. The

command deletes all the pairs in the consistency group.2. Use the CQUERY or PPRCOPY QUERY command to make sure that the

volume is not assigned to a pair (“SIMPLEX” status).

Showing pair information with CQUERY TSO, QUERY ICKDSFYou can view pair status and volume information using the CQUERY TSO andthe QUERY ICKDSF commands.

• The commands can be issued to the P-VOL or S-VOL.• If a P-VOL has multiple S-VOL, status is shown for the pair whose S-VOL

has the lowest LDEV ID. To obtain status of a pair with another S-VOL,issue the command to the desired S-VOL.


• If the system contains both SIz and TCz pairs, the CQUERY and thePPRCOPY QUERY commands report TCz pair status. To obtain the SIzstatus, issue the command to the SIz S-VOL.

• When SIz and TCz share volumes, path status is shown for TCz. If they donot share volumes, path status for the SIz pair is shown as FFFF FFFF.

The following topics shows the commands, parameters, and examples forshowing pair information.

CQUERYThe following table shows CQUERY command parameters used to show pairinformation.

Parameter Value

DEVN Device number

CQUERY example

If the command is issued to the S-VOL in a consistency group, output for theSECONDARY serial number is shown in the following format:

00|S|@|000|30158

where:

• S indicates that it belongs to a consistency group.• @ indicates the consistency group split operation.• 30158 is the serial number.


PPRCOPY QUERYThe following table shows the PPRCOPY QUERY command parameters used toshow pair information.





QUERY example

Output descriptionsThe following table shows the field descriptions of the output resulting whenCQUERY TSO and QUERY ICKDSF commands are run.

Field Description

DEVICE Device number of the volume on which the CQUERY command isissued.


Field Description

LEVEL PRIMARY indicates that the volume is a P-VOL. SECONDARYindicates that the volume is a T-VOL.

STATE Pair status

PATH STATUS Invalid for SI; “Active” is shown.

CRIT Invalid for SI; “NO” is shown.

CGRPLB Invalid for SI; “NO” is shown.

PRIMARY-SSID SSID of the P-VOL CU

PRIMARY-CCA P-VOL LDEV number

PRIMARY-LSS P-VOL CU number

PRIMARY-SERIAL P-VOL serial number

SECONDARY-SSID SSID of the S-VOL CU

SECONDARY-CCA S-VOL LDEV number

SECONDARY-LSS S-VOL CU number

SECONDARY-SERIAL S-VOL serial number. Running the CQUERY TSO command for theS-VOL also show following information:00ab000nnnnnwhere “a” indicates that the pair is defined as a consistency groupand “b” indicates the pair was split using consistency group pair-split. “0” indicates otherwise. “nnnnn” is the S-VOL serial number.

PATHS Invalid for SI; “1” is shown.

SAID DEST STATUS Invalid for SI; “FFFF FFFF” is shown.

DESCRIPTION Invalid for SI; “PATH ESTABLISH” is shown.

PERCENT OF COPYCOMPLETE

Invalid for SI; “100%” is shown.

SUBSYSTEM Invalid for SI, not valid content.

WWN Invalid for SI, not valid content.

LIC LEVEL Invalid for SI, not valid content.

When the MCU-RCU path for TCz is created on the CU where an SIz pair exists, MCU-RCU path information is shown.


BInterface support for SIz operations and

options

This appendix lists SIz operations and options, and consistency groupoperations and options, and the interfaces that support them.

□ Operations supported by Storage Navigator, CCI, Business ContinuityManager, and PPRC

□ Consistency group operations supported by Storage Navigator, CCI,Business Continuity Manager, PPRC

Interface support for SIz operations and options B-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Operations supported by Storage Navigator, CCI, BusinessContinuity Manager, and PPRC

The following table lists SIz operations and options supported by:

• SN• CCI• BCM• PPRC

Operation Options

SN CCI BCM PPRC

Command Option

TSOcomma

nd

ICKDSFcomman

d

Reservevolumeas T-VOL

Nooptions

YES Notapplicable

Notapplicable

NO NO NO

Removereserveas T-VOL

Nooptions

YES Notapplicable

Notapplicable

NO NO NO

Changesystemoptions

Nooptions

YES Notapplicable

Notapplicable

NO NO NO

Createpairs

Nooptions

YES paircreate Notapplicable

YKMAKE CESTPAIR

PPRCOPYESTPAIR

MUnumber

YES1 paircreate Uses MU# inHORCM.conffile

NO NO NO

Copypace

YES paircreate -c <size> YES3 NO2 NO2

SteadySplit

YES paircreate -split -fqnormal

NO CESTPAIR

PPRCOPYESTPAIR

QuickSplit

YES paircreate -split -fqquick

NO NO NO

MSGREQ NO NO NO NO CESTPAIR

PPRCOPYESTPAIR

ONLINSEC

NO NO NO YKMAKE CESTPAIR

PPRCOPYESTPAIR

Splitpairs

Nooptions

YES pairsplit Notapplicable

YKSUSPND CSUSPEND

PPRCOPYSUSPEND

Copypace

YES pairsplit -C <size> NO NO NO

SteadySplit

YES pairsplit -fq normal YKSUSPND CSUSPEND

PPRCOPYSUSPEND

B-2 Interface support for SIz operations and optionsHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Operation Options

SN CCI BCM PPRC

Command Option

TSOcomma

nd

ICKDSFcomman

d

QuickSplit

YES pairsplit -fq quick YKSUSPND CSUSPEND

PPRCOPYSUSPEND4

Resyncpairs

Nooptions

YES pairresync

Notapplicable

YKRESYNC CESTPAIR

PPRCOPYESTPAIR

Copypace

YES pairresync

-c <size> YKRESYNC3

NO2 NO2

NormalCopy

YES pairresync

-fq normal YKRESYNC CESTPAIR

PPRCOPYESTPAIR

QuickResync

YES pairresync

-fq quick YKRESYNC CESTPAIR

PPRCOPYESTPAIR

ReverseCopy

YES pairresync

-fq normal -restore

YKRESYNC CESTPAIR

PPRCOPYESTPAIR

QuickRestore

YES pairresync

-fq quick -restore

YKRESYNC CESTPAIR

PPRCOPYESTPAIR

ONLINSEC

NO NO Notapplicable

YKRESYNC CESTPAIR

PPRCOPYESTPAIR

Suspendpairs

Nooptions

YES pairsplit -E NO NO NO

Deletepairs

Nooptions

YES pairsplit -S YKDELETE CDELPAIR

PPRCOPYDELPAIR

Notes:1. Not supported in the old SN GUI (which is still supported and is shown in a

secondary window).2. Medium speed is used by the system regardless of what you specify.3. Only Slow or Normal speeds can be selected. The default is Normal.4. If you do not specify an option, the system uses Quick Split.

Consistency group operations supported by StorageNavigator, CCI, Business Continuity Manager, PPRC

The following table lists SIz consistency group (CG) operations and optionssupported by:

• SN• CCI• BCM• PPRC


Operation Option

SN CCI BCM PPRC

Command Option

TSOcomman

d

ICKDSFcomman

d

ReserveCG

Nooptions

YES Notnecessary

Notnecessary

NO NO NO

RemoveCGreserve

Nooptions

YES Notnecessary

Notnecessary

NO NO NO

Add pairsto a CG

Nooptions

NO paircreate -m grp[CTGID]

YKMAKE CESTPAIR PPRCOPYESTPAIR

MUnumber

NO paircreate Uses MU#inHORCM.conffile

NO NO NO

Copy pace NO paircreate -m grp[CTGID] -c<size>

YKMAKE1 NO2 NO3

User canspecify CGnumber

NO paircreate -m grp xx(xx =CTGID)

YKMAKE CESTPAIR PPRCOPYESTPAIR

SystemallocatesCGnumber

NO paircreate -m grp(CTGID isomitted)

NO NO NO

ATTIMESuspend

Nooptions

NO NO NO YKSUSPND

NO NO

SteadySplit

NO NO NO YKSUSPND

NO NO

QuickSplit

NO NO NO YKSUSPND

NO NO

SteadySplit whenSIzvolumessharedwith UR

NO NO NO YKSUSPND

NO NO

QuickSplit whenSIzvolumessharedwith UR

NO NO NO YKSUSPND

NO NO

CancelATTIMESuspend

Nooptions

NO NO NO YKSUSPND

NO NO


Operation Option

SN CCI BCM PPRC

Command Option

TSOcomman

d

ICKDSFcomman

d

CG split(splittime notspecified)

Nooptions

NO pairsplit Notapplicable

YKSUSPND

CSUSPEND2

PPRCOPYSUSPEND2

Copy pace NO pairsplit -C <size> NO NO3 NO3

SteadySplit

NO pairsplit -fq normal YKSUSPND

NO NO

QuickSplit

NO pairsplit -fq quick YKSUSPND

NO NO

UR-SIcombination(SteadySplit)

NO pairsplit -fq normal NO NO NO

UR-SIcombination (QuickSplit)

NO pairsplit -fq quick NO NO NO

Resyncpairs

Nooptions

NO pairresync4

Notapplicable

YKRESYNC

CESTPAIR5

PPRCOPYES2TPAIR5

Copy pace NO pairresync4

-c <size> YKRESYNC1

NO3 NO3

NormalCopy

NO pairresync4

-fq normal YKRESYNC

NO NO

QuickResync

NO pairresync4

-fq quick YKRESYNC

NO NO

ReverseCopy

NO pairresync4

-fq normal -restore

YKRESYNC

NO NO

QuickRestore

No pairresync4

-fq quick -restore

YKRESYNC

No No

ONLINSEC No No No YKRESYNC

CESTPAIR PPRCOPYES2TPAIR

Deletepairs

Nooptions

NO pairsplit4 -S YKDELETE4

CDELPAIR PPRCOPYDELPAIR

Notes:1. Only Slow or Normal speeds can be selected. The default is Normal.2. Quick Split is used regardless of what you specify.3. Medium speed is used regardless of what you specify.4. You must use a CCI pair group to run the command for the consistency group.5. Normal Resync is used regardless of what you specify.


CShadowImage for Mainframe GUI

reference

This appendix describes SIz windows and dialog boxes in SN.

□ Replications window

□ Local Replications window

□ View Pair Properties window

□ View Pair Synchronous Rate window

□ View Histories window

□ Consistency Group Properties window

□ Create Pairs wizard

□ Split Pairs wizard

□ Resync Pairs wizard

□ Suspend Pairs window

□ Delete Pairs window

□ Edit Mirror Units dialog box

□ Change Options dialog box

□ Add Reserve Volumes Wizard

ShadowImage for Mainframe GUI reference C-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

□ Remove Reserve Volumes window

□ Reserve Consistency Groups wizard

□ Release Reserve Mainframe CTGs window

□ Edit Local Replica Option wizard

C-2 ShadowImage for Mainframe GUI referenceHitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Replications windowUse this window to view pair information for local replication.

Summary tab

Item Description

Licensed Capacity Used and licensed capacity of each product.

Number of Replica LDEVs Number of LDEVs used for all local replication pairs.

Number of FCv2/FCSERelationships

Number of relationships that Compatible FlashCopy® V2and Compatible FlashCopy® SE use.


Item Description

Number of DifferentialTables

(SI, SIz, and SS only.)Number of differential tables in use.

View Histories button Click to open the View History window.

Replica LDEVs tab

Item Description

LDEV ID Selected LDEV’s identifier

LDEV Name Selected LDEV’s name

Emulation Type Selected LDEV’s emulation type

Capacity Selected LDEV’s capacity

Copy Type Shows the following copy types:• SI-L1: SI L1 P-VOL or S-VOL• SI-L2: SI L2 P-VOL or S-VOL• TI: HTI P-VOL or S-VOL• SS: SS P-VOL or S-VOL• SIMF: SIz P-VOL or S-VOL• FCv2: Compatible FlashCopy® V2 relationship• FCSE: Compatible FlashCopy® SE relationship

Export button Click to open the dialog box for downloading tableinformation to a file.

Local Replications windowUse this window to view pair, reserve volume, and consistency groupinformation for local replication. Use it also to perform the followingoperations:

• Creating pairs on page 5-4• Splitting pairs on page 5-10• Resynchronizing pairs on page 5-14• Deleting pairs on page 5-15


Summary tab

Item Description

Number of Pairs Number of pairs for each local replication software type

Number of ConsistencyGroups

Number of consistency groups whose status is other than“Free”

Number of ReserveVolumes

Number of reserved volumes.Values:• Open: Number of OPEN system reserved volumes• Mainframe: Number of mainframe system reserved

volumes• Total: Total reserved volumes• Total including S-VOLs: Includes number of reserve

volumes and number of S-VOL for SI, SIz, HTI, and SS.

Snapshot EstimatedManageable Capacity Estimated HTI pair capacity. An icon is shown, , when the

value is less than 128 TB. For more information, see theHitachi Thin Image User Guide.


Item Description

Number of Pair Tables Number of pair tables in use for the following:• SI/SIz/Volume Migration: SI, SIz, Volume Migration• TI/SS: HTI and SS

Number of DifferentialTables

(SI, SIz, and SS only.)Number of differential tables in use.

Edit Local Replica Optionsbutton

Click to open the Edit Local Replica Options window.

Edit SCP Time button Click to open the Edit SCP Time window.

Pairs tab

The Pairs tab shows only pairs to which you are allocated the P-VOL and/orS-VOL.

Item Description

Primary Volume • LDEV ID: The P-VOL’s LDEV identifier. Click to openthe LDEV Properties window.

• LDEV Name: The P-VOL’s LDEV name.• Port ID: The port name of the P-VOL LDEV’s LUN path.

For SIz, a hyphen (-) is shown.• Host Group Name: The host group name of the P-VOL

LDEV’s LUN path.For SIz, a hyphen (-) is shown.

• LUN ID: LUN identifier of the P-VOL LDEV's LUN path.For SIz, a hyphen (-) is shown.

• Capacity: The P-VOL’s capacity.• CLPR: The P-VOL’s CLPR number.

Copy Type Shows the following types of pairs:• SI-L1: SI L1• SI-L2: SI L2• TI: HTI• SS: SS• SIMF: SIz

Snapshot Group (HTI only.)The snapshot group name.If you have not set a snapshot group for HTI pairs, this itemis blank.For SI, SIz, and SS, a hyphen (-) is shown.

Status Shows the following icons and pair status names:(“SIMPLEX” and “SMPL” are not statuses that are shown inSN.)•


Item Description

The pair is being deleted. Status names are:SI, HTI: SMPL(PD)SIz: Deleting/TRANS

• This icon is used for the following:

The pair is being copied. Status names are:SI: COPY(PD)/COPYSIz: PENDINGHTI, SS: COPYThe pair is being resynchronized. Status namesare:SI: COPY(RS)/COPYSIz: Resync/PENDINGThe pair is being resynchronized from secondaryto primary volume. Status names are:SI: COPY(RS-R)/RCPYSIz: Resync-R/REVRSYHTI, SS: COPY(RS-R)/RCPYThe pair is being split in normal mode. Statusnames are:SI: COPY(SP)/COPYSIz: SP-Pend/TRANS

• This icon is used for the following:

The volumes are paired. Status names are:SI: PAIRSIz: DUPLEXThe pool has exceeded the threshold. Status nameis:HTI, SS: PFUL

Status, continued • This icon is used for the following:

The pair is split. Status names are:SI: PSUSSIz: Split/SUSPOPThe pair is being split in Quick Split mode. Statusnames are:SI: PSUS(SP)PSUSSIz: V-Split/SUSPVSThe pool is full. Status name is:HTI, SS: PFUS

•

The pair is suspended. Status names are:SI: PSUESIz: Suspend/SUSPER


Item Description

For more information, see Pair status definitions on page6-2.

Secondary Volume • LDEV ID: The S-VOL’s LDEV identifier.• LDEV Name: The S-VOL’s LDEV name.• Port ID: The port name of the P-VOL LDEV’s LUN path.

For SIz, a hyphen (-) is shown.• Host Group Name: The host group name of the P-VOL

LDEV’s LUN path.For SIz, a hyphen (-) is shown.

• LUN ID: The LUN ID of the S-VOL LDEV's LUN path.For SIz, a hyphen (-) is shown.

• Emulation Type: The S-VOL’s emulation type.• Capacity: The S-VOL’s capacity.• CLPR: The S-VOL’s CLPR number.

Snapshot Date (HTI and SS only.)The date and time that a snapshot was acquired.If you have not set a snapshot date for HTI pairs, this itemis blank.For SI and SIz, a hyphen (-) is shown.

Pool Name (ID) (HTI and SS only.)The pool name and identification number.If you have not set a pool name for HTI pairs, this item isblank.For SI and SIz, a hyphen (-) is shown.

Copy Pace (SI and SIz only.)The speed at which the split operation is performed.Values: Faster, Medium, SlowerIf you have not set a copy pace for HTI pairs, this item isblank.For HTI and SS pairs, a hyphen (-) is shown.

CTG ID Consistency Group ID

Mirror Unit Mirror unit number

Topology ID LDEV’s topology identifier

Create Pairs button Click to open the Create Pairs wizard.

Split Pairs button Click to open the Split Pairs window.

Resync Pairs button Click to open the Resync Pairs window.

View Pair SynchronousRate*

Opens the View Pair Synchronous Rate window.

View Pair Properties* Opens the View Pair Properties window.

Suspend Pairs* Opens the Suspend Pairs window.


Item Description

Delete Pairs* Opens the Delete Pairs window.

Export* Opens the dialog box for downloading table information to afile.

*An option you can choose from the More Actions menu.

Reserve Volumes tab

Use this tab on the Local Replications window to view reserved volumeinformation for local replication, and to perform the following operations:

• Reserving secondary volumes on page 4-2• Removing reserve attribute from a volume on page 6-9

Item Description

LDEV ID Reserved volume LDEV’s identifier

LDEV Name Reserved volume LDEV’s name

Capacity Reserved volume’s capacity

Number of Paths The number of paths to reserved volume.

Add Reserve Volumesbutton

Click to open the Add Reserve Volumes window.

Remove Reserve Volumesbutton

Click to open the Remove Reserve Volumes window.



Consistency Group tab

Use this tab in the Local Replications window to view consistency groupinformation for local replication, and to perform the following operations:

• Reserving a consistency group on page 4-3• Releasing a reserved consistency group on page 6-9

Item Description

CTG ID Consistency group identifier. Click to open the ConsistencyGroup Properties window.

Status Possible values include:• SI Used: Consistency group used by SI.• SIMF Used (RAID Manager): Consistency group used

for SIz pairs and managed with CCI.• SIMF Used (PPRC/BCM): Consistency group used for

SIz pairs and managed using PPRC or BCM.• TI Used: Consistency group used by HTI pairs.• SS Used: Consistency group used for SS pairs.• Mainframe Reserved: Consistency group reserved for

PPRC or BCM.• Free: Consistency group not being used and is not

reserved.• (Changing...): Status is in the process of changing.

Number of Pairs Number of pairs for the consistency group in use.


Item Description

Reserve Mainframe CTGsbutton

Click to open the Reserved Mainframe CTGs window.

Release ReservedMainframe CTGs button

Click to open the Release Reserved Mainframe CTGswindow.


View Pair Properties windowUse this window to review pair and volume details for local replication.

For detailed information, see Monitoring pair, volume details on page 6-6.

Pair Properties tab

Item Description

Copy Type Type of pair:• ShadowImage• ShadowImage for Mainframe• Thin Image• COW Copy-on-Write Snapshot


Item Description

Pool Name (ID) (HTI and SS only.)The pool name and ID.If you have not set a pool name for HTI pairs, this item isblank.For SI and SIz, a hyphen (-) is shown.

Most Recent Snapshot Date (HTI and SS only.)Date and time that the most recent snapshot was acquired.If you have not set a most recent snapshot date for HTIpairs, this item is blank.For SI and SIz, a hyphen (-) is shown.

LDEV ID Identifiers of P-VOL and S-VOL LDEVs

LDEV Name Names of P-VOL and S-VOL LDEVs

Pairs table

Item Description

Primary Volume • LDEV ID: The P-VOL’s LDEV identifier.• LDEV Name: The P-VOL’s LDEV name.• Emulation Type: The P-VOL’s emulation type.• Capacity: The P-VOL’s volume capacity.• CLPR: The P-VOL’s CLPR number.

Snapshot Group (HTI only.)The snapshot group name.If you have not set a snapshot group for HTI pairs, this itemis blank.For SI, SIz and SS, a hyphen (-) is shown.

Status Pair status.For more information, see Pair status definitions on page6-2.

Secondary Volume • LDEV ID: The S-VOL’s LDEV identifier.• LDEV name: The S-VOL’s LDEV name.• Emulation Type: The S-VOL’s emulation type.• Capacity: The S-VOL’s volume capacity.• CLPR: The S-VOL’s CLPR number.• Mode: Indicates whether the S-VOL has been written

to. For SI, this item also indicates whether the S-VOLcan be read.¢ For SI:

- “W” is shown if the S-VOL was written to andwhen the S-VOL was written to and cannot be readwhen its pair status is “PSUS(SP)/PSUS” or“PSUS”.


Item Description

- “N” is shown if the S-VOL cannot be read. Youhave specified “-m noread” using CCI.- A hyphen (-) indicates that the S-VOL has notbeen written to and it can be read.

¢ For HTI and SS:- “W” is shown if the S-VOL was written to when itspair status is “PSUS(SP)/PSUS” or “PSUS”.- A hyphen (-) indicates that the S-VOL has notbeen written to.

¢ For SIz:- “W” is shown if the S-VOL was written to when itspair status is “V-Split/SUSPVS” or “Split/SUSPOP”.- “Protect” is shown if the S-VOL is write-protected.You specified the PROT MODE in BCM as PROTECTwhen the S-VOL’s pair status was “Split/SUSPOP”,SP-Pend/TRANS”, or “V-Split/SUSPVS”.- A hyphen (-) indicates that the S-VOL has notbeen written to and you made Protect settings.

Snapshot Date (HTI and SS only.)The date and time when a snapshot was acquired.For SI and SIz, a hyphen (-) is shown.

CTG ID Consistency group identifier

COPY Pace (SI and SIz only.)The copy speed.For HTI and SS pairs, a hyphen (-) is shown.

Mirror Unit The mirror unit number.

View Pair Synchronous Rate windowUse this window to view the percentage of synchronized data between the P-VOL and S-VOL.

For detailed information, see Monitoring synchronous rates on page 6-6.


Pairs table

Item Description

Primary Volume • LDEV ID: The P-VOL’s LDEV identifier.• LDEV Name: The P-VOL’s LDEV name.• CLPR: The P-VOL’s CLPR number.


Snapshot Group (HTI only.)The snapshot group name.If you have not set a snapshot group for HTI pairs, this itemis blank.For SI, SIz and SS pairs, a hyphen (-) is shown.

Status Pair status. For more information, see Pair status definitionson page 6-2.

Synchronous Rate (%) Synchronous rate (%) between P-VOL and S-VOL.

Secondary Volume • LDEV ID: The S-VOL’s LDEV identifier.• LDEV Name: The S-VOL’s LDEV name.


Item Description

• CLPR: The -VOL’s CLPR number.

Copy Pace (SI and SIz only.)The speed at which the split operation is performed.Values: Faster, Medium, or SlowerFor HTI and SS pairs, a hyphen (-) is shown.


Refresh When clicked, updates the information in the Pairs table.

View Histories windowUse this window to review the operations that have been performed on pairs.You can view a maximum of 16,384 operation histories.

For full information, see Monitoring a pair’s operation history on page 6-7.

Setting fields

Item Description

Copy Type Shows the following types of pairs:• SI: SI• TI: HTI• SS: SS• SIMF: SIz• FCv2/FCSE: Compatible FlashCopy® V2 and

Compatible FlashCopy® SE


Histories table

Item Description

Date Operation date and time

Primary Volume (“SourceVolume” for FCv2/FCSE)

• LDEV ID: The P-VOL/source volume’s LDEV identifier• Provisioning Type: The provisioning type.

Values:- Basic: Internal volume- DP: DP-VOL- External: External volume- External MF: Migration volume

Secondary Volume (“TargetVolume” for FCv2/FCSE)

• LDEV ID: The secondary/target volume’s LDEVidentifier.

• Provisioning Type: The provisioning type.Values:- Basic: Internal volume- DP: DP-VOL- External: External volume

Mirror Unit The mirror unit number.Shown only when TI or SS is the selected Copy Type.

Pool ID The pool identifier.Shown only when TI or SS is the selected Copy Type.

Relationship ID The relationship identifier.Shown only when FCv2/FCSE is the selected Copy Type.

Description Code The code for the type of operation performed.

Description Description of the operation.

Export Click to open the dialog box for downloading tableinformation to a file.

Consistency Group Properties windowUse this window to view a list of consistency groups, with status and numberof pair information; also use it to view a consistency group’s properties.

For full information, see Monitoring consistency groups on page 6-7.


Consistency Group Properties table

Item Description

CTG ID Consistency group identifier

Status Consistency group status• SI Used: The consistency group is in use by SI.• SIMF Used (RAID Manager): The consistency group

is used by SIz and managed with CCI.• SIMF Used (PPRC/BCM): The consistency group is

used by SIz and managed with PPRC/BCM.• TI Used: The consistency group is used by HTI.• SS Used: The consistency group is used by SS.• Mainframe Reserved: Consistency group is reserved for

use by PPRC and BCM.• Free: The consistency group is not being used and is

not reserved.• (Changing...): Status is the process of changing.

Number of Pairs Number of pairs assigned to the consistency group

Pairs table

This table shows pairs for P-VOL and/or S-VOL to which you are allocated.


Item Description




Status The pair status.For more information, see Pair status definitions on page6-2.

Secondary Volume • LDEV ID: The S-VOL’s LDEV identifier.• LDEV Name: The S-VOL’s LDEV name.• Emulation Type: The S-VOL’s emulation type.• Capacity: The S-VOL’s volume capacity.• CLPR: The S-VOL’s CLPR number.

Snapshot Date (HTI and SS only.)The date and time that a snapshot was acquired.For SI and SIz pairs, a hyphen (-) is shown.

Pool Name (ID) (HTI and SS only.)The pool name and identification number.For SI and SIz pairs, a hyphen (-) is shown.

Copy Pace (SI and SIz only.)The speed at which the split operation is performed.Values: Faster, Medium, SlowerFor HTI and SS pairs, a hyphen (-) is shown.


Detail button Click to open the Pair Properties window.

Create Pairs wizardUse this wizard to create pairs, including specifying new pair details.


This wizard includes the following windows:

• Select Pair Configuration window• Select Primary Volumes window• Select Secondary Volumes window• Confirm window

For full information, see Creating pairs on page 5-4.

Select Pair Configuration windowUse this window to configure the pairs you will create.

Item Description

Copy Type The copy type.Values: ShadowImage, ShadowImage for Mainframe,TI, or COW Snapshot

Emulation Type The emulation type.For HTI or SS, you can only specify OPEN-V.

Pair Topology Type (SI only.)Use the check boxes to select the pair configuration for theL1 and L2 pairs.

Number of SecondaryVolumes

(SIz, HTI and SS only.)The total number of S-VOL assigned to the P-VOL. Includesvolumes for the pairs you are creating and volumes forexisting pairs.

Initial MU Number (SIz and SS only.)The initial MU number.

Split Type (SI and SIz only.)• Non Split: Does not split the pair• Quick Split: Splits the pair immediately• Steady Split: After all differential data is copied, the

pair is split.


Item Description


Select Primary Volumes windowUse this window to select LDEVs that are P-VOLs.

Item Description

Use Primary Volumes ofSnapshot Pairs

(HTI and SS only.)Indicates whether the P-VOLs are used.• Yes: Only HTI and SS P-VOL LDEVs are shown in the

Available LDEVs table.• No: Only unpaired LDEVs are shown in the Available

LDEVs table.

Port ID (SI, HTI, SS only.)Filters LDEVs in the Available LDEVs table according tothe port ID.

Host Group Name (SI, HTI, SS only.)Filters LDEVs in the Available LDEVs table according tohost group name. Any is the default.


Available LDEVs table

Item Description

LDEV ID The LDEV’s identifier.

LDEV Name The LDEV’s name.

Port ID (SI, HTI, SS only.)Port name of the LDEV’s LUN path.

Host Group Name (SI, HTI, SS only.)Host group name of the LDEV’s LUN path.

LUN ID (SI, HTI, SS only.)LUN ID of the LDEV's LUN path.

Provisioning Type The LDEV’s provisioning type.Values:• Basic: Internal volume• HDP: HDP volume• External: External volume

Emulation Type The LDEV’s emulation type.

Capacity Capacity of the LDEV

CLPR CLPR number of the LDEV


The number of S-VOLs.(SI only) The number for an L1 pair does not include thenumber of L2 S-VOL.

Primary Volumes (HTI and SS only.)Information about the P-VOL when the LDEV is used as a S-VOL for an existing pair.Values:• LDEV ID: The LDEV identifier.• LDEV Name: The LDEV name.• Port ID: The port name of the LDEV’s LUN path.• Host Group Name: The host group name of the

LDEV’s LUN path.• LUN ID: The LUN ID of the LDEV's LUN path.• Emulation Type: The volume’s emulation type.• Capacity: The volume’s capacity.• CLPR: The volume’s CLPR number.

Mirror Unit (HTI and SS only.)The mirror unit number.

Pool Name (ID) (HTI and SS only.)The pool name and ID.For SI and SIz, this item is blank.

Select Pool button (HTI and SS only.)Click to open the Select Pool window.


Item Description

Note: If you selected Yes for Use Primary Volumes ofSnapshot Pairs, this button is not available.

Selected LDEVs table

Item Description

LDEV ID The selected P-VOL’s LDEV identifier.

LDEV Name The selected P-VOL’s LDEV name.

Port ID (SI, HTI, and SS only.)The port name of the LDEV’s LUN path.

Host Group Name (SI, HTI, and SS only.)Host group name of the LDEV’s LUN path.

LUN ID (SI, HTI, and SS only.)LUN ID of the LDEV's LUN path.

Provisioning Type The LDEV’s provisioning type.Values:• Basic: Internal volume• HDP: HDP volume• External: External volume

Emulation Type Emulation type of LDEV

Capacity Capacity of LDEV.

CLPR CLPR number


The number of S-VOL.(SI only) The number for an L1 pair does not include thenumber of L2 S-VOL.

Primary Volume (HTI and SS only.)Information about the P-VOL.Values:• LDEV ID: The P-VOL’s LDEV identifier:• LDEV Name: The P-VOL’s LDEV name.• Port ID: The port name of the P-VOL LDEV’s LUN path.• Host Group Name: The host group name of the P-VOL

LDEV’s LUN path.• LUN ID: The LUN ID of the P-VOL LDEV's LUN path.• Emulation Type: The P-VOL’s emulation type.• Capacity: The P-VOL’s capacity.• CLPR: The P-VOL’s CLPR number.

Mirror Unit (HTI and SS only.)The mirror unit number.


Item Description

Pool Name (ID) (HTI and SS only.)The pool name and identifier.

Select Secondary Volumes windowUse this window to select LDEVs that are the S-VOL.

Item Description

Capacity list Allows you to filter the available LDEVs according to thecapacity you select.

The remaining number youhave to select

Refers to the selected P-VOLs in the Selected Pairs tablethat do not have an assigned S-VOL.

Exclude Paired Volumes (SI only.)Select to hide the volumes that are already in a pair fromthe list.Default: Selected

Port ID (SI, HTI, and SS only.)Filters LDEVs in the Available LDEVs table according tothe port ID.

Host Group Name (SI, HTI, and SS only.)


Item Description

Filters LDEVs in the Available LDEVs table according tohost group name. Any is the default.

Detail button Click to open the LDEV Properties window, which containsadditional information for the selected LDEV.

Set button Click to move the selected LDEV to the Selected Pairstable.

Clear button Click to move the selected S-VOL from the Selected Pairstable to the Available LDEVs table.

Edit Mirror Unit button Click to open the Edit Mirror Units dialog box, from whichyou can change the mirror unit numbers, and thereby, pairtopology.(SI only) For more information, see the step on pairtypology type in Creating pairs on page 5-4.)

Snapshot Group (HTI only.)Choose to create a new snapshot group or use an existingsnapshot group.• Create new snapshot group: The new snapshot

group name is entered.• Use defined snapshot group: An existing snapshot

group is selected.If you have not set a snapshot group for HTI pairs, this itemis blank.

Change Options button (SI and SIz only.)Click to open the Change Options dialog box, from whichyou can change the Split Type and Copy Pace.

Remove button Click to remove the pair from the table.(SI only) You cannot remove L1 pairs if they have an L2pair.


Item Description

LDEV ID The LDEV’s identifier.

LDEV Name The LDEV’s name.

Emulation Type The LDEV’s emulation type.

Capacity The LDEV’s capacity.

Provisioning Type Provisioning type of the LDEV:• Basic: Internal volume• DP: DP-VOL• External: External volume• Snapshot: HTI or SS volume

CLPR LDEV’s CLPR number


Item Description

Reserve Volume (SI and SIz only.)Indicates whether LDEV is reserved as an S-VOL.Values: Yes or No

Selected Pairs table

Item Description

Primary Volume Information about the P-VOL.• LDEV ID: The P-VOL’s LDEV identifier.• LDEV Name: The P-VOL’s LDEV name.• Port ID: The port name of the P-VOL LDEV’s LUN path.

For SIz, this item is blank.• Host Group Name: The host group name of the P-VOL

LDEV’s LUN path.For SIz, this item is blank.

• LUN ID: The LUN ID of the P-VOL LDEV's LUN path.For SIz, this item is blank.

• Emulation Type: The P-VOL’s emulation type.• Capacity: The P-VOL’s volume capacity.

Snapshot Group (HTI only.)The snapshot group name.If you have not set a snapshot group for TI pairs, this itemis blank.

New Snapshot Group (HTI only.)Values:• Yes: New snapshot group is used.• No: Existing snapshot group is used.

Secondary Volume • LDEV ID: The S-VOL’s LDEV identifier.• LDEV Name: The S-VOL’s LDEV name.• Emulation Type: The S-VOL’s emulation type.• Capacity: The S-VOL’s volume capacity.

Copy Type The following types of pairs are shown:• SI-L1: SI L1• SI-L2: SI L2• TI: HTI• SS: SS• SIMF: SIz

Mirror Unit The mirror unit number.For HTI and SS pairs, a hyphen (-) is shown.

Split Type (SI and SIz only.)


Item Description

One of the following selected split types are shown:• Non Split: Does not split the pair.• Quick Split: Splits the pair immediately• Steady Split: Splits the pair after all differential data is

copied


Pool Name (ID) (HTI and SS only.)The pool name and ID number.For SI and SIz pairs, a hyphen (-) is shown.

Confirm window


Item Description


Copy Type Shows the following types of pairs:• SI-L1: SI L1


Item Description

• SI-L2: SI L2• TI: TI• SS: SS• SIMF: SIz

Snapshot Group (HTI only.)The snapshot group name.If you have not set a snapshot group for TI pairs, this itemis blank.

New Snapshot Group (HTI only.)• Yes: New snapshot group is used.• No: Existing snapshot group is used.


Split Type (SI and SIz only.)• Non Split: Does not split the pair.• Quick Split: Splits the pair immediately• Steady Split: Splits the pair after all differential data is

copied

Copy Pace (SI and SIz only.)The speed at which the split operation is performed.Values: Faster, Medium, Slower

Pool Name (ID) (HTI and SS only.)The pool name and ID number.

Mirror Unit (SI and SIz only.)The mirror unit number.

Split Pairs wizardUse this wizard to split pairs.

Split Pairs windowUse this window to split pairs.

For full information, see Splitting pairs on page 5-10.



The same Selected Pairs table appears on the Confirm window and theSplit Pairs window.

Item Description

Primary Volume • LDEV ID: P-VOL’s LDEV identifier• LDEV Name: P-VOL’s LDEV name• Emulation Type: P-VOL’s emulation type• Capacity: P-VOL’s volume capacity• CLPR: P-VOL’s CLPR number


Snapshot Group (HTI only.)The snapshot group name.


Item Description

If you have not set a snapshot group for HTI pairs, this itemis blank.For SI, SIz and SS pairs, a hyphen (-) is shown.

Status Pair status. For more information, see Pair status definitionson page 6-2.

Secondary Volume • LDEV ID: S-VOL’s LDEV identifier• LDEV Name: S-VOL’s LDEV name• Emulation Type: S-VOL’s emulation type• Capacity: S-VOL’s volume capacity• CLPR: S-VOL’s CLPR number

Pool Name (ID) (HTI and SS only.)The pool name and ID number.For SI and SIz pairs, hyphen (-) is shown.


Split Type list The split type.Values:• Quick Split: Splits the pair immediately• Steady Split: After all differential data is copied, the

pair is split.For HTI and SS, this is the only option you can select.

Default: Quick Split

Copy Pace list (SI and SIz only.)The speed at which the split operation is performed.Values: Faster, Medium, SlowerDefault: MediumFor HTI and SS pairs, a hyphen (-) is shown.


Confirm window


Item Description

Primary Volume • LDEV ID: The P-VOL’s LDEV identifier• LDEV Name: The P-VOL’s LDEV name• Emulation Type: The P-VOL’s emulation type• Capacity: The P-VOL’s volume capacity• CLPR: The P-VOL’s CLPR number




Split Type • Quick Split: Splits the pair immediately• Steady Split: Splits the pair after all differential data is

copied.

Copy Pace (SI and SIz only.)


Item Description

The speed at which the split operation is performed.Values: Faster, Medium, SlowerFor HTI and SS pairs, a hyphen (-) is shown.

Secondary Volume • LDEV ID: The S-VOL’s LDEV identifier• LDEV Name: The S-VOL’s LDEV name• Emulation Type: The S-VOL’s emulation type• Capacity: The S-VOL’s volume capacity• CLPR: The S-VOL’s CLPR number



Resync Pairs wizardUse this wizard to resynchronize pairs. This wizard includes the followingwindows:

• Resync Pairs window• Confirm window

Resync Pairs windowUse this window to specify resync operation details.

For full information, see Resynchronizing pairs on page 5-14.



Item Description





Item Description


Secondary Volume • LDEV ID: The S-VOL’s LDEV identifier• LDEV Name: The S-VOL’s LDEV name• Emulation Type: The S-VOL’s emulation type• Capacity: The S-VOL’s volume capacity• CLPR: The S-VOL’s CLPR number




Resync Type The type of resynchronization is specified:• Normal Copy (Primary > Secondary)• Reverse Copy (Secondary > Primary)• Quick Resync (Primary > Secondary)• Quick Restore (Secondary > Primary)For more information, see Types of resync operations onpage 5-12.

Copy Pace list (SI and SIz only.)The speed at which the split operation is performed.Values: Faster, Medium, SlowerDefault: MediumFor HTI and SS pairs, a hyphen (-) is shown.


Confirm window


Item Description





Resync Type The resync type.Values:• Normal Copy (Primary > Secondary)


Item Description

• Reverse Copy (Secondary > Primary)• Quick Resync (Primary > Secondary)• Quick Restore (Secondary > Primary)For more information, see Types of resync operations onpage 5-12.

Copy Pace (SI and SIz only.)The speed at which the split operation is performed.Values: Faster, Medium, SlowerDefault: MediumFor HTI and SS pairs, a hyphen (-) is shown.

Secondary Volume The secondary information.Values:• LDEV ID: The S-VOL’s LDEV identifier• LDEV Name: The S-VOL’s LDEV name• Emulation Type: The S-VOL’s emulation type• Capacity: The S-VOL’s volume capacity• CLPR: The S-VOL’s CLPR number




Suspend Pairs windowUse this window to suspend pair creation.

For full information, see Suspending pair creation on page 5-8.



Item Description


Copy Type Shows the following types of pairs:• SI-L1: SI L1• SI-L2: SI L2• TI: TI• SS: SS• SIMF: SIz





Delete Pairs windowUse this window to delete pairs.

For full information, see Deleting pairs on page 5-15.


Item Description




Status The pair status.


Item Description

For more information, see Pair status definitions on page6-2.


Snapshot Date (HTI and SS only.)The date and time that a snapshot was acquired.For SI and SIz, a hyphen (-) is shown.

Pool Name (ID) (HTI and SS only.)The pool name and identification number.For SI and SIz, a hyphen (-) is shown.


Edit Mirror Units dialog boxUse this dialog box to change mirror unit numbers.

Item Description

Mirror Unit Mirror unit number assigned to L1 and L2 volumes (SIonly). For more information, see the step on MU number inCreating pairs on page 5-4.

Change Options dialog boxUse this dialog box to change the Split Type and Copy Pace. The changes youmake in this dialog box applies to all new pairs you create.


Item Description

Split Type • Non Split: Does not split the pair• Quick Split: Splits the pair immediately. Specify this if

you want to have the S-VOL available for read andwrite I/O immediately after the pair split operation isissued. Any remaining differential data is copied to theS-VOL in the background.

• Steady Split: After all differential data is copied, thepair is split.

Default: Non Split

Copy Pace (SI and SIz only.)The speed at which the split operation is performed.Values: Faster, Medium, or SlowerDefault: MediumFor HTI and SS pairs, a hyphen (-) is shown.

Add Reserve Volumes WizardUse this wizard to reserve a volume as a S-VOL.

Add Reserve Volumes windowUse this window to select LDEVs for use as reserved S-VOL.

For full information, see Reserving secondary volumes on page 4-2.



Item Description

LDEV ID LDEV identification number.

LDEV Name LDEV name

Emulation Type Emulation Type of each LDEV

Capacity Capacity of each LDEV

Number of Paths Number of paths to each LDEV


Item Description

LDEV ID Selected reserved volume’s LDEV identifier.

LDEV Name Selected reserved volume’s LDEV name

Emulation Type Selected reserved volume’s emulation type

Capacity Selected reserved volume’s capacity



Confirm window


Item Description

LDEV ID Selected reserved volume’s LDEV identifier.

LDEV Name Selected reserved volume’s name



Number of Paths Number of paths for each LDEV

Remove Reserve Volumes windowUse this window to remove the reserve attribute from a volume.

For full information, see Removing reserve attribute from a volume on page6-9.


Selected Reserve Volumes table

Item Description

LDEV ID Selected reserved volume’s LDEV identifier

LDEV Name Selected reserved volume’s LDEV name




Reserve Consistency Groups wizardUse this wizard to reserve consistency groups for SIz.

Reserve Mainframe CTGs windowUse this window to reserve a mainframe consistency group.

For full information, see Reserving a consistency group on page 4-3.


Available and Selected Consistency Groups tables

Item Description

CTG ID Consistency group’s identifier

Confirm window


Available and Selected Consistency Groups tables

Item Description

CTG ID Consistency group’s identifier.

Status Consistency group’s status.“Mainframe Reserved” is a reserved mainframe consistencygroup’s status.

Release Reserve Mainframe CTGs windowUse this window to release a mainframe consistency group.

For full information, see Releasing a reserved consistency group on page 6-9.

Selected Reserved Consistency Groups table

Item Description

CTG ID The consistency group’s identifier whose reserved status isto be released.

Status Consistency group’s status.Value: Mainframe Reserved: A reserved mainframeconsistency group’s status.

Edit Local Replica Option wizardUse this wizard to enable and disable options that affect performance.


Edit Local Replica Option windowUse this window to specify options that affect performance.

For full information, see System options that affect performance on page 4-4.

SIMF/FCv2/FCSE System Options table

Item Description

System Option Options that you can change.Values:• Swap & Freeze• Host I/O Performance• FC Slower Copy1 (FCv2 and FCSE only)• FC Slower Copy2 (FCv2 and FCSE only)• Copy Pace Ext. Slower1• Copy Pace Ext. Slower2• Copy Pace Ext. NoneFor more information, see Setting performance options onpage 4-5.

Status Shows whether the option is currently enabled or disabled.

Enable button Click to enable the selected option.

Disable button Click to disable the selected option.


Confirm window

SIMF/FCv2/FCSE System Options table

Item Description

System Option Options that can be changed.

Status Shows whether the option is currently enabled or disabled.


DConfiguration operations (secondary

window)

This appendix provides instructions for configuring SIz using the previous SNGUI, which opens in a secondary window.

□ Configuration workflow

□ Setting up source and target volumes

□ Reserving T-VOLs

□ Reserving a consistency group

□ Setting performance options

Configuration operations (secondary window) D-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Configuration workflowSetup for SIz consists of the following:

1. Ensuring that source and target volumes are set up correctly.2. (Optional) Reserving volumes for use as T-VOLs.3. Setting the HOST I/O Performance option, which boosts I/O performance,

though copy time slows as a result. (Optional.)

Setting up source and target volumesSet up the source and target volumes before making copies. Ensure that thevolumes you plan to use meet the requirements for pair volumes in Planningpair volumes on page 2-5.

Reserving T-VOLsThis is an optional feature you can use to reserve volumes that are notassigned to a pair (“SIMPLEX” status) for use as T-VOLs. The storage systemrejects write I/Os to reserved volumes except those that are split (“Split/SUSPOP” status).


Volumes to be reserved must be:

• Not assigned to a pair (“SIMPLEX” status)• Unreserved and unpaired

1. Select the volume or volumes that you want to reserve offline from thehost.

2. In SN, click Actions > Local Replications > SIMF/FCv2 > PairOperation.

3.

Change to Modify mode by clicking the icon.4. In the tree in the Pair Operations window, select the appropriate port or

host group CU image for the volumes you want to reserve.Related volumes are shown in the volume list.

5. To show unreserved volumes (“SIMPLEX” status), complete the following:

a. Click Display Filter.b. Clear the Reserved and Pair check boxes.c. Select Non-Pair, and click OK.

6. In the Volume list, right-click the desired unreserved pair (“SIMPLEX”status), then click Change Reserve from the menu.

D-2 Configuration operations (secondary window)Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

7. In the Set Reserve Attribute dialog box, confirm that the volumes youwant to reserve are shown and selected, then click OK.The selected volumes are shown in the Preview list.

8. In the Pair Operations window, click Apply.

Reserving a consistency groupA consistency group number is required when assigning pairs to a consistencygroup. Once you have assigned pairs to a consistency group, you can performpair operations on the pairs in the group, including consistency group pair-split.

1. In SN, click Actions > Local Replications > SIMF/FCv2 > CTG.


2.

Change to Modify mode by clicking the icon.3. Select and right-click one or more CTGs with status Free, then click Add

CT Group.4. Click Apply. The status changes to Reserved.

You can remove the reserve attribute by selecting the Reserved group orgroups, right-clicking, and selecting Delete CT Group.

Setting performance optionsYou can enable and disable the following options that affect performance. Fordescriptions of these options, see System options that affect performance onpage 4-4.

If you have both SIz and SI pairs, Hitachi recommends that you enable thisoption on both; otherwise host I/O response may not improve.

1. In SN, click Actions > Local Replications > SIMF/FCv2 > Option.2.

Change to Modify mode by clicking the icon.3. In the ShadowImage for Mainframe Option window, select the option

you want and click Apply.


EPair operations (secondary window)

This appendix provides instructions for performing pair operations using theprevious SN GUI, which opens in a secondary window.

□ Pair operations workflow

□ Check pair status

□ Creating pairs

□ Splitting pairs, creating and splitting pairs

□ Suspending pair creation

□ Resynchronizing pairs

□ Deleting pairs

Pair operations (secondary window) E-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Pair operations workflowA typical pair-operations workflow follows:

• Check pair status. Each operation requires a pair to have a specific status.You also check pair status to ensure that an operation completedsuccessfully.

• Create the pair, in which the T-VOL becomes a duplicate of the S-VOL.You can create the pair and immediately split it so that you can haveinstant access to the T-VOL.

• Split the pair, which separates the source and target volumes and allowsuse of T-VOL data by secondary applications.

• Resynchronize the pair, in which the T-VOL is again updated from the S-VOL.

• Delete the pair, in which the pair relationship between the pair volumes isended, though the data remains.

Check pair statusEvery pair operation requires the pair to have a specific status. When youwant to perform a pair operation, check pair status to ensure that you canproceed successfully.

• For pair status definitions and instructions for finding pair status, seeMonitoring the system on page 6-2.

Creating pairsWhen you create the initial copy, data in the S-VOL is copied to the T-VOL.During the operation, the S-VOL can receive updates from the host. When theinitial copy is completed, the updated data in the S-VOL—differential data—iscopied to the T-VOL periodically (update copy).

You can create the pair and immediately split it so that you can have instantaccess to the T-VOL. For more information about creating and splitting pairs,see Splitting pairs, creating and splitting pairs on page E-4.


• Make sure that your volumes are set up for pairing. For more information,see Planning pair volumes on page 2-5.

• If the S-VOL is used with another pair, the pair status of the existing pairsmust be “DUPLEX”.

• If the S-VOL is not used with another pair, the S-VOL and T-VOL must notbe assigned to a pair (“SIMPLEX” status).

• Because pair creation affects performance on the host, observe thefollowing:

¢ Create a pair when I/O load is light.

E-2 Pair operations (secondary window)Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

¢ Limit the number of pairs that you create simultaneously.• When a pair is created, the T-VOL’s LDEV is allocated to the same

processor blade to which the S-VOL’s LDEV is allocated.

WARNING: The SIz paircreate operation overwrites all existing data on theT-VOL. The user is responsible for backing up data on the T-VOLs beforecreating SIz pairs.


2.

Change to Modify mode by clicking the icon.3. In the tree, in the Pair Operations window, select the CU image where

the volumes to be S-VOLs are located.Related volumes are shown in the volume list.

4. In the volume list, select the volumes that are the S-VOLs. Do not selectreserved volumes.

5. Right-click your selections and select Add Pair.

6. In the Add Pair dialog box, verify that the desired S-VOLs are shown inthe pair list. To remove a volume, right-click and select Delete.

7. Select the S-VOL that you want to pair.8. In Copy Pace, select the pace at which data is to be copied, Slower,

Medium, or Faster. System performance is affected by the pace youselect, less for Slower, more for Faster.


Note: The copy pace you assign is always reflected to any pairs that youadded earlier and are still present in the Preview list. To maintain thecopy pace given to the earlier pairs, click Apply before adding new pairswith a different copy pace.

9. Show the volumes available for T-VOLs by selecting the following filtersfrom the Select T-VOL box:

¢ Select an LDKC (if selectable).¢ Select the appropriate CU image.¢ Select a Volume Type to show internal or external volumes. You can

select both if desired.¢ Select an Attribute to show volumes previously reserved as T-VOLs,

or volumes that are not reserved. You can select both if desired.10. Select the volume to be the T-VOL from the volume list in the Select T-

VOL box.11. Click Set. This places the volume as the T-VOL in the pair list.12. Add a second or third T-VOL to the same S-VOL as desired.13. If you need to change a T-VOL, highlight the pair then select the new

volume in the T-VOL list and click Change. The changed pair is shown inthe pair list.

14. Click OK when finished creating pairs.15. In the Pair Operation window, review the information in the Preview

list. To change a selection, right-click it, select Modify, and make yourchanges.

16. Click Apply to commit the pairs to the storage system.

Splitting pairs, creating and splitting pairsUpdate copying continues until the pair is split. After the pair is split, updatescontinue to the S-VOL but not to the T-VOL; data in the T-VOL is ensured atthe time of the split. All update data are stored in the differential bitmap foruse when resynchronizing the pair.

You can use one of the following options to split a pair:

• Steady split, which is a typical pair split operation in which anyremaining differential data from the S-VOL is copied to the T-VOL andthen the pair is split.

• Quick split, in which the pair is immediately split so that the T-VOL isimmediately available for read and write I/O. Any remaining differentialdata is copied to the T-VOL in the background.


• Pair status must be one of the following:

¢ If you are splitting an existing pair, “DUPLEX”¢ If you are creating and immediately splitting a pair, “SIMPLEX” status


• For a split operation on an existing pair to complete faster, stop hostaccess to the S-VOL.

• If you are performing multiple split operations before clicking Apply, bothCopy Pace and Split Type that you set during the last operation are thesettings that are used for all split operations (in the Preview list) whenyou click Apply.

• The split operation may take longer than normal if system option mode459 is ON and the T-VOL is an external volume. The reason is becauseafter differential data is copied to cache, it must also be destaged to theexternal storage system, which takes more time.


2.


the pairs or volumes are located.Related volumes are shown in the volume list. If a volume is alreadypaired, pair information is also shown.

4. Select the pair or pairs to be split, or select the volume to be split.5. Right-click the selection and from the menu, click Split Pair.

6. For Split Volume Pair, complete the following:

a. Ensure the pairs that you want to split are shown.


b. Select the volume that is not assigned to a pair (“SIMPLEX” status)that you want to be the S-VOL in an L1 pair-create-and-splitoperation.

7. From Copy Pace, select the pace at which the pairs are to be split,Slower, Medium, or Faster. Copy Pace affects the host I/Operformance: a slower pace minimizes impact, a faster pace has thegreatest impact. The pace you select is used for all pairs in the operation.

8. From Select Split Type, select one of the following:

¢ Steady Split: Any remaining differential data between S-VOL and T-VOL is copied to the T-VOL before the split. Read and write access tothe T-VOL is available only when the operation completes.

¢ Quick Split: Read and write access to the T-VOL is availableimmediately. Any remaining differential data between S-VOL and T-VOL is copied to the T-VOL in the background.

9. If you are splitting an existing pair or pairs, click OK and go to the lasttwo steps in this procedure.If you are creating and splitting a pair, continue to the next step.

10. Show the volumes available for T-VOLs by selecting the following filtersfrom the Select T-VOL box:

¢ Select an LDKC (if selectable).¢ Select the appropriate CU image.¢ Select a Volume Type to show internal or external volumes. You can

select both if desired.¢ Select an Attribute to show volumes previously reserved as T-VOLs,

or volumes that are not reserved. You can select both if desired.11. Select the volume to be the T-VOL from the volume list in the Select T-

VOL box.12. Click Set. This places the volume as the T-VOL in the pair list.13. If creating and splitting pairs, pair additional T-VOLs to a S-VOL as

desired.14. To replace an T-VOL in the volume/pair list, select the pair, select the

desired T-VOL in the Select T-VOL box and then click Change.15. To complete the operation, click OK.16. In the Pair Operation window, review the information in the Preview

list. To change a selection, right-click it, select Modify, and make yourchanges.

17. Click Apply to commit the operation to the storage system.

Splitting pairs in a consistency groupUse consistency group pair-split to simultaneously split all the pairs in aconsistency group.

If you use BCM, you can split the pairs at a specified time. With PPRC, youcan split the pairs in a consistency group, but without a specified time. For


more information, see the instructions in Appendix A, Pair operations usingPPRC on page A-1.


• Make sure to change the status of pairs in the same consistency groupaccording to the copy group.

• On registering split time:

¢ When you register the Split time, you can only perform Suspend orDelete pair operations. Split time is rejected if you perform Add Pair,Split, or Resync operation. If you want to perform one of theseoperations, reset the registration of the Split time.

¢ The Split time you specified is reset when power is switched off.¢ The operation is performed when the read/write request—with a time

stamp past the specified Split time—is received. The Split operationcan be delayed if you do not issue a read/write request. If I/O doesnot occur, the storage system timer performs the split operation.

¢ If the Split time is registered, and if there is a pair in the consistencygroup that cannot be split completely during the Split operation, thestatus of this pair remains the same as before the Split operation.

• Before performing consistency group pair-split a second time, verify thatstatus of all the pairs in the same consistency group is changed to thestatus which is specified by the YKEWAIT command.For detailed information about monitoring status changes for copy pairs ina specified copy group using the YKEWAIT command, see the BusinessContinuity Manager User’s Guide.

• For more information about splitting pairs using consistency group pair-split on pairs shared with TCz or URz volumes, see Consistency grouppair-split for shared volumes on page 2-11.

1. Define a consistency group for the SIz pairs that you will split usingconsistency group pair-split.

2. Specify the consistency group as a BCM copy group, or register the splittime.When you specify the copy group, select the split type: Quick Split orSteady Split. When you register the split time, the split type is QuickSplit.

3. Specify the consistency group split option, then create the pairs.4. Split the pairs in the consistency group. The pairs are split

simultaneously.

Suspending pair creationSuspending the creation of pairs (initial copy to the T-VOL) changes the pairstatus to “Suspend/SUSPER”. The T-VOL continues accepting write I/Ooperations from the S-VOL and marks the entire S-VOL track as differencedata. Resynchronizing a suspended pair changes the pair status to “Resync/PENDING” and copies the entire S-VOL to the T-VOL. While the pairresync


operation for a split pair can be very fast, the pairresync operation for asuspended pair takes as long as the initial copy operation.

The storage system automatically suspends a pair when it detects an errorcondition related to an update copy operation, or when it cannot keep thepair mirrored.


2.



4. Select the pairs that you want to suspend (or the volumes whose pairsyou want to suspend), right-click the selected pairs to show the menu,and select the Suspend Pair command to open the Suspend VolumePair dialog box.

5. On the Suspend Volume Pair dialog box, select the pairs you want tosuspend, and click OK to reflect the settings to the Preview List on thePair Operation window.To remove pairs from the list, complete the following:

a. Select the unneeded pairs.b. Right-click while selecting the pairs.c. From the menu, select the Delete command.

6. Repeat steps 4 and 5 to suspend additional pairs in the Pair Operationwindow.

7. In the Pair Operation window, click Apply to suspend the specifiedpairs.The Pair Operation window shows the results of the Suspend VolumePair operations, that is, the pair status changed to “Suspend/SUSPER”.


Resynchronizing pairsYou resynchronize a pair that was split by a user or suspended by the storagesystem. Resynchronizing updates the T-VOL so that it is again paired with theS-VOL.

Caution: Resynchronizing the pair does not guarantee that S-VOL data is thesame as T-VOL data. Data in the two volumes is the same only when the pairis split.

• You can forward resync, from S-VOL to T-VOL, and reverse resync, fromT-VOL to S-VOL.

¢ You can perform a Normal Copy or a Quick Resync, in both directions.¢ The S-VOL remains accessible to hosts for both read and write

operations during a Normal Copy operation. The T-VOL is inaccessibleto hosts during a Normal Copy operation.

¢ The S-VOL remains read-disabled during the Reverse Copy operation.• In a forward Quick Resync from S-VOL to T-VOL, status changes to

“DUPLEX” without actually resynchronizing the data in the T-VOL.Differential data is copied to the T-VOL when update copy operations areperformed.

¢ The S-VOL remains accessible to all hosts for both read and writeoperations during a quick resync operation. The T-VOL is inaccessibleto all hosts during a Normal Copy operation.

¢ In a forward Quick Resync you cannot be sure the data in the S-VOLand T-VOL is the same when an host I/O is not present during theoperation. Split the pair to ensure that data is the same.

• In a Quick Restore (reverse Quick Resync), the S-VOL and T-VOL areswapped. No actual data is copied, and the pair is placed in “DUPLEX”status.

¢ The S-VOL and T-VOL are inaccessible during this operation. Whenthe operation completes, the S-VOL is accessible.

¢ When differential data between S-VOL and T-VOL is small, theReverse Copy operation may be completed faster than the QuickRestore operation.

• Performing LDEV maintenance work during the Quick Restore processincreases the time for the operation to complete.

Note: You can use PPRC to perform a Normal Resync operation on all pairs ina consistency group. To perform the Quick Resync, Reverse Copy, or QuickRestore with PPRC, you must run the desired command on one pair at a time.


• To Reverse Copy or Quick Restore, the pair must be split (“Split/SUSPOP”status).

• While you are performing a Quick Restore, make sure of the following:

¢ The SVP is in View mode, not Modify mode


¢ SN configuration and other tasks are stopped• The pairresync normally takes less time when the pair is split (“Split/

SUSPOP status) than when the pair is suspended (“Suspend/SUSPER”status). This is because the amount of differential data accumulated for asplit pair is usually far less than the total amount of data in the S-VOL,which must be copied in full when the pair was suspended by the storagesystem.

• If you use BEDs supporting encryption, you can create an SIz pair byusing an encrypted volume and a non-encrypted volume. For example,you can create the pair specifying an encrypted volume as the S-VOL anda non-encrypted volume as the T-VOL. In this case, data in the encryptedS-VOL changes to non-encrypted data in the T-VOL.

• If a pair consists of encrypted volumes and a non-encrypted volume, andthe Quick Restore is run, the S-VOL and T-VOL encryption statuses arereversed.

• With a Quick Restore, SN may show outdated information. Click RefreshView to ensure the most up-to-date information.

• To keep the S-VOL and T-VOL unsynchronized when performing a QuickRestore, enable the Swap&Freeze option prior to performing theoperation. Update copy operations are then suppressed when the QuickRestore is completed, and the pair is in “DUPLEX” status.

• If you perform a reverse or quick restore operation on a pair whose S-VOL is also paired with other T-VOLs, the S-VOL and other T-VOLs are nolonger synchronized.

• For Reverse Copy or Quick Restore operation, the following restrictionsapply:

¢ Pairs sharing the same S-VOL must be split (“Split/SUSPOP” status) orsuspended (“Suspend/SUSPER” status).

¢ If the pair shares a volume with TCz or URz, the TCz or URz pair mustbe suspended to perform either backward resync operation.

¢ You cannot create a TCz or URz pair with a volume shared by SIzduring either backward resync operation.

¢ When the Reverse Copy or Quick Restore operation is in progress, youcannot create, split, or resync any pair sharing the same S-VOL. Youcan delete or suspend the pairs, however.

¢ The Quick Restore operation cannot be performed on a Cross OS FileExchange pair.


2.




4. In the volume list, select the pairs to be resynchronized, right-click, andselect Resync Pair.

5. In the Resynchronize Volume Pair dialog box, select the Resync Typeas follows:

¢ Normal Copy(S->T) to resynchronize the pairs normally. Alldifferential data is updated to the T-VOL.

¢ Quick Resync(S->T) to immediately change pair status to“DUPLEX”. Resynchronization of data does not occur immediately.Differential data is copied during update copying.

¢ Reverse Copy(T->S) to copy the T-VOL data to the S-VOL. Alldifferential data is updated to the S-VOL.

¢ Quick Restore(T->S) to swap the S-VOL and T-VOL. Any differentialdata between the volumes is copied during update copying.

6. From Copy Pace, select the pace at which the pairs are to beresynchronized, Slower, Medium, or Faster. Copy Pace affects thehost I/O performance: a slower pace minimizes impact, a faster pace hasthe greatest impact. The pace you select is applied for all pairs in theoperation.

7. Click OK.8. In the Pair Operation window, review the information in the Preview

list. To change a selection, right-click it, select Modify, and make anychanges.

9. Click Apply to commit the operation to the storage system.10. Make sure that pair status changes to “DUPLEX” before attempting any

other operation.

Note: Note the following:

• If the reverse or Quick Restore ends abnormally, the pair is suspended(“Suspend/SUSPER” status). In this case, the S-VOL is read/write-enabled


for all hosts, but the data is not guaranteed. The T-VOL remains write-disabled (read-only) and data is not guaranteed. The status of other pairssharing the same S-VOL does not change.

• After a reverse copy or quick restore operation is performed, make surethat the pair status changes to “DUPLEX” before performing a TCz resumepair operation. If you perform the TCz resume pair operation before thepair status changes to “DUPLEX”, the command (resume pair operation)is rejected.

Deleting pairsYou can delete a pair when you do not need it. Deleting a pair unassigns theS-VOL and T-VOL from the pair (“SIMPLEX” status) and their data remainsintact. After deletion, both volumes are available for use in another pair.


• The pair cannot be in the process of Quick Split (“V-Split/SUSPVS”status).

• When a pair is created, the processor blade allocated to the P-VOL's LDEVis also allocated to the S-VOL's LDEV. When a pair is deleted, theprocessor blade that was originally allocated to the S-VOL'S LDEV isallocated to it again. If the original processor blade was removed, anotherprocessor blade is allocated.

• To perform tasks such as pair operation or event waiting, after deleting apair, wait 10 seconds—until the volume status changes from “Deleting/TRANS” to “SIMPLEX” as is unassigned from the pair. If you do not wait10 seconds, the operation might end abnormally.

1. Synchronize the S-VOL and T-VOL before deleting the pair. Complete thefollowing:

a. Wait until all write I/Os to the P VOL are complete.b. Set the S-VOL offline.c. Split the pair. This copies differential data to the S VOL.


3.



5. Select the pairs you want to delete, right-click, and from the menu, selectDelete Pair.


6. If you selected a pair that you do not want to delete, select the pair onthe Delete Pair dialog box, right-click, then click Delete. The pair isremoved from the deletion list.

7. Click OK.8. In the Pair Operation, review the information in the Preview list.9. Click Apply to commit the operation to the storage system.


FMonitoring and maintaining the system

(secondary window)

This appendix provides information and instructions for monitoring andmaintaining the SIz system using the previous SN GUI, which opens in asecondary window.

□ Monitoring the system (secondary window)

□ Maintaining the system (secondary window)

Monitoring and maintaining the system (secondary window) F-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Monitoring the system (secondary window)Monitoring helps you keep track of pairs and volumes and their current andpast conditions. Monitoring should be an ongoing activity. This topic providesinformation for monitoring the following:

• Pair status.• Pair and pair volume details.• Status and other pair information for pairs in a consistency group.• T-VOL path information.• Number of pairs in the storage system, with remaining license capacity.• A pair’s history of operations.

Monitoring pair activity, status (secondary window)Monitoring the SIz system is necessary to maintain your pairs.

• Each operation requires a specific status or statuses. When you want toperform a pair command, first check the pair’s status.

• Pair-status changes when an operation is performed. Check status to seethat pairs are operating correctly and that status is changing to theappropriate state during and after the operation.

Monitoring using the SN GUI is done at the user’s discretion. Monitoringshould be repeated frequently. Email notifications of problems in pairoperations can be set up using the GUI.


2. Locate the pair whose status you want to review. Review pair status inthe Status column.

You can view more details for the pair by right-clicking and selecting Detail.For more information about the fields, see Reviewing pair, volume details onpage F-3.

Pair status definitions (secondary window)

When checking your pairs’ status in the SN secondary window, click RefreshView to make sure pair data is current.

See the following topics related to pair status:

• Pair status definitions on page 6-2.• Status, pair operations permitted on page 6-5.• Status of unaffected S-VOLs, operations permitted on page 6-5.

F-2 Monitoring and maintaining the system (secondary window)Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Reviewing pair, volume detailsYou can review the data related to pairs and their volumes. This includesvolume capacity, pair status, S-VOL and T-VOL identifiers, and several otherdetails.

Note: LDEVs for S-VOLs and T-VOLs listed in SN may end in the followingspecial symbols:

• A pound or gate symbol (#), which indicates an external volume (forexample, 00:00:01#).


2. In the tree, select the CU image where the pairs or volumes are located.Related volumes are shown in the volume list.

3. From the volume list, complete the following:

a. Select and right-click the volume or pair whose information you wantto see.

b. From the menu, select Detail.The Detail dialog box opens.

Field descriptions are provided in the following table.

Field Description

S-VOLInformation

Volume ID: Shows LUN information using LDKC number:CUnumber:LDEV number format.CLPR: Shows CLPR number:CLPR name.

VolumeInformation

Shows the volume’s emulation type and capacity.

Pair Information • S-VOL: Shows LUN information using LDKC number:CUnumber:LDEV number format.


Field Description

• T-VOL: Shows LUN information using LDKC number:CUnumber:LDEV number format.

• Status: The status of the pair.• Sync: Percentage that S-VOL and T-VOL are synchronized.• CTG: The consistency group number shows if the pair is

registered in the group. If the pair is not registered to theconsistency group, dashes (---) are shown.

• CLPR(P): The identifier for the S-VOL’s cache logical partition(CLPR) shows in CLPR number:CLPR name format.

• CLPR(S): The identifier for the T-VOL’s cache logical partition(CLPR) shows in CLPR number:CLPR name format.

• Tvol Mode: Indicates whether the T-VOL has been written to andwhether it can be read. For more information about Svol Mode,see Volume list on page G-3.

• Copy Pace: Indicates the speed that data is copied according tothe pair status. For more information about Copy Pace, seeVolume list on page G-3.

• Relationship (S): The current state of the volume in terms ofwhether the Compatible FlashCopy® or Compatible FlashCopy®SE relationship is established or not. For more information aboutCompatible FlashCopy® SE, see the Hitachi CompatibleFlashCopy® User Guide.

Refresh thewindow after thisdialog box isclosed.

If you select the check box, the information shown in the PairOperation window is updated after the Detail dialog box closes. Ifyou do not select the check box, the information in the PairOperation window is the same before and after you close the Detaildialog box.

Reviewing pair, license informationYou can check the current state of your pairs and licensed capacity. Do thisusing the Information dialog box.


2. Complete the following:

a. Right-click the volume list, in any location.b. From the menu, select Information.

The Information dialog box opens.Field descriptions are provided in the following table.


Field Description

SIz pair(s) Shows the number of SIz pairs/and the total number of pairtables for SI and SIz. For example: 12/12.Notes:• The maximum number of pairs allowed in one storage

system is 16,384, including migration plans andrelationships. For example, if a storage system contains TIor SS pairs, migration plans of Volume Migration, andrelationships of Compatible FlashCopy® V2 and CompatibleFlashCopy® SE, the maximum number of pairs allowed forSIz would be 16,384 minus these.

• Volume size also limits the number of pairs. For moreinformation, see Planning number of pairs on page 2-6.

Reserve volume(s) The number total number of reserved volumes for SI and SIz.

CompatibleFlashCopy® V2/CompatibleFlashCopy® SErelationship(s)

The number of Compatible FlashCopy® V2 and CompatibleFlashCopy® SE relationships.

Remaining pair table(s) The number of remaining pair tables in the storage system/andthe total number of pair tables in the system. For moreinformation, see Planning number of pairs on page 2-6.The following software use pair tables:• SIz• Volume Migration (when migration plan is used)

Remaining differentialtable(s)

The number of remaining differential tables in the storagesystem/and the total number of differential tables in thesystem. For more information, see Planning number of pairs onpage 2-6.


Field Description

The following software use pair tables:• SIz• Compatible FlashCopy® V2• Compatible FlashCopy® SE• SS• Volume Migration

Used Capacity (TB) Shows license information used by SIz, and the total licensecapacity reserved for SIz. “Unlimited” is shown when there isno limit on license capacity for SIz.

Reviewing a pair’s operation history You can review the operations that have been performed on a pair using theHistory window.

1. In SN, click Actions > Local Replications > SIMF/FCv2 > History.If some of the pairs include LUSE volumes, or if the total number of thefollowing pairs and migration plans is 500 or more in the storage system,you may need to wait for a while until the History window showsoperation history. In addition, if you use 1,000 or more pairsconcurrently, some operation history might not be recorded.The History window show the following pair types:

¢ SIz¢ Compatible FlashCopy®¢ Compatible FlashCopy® SE


2. Locate the SIz History list in the upper area.3. To change the order in which items are listed, click a column title 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 dividedinto multiple pages and only the list which is currently shown issorted.

¢ If you click the same column title again, you can switch the sortingorder (Ascending or Descending).

4. If the information on the list is not updated, click File and then Refresh.The list is updated to the latest information.For operations involving the copying process, the History window doesnot show information about the operations until the copying processstarts. If you perform an operation on a pair before the copying processstarts, the History window does not show information about theoperation.

5. If there are many records of operations, click the scroll button. The listscrolls and the operation history that was not previously shown is shown.If you click and drag down the frame border that divides the Historywindow into upper and lower panes, you can expand the display area ofthe list.

6. If there are more than 16,384 records of operations, click Next.The list shows 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 storage system saves up to 512,000 records of latest operations.

Reviewing pair details for a consistency groupYou can check information including status about the pairs belonging to aconsistency group.

1. In SN, click Actions > Local Replications > SIMF/FCv2 > CTG.2. Locate the consistency group whose pair information you want to review,

right-click, and select CT Group Status.The CT Group Status dialog box opens. You cannot edit the pairinformation.

Field Description

CTG Consistency groups that you can show.

S-VOL S-VOL’s LDKC number:CU number:LDEV number

Status Pair’s current status

T-VOL T-VOL’s LDKC number:CU number:LDEV number

Sync Percentage of synchronization between S-VOL and T-VOL

Emulation Pair’s emulation type

Capacity (Cyl) Volume capacity by number of cylinders

CLPR(S) S-VOL’s cache logical partition

CLPR(T) T-VOL’s cache logical partition


Maintaining the system (secondary window)Some maintenance tasks are a response to behavior discovered duringsystem monitoring. You can also change certain settings to keep the systemin tune with your changing requirements.

This topic provides maintenance information and instructions for Removingreserve attribute from a volume on page F-9.

For other maintenance tasks, including maintaining pairs during system anddevice maintenance, see Maintaining the system on page 6-9.

Removing reserve attribute from a volume You can remove the T-VOL reserve attribute from a volume.


Before removing the reserve attribute from a volume, make sure that thestatus is SIMPLEX.


2.

Click to change to the Modify mode.3. In the tree, select the appropriate CU group for the volumes from which

you want to remove the reserve attribute.Related volumes display in the volume list. To show only reservedvolumes (“SIMPLEX” status), click Display Filter, then complete thefollowing:

a. Make sure that the Pair attribute is cleared.b. Select Reserve.c. Click OK.

4. In the volume list, right-click the desired SIMPLEX volumes, then clickChange Reserve from the menu.The Reset Reserve Attribute dialog box opens.


5. Select the pairs from which you want to remove the attribute, then clickOK.The selected volumes display in the Preview list.

6. To change a selection, right-click, select Modify, and make your changes.7. When ready, on the Pair Operations window click Apply.


GShadowImage for Mainframe GUI

reference (secondary window)

This appendix describes the SIz windows and dialog boxes in the previousversion of the SN GUI, which opens in a secondary window.

□ Pair Operation window

□ History window

□ Option window

□ CTG window

ShadowImage for Mainframe GUI reference (secondary window) G-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Pair Operation windowUse this window to view SIz pairs.

You can perform the following procedures from the window:

• Creating pairs on page E-2• Splitting pairs, creating and splitting pairs on page E-4• Suspending pair creation on page E-7• Resynchronizing pairs on page E-9• Deleting pairs on page E-12• Monitoring pair activity, status (secondary window) on page F-2

Select one of the following areas of the Pair Operations window forinformation:

Note: The Pair Operation window opens and shows information for SIz andCompatible FlashCopy®/Compatible FlashCopy® SE pairs. This topic explainsthe items related to the SIz pairs. For more information about the itemsrelated to the Compatible FlashCopy®/Compatible FlashCopy® SE pairs, seethe Hitachi Compatible FlashCopy® User Guide.

G-2 ShadowImage for Mainframe GUI reference (secondary window)Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Main components

Field Description

Tree The connected CU image or LDEV ID. Select the desired CU imageor LDEV ID to display related LUs.If you select storage system on the top of the tree, a volume is notshown.

Volume list Pair information. For more information, see Volume list on pageG-3.Note: S-VOLs and T-VOLs listed in SN 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#).

Icons Indicate the following information:

S-VOL

T-VOL

Reserved volume. In Preview list, this is a preview item.

Error. Is shown in Preview list.

SIMPLEX volume. This icon indicates a volume in “SIMPLEX”status when it is shown in the Volume list.

CU. Is shown in Tree.

Root. Is shown in Tree.

Display Filterbutton

When clicked, the Display Filter dialog box appears. In it, you canfilter the fields and volume types in the Volume list.

Previous list Shows the operation(s) you have specified but not yet applied tothe storage system. You can change or delete the operations whenyou right-click the item in the Preview list.

Apply Saves changes shown in the in the Preview list to the storagesystem.If an error occurs during an operation, the failed operation willremain in the Preview list with an error icon () shown on the left ofthe operation name.For more information about the SIz error codes, see the HitachiStorage Navigator Messages.

Cancel Cancels the changes shown in the Preview list.

Volume listThe Volume list shows the installed volumes on the selected CU image, withstorage system and pair information for each volume.

You can filter the information in the list to show the data you want, includingthe types of volumes that display such as SIz.

For more information, see Display Filter dialog box on page G-6.


The maximum number of volumes on one screen is 1,024. If you have morethan this to view, click Next above the list.

Field Description

Message A message displays if a volume or pair does not exist. If you see themessage in the Volume list, click a different icon in the tree on theleft area of the Pair Operation window.

S-VOL S-VOL information in XX:YY:ZZ format.• XX:YY:ZZ is the LDKC number:CU number:LDEV number

Status Pair status. For more information, see Pair status definitions onpage 6-2.

T-VOL T-VOL information in XX:YY:ZZ format.• XX:YY:ZZ is the LDKC number:CU number:LDEV number

TvolMode Indicates whether the T-VOL has been written to, and whether itcan be read.• A hyphen (-) indicates that it has not been written to and can

be read.• W indicates that it has been written to• N indicates that it cannot be read

Copy Pace Indicates the speed that data is copied according to pair status.• Slower, Medium, or Faster is shown if the pair status is

“PENDING”, “SP-Pend”, “V-Split”, “Resync”, or “Resync-R”.• Dashes (----) display if the pair status is none of the above.Note: When you create SIz pairs by using CCI, the copy pace is setas follows:• When the track size is 1 or 2, Slower is set.• When the track size is 3, Medium is set.• When the track size is 4 to 15, Faster is set.

Sync Indicates the percentage of pair synchronization:• Dashes (----) display for volumes or pairs in “SIMPLEX” and

“Deleting/TRANS” status.• The percentage of copied data is shown for pairs in “PENDING”,

“SP-Pend/TRANS”, “V-Split/SUSPVS”, and “Suspend/SUSPER”status.

• The percentage of identical data in the S-VOL and T-VOL forvolumes in “DUPLEX”, “Split/SUSPOP”, “Resync/PENDING”, or“Resync-R/REVRSY” status.

Emulation The volume’s emulation type.

Capacity (Cyl) The number of cylinders assigned to the volume

CTG The T-VOL’s consistency group number. If you have not set aconsistency group for the T-VOL, dashes (---) are shown.

CLPR (S) The S-VOL’s cache logical partition

CLPR (T) The T-VOL’s cache logical partition


Field Description

Relationship (S) The current state of the volume in terms of whether the CompatibleFlashCopy® or Compatible FlashCopy® SE relationship isestablished or not.For more information about Compatible FlashCopy® SE, see theHitachi Compatible FlashCopy® User Guide.

Preview listThe Preview list is shown below the Volume list. It shows the pairoperations and changes you have made. You can review your changes, makemodifications, and apply them to the storage system.

Field Description

S-VOL S-VOL information in XX:YY:ZZ format.• XX:YY:ZZ is the LDKC number:CU number:LDEV number

T-VOL T-VOL information in XX:YY:ZZ format.• XX:YY:ZZ is the LDKC number:CU number:LDEV number

Copy Pace Speed that data is copied according to the pair status.

CLPR (S) S-VOL’s cache logical partition

CLPR (T) T-VOL’s cache logical partition

Error Code If you click Apply and then the operations in the Preview list fail, anerror code indicates the cause of the error.

Data in the status bar below the Preview list indicate the number of changes,the type of change (the operation), and any command options.

Pair Operation command menuRight-click a volume or pair to open the pair operation command menu. Thefollowing table describes the commands that display in the menu.

Command Description

Detail Opens the Detail dialog box, which shows detailed information forthe selected volume or pair.

Add Pair Opens the Add Pair dialog box, in which you create new pairs.

Split Pair Opens the Split Pair dialog box, in which you split pairs.

Resync Pair Opens the Resync Pair dialog box, in which you resynchronizepairs.

Suspend Pair Opens the Suspend Pair dialog box, in which you suspend pairs.

Delete Pair Opens the Delete Pair dialog box, in which you delete pairs.

Change Reserve Opens the Set/Reset Reserve Attribute dialog box, in which youset/reset the S-VOL reserve attribute.


Command Description

Information Opens the Information dialog box, which shows number of pairs orreserved volumes.

Display Filter dialog box Use this dialog box to filter the volumes on the Pair Operations window. Toopen this dialog box, click Display Filter in the Pair Operation window.

The filter settings you select are effective in the current session only. Theyreset when you select another software product.

Field Description

CLPR Cache logical partition (CLPR)

Volume Type Internal or external volumes are specified. Both boxes are selectedby default. Clear the box you do not want.

Attribute • Volume Attribute. If you select the Reserved check box, onlyreserved volumes display. Reserved volumes include volumesspecified as T-VOLs.

• Pair Attribute. You can select pair volumes or non-pairvolumes.


Field Description

Pair Status Status of the pairs you want to see.

History windowUse this window to view the history of operations performed on SIz,Compatible FlashCopy®, and Compatible FlashCopy® SE pairs and dataassociated with the operations.

• The upper pane shows SIz history.• The lower pane shows Compatible FlashCopy® and Compatible

FlashCopy® SE history.

Field Description

Date Date and time of the operation.

S-VOL The LDKC:CU:LDEV of the S-VOL used in the operation.

T-VOL The LDKC:CU:LDEV of the T-VOL used in the operation.

Code SIz reference codes. The codes refer to the messages shown in thefollowing table.

Message The description of the operation or part of an operation.


The following table shows reference codes.

Code Message Description

4710 DUPLEX START The initial copy started.

4720 DUPLEX END The initial copy ended, and the pairstatus changed to “DUPLEX”.

4730 SUSPOP START The pair split started.

4740 SUSPOP END The pair split ended, and the pair statuschanged to “Split/SUSPOP”.

4750 PENDING STARTREVRSY START

Resynchronization of pairs started.

4760 PENDING ENDREVRSY END

Resynchronization of pairs ended, andthe pair status changed to “DUPLEX”.

4780 SIMPLEX The pair was deleted, and the pairstatus changed to “SIMPLEX”.

4790 DUPLEX SUSPEND The pair was suspended, and the pairstatus changed to “Suspend/SUSPER”.

47D0 COPY ABNORMAL END A copy ended abnormally (reason otherthan above).

47E9 INITIALIZE START Initialization started.

47EA INITIALIZE END Initialization ended normally.

47EB INITIALIZE ENDED ABNORMAL Initialization ended abnormally.

Option windowUse this window to set the Swap&Freeze, the HOST I/O Performance, CopyThreshold, and Copy Pace options. For more information, see System optionsthat affect performance on page 4-4. (FC Slower Copy1, FC Slower Copy2, FCExt. Slower Copy1, and FC Ext. Slower Copy2 are Compatible FlashCopy®options.)


CTG window Use this window to view information about consistency groups that arereserved in a mainframe storage system.


Field Description

CTG Tree Select to show consistency groups:• Storage system shows all the consistency groups.• Reserved shows only reserved consistency groups.• Free shows only unreserved consistency groups.• Used shows only the consistency groups that are currently

used (meaning those with registered pairs).

CTG list • CTG: Consistency group number• Group Status: Shows one of the following consistency group

statuses:- Used (RAID Manager): Consistency group is used andmanaged with CCI.- Used (PPRC/BCM): Consistency group is used andmanaged with PPRC or BCM.- Reserved: Consistency group is reserved.- Free: Consistency group is not being used and is notreserved.- Open: Consistency group is used by an OPEN pair.

• Code: The error code when a consistency group operationfails.

Apply Commits an operation to the storage system.

Cancel Cancels any ongoing operation.


CTG command menu A command menu appears when you right-click a consistency group in theCTG list, as shown below.

Command Description

Add CT Group For reserving a free consistency group. The command is dimmedif the consistency group is used or reserved.

Delete CT Group For changing the status of a reserved consistency group to Free.The command is dimmed if the consistency group is already Free.

CT Group Status For displaying pair information for pairs in the selected group;opens the CT Group Status dialog box. The command is dimmedif the consistency group is already Reserved or Free.

Error Detail For displaying error information of a failed consistency groupoperation. If an error does not exist, the command is dimmed.For SIz error codes and corrective actions, see the Hitachi StorageNavigator Messages.


Glossary

This glossary defines the special terms used in this document. Click the letter links below tonavigate.

#

2DCtwo-data-center. Refers to the local and remote sites, or data centers, in whichTrueCopy for Mainframe (TCz) and Universal Replicator for Mainframe (URz) combine toform a remote replication configuration.In a 2DC configuration, data is copied from a TCz primary volume at the local site to theURz master journal volume at an intermediate site, then replicated to the URzsecondary volume at the remote site. Since this configuration side-steps the TCzsecondary volume at the intermediate site, the intermediate site is not considered adata center.

3DCthree-data-center. Refers to the local, intermediate, and remote sites, or data centers,in which TCz and URz combine to form a remote replication configuration. A 3DCconfiguration can also combine three URz sites.In a 3DC configuration, data is copied from a local site to an intermediate site and thento a remote site (3DC cascade configuration), or from a local site to two remote sites(3DC multi-target configuration).

A

alternate pathA secondary path (port, target ID, LUN) to a logical volume, in addition to the primarypath, that is used as a backup in case the primary path fails.

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Glossary-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

arrayAnother name for a RAID storage system.

array groupSee RAID group.

asyncasynchronous

ATTIME SuspendConsistency group operation that allows multiple pairsplit operations to be performed ata pre-determined time. Also known as ATTIME Split or at-time split.

audit logFiles that store a history of the operations performed from Storage Navigator and theservice processor (SVP), commands that the storage system received from hosts, anddata encryption operations.

B

base emulation typeEmulation type that is set when drives are installed. Determines the device emulationtypes that can be set in the RAID group.

BCbusiness continuity

BCMBusiness Continuity Manager

bladeA computer module, generally a single circuit board, used mostly in servers.

BLK, blkblock

bmpbitmap

C

C/TSee consistency time (C/T).



cacache

cache logical partition (CLPR)Consists of virtual cache memory that is set up to be allocated to different hosts incontention for cache memory.

capacityThe amount of data storage space available on a physical storage device, usuallymeasured in bytes (for example MB, GB, and TB).

cascade configurationIn a 3DC cascade configuration for remote replication, data is copied from a local site toan intermediate site and then to a remote site using TrueCopy and Universal Replicator.See also 3DC.In an SIz cascade configuration, two layers of secondary volumes can be defined for asingle primary volume. Pairs created in the first and second layer are called cascadedpairs.

shared volumeA volume that is being used by more than one replication function. For example, avolume that is the primary volume of a TrueCopy pair and the primary volume of aShadowImage pair is a shared volume.

CCICommand Control Interface

CFLConfiguration File Loader. A Storage Navigator function for validating and runningscripted spreadsheets.

CFWcache fast write

CGSee consistency group (CTG).

CTGSee consistency group (CTG).

CHchannel

channel pathThe communication path between a channel and a control unit. A channel path consistsof the physical channel path and the logical path.



CHAPchallenge handshake authentication protocol

CLcluster

CLIcommand line interface

CLPRcache logical partition

clusterMultiple-storage servers working together to respond to multiple read and writerequests.

command deviceA dedicated logical volume used only by Command Control Interface and BusinessContinuity Manager to interface with the storage system. Can be shared by severalhosts.

configuration definition fileDefines the configuration, parameters, and options of Command Control Interfaceoperations. A text file that defines the connected hosts and the volumes and groupsknown to the Command Control Interface instance.

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 and extended consistency group.

controllerThe component in a storage system that manages all storage functions. It is analogousto a computer and contains a processors, I/O devices, RAM, power supplies, coolingfans, and other sub-components as needed to support the operation of the storagesystem.

copy-on-writePoint-in-time snapshot copy of any data volume within a storage system. Copy-on-writesnapshots only store changed data blocks, therefore the amount of storage capacityrequired for each copy is substantially smaller than the source volume.

copy pairA pair of volumes in which one volume contains original data and the other volumecontains 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 (localcopy) or in different storage systems (remote copy).A copy pair can also be called a volume pair, or just pair.

COWcopy-on-write

COW SnapshotHitachi Copy-on-Write Snapshot

CTGSee consistency group (CTG).

CTLcontroller

CUcontrol unit

currency of dataThe synchronization of the volumes in a copy pair. When the data on the secondaryvolume (S-VOL) is identical to the data on the primary volume (P-VOL), the data on theS-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, cylcylinder

cylinder bitmapIndicates the differential data (updated by write I/Os) in a volume of a split orsuspended copy pair. The primary and secondary volumes each have their own cylinderbitmap. When the pair is resynchronized, the cylinder bitmaps are merged, and thedifferential data is copied to the secondary volume.

D

DASDdirect-access storage device

data consistencyWhen the data on the secondary volume is identical to the data on the primary volume.

data pathThe physical paths used by primary storage systems to communicate with secondarystorage systems in a remote replication environment.



data poolOne or more logical volumes designated to temporarily store original data. When asnapshot is taken of a primary volume, the data pool is used if a data block in theprimary volume is to be updated. The original snapshot of the volume is maintained bystoring the to-be-changed data blocks in the data pool.

DBdatabase

DBMSdatabase management system

delta resyncA disaster recovery solution in which TrueCopy and Universal Replicator systems areconfigured to provide a quick recovery using only differential data stored at anintermediate site.

deviceA physical or logical unit with a specific function.

device emulationIndicates the type of logical volume. Mainframe device emulation types provide logicalvolumes of fixed size, called logical volume images (LVIs), which contain EBCDIC datain CKD format. Typical mainframe device emulation types include 3390-9 and 3390-M.Open-systems device emulation types provide logical volumes of variable size, calledlogical units (LUs), that contain ASCII data in FBA format. The typical open-systemsdevice emulation type is OPEN-V.

DEVNdevice number

DFWDASD fast write

DHCPdynamic host configuration protocol

differential dataChanged data in the primary volume not yet reflected in the copy.

disaster recoveryA set of procedures to recover critical application data and processing after a disaster orother failure.

disk arrayDisk 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. Theterm DKC is sometimes used to refer to the entire RAID storage system.

DKCdisk controller. Can refer to the RAID storage system or the controller components.

DKCMAINdisk controller main. Refers to the microcode for the RAID storage system.

DKPdisk processor. Refers to the microprocessors on the back-end director features of theUniversal Storage Platform V.

DKUdisk unit. Refers to the cabinet (floor model) or rack-mounted hardware component thatcontains data drives and no controller components.

DMPDynamic Multi Pathing

DRUHitachi Data Retention Utility

DP-VOLDynamic Provisioning-virtual volume. A virtual volume with no memory space used byDynamic Provisioning.

dynamic provisioningAn approach to managing storage. Instead of “reserving” a fixed amount of storage, itremoves capacity from the available pool when data is actually written to disk. Alsocalled thin provisioning.

E

ECerror code

emulationThe operation of the Hitachi RAID storage system to emulate the characteristics of adifferent storage system. For device emulation the mainframe host “sees” the logicaldevices on the RAID storage system as 3390-x devices. For controller emulation themainframe host “sees” the control units (CUs) on the RAID storage system as 2105 or2107 controllers.RAID storage system operates the same as the storage system being emulated.



emulation groupA set of device emulation types that can be intermixed within a RAID group and treatedas a group.

env.environment

ERCerror reporting communications

ESCONEnterprise System Connection

EXCTGSee extended consistency group (ECTG).

EXGexternal volume group

ext.external

extended consistency group (EXCTG)A set of Universal Replicator for Mainframe journals in which data consistency isguaranteed. When performing copy operations between multiple primary and secondarysystems, the journals must be registered in an EXCTG.

external applicationA software module that is used by a storage system but runs on a separate platform.

external portA fibre-channel port that is configured to be connected to an external storage systemfor Universal Volume Manager operations.

external volumeA logical volume whose data resides on drives that are physically located outside theHitachi storage system.

F

failbackThe process of switching operations from the secondary path or host back to theprimary path or host, after the primary path or host has recovered from failure. Seealso failover.



failoverThe process of switching operations from the primary path or host to a secondary pathor host when the primary path or host fails.

FBAfixed-block architecture

FCfibre channel; FlashCopy

FCAfibre-channel adapter

FC-ALfibre-channel arbitrated loop

FCIPfibre-channel internet protocol

FCPfibre-channel protocol

FCSPfibre-channel security protocol

FIBARCFibre Connection Architecture

FICONFibre Connectivity

FIFOfirst in, first out

free capacityThe amount of storage space (in bytes) that is available for use by the host system(s).

FSWfibre switch

FTPfile-transfer protocol

FVfixed-size volume



FWDfast-wide differential

G

GIDgroup ID

GUIgraphical user interface

H

HAhigh availability

HACMPHigh Availability Cluster Multi-Processing

HAMHitachi High Availability Manager

HDLMHitachi Dynamic Link Manager

HDPHitachi Dynamic Provisioning

HDSHitachi Data Systems

HDTHitachi Dynamic Tiering

HDvMHitachi Device Manager

HGLAMHitachi Global Link Availability Manager

H-LUNhost logical unit



HOMRCFHitachi Open Multi-RAID Coupling Feature. Another name for Hitachi ShadowImage.

HORCHitachi Open Remote Copy. Another name for Hitachi TrueCopy.

HORCMHitachi Open Remote Copy Manager. Another name for Command Control Interface.

host failoverThe process of switching operations from one host to another host when the primaryhost fails.

host groupA group of hosts of the same operating system platform.

host modeOperational modes that provide enhanced compatibility with supported host platforms.Used with fibre-channel ports on RAID storage systems.

host mode optionAdditional options for fibre-channel ports on RAID storage systems. Provide enhancedfunctionality for host software and middleware.

HRCHitachi Remote Copy. Another name for Hitachi TrueCopy for IBM z/OS.

HRpMHitachi Replication Manager

HSCSHitachi Storage Command Suite. This suite of products is now called the HitachiCommand Suite.

HURHitachi Universal Replicator

HXRCHitachi Extended Remote Copy. Another name for Hitachi Compatible Replication forIBM XRC.

I

iFCPinternet fibre-channel protocol



IMLinitial microcode load; initial microprogram load

IMPLinitial microprogram load

initial copyAn initial copy operation is performed when a copy pair is created. Data on the primaryvolume is copied to the secondary volume.

initiator portA fibre-channel port configured to send remote I/Os to an RCU target port on anotherstorage system. See also RCU target port and target port.

in-system replicationThe 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 arestored 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 Replicatorprimary site in a 3-data-center (3DC) cascading configuration.

internal volumeA logical volume whose data resides on drives that are physically located within thestorage system. See also external volume.

IO, I/Oinput/output

IOPSI/Os per second

IPinternet protocol

IPLinitial program load

J

JNLjournal



JNLGjournal group

journal group (JNLG)In a Universal Replicator system, journal groups manage data consistency betweenmultiple primary volumes and secondary volumes. See also consistency group (CTG).

journal volumeA 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 dataand maintain data integrity.In Universal Replicator, differential data is held in journal volumes on until it is copied tothe S-VOL.

JREJava Runtime Environment

L

L1 pairSee layer-1 (L1) pair.

L2 pairSee layer-2 (L2) pair.

LANlocal-area network

layer-1 (L1) pairIn a ShadowImage cascade configuration, a layer-1 pair consists of a primary volumeand secondary volume in the first cascade layer. An L1 primary volume can be pairedwith up to three L1 secondary volumes. See also cascade configuration.

layer-2 (L2) pairIn a ShadowImage cascade configuration, a layer-2 (L2) pair consists of a primaryvolume and secondary volume in the second cascade layer. An L2 primary volume canbe paired with up to two L2 secondary volumes. See also cascade configuration.

LBAlogical block address

LCPlocal control port; link control processor

LCUlogical control unit



LDEVlogical device

LDKCSee logical disk controller (LDKC).

leaf volumeA level-2 secondary volume in a ShadowImage cascade configuration. The primaryvolume of a layer-2 pair is called a node volume. See also cascade configuration.

LEDlight-emitting diode

license keyA specific set of characters that unlocks an application and allows it to be used.

local copySee in-system replication.

local siteSee primary site.

logical device (LDEV)An individual logical data volume (on multiple drives in a RAID configuration) in thestorage system. An LDEV may or may not contain any data and may or may not bedefined to any hosts. Each LDEV has a unique identifier or “address” within the storagesystem 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.AnLDEV formatted for use by mainframe hosts is called a logical volume image (LVI). AnLDEV 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 controlledby a virtual (logical) storage system within the single physical storage system. Forexample, the Universal Storage Platform V storage system supports two LDKCs, LDKC00 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) pathThe path between an open-systems host and a logical unit.

logical volumeSee volume.



logical volume image (LVI)A logical volume that is configured for use by mainframe hosts (for example, 3390-9).

LUlogical unit

LUNlogical unit number

LUNMHitachi LUN Manager

LUSEHitachi LUN Expansion; Hitachi LU Size Expansion

LVlogical volume

M

main control unit (MCU)A storage system at a primary or main site that contains primary volumes of TrueCopyfor Mainframe remote replication pairs. The MCU is configured to send remote I/Os toone or more storage systems at the secondary or remote site, called remote controlunits (RCUs), that contain the secondary volumes of the remote replication pairs. Seealso remote control unit (RCU).

main siteSee primary site.

main volume (M-VOL)A primary volume on the main storage system in a TrueCopy for Mainframe 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 tothe restore journal (R-JNL) on the secondary system. See also restore journal (R-JNL).

max.maximum

MBmegabyte



Mb/sec, Mbpsmegabits per second

MB/sec, MBpsmegabytes per second

MCUSee main control unit (MCU).

MF, M/Fmainframe

MIHmissing interrupt handler

mirrorIn Universal Replicator, each pair relationship in and between journals is called a“mirror”. Each pair is assigned a mirror ID when it is created. The mirror ID identifiesindividual pair relationships between journals.

M-JNLmain journal

modify modeThe mode of operation of Storage Navigator that allows changes to the storage systemconfiguration. See also view mode.

MPmicroprocessor

MP bladeBlade containing an I/O processor. Performance in the storage system is tuned byallocating a specific MP blade to each I/O-related resource (LDEV, external volume, orjournal). Specific blades are allocated, or the storage system can automatically select ablade.

MSCSMicrosoft Cluster Server

mto, MTOmainframe-to-open

MUmirror unit



multi-pathingA performance and fault-tolerant technique that uses more than one physicalconnection between the storage system and host system. Also called multipath I/O.

M-VOLmain volume

N

node volumeA level-2 primary volume in a ShadowImage cascade configuration. The secondaryvolume of a layer-2 pair is called a leaf volume. See also cascade configuration.

NUMnumber

NVSnonvolatile storage

O

OPEN-VA logical unit (LU) of user-defined size that is formatted for use by open-systems hosts.

OPEN-xA logical unit (LU) of fixed size (for example, OPEN-3 or OPEN-9) that is used primarilyfor sharing data between mainframe and open-systems hosts using Hitachi Cross-OSFile Exchange.

OSoperating system

OS/390Operating System/390

P

pairTwo logical volumes in a replication relationship in which one volume contains originaldata to be copied and the other volume contains the copy of the original data. The copyoperations can be synchronous or asynchronous, and the pair volumes can be located inthe same storage system (in-system replication) or in different storage systems(remote replication).



pair statusIndicates the condition of a copy pair. A pair must have a specific status for specificoperations. When an operation completes, the status of the pair changes to the newstatus.

parity groupSee RAID group.

path failoverThe ability of a host to switch from using the primary path to a logical volume to thesecondary path to the volume when the primary path fails. Path failover ensurescontinuous host access to the volume in the event the primary path fails.See also alternate path and failback.

PGparity group. See RAID group.

physical deviceSee device.

PiTpoint-in-time

point-in-time (PiT) copyA copy or snapshot of a volume or set of volumes at a specific point in time. You canuse a point-in-time copy for backup or mirroring application to run concurrently with thesystem.

poolA set of volumes that are reserved for storing SS data or Dynamic Provisioning writedata.

pool volume (pool-VOL)A logical volume that is reserved for storing snapshot data for Copy-on-Write Snapshotoperations or write data for Dynamic Provisioning.

port attributeIndicates the type of fibre-channel port: target, RCU target, or initiator.

port blockA group of four fibre-channel ports that have the same port mode.

port modeThe operational mode of a fibre-channel port. The three port modes for fibre-channelports on the Hitachi RAID storage systems are standard, high-speed, and initiator/external MIX.



PPRCPeer-to-Peer Remote Copy

Preview listThe list of requested operations on Storage Navigator.

primary siteThe physical location of the storage system that contains the original data to bereplicated and that is connected to one or more storage systems at the remote orsecondary site via remote copy connections. A primary site can also be called a “mainsite” or “local site”.The term “primary site” is also used for host failover operations. In that case, theprimary site is the host computer where the production applications are running, andthe secondary site is where the backup applications run when the applications at theprimary site fail, or where the primary site itself fails.

primary volumeThe volume in a copy pair that contains the original data to be replicated. The data inthe primary volume is duplicated synchronously or asynchronously on the secondarypairs.The following Hitachi products use the term P-VOL: Storage Navigator, SS,ShadowImage, ShadowImage for Mainframe, TrueCopy, Universal Replicator, UniversalReplicator for Mainframe, and High Availability Manager.See also secondary volume (S-VOL).

P-siteprimary site

P-VOLSee primary volume.

Q

quick formatThe quick format feature in Virtual LVI/Virtual LUN in which the formatting of theinternal volumes is done in the background. This allows system configuration (such asdefining a path or creating a TrueCopy pair) before the formatting is completed. Toexecute quick formatting, the volumes must be in blocked status.

quick restoreA reverse resynchronization in which no data is actually copied: the primary andsecondary volumes are swapped.

quick splitA split operation in which the pair is split immediately before the differential data iscopied 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 is immediately available forread and write I/O.

R

R/W, r/wread/write

RAIDredundant array of inexpensive disks

RAID groupA redundant array of inexpensive drives (RAID) that have the same capacity and aretreated as one group for data storage and recovery. A RAID group contains both userdata and parity information, which allows the user data to be accessed in the event thatone or more of the drives within the RAID group are not available. The RAID level of aRAID 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, sothere is no parity data for RAID1 RAID groups.A RAID group can also be called an array group or a parity group.

RAID levelThe type of RAID implementation. RAID levels include RAID0, RAID1, RAID2, RAID3,RAID4, RAID5 and RAID6.

RCPremote control port

RCUSee remote control unit (RCU).

RDread

RCU target portA fibre-channel port that is configured to receive remote I/Os from an initiator port onanother storage system.

remote console PCA previous term for the personal computer (PC) system that is LAN-connected to a RAIDstorage 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 configuredto 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 remoteI/Os from one or more storage systems at the primary or main site.

remote copySee remote replication.

remote copy connectionsThe physical paths that connect a storage system at the primary site to a storagesystem at the secondary site. Also called data path.

remote replicationData replication configuration in which the storage system that contains the originaldata is at a local site and the storage system that contains the copy of the original datais at a remote site. TrueCopy and Universal Replicator provide remote replication. Seealso in-system replication.

remote siteSee secondary site.

remote volume (R-VOL)In TrueCopy for Mainframe, a volume at the remote site that contains a copy of theoriginal 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 tothe secondary volume.

resync“Resync” is short for resynchronize.

RFrecord format

RIOremote I/O

R-JNLrestore journal

RLrecord length

RMIRemote Method Invocation



rndrandom

root volumeA level-1 primary volume in a ShadowImage cascade configuration. The secondaryvolume of a layer-1 pair is called a node volume. See also cascade configuration.

RPOrecovery point objective

R-SIMremote service information message

R-siteremote site (used for Universal Replicator)

RTCreal-time clock

RTOrecovery time objective

R-VOLSee remote volume (R-VOL).

R/Wread/write

S

S#serial number

S/Nserial number

s/wsoftware

SAIDsystem adapter ID

SANstorage-area network



SATAserial Advanced Technology Attachment

SCstorage control

SCDSsource control dataset

SCIstate change interrupt

scriptingThe use of command line scripts, or spreadsheets downloaded by Configuration FileLoader, to automate storage management operations.

SCSIsmall computer system interface

secondary siteThe physical location of the storage system that contains the primary volumes ofremote replication pairs at the main or primary site. The storage system at thesecondary site is connected to the storage system at the main or primary site viaremote copy connections. The secondary site can also be called the “remote site”. Seealso primary site.

secondary volumeThe volume in a copy pair that is the copy. The following Hitachi products use the term“secondary volume”: Thin Image, Copy-on-Write Snapshot, ShadowImage,ShadowImage for Mainframe, TrueCopy, Universal Replicator, Universal Replicator forMainframe, High Availability Manager, and Compatible XRC.See also primary volume.

seq.sequential

service information message (SIM)SIMs are generated by a RAID storage system when it detects an error or servicerequirement. SIMs are reported to hosts and displayed on Storage Navigator.

service processor (SVP)The computer inside a RAID storage system that hosts the Storage Navigator softwareand is used by service personnel for configuration and maintenance of the storagesystem.

severity levelApplies to service information messages (SIMs) and Storage Navigator error codes.



SIHitachi ShadowImage

SIzHitachi ShadowImage for Mainframe

sidefileAn area of cache memory that is used to store updated data for later integration intothe copied data.

SIMservice information message

sizeGenerally refers to the storage capacity of a memory module or cache. Not usually usedfor storage of data on disk or flash drives.

SMshared memory

SMTPsimple mail transfer protocol

SNserial number shown in Storage Navigator

snapshotA point-in-time virtual copy of a SS primary volume (P-VOL). The snapshot ismaintained when the P-VOL is updated by storing pre-updated data (snapshot data) in adata pool.

SNMPsimple network management protocol

SOMsystem option mode

source volume (S-VOL)The volume in a mainframe local copy pair containing the original data. This term isused only for the following Hitachi products: ShadowImage for Mainframe, IBMFlashCopy, Compatible FlashCopy® V2, and Dataset Replication.

spaceGenerally refers to the data storage capacity of a disk drive or flash drive.

SRMStorage Replication Manager



SSsnapshot

SSBsense byte

SSID(storage) subsystem identifier. SSIDs are used as an additional way to identify a controlunit on mainframe operating systems. Each group of 64 or 256 volumes requires oneSSID, therefore there can be one or four SSIDs per CU image. For VSP, one SSID isassociated with 256 volumes.

SSLsecure socket layer

steady splitIn ShadowImage, a typical pair split operation in which any remaining differential datafrom the P-VOL is copied to the S-VOL and then the pair is split.

S-VOLSee secondary volume or source volume (S-VOL).

SVPSee service processor (SVP).

syncsynchronous

system option mode (SOM)Additional operational parameters for the RAID storage systems that enable the storagesystem to be tailored to unique customer operating requirements. SOMs are set on theservice processor.

T

target portA 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. The term is used only in theearlier version of the Storage Navigator GUI (still in use), for the following Hitachiproducts: ShadowImage for Mainframe, Dataset Replication, Compatible FlashCopy®V2.See also source volume (S-VOL).



TBterabyte

TCHitachi TrueCopy

TCzHitachi TrueCopy for Mainframe

TDEVNtarget device number

TGTtarget; target port

THDthreshold

TIDtarget ID

total capacityThe aggregate amount of storage space in a data storage system.

T-VOLSee target volume (T-VOL).

U

update copyAn operation that copies differential data on the primary volume of a copy pair to thesecondary volume. Update copy operations are performed in response to write I/Os onthe primary volume after the initial copy operation is completed.

URHitachi Universal Replicator

URzHitachi Universal Replicator for Mainframe

USPHitachi TagmaStore® Universal Storage Platform

USP VHitachi Universal Storage Platform V



USP VMHitachi Universal Storage Platform VM

UTUniversal Time

UTCUniversal Time-coordinated

V

Vversion; variable length and de-blocking (mainframe record format)

VBvariable length and blocking (mainframe record format)

view modeThe mode of operation of Storage Navigator that allows viewing only of the storagesystem configuration. The two Storage Navigator modes are view mode and modifymode.

virtual device (VDEV)A group of logical devices (LDEVs) in a RAID group. A VDEV typically consists of somefixed volumes (FVs) and some free space. The number of fixed volumes is determinedby the RAID level and device emulation type.

Virtual LVI/LUN volumeA 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 Thin Image or 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.

VLLHitachi Virtual LVI/LUN

VLVIHitachi Virtual LVI

VMvolume migration; volume manager



VOL, volvolume

VOLIDvolume ID

volservolume serial number

volumeA logical device (LDEV), or a set of concatenated LDEVs in the case of LUSE, that hasbeen defined to one or more hosts as a single data storage unit. A mainframe volume iscalled a logical volume image (LVI), and an open-systems volume is called a logicalunit. (LU).

volume pairSee copy pair.

V-VOLvirtual volume

V-VOL management areaContains the pool management block and pool association information for SSoperations. The V-VOL management area is created automatically when additionalshared memory is installed and is required for SS operations.



Index

Numerics

3 data center, sharing volumes with 3-9, 3-103 URz data center, sharing volumes with 3-5

A

adjusting pair configuration 5-4

B

BCM, requirements for 2-2Business Continuity Manager 2-15

C

Cache Residency Manager 3-2calculating number of pairs 2-6CCI

description 1-4error codes 7-5pair statuses 6-4requirements for 2-2

changes in this revision xicommand device for BCM 2-15Compatible XRC 3-2Concurrent Copy 3-3configuration workflow 4-2consistency group

releasing 6-9reserving 4-3

Consistency group operations using CCI, StorageNavigator, BCM, PPRC B-3consistency group pair-split

description 2-10for shared volumes 2-11operation 5-11troubleshooting 7-13

Copy Pace option 4-4Copy Threshold option 4-4creating pairs 5-2, E-2CTG command menu G-11CTG window G-9

D

deleting pairs 5-15, E-12differential tables 2-6Display Filter dialog box G-6

E

emulation types 2-2

F

FlashCopy 3-2

H

Histories window C-15history of pair operations, viewing 6-7Host I/O Performance option 4-4, D-4how ShadowImage for Mainframe works 1-2

Index-1Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

L

licensecapacity exceeded 2-5capacity requirements 2-5expired 2-5viewing information about 6-2

load sharing and performance 2-9

M

maximum number of pairs 2-6monitoring and pair statuses 6-2MU number 2-2, 5-4

N

normal copy 5-12Number of Secondary Volumes, Create Pair wizard

5-3

O

Operations and settings using CCI, StorageNavigator, BCM, PPRC B-2Option window G-8

P

pair configurationadjusting 5-4Create Pair wizard 5-3

pair creation overview 1-4pair information, reviewing 6-6, F-3pair operation history, reviewing 6-7, F-6pair operations

and system maintenance 6-9workflow 5-2

pair split types 5-9pair status

definitions 6-2monitoring 6-2

pair tables 2-6pair volumes 2-2performance options 4-4performance, planning 2-9permitted operations

and pair status 6-5

and status of unaffected S-VOL 6-5pinned track 7-2planning to create pairs 2-5PPRC commands A-2Preview list G-5

Q

quick restore 5-13quick restore and performance 2-9quick resync 5-12quick split 5-9

R

RAID level 2-2releasing a reserved consistency group 6-9reserve attribute D-4reserve volumes

adding 4-2, D-2information about 6-7removing 6-9, F-9

reserving a consistency group 4-3reserving a consistency group (secondary window)

D-3Resource Partition Manager 3-3resynchronizing pairs 5-11resynchronizing pairs (subwindow) E-9reverse copy 5-12role required for SI, SIz operations 4-2, 5-2

S

secondary volumes, reserving 4-2service information messages 7-3sharing volumes 3-1SI, SIz - role required to perform operations 4-2SIMs 7-3special characters (secondary window) F-3splitting pairs 5-8, E-4splitting pairs in a consistency group 5-9status

and permitted operations 6-5for unaffected S-VOL and operations permitted

6-5steady split 5-9Storage Navigator 1-3Swap&Freeze option 4-4


system requirements 2-2

T

technical support 7-14troubleshooting

consistency group pair-split 7-13general 7-2

TrueCopy, TrueCopy for Mainframe 3-3TSO and ICKDSF commands A-2types of pair split 5-9types of resync 5-12

U

Universal Replicator 3-4update copy 1-5

V

Virtual LVI 3-11volume

information 6-6pairs 1-3types 2-2


Hitachi Virtual Storage Platform Hitachi ShadowImage® for Mainframe User Guide

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0)1753 [email protected]

Asia Pacific+852 3189 [email protected]

MK-90RD7023-14

hitachi virtual storage platform - hitachi data systems ibm, lotus, mvs, os/390, ... manager, pprc...

Documents