Hitachi Virtual Storage Platform

Transcription

1 Hitachi Virtual Storage Platform Hitachi Thin Image User Guide Document Organization Product Version Getting Help Contents MK-90RD

2 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users. Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed 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 be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain 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. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries. Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered 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 International Business Machines Corporation. All other trademarks, service marks, and company names in this document or website are properties of their respective owners. Microsoft product screen shots are reprinted with permission from Microsoft Corporation. ii

3 Contents Preface... vii Intended audience...viii Product version... viii Document revision level... viii Referenced documents...viii Changes in this revision... ix Document organization...ix Document conventions... x Convention for storage capacity values... xi Resources and performing tasks...xi Accessing product documentation...xii Getting help... xii Comments... xii 1 Overview of Thin Image Thin Image Components of Thin Image Components of volumes Consistency groups Snapshot groups Thin Image Dynamic Provisioning Command Control Interface How Thin Image works Thin Image Pools V-VOLs Releasing V-VOL definitions Thin Image pairs Storing snapshot data for a group workflow Snapshot data storage methods Differences in methods for storing snapshots depending on volumes CAW storage method workflow COW storage method workflow Restoring Thin Image pairs HTI pair status and deleting snapshot data Deleting Thin Image pairs iii

4 Pair status Copy threshold option Interoperability with other software applications Data Retention Utility Volume Migration ShadowImage TrueCopy and Universal Replicator Using Thin Image in a 3DC multi-target configuration Dynamic Provisioning Resource Partition Manager About acronyms and abbreviations for software applications Planning and design System requirements Requirements for Thin Image Installing Thin Image workflow The workflow for removing Thin Image Requirements for licensed capacity Thin Image shared memory requirements Removing shared memory Thin Image volume requirements Requirements for consistency groups Requirements for snapshot groups Requirements for Thin Image tasks Calculating the number of virtual volumes that the storage system can create Calculating the number of Thin Image pairs Calculating the maximum number of pairs based on differential tables Calculating the number of Thin Image pairs based on pair tables Calculating the number of Thin Image pairs based on the snapshot estimated manageable capacity Calculating the number of Thin Image pairs based on the number of cache management devices Calculating the number of cache management devices Thin Image cache management device requirements Effects on I/O performance of the storage system Calculating pool capacity Pool capacity calculations Using external volumes as pool-vols Performing configuration tasks Configuration tasks workflow Pool volumes with system area Creating Thin Image data pools Creating V-VOLs Editing the V-VOL SSID Changing the V-VOL settings Removing the V-VOL to be registered On setting up a command device iv

5 4 Pair tasks Creating Thin Image pairs Thin Image pair creation workflow using Storage Navigator Splitting pairs Using the At-Time Snapshot function to acquire snapshot data for a consistency group At-Time Snapshot when Thin Image volume shared with UR and TC Notes on using Thin Image P-VOLs as TrueCopy or Universal Replicator pair volumes Notes on acquiring snapshot data Restoring pairs Deleting snapshot data Deleting HTI pairs Monitoring and maintenance Monitoring pair information Viewing the number of pairs and a list of pairs Pair status definitions Monitoring pair properties Monitoring synchronous rates Monitoring consistency groups Viewing the number of consistency groups Viewing a list of consistency groups Viewing consistency group properties Monitoring pair operation history Monitoring pair operation history using secondary window Monitoring licensed capacity Monitoring the number of cache management devices Managing pools and V-VOLs Monitoring pool information Viewing used pool capacity Viewing used capacity by pool Viewing used pool capacity by HTI P-VOL Viewing formatted pool capacity Increasing pool capacity Changing pool threshold Changing pool names Recovering pools Deleting pools Changing V-VOL names Deleting V-VOLs Viewing snapshot data capacity Maintenance requirements Replacing the microcode offline Powering-off Troubleshooting General troubleshooting The workflow for recovering blocked pools workflow The workflow for processing pool-related SIMs Completing SIMs v

6 Completing warning SIMs before depletion of cache management devices Calling the Hitachi Data Systems customer support A CCI command reference... A-1 Statuses required for CCI tasks...a-2 CCI pair status names...a-2 Troubleshooting with Command Control Interface...A-3 B Thin Image GUI reference...b-1 Replications window... B-2 Local Replications window... B-3 View Pair Properties window...b-10 View Pair Synchronous Rate window... B-12 View Histories window...b-13 Consistency Group Properties window... B-15 Create Pairs wizard... B-17 Select Pair Configuration window... B-17 Select Primary Volumes window...b-18 Select Pool window...b-21 Select Secondary Volumes window...b-22 Confirm window... B-24 Split Pairs wizard... B-25 Split Pairs window...b-26 Confirm window... B-28 Resync Pairs wizard... B-29 Resync pairs window...b-30 Confirm window... B-32 Delete Pairs window...b-33 Edit Local Replica Option wizard...b-35 Edit Local Replica Option window...b-35 Confirm window... B-37 Glossary Index vi

7 Preface This document describes and provides instructions for using Thin Image (HTI) to plan, configure, and perform pair tasks on the 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. Intended audience Product version Document revision level Referenced documents Changes in this revision Document organization Document conventions Convention for storage capacity values Resources and performing tasks Accessing product documentation Getting help Comments Preface vii

8 Intended audience This document is intended for system administrators, Hitachi Data Systems representatives, and authorized service providers who are involved in installing, configuring, and operating the Virtual Storage Platform storage system. This document is for users who: Have a background in data processing and RAID storage systems. Are familiar with the Virtual Storage Platform storage system, Storage Navigator (SN), and have read the Hitachi Virtual Storage Platform User and Reference Guide and the Hitachi Storage Navigator User Guide. Are familiar with Hitachi Dynamic Provisioning, Hitachi Dynamic Tiering software, Hitachi LUN Manager, Hitachi LUN Expansion, Hitachi Virtual LVI, Virtual LUN, and Hitachi Data Retention Utility. Product version This document revision applies to Virtual Storage Platform microcode x or later. Document revision level Revision Date Description MK-90RD November 2012 Initial release. MK-90RD January 2013 Supersedes and replaces MK-90RD MK-90RD February 2013 Supersedes and replaces MK-90RD MK-90RD July 2013 Supersedes and replaces MK-90RD MK-90RD December 2013 Supersedes and replaces MK-90RD MK-90RD September 2014 Supersedes and replaces MK-90RD MK-90RD March 2016 Supersedes MK-90RD Referenced documents Virtual Storage Platform documents: Command Control Interface User and Reference Guide, MK-90RD7010 Hitachi Copy-on-Write Snapshot User Guide, MK-90RD7013 Hitachi Virtual Storage Platform Performance Guide, MK-90RD7020 viii Preface

9 Hitachi Virtual Storage Platform Provisioning Guide for Open Systems, MK-90RD7022 Hitachi ShadowImage User Guide, MK-90RD7024 Hitachi Storage Navigator User Guide, MK-90RD7027 Hitachi TrueCopy User Guide, MK-90RD7029 Hitachi Universal Replicator User Guide, MK-90RD7032 Hitachi Universal Volume Manager User Guide, MK-90RD7033 Hitachi Volume Migration User Guide, MK-90RD7034 Hitachi Volume Shredder User Guide, MK-90RD7035 Hitachi Virtual Storage Platform User and Reference Guide, MK-90RD7042 Changes in this revision Updated requirements in Creating Thin Image pairs on page 4-2. Document organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter Chapter 1, Overview of Thin Image on page 1-1 Chapter 2, Planning and design on page 2-1 Chapter 3, Performing configuration tasks on page 3-1 Chapter 4, Pair tasks on page 4-1 Chapter 5, Monitoring and maintenance on page 5-1 Chapter 6, Troubleshooting on page 6-1 Appendix A, CCI command reference on page A-1 Appendix B, Thin Image GUI reference on page B-1 Description Provides an overview of Thin Image. Describes the system and operational requirements. Describes creating pools, creating V-VOLs, and settings of the command device. Provides instructions for pair tasks. Provides instructions for monitoring and maintaining pairs. Provides troubleshooting information. Describes Command Control Interface commands corresponding to actions in the GUI. Describes Thin Image windows and dialog boxes in SN. Preface ix

10 Document conventions The term Hitachi Virtual Storage Platform refers to all models of the VSP storage system, unless otherwise noted. This document uses the following typographic conventions. Convention Bold Italic screen/code Description Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK. Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file Note: Angled brackets (< >) are also used to indicate variables. Indicates text that is shown on screen or typed by the user. Example: # pairdisplay -g oradb < > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: # pairdisplay -g <group> Note: Italic font is also used to indicate variables. [ ] square brackets Indicates optional values. Example: [ a b ] indicates that you can choose a, b, or nothing. { } braces Indicates required or expected values. Example: { a b } indicates that you must choose either a or b. vertical bar Indicates that you have a choice between two or more options or arguments. Examples: [ a b ] indicates that you can choose a, b, or nothing. { a b } indicates that you must choose either a or b. This document uses the following icons to draw attention to information. Icon Meaning Description Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Note Calls attention to important and/or additional information. Caution Warns 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. x Preface

11 Convention for storage capacity values Physical storage capacity values, such as disk drive capacity, are calculated based on the following values. Physical capacity unit Value 1 KB 1,000 bytes 1 MB 1,000 2 bytes 1 GB 1,000 3 bytes 1 TB 1,000 4 bytes 1 PB 1,000 5 bytes 1 EB 1,000 6 bytes Logical storage capacity values, such as logical device capacity, are calculated based on the following values. Logical capacity unit Value 1 KB 1,024 bytes 1 MB 1,024 KB or 1,024 2 bytes 1 GB 1,024 MB or 1,024 3 bytes 1 TB 1,024 GB or 1,024 4 bytes 1 PB 1,024 TB or 1,024 5 bytes 1 EB 1,024 PB or 1,024 6 bytes 1 block 512 bytes Resources and performing tasks When you use the functions described in this guide, the resources for each task must satisfy the specific conditions. The SN main window shows only the resources that are assigned to a user who logs into the SN. This window can also show the related resources that are required to manage the assigned resources. The SN secondary window shows all the resources in the storage system. When you perform and task in the SN secondary window, verify the resource group ID in the Basic Information Display dialog boxes, and then perform the tasks for the resources assigned to the user account. For more information about user accounts, see Hitachi Storage Navigator User Guide. Preface xi

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

13 1 Overview of Thin Image You can use Thin Image (HTI) to perform cost-effective local replication by storing only differential data between primary volumes (P-VOLs) and secondary volumes (S-VOLs) of virtual volumes (V-VOLs). Thin Image Components of Thin Image How Thin Image works Pair status Copy threshold option Interoperability with other software applications About acronyms and abbreviations for software applications Overview of Thin Image 1-1

14 Thin Image HTI stores snapshots, or a duplicate, of data in your Hitachi Virtual Storage Platform (VSP) storage system. Snapshot data is a copy of updated data in HTI P-VOLs. You can use this data in open-system volumes. If a data storage failure occurs in your storage system, you can use the snapshot data to restore the data. The following image shows an overview of HTI. Use the following process to store snapshot data: 1. You create an HTI pair. The P-VOL of an HTI pair is a logical volume. The S-VOL of an HTI pair is a V-VOL. 2. The host updates the P-VOL. Updating the P-VOL first copies the updated data as snapshot data in pool volumes (pool-vol). This processing is referred to as the storing of snapshot data. 3. You split the HTI pair. The P-VOL snapshot data is stored (this is snapshot A in the figure below). 4. The host updates the P-VOL again. 5. You split the HTI pair. HTI stores the updated data in the P-VOL as snapshot data. You can store up to 1,024 snapshots for a P-VOL. Using HTI, you can create up to 1,024 snapshots of data. The following figure shows how data is stored. The updated data in the P- VOL is Snapshot data B. The host references the P-VOL, which includes 1-2 Overview of Thin Image

15 Snapshot data A and Snapshot data B. Snapshot data A and B are handled as HTI S-VOLs. Required software applications Dynamic Provisioning (HDP) is required to use HTI. HDP accesses data in pool volumes by way of V-VOLs, and can handle data in open-system servers such as UNIX and PC servers. For more information about HDP, see Dynamic Provisioning on page 1-5. Components of Thin Image HTI typically consists of the following components: HTI pairs - Components of volumes (P-VOL, S-VOL, and pool-vol) For more information, see Components of volumes on page 1-4. Groups: A consistency group For more information, see Consistency groups on page 1-4. A snapshot group For more information, see Snapshot groups on page 1-4. Software applications: HTI For more information, see Thin Image on page 1-5. HDP For more information, see Dynamic Provisioning on page 1-5. Overview of Thin Image 1-3

16 Components of volumes Command Control Interface (CCI) For more information, see Command Control Interface on page 1-5. HTI manages logical volumes of P-VOLs and V-VOLs of S-VOLs as HTI pairs. Logical volumes of P-VOLs include V-VOLs that have a provisioning type defined as Dynamic Provisioning. You can only use V-VOLs that are used by an HTI pair as an S-VOL. The differential data of P-VOLs are stored as snapshot data in pool volumes. To use HTI, include at least one of the following volumes: P-VOL Secondary volume (V-VOL) HTI pool-vol, as a container for snapshot data Note: HTI, HDP, and the other VSP software applications require license agreements with Hitachi Data Systems. Consistency groups Snapshot groups If you use the CCI, you can define multiple HTI pairs as a consistency group. If you define the consistency group in advance, you can store snapshot data per consistency group. Therefore, data of the time when the VSP storage system receives the request of storing data are assured. For more information about storing snapshot data for a consistency group, see Storing snapshot data for a group workflow on page 1-7. When you define new pairs using HTI, and you want to perform the HTI task per group, add pairs to a consistency group or a snapshot group. The following table shows the difference between consistency groups and snapshot groups. Item Consistency group Snapshot group Pair limit per group 8,192 8,192 Group limit Data consistency Guaranteed Not guaranteed For more information about storing snapshot data for a group, see Storing snapshot data for a group workflow on page Overview of Thin Image

17 Thin Image You use HTI on the Storage Navigator (SN) computer that is connected to the service processor (SVP) by means of the TCP/IP local-area network (LAN). When you log in to the SVP from your SN computer, HTI for SN is downloaded. You can use HTI for SN to configure or view statistics on your storage system and perform tasks on HTI pairs. Dynamic Provisioning To perform HTI tasks, you must install HDP on the SN computer. An HDP license is required. Reserve enough license capacity to accommodate the pairs or pools that you plan to create. Calculate the licensed capacity for HDP based on the capacity of pool-vols for HTI and HDP. These volumes are referred to as used volumes. The licensed capacity must exceed the total capacity of used volumes. Command Control Interface Use the CCI to perform HTI tasks. You do this by running commands from a host. For more information about the commands, see Appendix A, CCI command reference on page A-1 and Command Control Interface Command Reference. How Thin Image works Thin Image Pools This topic explains how HTI works. HTI stores snapshot data in pools. A pool consists of multiple pool-vols. The pool-vols contain the snapshot data. A pool can contain up to 1,024 pool- VOLs. Each storage system can contain up to 128 pools, and can include the following pools: HDP Dynamic Tiering (HDT) HTI Copy-on-Write Snapshot (SS) The following figure illustrates the relationship between an HTI pair and a pool. Overview of Thin Image 1-5

18 To use HTI, create pools. With HTI, you can add pool-vols but you cannot delete them. To delete a pool, delete all of the HTI pairs. Caution: The pool capacity is calculated by subtracting the capacity of V-VOL management areas from the total capacity of pool-vols in the pool. If you write data to HTI pair volumes and the amount of pool usage exceeds the pool capacity, the following occurs: You cannot store snapshot data. The HTI pair status changes to PSUE, which indicates a failure. You cannot create additional HTI pairs. Reserve a sufficient amount of pool capacity when creating pools. V-VOLs V-VOLs do not have any physical storage space. V-VOLs must be created prior to creation of HTI pairs because HTI uses V-VOLs as S-VOLs. Releasing V-VOL definitions Thin Image pairs You cannot release V-VOL definitions that you are using as HTI S-VOLs. To release definitions of V-VOLs, release the HTI pairs that are using the V- VOLs. S-VOLs of HTI pairs are V-VOLs. First define the V-VOLs then create HTI pairs. You can specify up to 1,024 S-VOLs for a P-VOL. To create HTI pairs, use the Create Pair window. 1-6 Overview of Thin Image

19 For more information about how to create HTI pairs, see Creating Thin Image pairs on page 4-2. To create an HTI pair, specify the pool to be used for the HTI pair. If multiple HTI pairs share the same P-VOL, the pairs must also share the same pool. For example, if you specify three S-VOLs for a P-VOL, specify the same pool for the three HTI pairs. To release an HTI pair, use the Delete Pairs window. Deleting an HTI pair changes the volume status to SMPL. You cannot create HTI pairs using unpaired volumes ( SMPL status). You can confirm the status of a volume on Local Replications window and the View Pair Properties window. Storing snapshot data for a group workflow You can use the CCI to define a consistency group or a snapshot group and store snapshot data for the group. The following figure illustrates how snapshot data for a group is stored. For information about differences between snapshot groups and consistency groups, see Consistency groups on page 1-4. Overview of Thin Image 1-7

20 Figure 1-1 Storing snapshot data for a group Use the following process to store snapshot data: 1. Issue a request to store snapshot data for a group. To do this, run the raidcom modify snapshot -snapshot_data create CCI command. 2. The host issues a write request to each P-VOL in the group. Snapshot data for the volumes are stored. 1-8 Overview of Thin Image

21 3. Store snapshot data for a consistency group or a snapshot group using the CCI command. Note: You can use SN only to reference consistency groups and snapshot groups. Snapshot data storage methods You can use the Copy-On-Write (COW) method or the Copy-After-Write (CAW) method to store snapshot data. In the COW method, when the P-VOL snapshot data is acquired, the status changes to the write completion status. In the CAW method, when the P-VOL snapshot data is written, the status changes to the write completion status. The CAW method wait time is shorter than that of the COW method. The following figure illustrates the CAW method. The following figure illustrates the COW methods. Overview of Thin Image 1-9

22 Differences in methods for storing snapshots depending on volumes The method in which you store snapshot data is dependent on the types and RAID levels of P-VOLs. Use the following list to determine which method to use to store snapshot data: The P-VOL is an internal volume. If the P-VOL RAID level is RAID 1, use the COW method. If the P-VOL RAID level is something other than RAID 1, use the CAW method. The P-VOL is a HDP volume. If one of the following applies to the pool, use the CAW method: The pool is a RAID5 pool The pool contains volumes of different RAID levels The pool contains external volumes created using the DKCMAIN microcode program version X-XX/XX or later HDP and HDT pools If the pool is none of the above, use the COW method. In the above cases, even if the snapshot data is stored with the CAW method, if the write pending rate (percentage of data waiting to be written in cache memory) is 60% or higher when writing in random access mode, or 30% or higher when writing in sequential access mode, the COW method is used. For more information about performance monitoring and the write pending rate, see the Hitachi Virtual Storage Platform Performance Guide. The P-VOL is an external volume. Use the COW method. CAW storage method workflow Use the following process to store snapshot data using the CAW method: 1. The host writes data to a P-VOL. 2. The write completion status is returned to the host before the snapshot data is stored. 3. Snapshot data for the P-VOL is stored in the background. COW storage method workflow Use the following process to store snapshot data using the COW method: 1. The host writes data to a P-VOL. 2. Snapshot data for the P-VOL is stored. 3. The write completion status is returned to the host Overview of Thin Image

23 Restoring Thin Image pairs Use HTI to overwrite snapshot data in pools to P-VOLs so that the P-VOL content is returned to the condition it was when you stored the snapshot data. Overwriting snapshot data to P-VOLs restores HTI pairs. If data is written to a S-VOL, this data (not the snapshot data) is overwritten to the P-VOL when the HTI pair is restored. If a problem occurs with a P-VOL due to a failure, you can restore the pair so that data in the P-VOL is returned to a normal condition it was when snapshot data was stored. For more information about restoring pairs, see Restoring pairs on page HTI pair status and deleting snapshot data Deleting all of the pairs in a snapshot group ( SMPL status) deletes the snapshot group. Delete the snapshot group before performing the next pair task. If a failure occurs while you delete an HTI pair, the HTI pair status changes to PSUE status, data is written to the HTI pair volumes, and the capacity of snapshot data exceeds the pool capacity. You cannot create new HTI pairs. Delete the unneeded snapshot data. Use one of the following methods to delete snapshot data: Delete the HTI pairs. For more information about deleting pairs, see Deleting HTI pairs on page Delete the only the snapshot data. For more information about deleting snapshot data, see Deleting snapshot data on page Deleting the snapshot data changes the pair status to PAIR. While the pair is in this status, you cannot store snapshots, even when the hosts update the P-VOLs. To resume storing snapshot data, split the pair again. Deleting snapshot data or pairs requires time. The more pool capacity the pair uses, the longer the time that is required to delete the data or pair. The more pairs are operated concurrently, the longer the time that is required to delete the data or pair. For more information about deleting snapshot data, see Deleting snapshot data on page Deleting Thin Image pairs To delete HTI pairs, use the Delete Pairs window. You can delete a pair when you do not need it or you want to delete snapshot data. Deleted pairs ( SMPL status) are not shown in SN. You can use the P-VOL and S-VOLs of deleted pairs in another pair. Overview of Thin Image 1-11

24 To shorten the time when the pair is in the process of being deleted ( SMPL (PD) status), complete the following: 1. Delete the snapshot data. The pair status changes to PAIR. 2. Delete the HTI pair. For more information about deleting pairs, see Deleting HTI pairs on page 4-11 Pair status The status of an HTI pair changes as you create, split, or perform other tasks on the pair, as illustrated in the following figure. If you do not use the volumes as an HTI pair, the volumes remain unpaired ( SMPL status). If you do not pair the P-VOL with an S-VOL and you create the pair, the pair status changes to COPY and then to PAIR. If you pair the P-VOL with one or more S-VOLs and you create the pair, the pair status changes to PAIR Overview of Thin Image

25 If you create an HTI pair directly after deleting the last P-VOL snapshot data, the process can take time. While the HTI pair is in PAIR status and the pool exceeds its threshold, the pair status changes to PFUL. While in this status, you cannot create additional HTI pairs. Splitting the pair in PAIR status stores the snapshot data and changes the HTI pair status to PSUS. If you exceed the pool threshold while in this status, then the pair status changes to PFUS. For more information about splitting pairs, see Splitting pairs on page 4-5. You can delete snapshot data but not also release the HTI pair. To do this, delete the snapshot data for the pair in PFUS status. For more information about deleting snapshot data, see Deleting HTI pairs on page Restoring an HTI pair in PSUS status overwrites the snapshot data to the P- VOL. While the restore process is in progress, the pair status changes to RCPY. When the restore process finishes, the pair status changes to PAIR. For more information about restoring HTI pairs, see Restoring Thin Image pairs on page The pool can only contain data of predetermined capacity. The HTI pair status changes to PSUE when one of the following occurs: The total capacity of snapshot data in the pool exceeds the pool capacity. A failure occurs during the restore process. Note: Even if the restore process is not in progress, the pair status can change to PSUE when a failure occurs. The pool usage rate reaches 100 percent. The status of HTI pairs depends on whether the hosts can read from or write to the HTI pair P-VOL or S-VOLs. The following table explains the host access and pair status. HTI pair status P-VOL S-VOL Read Write Read Write SMPL Yes Yes No No SMPL(PD) Yes Yes No No COPY Yes Yes No No PAIR/PFUL Yes Yes No No PSUS/PFUS Yes Yes Yes Yes RCPY Yes Yes No No PSUE Yes Yes No No Legend Yes: Hosts can access the volume Overview of Thin Image 1-13

26 P-VOL S-VOL HTI pair status Read Write Read Write No: Hosts cannot access the volume Caution: If a host uses a software application to monitor HTI pair volumes, the software application can abnormally terminate depending on the status of a S-VOL. For example, a monitoring application can terminate abnormally if access from the application is rejected, because S-VOLs in a status other than PSUS and PFUS reject access from hosts. If a host connects to two or more ports, an abnormality can occur with ports that are not connected to S-VOLs rejecting access from hosts. To resolve these issues, terminate the software application that monitors volumes. Copy threshold option Use the copy threshold option to help minimize the decline of host server I/O performance. The host server I/O performance can decrease as the workload on the storage system increases. If you restore HTI pairs when the workload on the storage system is high, replication processes for the P-VOLs begin. During the replication processes, the host server I/O performance can decrease and the workload on the storage system can become excessively heavy. You can temporarily stop the HTI replication processes and the following software by enabling the copy threshold option: SI SIz Compatible FlashCopy V2 (FCv2) Volume Migration SS As the workload on the storage system decreases, the replication processes that were stopped by the copy threshold option restart. For more information about enabling the copy threshold option, call the Support Center. Interoperability with other software applications You can create HTI pairs using pair volumes for replication software applications such as SI and TrueCopy (TC). You can also create HTI pairs using volumes to which attributes are defined by Data Retention Utility (DRU) or CCI. The following table shows whether you can share pair volumes by HTI and other software applications Overview of Thin Image

27 Software volume types Used as HTI P-VOL Used as HTI S-VOL SS P-VOL No No SS S-VOL No No SI P-VOL Yes 3 No SI S-VOL Yes No SI reserve volume No No TC P-VOL Yes No TC S-VOL Yes No Universal Replicator (UR) P-VOL Yes No UR S-VOL Yes No UR journal volume No No Volume Migration source volume No No Volume Migration target volume No No Volume Migration reserve volume No No High Availability Manager P-VOL No No High Availability Manager S-VOL No No High Availability Manager quorum disk No No Nondisruptive Migration volume No No Read Only volume 1, 4, 6 Yes Yes Protect volume 1, 4, 6 Yes Yes "S-VOL Disable" volume 4, 6 Yes No Zero Read Capacity volume 2, 5 Yes Yes Invisible volume 2, 5 Yes Yes VMA volume No No Reserve volume Yes Yes DP-VOL Yes No 1. If you use SN to share the volume with other software applications, the pair status determines whether you can share the volume. 2. You can use the CCI to share the volume with other software applications; you cannot use SN to do this. 3. You cannot Quick Restore. 4. DRU is required to set Read Only, Protect, and S-VOL Disable attributes. 5. CCI is required to set Zero Read Capacity and Invisible attributes. 6. You can use DRU to confirm whether Read Only, Protect, S-VOL Disable, Zero Read Capacity and Invisible attributes are set to volumes. Legend Yes: You can share the volume. Overview of Thin Image 1-15

28 Software volume types Used as HTI P-VOL Used as HTI S-VOL No: You cannot share the volume. If you share a volume with a software application listed in the previous table, the pair status determines whether tasks are performed. Data Retention Utility You can create HTI pairs using volumes that have access attributes assigned by DRU. Depending on access attributes, however, you cannot perform some pair tasks and pool tasks with HTI. Also, you can assign access attributes to HTI P-VOL and S-VOLs. The tables below also explain HTI pair tasks and pool tasks after access attributes are assigned. The following tables explain whether you can perform HTI pair tasks and pool tasks on volumes that have access attributes assigned by DRU. The following table shows the access attributes and HTI pair tasks. HTI pair task Access attribute of P-VOL Access attribute of S-VOL Create pair Split pair Suspend pair Resync pair (normal copy) Resync pair (reverse copy) Delete pair Read/Write Read/Write Yes Yes Yes Yes Yes Yes Read Only No No No No No No Protect No No No No No No S-VOL Disable No No No No No No Read Only, Protect, S- VOL Disable Read/Write Yes Yes Yes Yes No Yes Read Only No No No No No No Protect No No No No No No S-VOL Disable No No No No No No Legend Yes: You can perform the task No: You cannot perform the task The following table shows access attributes and HTI pool tasks. Access attribute of volume specified by HTI HTI pool task Pool-VOL setting Read/Write Yes 1-16 Overview of Thin Image

29 Access attribute of volume specified by HTI HTI pool task Pool-VOL setting Read Only Protect S-VOL Disable No No No Legend Yes: You can perform the task No: You cannot perform the task Note: HTI tasks do not change access attributes of volumes. Reverse resync tasks do not copy access attributes of S-VOLs to P-VOLs when writing snapshot data to P-VOLs, As shown in the following table, DRU cannot assign access attributes to some HTI P-VOL and S-VOLs, depending on the HTI pair status. HTI volume Access attribute to be assigned Pair status Volume Read/Write Read Only Protect S-VOL Disable COPY P-VOL Yes Yes S-VOL Yes No PAIR, PFUL P-VOL Yes Yes S-VOL Yes Yes PSUS, PFUS P-VOL Yes Yes S-VOL Yes Yes SMPL(PD) P-VOL Yes Yes S-VOL Yes No RCPY P-VOL Yes No S-VOL Yes No PSUE P-VOL Yes Yes S-VOL Yes No Legend Yes: You can perform the setting No: You cannot perform the setting Overview of Thin Image 1-17

30 Volume Migration ShadowImage To perform HTI tasks on volumes, the volume must not be in a migration plan, regardless of the migration plan status. You can use HTI pair volumes or pool volumes, but not for Volume Migration migration plans. For more information about the migration plan status and Volume Migration tasks, see the Hitachi Volume Migration User Guide. You can share HTI P-VOLs with SI P-VOL and S-VOLs. The following tables list the relationship between pair tasks and status. SI pair status HTI task COPY(P D)/ COPY PAI R COPY(S P)/ COPY PSUS(S P)/ PSUS PSU S COPY(R S)/ COPY COPY(RS- R)/RCPY PSU E Create pair Yes Yes Yes Yes Yes Yes No Yes Store snapshot data Yes Yes Yes Yes Yes Yes No Yes Restore pair No No No No Yes No No Yes Delete snapshot data Yes Yes Yes Yes Yes Yes Yes Yes Release pair Yes Yes Yes Yes Yes Yes Yes Yes Legend Yes: You can perform the task No: You cannot perform the task (the command is rejected) SI pair status HTI task COPY(P D)/ COPY PAI R COPY(S P)/ COPY PSUS(SP )/PSUS PSU S COPY(R S)/ COPY COP Y(RS -R)/ RCPY PSU E Create pair No No No No Yes No No No Store snapshot data N/A No No No Yes No No No Store snapshot data for a consistency group N/A No No No Yes* No No No Restore pair N/A No No No Yes No No No Delete snapshot data N/A Yes Yes Yes Yes Yes Yes Yes Release pair N/A Yes Yes Yes Yes Yes Yes Yes * The SI pair status must be PSUS during the period between when HTI starts to store snapshot data for a consistency group and when the status of all pairs in the consistency 1-18 Overview of Thin Image

31 HTI task COPY(P D)/ COPY PAI R COPY(S P)/ COPY SI pair status PSUS(SP )/PSUS PSU S COPY(R S)/ COPY COP Y(RS -R)/ RCPY group changes to PSUS. If the SI pair status changes to a status other than PSUS when you are storing snapshot data for the consistency group, the snapshot data consistency is not guaranteed. Legend Yes: You can perform the task No: You cannot perform the task (the command is rejected) N/A: Not applicable PSU E The following is a list of the SI tasks that you can perform when you share an HTI P-VOL with an SI P-VOL. HTI pair status SI task COPY PAIR, PFUL PSUS, PFUS SMPL(PD) RCPY PSUE Create pair Yes Yes Yes Yes No Yes Create and split pair Yes Yes Yes Yes No Yes Split pair Yes Yes Yes Yes No Yes Normal Copy Yes Yes Yes Yes No Yes Reverse Copy Yes Yes Yes Yes No Yes Quick Restore No No No No No No Suspend replication Yes Yes Yes Yes Yes Yes Delete pair Yes Yes Yes Yes Yes Yes Legend Yes: You can perform the task No: You cannot perform the task (the command is rejected) The following table shows a list of the SI tasks that you can perform when you share an HTI P-VOL with an SI S-VOL. HTI pair status SI task COPY PAIR, PFUL PSUS, PFUS SMPL(PD) RCP Y PSU E Create pair No No No No No No Create and split pair No No No No No No Split pair Yes Yes Yes Yes No Yes Normal Copy Yes Yes Yes Yes No Yes Overview of Thin Image 1-19

32 HTI pair status SI task COPY PAIR, PFUL PSUS, PFUS SMPL(PD) RCP Y PSU E Reverse Copy Yes Yes Yes Yes No Yes Quick Restore No No No No No No Suspend replication Yes Yes Yes Yes No Yes Delete pair Yes Yes Yes Yes Yes Yes Legend Yes: You can perform the task No: You cannot perform the task (the command is rejected) Even after snapshot data is stored, you can operate SI pairs. In this case, the consistency of the stored snapshot data is not maintained. HTI S-VOLs use the data in the P-VOL. You cannot Quick Restore using SI. For more information on SI tasks and pair statuses, see the Hitachi ShadowImage User Guide. Caution: HTI uses MU numbers 0 to 1,023, and they are assigned in the order of 3 to 1,023, followed by 0 to 2. SI uses MU numbers 0 to 2, therefore HTI cannot use the MU numbers 0 to 2 if you want to share HTI volumes with SI. To share a volume with HTI and SI, delete HTI pairs using the MU numbers 0 to 2. Then, create SI pairs and HTI pairs. TrueCopy and Universal Replicator You can share HTI P-VOLs with TrueCopy (TC) and UR pair volumes. The following tables list the relationship between pair tasks and status. The following table shows the HTI tasks you can perform based on TC/UR pair volume status. HTI task TC/UR status COPY PAIR PSUS PSUE Suspending Deleting Create pair Yes Yes Yes Yes Yes Yes Store snapshot data Yes Yes Yes Yes Yes Yes Restore pair No No Yes Yes No No Delete snapshot data Yes Yes Yes Yes Yes Yes Delete pair Yes Yes Yes Yes Yes Yes Legend Yes: You can perform the task No: You cannot perform the task (the command is rejected) 1-20 Overview of Thin Image

33 The following table shows the HTI tasks you can perform when an HTI P-VOL is shared with a TC/UR S-VOL. TC/UR status HTI task COP Y PAIR PSUS PSUE SSWS Suspendi ng Deleting Create pair Yes Yes Yes Yes Yes Yes Yes Store snapshot data No Yes Yes Yes Yes Yes Yes Restore pair 1 No No No No No No No Delete snapshot data Yes Yes Yes Yes Yes Yes Yes Delete pair Yes Yes Yes Yes Yes Yes Yes 1. When restoring an HTI pair and you are using the P-VOL as a TC or UR S-VOL, switch tasks to the remote site using the horctakeover command. Legend Yes: You can perform the task No: You cannot perform the task (the command is rejected) The following table shows the TC/UR tasks you can perform when the HTI P- VOL is shared with TC/UR P-VOL. TC/UR task HTI status COPY PAIR, PFUL PSUS, PFUS RCPY PSUE Create pair Yes Yes Yes No Yes Split pair Yes Yes Yes N/A Yes Resynchronize pair Yes Yes Yes No Yes Delete pair Yes Yes Yes Yes Yes Switch to remote site Yes Yes Yes No Yes Legend Yes: You can perform the task No: You cannot perform the task (the command is rejected) N/A: Not applicable The following table shows the TC/UR tasks you can perform when the HTI P- VOL is shared with a TC/UR S-VOL. TC/UR task HTI status COPY PAIR, PFUL PSUS, PFUS RCPY PSUE Create pair No No No No No Split pair Yes Yes Yes N/A Yes Overview of Thin Image 1-21

34 TC/UR task HTI status COPY PAIR, PFUL PSUS, PFUS RCPY PSUE Resynchronize pair Yes Yes Yes N/A Yes Delete pair Yes Yes Yes N/A Yes Switch to remote site Yes Yes Yes N/A Yes *To use a TC/UR S-VOL as an HTI P-VOL, create a pair after creating the TC/UR pair. For more information about TC tasks and pair status, see the Hitachi TrueCopy User Guide. For more information about UR tasks and pair status, see the Hitachi Universal Replicator User Guide. Legend Yes: You can perform the task No: You cannot perform the task (the command is rejected) N/A: Not applicable Using Thin Image in a 3DC multi-target configuration The following figure shows a pair configuration where you use HTI in a 3DC multi-target TC/UR configuration. Note: HTI volumes cannot be shared in 3DC UR/UR configurations. Pair 1 is a TC pair. Pair 2 is a UR pair. Pair 3 is a UR pair for delta resync. Pairs 4, pair 5, and pair 6 are HTI pairs Overview of Thin Image

35 1. Create 3DC multi-target and delta resync pairs (pairs 1, 2, and 3). 2. Create pair Create pairs 5 and 6. Dynamic Provisioning Note the following if you are using HTI, HDP, and Dynamic Provisioning for Mainframe (HDPz) in a single storage system: If you are expanding the HDP V-VOL capacity, you cannot create HTI pairs that has an HDP V-VOL as the P-VOL. Peforming an HTI paircreate operation while zero pages are being reclaimed (including reclamation by Writesame, Unmap command, or rebalancing) results in the zero-page operation being interrupted. HTI pair creation might be rejected if the Unmap command operation is in progress with system option mode 905 ON. Wait a while and then retry the operation. If the operation still fails, set system option mode 905 to OFF and retry again. You can use a maximum volume size of 4 TB (4,398,046,511,104 bytes) HDP volume as an HTI P-VOL. If you specify TB, GB, or MB as the unit when creating a volume, you cannot create a volume of 4 TB (4,398,046,511,104 bytes). To create a volume of 4 TB (4,398,046,511,104 bytes), for unit, specify block. The following table explains how the maximum LDEV capacity differs depending on the specified unit. Unit specification Maximum LDEV capacity TB 3.99 GB 4, MB 4,194, block 8,589,934,592 Resource Partition Manager You can create an HTI pair without regards to the P-VOL and S-VOLs resource group assignment. Assign the pool you are using to the resource group where the P-VOL is assigned or to the resource group where you can create HTI pairs. For more information about resource groups, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. About acronyms and abbreviations for software applications This user guide uses the following acronyms and abbreviations for software names: Overview of Thin Image 1-23

36 HDP: Dynamic Provisioning SI: ShadowImage SIz: ShadowImage for Mainframe SS: Copy-on-Write Snapshot HTI: Thin Image UR: Universal Replicator TC: TrueCopy HDT: Dynamic Tiering FCv2: Compatible FlashCopy V Overview of Thin Image

37 2 Planning and design This topic discusses requirements for using HTI. Please read this topic before using HTI. System requirements Requirements for Thin Image tasks Planning and design 2-1

38 System requirements The following is a list of system requirements that are required to perform HTI tasks: A VSP storage system with P-VOL and S-VOLs. HTI and HDP, which run on SN computers. Requirements for Thin Image The following is a list of requirements to use HTI: The hardware and microcode is configured and set up. The license key for HDP is installed using SN. For more information about license keys and SN and HDP installation, see Hitachi Storage Navigator User Guide. Installing Thin Image workflow Use the following workflow to install HTI: 1. Install shared memory for differential tables. 2. Install the shared memory for V-VOL management areas. 3. Install HDP, which is prerequisite software for HTI. 4. Install HTI. HDP and HTI share the same shared memory. Before installing additional shared memory for V-VOL management areas, call the Support Center. Step 1 is unneeded if the shared memory for differential tables is already installed. The workflow for removing Thin Image Use the following process to remove HTI: 1. Release the HTI pairs. 2. Delete all pools. 3. Delete all V-VOLs. 4. Remove HTI. Requirements for licensed capacity If you use HTI, you must have the capacity licensed for the HTI P-VOLs and pools. The capacity of pools which are used for HTI is subtracted from the licensed capacity for HDP. Therefore, if you use HTI, secure the licensed capacity for HDP more than the total capacity used for both HDP and HTI. The following table shows the HTI volumes and capacity calculated as the HTI usage. The total amount of these values must not exceed HTI license capacity. 2-2 Planning and design

39 Product The intended volumes The kind of volumes Normal volume or DP-VOL The intended capacity HTI P-VOL Normal volume The volume capacity DP-VOL The pool capacity used by the volume Pool VOL Normal volume The volume capacity For details about license, see the Hitachi Storage Navigator User Guide. Thin Image shared memory requirements HTI requires dedicated shared memory for the HTI pair management area. The HTI pair management area is an area used to store information for associating HTI pairs. This area is automatically created when you install shared memory. The following is a list of the shared memory requirements: A minimum of 16 GB shared memory that consists of two sections. To use a pool or V-VOL with a capacity of more than 1.1 PB, then shared memory must be installed. Pool or V-VOL capacity requires an expanded status of the installed shared memory. For more information about installing the shared memory, call the Support Center. Removing shared memory You must delete all pools for HDP, HDT, and HTI before removing shared memory. Thin Image volume requirements HTI requires the following types of volumes: P-VOLs S-VOLs pool-vols The following tables lists the requirements for HTI P-VOLs, S-VOLs, and pool volumes. The following table shows the requirements for HTI P-VOLs. Planning and design 2-3

40 Item Requirement Volume type Emulation type Logical volumes (LDEVs). You cannot specify the following volumes as HTI P-VOLs: pool volumes HTI S-VOLs LUSE volumes For more information about creating pairs using other software applications, see Interoperability with other software applications on page OPEN-V Maximum number of volumes 29,440 Note: This value can be increased depending on your system configuration. For information about the calculating the maximum number of HTI pairs, see Calculating the number of Thin Image pairs on page 2-7. Path definitions Volume capacity limit Required. 4 TB The following table shows the requirements for HTI S-VOLs. Item Requirement Volume type Emulation type V-VOLs You cannot specify the following volumes as HTI S-VOLs: Volumes that are already used as S- VOLs. Volumes that other software applications are using for pairs or migration plans. LUSE volumes. For more information about calculating the maximum number of V-VOLs, see Calculating the number of virtual volumes that the storage system can create on page 2-7. OPEN-V Volume limit 32,768 For more information about the maximum number of HTI pairs, see Calculating the number of Thin Image pairs on page 2-7. Path definitions Required The following table shows the requirements for HTI pool-vols. 2-4 Planning and design

41 Item Volume type Emulation type RAID level Hard disk drive type CLPR Logical volumes (LDEV) Requirement Use the following configurations to maintain performance levels: Do not mix normal volumes and pool-vols in a parity group (PG). Ensure that the pool-vols consist of LDEVs from multiple PGs. Assign different processor blade IDs 1 to LDEVs that make up pool- VOLs. You cannot specify the following volumes as HTI pool-vols: Volumes that have a volume status is not Normal or Normal (Quick Format). If you are blocking or copying a volume, you cannot specify the volume. LUSE volumes Volumes that are already being used as HTI P-VOL or S-VOLs. Volumes that are already contained in HTI, SS, HDP, or HDT pools. Volumes used as migration plans or pair volumes for another product. Volumes with Protect or Read Only attribute, or the S-VOL Disable attribute setting (DRU) Cache Residency Manager volumes. System disks Command devices High Availability Manager quorum disks RAID-1 RAID level volumes that have a SATA-E hard disk drive type. Note: Use only external pool-vols that has a cache mode that is the same, enabled or disabled, in the data pool. Use only volumes that are in different resource group in the data pool. Use only internal volumes and external volumes with an enabled cache mode in the data pool. OPEN-V All RAID levels are supported. You cannot register RAID-1 RAID level volumes that have a SATA-E hard disk drive type in pools. You can use serial-attached SCSI (SAS), SATA, and SSD. 2 If you use internal and external volumes, you can use pool-vols with different drive types in the same pool. You cannot register RAID-1 RAID level volumes that have a SATA-E hard disk drive type in pools. For best performance, use pool-vols with the same drive type in the same pool. A data pool cannot contain pool-vols belonging to different cache logical partitions. You cannot change CLPRs in the PG belonging to the pool- VOL. Planning and design 2-5

42 Item Pool-VOL limits Volume capacity Path definition Requirement You can contain up to 1,024 pool-vols in a pool. You can create up to 128 pools for a storage system. If a volume is already contained in a pool, you cannot contain the pool- VOL in other pools. The number of available pools for HTI decreases according to the number of HDP pools (including HDT pools), HDPz pools, and SS pools. 8 GB to 4 TB If you define unneeded paths to a volume, you cannot specify the volume as a pool-vol. 1. For more information about how to change processor blade IDs, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. 2. SSD contains SSD (SLC, MLC) and FMD. Requirements for consistency groups The following table explains requirements for consistency groups. Item Description Consistency group number Value: 0 to 255. Note: If you do not assign a number, an unassigned number is automatically assigned. You can view the consistency group number. For more information about viewing the consistency group number, see Viewing the number of consistency groups on page 5-4. You can create up to 256 consistency groups in a storage system, which includes SI, SIz, SS, and HTI consistency groups. (For HTI only) You can also use consistency group numbers 128 to 255 (80 to FF). Pair limit You can define up to 8,192 pairs in a consistency group. You cannot mix SI, SIz, SS, and HTI pairs in a consistency group. An HTI consistency group can only contain HTI pairs. Notes on consistency groups (If you are using the CCI to create snapshots) To avoid the raidcom add snapshot command from being rejected, define an HTI pair that shares the same P-VOL in the separate consistency groups. (If you are using the CCI to split pairs defined in consistency groups) To avoid the pairsplit command from finishing abnormally and to guarantee that the P-VOL snapshot data is stored when the VSP receives the command, assign pairs defined in consistency groups and pairs not 2-6 Planning and design

43 defined in consistency groups to separate groups defined by CCI s configuration definition file (this group is not a consistency group). You can only specify one consistency group for a group defined by CCI s configuration definition file. To create pairs using a group defined by CCI s configuration definition file, and if a pair with a consistency group specified is already created in the group, the addition will be made to the same consistency group even if you try to create a new pair with a different consistency group specified. To specify multiple consistency groups, define the same number of groups using CCI s configuration definition file. Requirements for snapshot groups The following table explains requirements for snapshot groups. Item Description Name Up to 32 characters. Once you create a snapshot group, you cannot change its name. Maximum number The maximum number of snapshot groups for a storage system is 512. The maximum number of HTI pairs for a snapshot group is 8,192. Requirements for Thin Image tasks This section discusses points to be considered regarding HTI tasks. Calculating the number of virtual volumes that the storage system can create Use the following formula to calculate the maximum number of V-VOLs that the storage system can create: The maximum number of V-VOLs = 58,800* - (The number of external volumes + The number of P-VOLs for HTI pairs) * Your system configuration determines the maximum value in this formula. Calculating the number of Thin Image pairs When you create HTI pairs for a P-VOL for the first time, the number of HTI pairs that you can create in a storage system depends on the following: The number of differential tables. The number of pair tables. The snapshot estimated manageable capacity. The number of cache management devices. Planning and design 2-7

44 To calculate the number of HTI pairs that you can create, complete the following: 1. Calculate the number using the number of differential tables (see Calculating the maximum number of pairs based on differential tables on page 2-8). 2. Compare the results of the three calculations. The smallest of the three is the maximum number of HTI pairs that you can create in the storage system. When you create HTI pairs again, you do not need to use the snapshot estimated manageable capacity and the number of cache management devices. Use only the number of pair tables and calculate the number of HTI pairs that you can create. For more information, see Calculating the number of Thin Image pairs based on pair tables on page 2-8. If you have multiple P-VOLs, calculate the number of HTI pairs that you can create for each P-VOL in the storage system. Calculating the maximum number of pairs based on differential tables Differential tables track updates that take place in pairs. A base that does not have shared memory has 26,176 differential tables. The remaining number of differential tables on a system is determined by the amount of shared memory that you have installed on the system. The following table shows various combinations and the number of differential tables that are associated with them. Combination Differential tables required Base that does not have shared memory 26,176 Extension 1 104,768 Extension 2 209,600 Differential tables are also used by the following software applications: SI SIz SS FCv2 Compatible Software for IBM FlashCopy SE Volume Migration Calculating the number of Thin Image pairs based on pair tables The following relationships and pairs require a pair table, which contains the information required to manage them: 2-8 Planning and design

45 FCv2 relationship Compatible Software for IBM FlashCopy SE relationship SS pair HTI pair You can use up to 1,048,575 pair tables in a storage system, you can share the pair tables among the following relationships and pairs. To calculate the number of HTI pairs, use the following formula: 1,048,575 - (the number of SS pairs) - (the number of FCv2 or Compatible Software for IBM FlashCopy SE relationships) - (the number of existing HTI pairs) For example, the number of HTI pairs that you can create in a storage system is calculated using the following formula, if the number of pair tables used by SS is 15,000 and the number of pair tables used by FCv2 and Compatible Software for IBM FlashCopy SE is 30,000: 1,048,575-15,000-30,000 = 1,003,575 The results of the calculation shows that you can create up to 1,003,575 HTI pairs. An HTI pair consists of a P-VOL and up to 1,024 V-VOLs. Differential tables are used per P-VOL. The number of differential tables you can you use does not depend on the number of V-VOLs. Calculating the number of Thin Image pairs based on the snapshot estimated manageable capacity You can view the snapshot estimated manageable capacity in the Local Replications window. To calculate the number of HTI pairs that you can create based on the snapshot estimated manageable capacity, use the following formula: The number of snapshot estimated manageable capacity / the snapshot manageable capacity per P-VOL The snapshot manageable capacity per P-VOL = (the P-VOL capacity of HTI pairs [TB] / 2.6 [TB]) * 3,024 [GB] + (168GB * 2 (consumed shared memory)) Calculating the number of Thin Image pairs based on the number of cache management devices You can view the number of cache management devices in the View Management Resource Usage window. To calculate the number of HTI pairs that you can create based on the number of cache management devices, use the following formula: Planning and design 2-9

46 The number of HTI pairs that you can create = the number of cache management devices / ceil (the P-VOL capacity of HTI pairs [TB]) / 2.6 [TB]) Related topics Calculating the number of cache management devices on page Calculating the number of cache management devices Cache management devices are the unit for controlling the cache in association with volumes (LDEVs). Each volume requires a minimum of one cache management device. You can manage up to 65,280 cache management devices in a system. You can view the number of cache management devices in the View Management Resource Usage window. This section explains the number of cache management devices that are required for HTI tasks. For more information about LDEVs and the cache management devices that are required for HDP volumes, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Thin Image cache management device requirements To create HTI pools for the first time, you must have a total of 8,192 cache management devices available. HTI assigns 4,096 cache management devices from the amount available. To create an HTI pair for a volume for the first time, you must have at least 4,097 cache management devices available. Otherwise, pair creation can fail. Use the following formula to calculate the number of cache management devices you will need to create pairs. Use the following formula when you create an HTI pair for a volume for the first time: ceil(size of P-VOL 2.6) (in terabytes) If the amount of pool usage for the P-VOL exceeds 70% of the total capacity of the cache management devices reserved for the P-VOL, another cache management device must be reserved. Each P-VOL requires up to 256 cache management devices. Effects on I/O performance of the storage system If you perform HTI restore tasks when the workload on the storage system is high, I/O performance of host servers can decline because replication process starts for the P-VOL. Enable the copy threshold option to lower the workload on the storage system. For more information about this option, see Copy threshold option on page Planning and design

47 For more information about enabling the copy threshold option, call the Support Center. Calculating pool capacity Calculate the capacity of which snapshot data you can store in the pool by subtracting the capacity of V-VOL management areas from the total capacity of pool-vols in the pool. The capacity of V-VOL management areas is 3% of the pool capacity. If the pool capacity is insufficient, the status of HTI pairs can change to PSUE. In this case, estimate the capacity of snapshot data to be copied to the pool and assign the pool capacity based on the estimate. If the capacity of snapshot data to be copied to the pool varies hour by hour, ensure that the largest capacity is your pool capacity. If snapshot data is copied to the pool, the pool capacity is always consumed in units of 42 megabytes. Even if snapshot data is smaller than 42 megabytes, at least 42 megabytes of pool capacity is needed. If you write data to the same area in the P-VOL more than one time, snapshot data is copied to the pool only when data is written for the first time. If data is written to the same area only once, the capacity of written data equals to the capacity of snapshot data to be copied to the pool. If data is written to the same area more than once, the capacity of snapshot data to be copied to the pool is smaller than the capacity of written data. Specify the capacity of a pool-vol in multiples of 42 megabytes to avoid truncation. Pool capacity calculations To decide the capacity of pools, estimate the capacity of snapshot data that you want to copy. The capacity of snapshot data that you want to copy equals to the capacity of data written to the same area in the P-VOL during the period from when you stored the snapshot data to when you deleted the snapshot data. If you have stored multiple snapshot data, you can share the data in a pool. If the snapshot data contains the shared data, you can release HTI pairs, but you cannot delete the snapshot data from the pool. If you release the HTI pairs that have snapshot data containing the shared data, the snapshot data are also deleted from the pool. Complete the following to create a backup of data using HTI: 1. Store the snapshot data. 2. Use an S-VOL. Note: During this process, a significant amount of data is read from the S- VOL. This can increase the accesses to the P-VOL and degrade the host I/O performance. The target for the backup is only the areas where the snapshot data is stored. Therefore, you can create a backup copy even if the pool capacity is small. Planning and design 2-11

48 Although pool capacity is decided according to the estimation, if the pool capacity exceeds the threshold, address the issue. For more information about addressing threshold issues, see General troubleshooting on page 6-2. Using external volumes as pool-vols You can use Universal Volume Manager to connect your VSP storage system to multiple other storage systems. In Universal Volume Manager terminology, your VSP storage system is referred to as a local storage system, and the other multiple storage systems are referred to as external storage systems. Volumes in external storage systems are referred to as external volumes. Volumes in a local storage system are referred to as internal volumes. If Universal Volume Manager is installed, you can use external and internal volumes as pool-vols. However, if external volumes are used, it increases the likelihood of a failure, and the disaster recovery is more complex and challenging. If you use external volumes as pool-vols, to minimize adverse effect of failure, use a pool for each external storage system. You can use multiple external volumes as pool-vols in a pool. However, if external volumes are used, it increases the likelihood of a failure. For example, the pool might be blocked. If the external pool-vols are blocked due to a failure, the pool is also blocked. For more information about how to restore a blocked pool, see The workflow for recovering blocked pools workflow on page 6-4. For more information about external storage systems and disaster recovery methods for external volumes, see the Hitachi Universal Volume Manager User Guide Planning and design

49 3 Performing configuration tasks This topic describes creating pools, creating V-VOLs, and settings of the command device for configuring HTI. Configuration tasks workflow Pool volumes with system area Creating Thin Image data pools Creating V-VOLs On setting up a command device Performing configuration tasks 3-1

50 Configuration tasks workflow The following image shows how to run HTI. Use the following process to run HTI: 1. Create a V-VOL management area in the shared memory. The V-VOL management area is created when you install additional shared memory. For more information about installing shared memory, see Installing Thin Image workflow on page 2-2. For more information about the additional shared memory, call the Support Center. 2. Create the pools. 3. Create the HTI pairs. 4. Acquire the snapshot data. 5. Maintain the HTI pair status, which includes deleting any unneeded snapshot data HTI pairs. Note: Deleting an HTI pair deletes the snapshot data, which is acquired with the HTI pair, from the pool. 6. (If a failure occurs) Perform the recovery task to write snapshot data over the P-VOL. Note: While the HTI pair is recovering, you cannot recover other HTI pairs. For more information about tasks on HTI pairs and pair statuses, see Pair status on page Pool volumes with system area Creating a pool automatically sets the new pool-vol with system area according to the priority of hard disk drive types. The following table shows the hard disk drive type priority. 3-2 Performing configuration tasks

51 Priority Hard disk drive type 1 SATA-W/V or SATA-E 2 SAS7.2K 3 SAS10K 4 SAS15K 5 SSD 6 External volume If more than one pool-vol of the same hard disk drive type exists, its priority is determined according to storage system s the internal index information. Creating Thin Image data pools You can create HTI data pools using SN. Prerequisite: The volumes that you plan to add to the pool have the same assigned CLPR. 1. In the Storage Systems tree, select Pools. 2. In the Pools window, click Create Pools. 3. In the Create Pools window, complete the following: For Pool Type, select Thin Image. Required: Yes Select a pool-vol. Complete the following and click Select Pool VOLs: - For Drive Type/RPM, select your system's data drive type and RPM. Values: External Storage Maximum: 3 - For RAID Level, select the system's RAID level. For example, RAID-1. Note: You can register only one system RAID level in a pool. If you selected External Storage for Drive Type/RPM, a dash (-) is shown for this item and this item is unavailable. 4. In the Select Pool Volumes window, from the Available Pool Volumes table, select the pool-vols that you want to assign and click Add. Maximum volumes per pool: 1,024 Required: Yes The selected pool-vols are registered to the Select Pool Volumes list. The information in the Selected Pool Volumes table is applied to Total Selected Pool Volumes and Total Selected Capacity. Performing configuration tasks 3-3

52 5. (Optional) In the Create Pools window, complete the following, and then click OK: - To filter the rows, click ON in the Filter field. - To select all pool-vols in the list, click Select All Pages. - To specify the capacity unit and the number of rows to be shown, click Options and make the selection. Caution: You cannot delete the added pool-vol. Make sure that the pool-vol settings are correct. 6. In the Create Pools window, for Pool Name, type a pool name, and then click Options. Character limit: 32 characters (for the Prefix and Initial Number). Required: Yes - For Prefix, type case-sensitive, alphanumeric characters. - For Initial Number, type a number, which is up to nine digits. 7. In the Options window, Initial Pool ID and other items are shown. Complete the following and then click Add: For Initial Pool ID, type a number. Values: 0 to 127 Default: The smallest available number If an available pool ID does not exist, a number is not shown. Typing the registered pool ID adds the smallest available pool ID automatically registered among the subsequent pool ID that you typed. For Warning Threshold, select a data pool capacity threshold between 20% and 95%. Default: 80% The pool you created is added to the Selected Pools table. 8. Click Finish. 9. In the Confirm window, for Go to tasks window for status, select to open the Tasks window, and then click Apply. The pool is created. Related topics Create Pools wizard in Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Thin Image volume requirements on page 2-3 Creating V-VOLs The V-VOL is the paired volume of the pool VOL. You must create a V-VOL before you can create the pair. 1. The following tab windows shows with which LDEVs you can create: 3-4 Performing configuration tasks

53 The LDEV tab when selecting Logical Devices The Pool tab when selecting Pool 2. Click Create LDEVs. 3. In the Create LDEVs window, confirm and complete the following: For Provisioning Type, confirm that Snapshot is selected. If it is not selected, select Snapshot from the menu. For System Type, confirm that OPEN is selected. Note: OPEN is the fixed value. For Emulation Type, confirm that OPEN-V is selected. Note: OPEN-V is the fixed value. For LDEV capacity, type the capacity of the V-VOL. Type the number within the range of capacity shown below the text box. You can use decimals up to two decimal places. To change the LDEV capacity unit, use the unit capacity menu. For Number of LDEVs, type the number of V-VOLs (LDEVs) to be created. The range is shown below the text box. For LDEV Name, type a name of the V-VOL. - For Prefix, type the alphanumeric characters, which are fixed characters placed before the V-VOL name. The characters are casesensitive. - For Initial Number, type the initial number for V-VOL. Digit limit: 9 Character limit: 32 including the Prefix and Initial number The following items are required: Provisioning Type System Type Emulation Type LDEV Capacity Number of LDEVs 4. Click Options. 5. In the option area of the window, for Initial LDEV ID, set the initial LDEV ID. Click View LDEV IDs to confirm the used number and unavailable number. 6. In the View LDEV IDs window, complete the following, and then click Add: For Initial SSID, type the SSID as the 4-digit representation of a hexadecimal number (0004 to FFFE). Performing configuration tasks 3-5

54 To confirm the generated SSID, click View SSID to open the View SSID window. For Cache Partition, select the CLPR. From the Processor Blade list, select a processor blade. Select a processor blade to be used by the LDEVs. If you assign a processor blade, select the processor blade ID. If you can assign any processor blade, click Auto. The created V-VOLs are added to the Selected LDEVs table. If the invalid values are set, an error message appears. If an item that must be set is not entered or selected, you cannot click Add. 7. Click Finish. 8. (Optional) In the Confirm window, to continue the task for setting the LU path and define LUN, click Next. For more information about setting the LU path and defining the LUN, see Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. 9. If necessary, change the settings of the V-VOLs. You can change the following settings: SSID Click Edit SSIDs to open the Edit SSIDs window. For more information about how to edit SSIDs, see Editing the V-VOL SSID on page 3-7. LDEV Click Change LDEV Settings to open the Change LDEV Settings window. For more information about how to change the LDEV settings, see Changing the V-VOL settings on page Complete the following and then click Apply: For Task Name, type the name of the task. Character limit: 32 Allowable characters and symbols: All alphanumeric except \ / :, ; *? " < > Default: date-task Name For Go to tasks window for status, select to open the Tasks window. The V-VOL is created. Caution: Note the following when you boot or reboot the host server, such as HP-UX or Solaris, or when you use the host server to run the read command on a V-VOL to recognize a device: You cannot change the volume of the device that is recognized by the host server to a V-VOL. You must first create the HTI pairs and acquire the snapshot data before you can boot or reboot the host server or run the command for recognizing devices (Maintain the pair status of the V-VOLs that is recognized to the host server the PSUS status). 3-6 Performing configuration tasks

55 Fulfill all of the above conditions to recognize the devices or to prevent failures stopping the host server. If you booted or rebooted the host server, or you ran commands to recognize devices and stopped the host server, run commands in the following steps: 1. Forcibly stop the command process and the process of its parent. 2. Create the HTI pair. 3. Get the snapshot data. 4. Run the command to recognize devices. On the server (including CCI), the emulation type of the V-VOL is shown with a zero (0), such as OPEN-0V. If you create an HTI pair, specify a volume that has an emulation type defined with a zero (0), such as OPEN-0V, for the S-VOL. Define V-VOL groups before you create V-VOLs. The emulation type of the VDEV for the V-VOL group is OPEN-V like the same type of the V- VOL. This VDEV capacity is always 4 TB, and the maximum capacity of a V-VOL is 4 TB, too. Related topics The Create LDEVs wizard. For more information about this wizard, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Editing the V-VOL SSID Before registering a V-VOL, you may need to edit the SSID of the V-VOL. 1. In the Create LDEVs window, click Edit SSIDs. 2. In the Edit SSIDs window, the SSIDs table shows the existing SSIDs and the SSIDs that you can add. Select the row of the SSID you want to edit and click Change SSIDs. 3. In the Change SSIDs window, type the new SSID and click OK. 4. In the Edit SSIDs window, click OK. 5. In the Create LDEVs window, click Finish. 6. In the Confirm window, complete the following and then click Apply: For Go to tasks window for status, select to open the Tasks window. The edited V-VOL SSID is registered to the storage system. Changing the V-VOL settings Before registering a V-VOL, you may need to change V-VOL settings. 1. In the Selected LDEVs table in the Create LDEVs window, select LDEV and click Change LDEV Settings. Performing configuration tasks 3-7

56 2. In the Change LDEV Settings window, change the following and then click OK: For LDEV Name, specify the prefix characters and the initial number of LDEV. For Initial LDEV ID, specify the LDKC number, CU number, LDEV number, and the interval. To check used LDEVs, click View LDEV IDs to confirm the used LDEVs. The View LDEV IDs window opens. For Processor Blade, click the list and specify the processor blade ID. To specify a process blade, click the processor blade ID. To assign an arbitrary process blade, click Auto. 3. In the Create LDEVs window, click Finish. 4. In the Confirm window, complete the following and then click Apply: For Go to tasks window for status, select to open the Tasks window. The settings are registered to the storage system. Removing the V-VOL to be registered If you do not want to register the V-VOL, you can remove it from the registering task. 1. In the Selected LDEVs table in the Create LDEVs window, select the LDEV you want to remove and click Remove. 2. In the message whether to remove the selected LDEV, click OK. 3. Click Finish. 4. In the message whether to remove the selected LDEVs, click OK. 5. In the Confirm window, for Go to tasks window for status, select to open the Tasks window, and then click Apply or to open the next window, click Next. The V-VOL is removed from the registering task. On setting up a command device To use the CCI and an in-band connection to perform HTI tasks, reserve a volume for use as a command device. (It is not necessary for an out-of-band connection.) To use CCI and an out-of-band connection, you do not need to do this. If you run CCI commands through an out-of-band connection, the host I/O performance may degrade. Run CCI commands through an in-band connection. For more information on how to configure a command device, see the Command Control Interface User and Reference Guide. 3-8 Performing configuration tasks

57 4 Pair tasks This chapter provides instructions for performing pair tasks. Creating Thin Image pairs Splitting pairs Restoring pairs Deleting snapshot data Deleting HTI pairs Pair tasks 4-1

58 Creating Thin Image pairs You can assign a P-VOL to a maximum of 1,024 HTI pairs. You can create up to 1,024 pairs at a time. To create more than 1,024 pairs, repeat this procedure. When specifying a P-VOL that is already used as the P-VOL of another HTI pair, make sure that the two HTI pairs share the same pool. The P-VOL and S-VOLs must be the same size in blocks. If the capacity is displayed in gigabytes, a small difference between P-VOL and S-VOL capacity might not be displayed. To view the capacity in blocks, click Options > Capacity Unit > block in the Logical Devices window. Caution: After creating the HTI pair, if the number of pairs is shown on the Summary tab and on the list is different, the configuration is being changed. If this occurs, wait for a while, then click File > Refresh All to reload the configuration information. Caution: To avoid the pair from being suspended ( PSUE status), do not create HTI pairs while you are shutting down. To use SI volumes as HTI volumes, complete the following: 1. Create the SI pair. 2. Create the HTI pair. To use an SI volume as an HTI P-VOL and there are no available MU numbers, complete the following: 1. Delete the HTI pairs of MU numbers 0 to Create the SI pair. 3. Recreate the HTI pair with an MU number of 3 or greater assigned. Prerequisites You have the Storage Administrator (Local Copy) role. The pair is in a status other than SMPL (PD). 1. Display the Create Pairs window by performing one of the followings: Click Create Pairs in General Tasks. In the Storage Systems tree, click Replications> Local Replications. In the Pairs tab, click Create Pairs. 2. In the Create Pair window, for Copy Type select Thin Image. 3. For Number of Secondary Volumes, specify the total number of S- VOLs (including the already configured pairs) that corresponds to the single P-VOL. 4. Click Next and complete the following: For Use Primary Volumes of Snapshot Pairs, select the kind of volumes you want to add the Available LDEVs table: 4-2 Pair tasks

59 - Yes shows LDEVs that are already used as P-VOLs. - No shows LDEVs that are not used as P-VOLs. If you selected No in Use Primary Volumes of Snapshot Pairs, click Select Pool. In the Select Pool window, select a pool then click OK. In Available LDEVs, select an LDEV to be the P-VOL and click Add. The LDEV is moved to Selected LDEVs. 5. Click Next and complete the following: In the Available LDEVs table, select the LDEV that you want to use as a S-VOL, and then select a snapshot group. To create a new snapshot group, type the name and click Set. The selected LDEV is shown in the Selected Pairs table. If you select a capacity for Capacity, the Available LDEVs and Selected Pairs tables show the LDEVs that match the selected capacity. Select whether you create a new snapshot group or use the defined snapshot group. You must set the snapshot group when creating an HTI pair. Create new snapshot group: Type new snapshot group name. Use defined snapshot group: Select the desired snapshot group. (If you are using the CCI to create pairs in a snapshot group by specifying the raidcom add snapshot command) The pairs can also belong to the consistency group. An example of creating pairs with specifying the P-VOL (LDEV#10:10), the S-VOL (LDEV#20:20), and the pool (SnapPool00) in the snapshot group (db1) and add pairs in a consistency group is shown below. raidcom add snapshot -ldev_id 0x1010 0x2020 -pool SnapPool00 -snapshotgroup db1 -snap_mode CTG If you click Remove, you can delete the pair in the selected row. If you select a row in the Available LDEVs table and a row in the Selected Pairs table and then click Set, you can configure a pair. 6. Click Finish. 7. In the Confirm window, type a Task Name then click Apply. Related topics Thin Image pair creation workflow using Storage Navigator on page 4-3 Create Pairs wizard on page B-17 Thin Image pair creation workflow using Storage Navigator The following image shows how pairs are configured in the main window based on the number of S-VOLs corresponding to the P-VOL. S-VOLs are assigned in the order of 1 to 1,024. Pair tasks 4-3

60 Use the following process to create HTI pairs using SN: 1. Select the pair configuration. 2. Select the P-VOL. 3. Select the S-VOLs. 4. Perform confirmation. Configuring a complex pair If you add S-VOLs to an existing pair, ensure that the Number of Secondary Volumes field contains a number that is larger than the current number of S-VOLs of the existing pair. For example, if you add an S-VOL to an existing pair that has one P-VOL and one S-VOL, specify 2 for the number of S-VOLs. Figure 4-1 Adding an S-VOL to an existing pair 4-4 Pair tasks

61 If you simultaneously create multiple pairs among which the number of S- VOLs differs, ensure that Number of Secondary Volumes is the largest number among those pairs. Then, when selecting S-VOLs, delete them. The following is an example of creating pairs of different configurations simultaneously. In this example, one pair of two S-VOLs and another pair of one S-VOL are created simultaneously. 1. Specify 2 as the number of S-VOLs, and select two P-VOLs. The storage system assumes two pairs of two S-VOLs each will be created. 2. Select the S-VOL. Select and delete the S-VOL MU#1 of the second pair. By deleting a S-VOL, you can create multiple pairs of different configurations. Figure 4-2 Creating two pairs of different pair configurations Splitting pairs You can create up to 1,024 snapshots from one P-VOL. This topic explains how to split pairs. Prerequisites You have the Storage Administrator (Local Copy) role. The HTI pair status is PAIR. 1. In the Storage Systems 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, complete the following item and then click Finish: Split Type The split type. Values: - Quick Split: Splits the pair immediately. Specify this function when you want to split a pair then immediately write to or read from the S- Pair tasks 4-5

62 VOL. After the pair is split, the remaining differential data is copied to the S-VOL in the background. - Steady Split: Copies the differential data then splits the pair. If you have specified TI or Snapshot as the copy type, this is the only available option. Default: Steady Split 4. In the Confirm window, type a Task Name then click Apply. Related topics Split Pairs wizard on page B-25 Using the At-Time Snapshot function to acquire snapshot data for a consistency group You can use CCI s At-Time Snapshot function to acquire snapshot data for a consistency group. Use the CCI to run the commands. 1. Run the raidcom add snapshot CCI command, using an option to specify the consistency group number. A consistency group is created that should be the target of the At-Time Snapshot function. The At-Time Snapshot function is automatically enabled when you use an option to specify the consistency group number. 2. Run the raidcom add snapshot CCI command again, specifying the same consistency group number as specified in step 1. You can add pairs to the same consistency group. Repeat this as many times as you want. 3. Run the raidcom modify snapshot -snapshot_data create command on the consistency group that is the target of the At-Time Snapshot function. The VSP storage system receives the command. 4. A host issues a write request to the P-VOL of an HTI pair in the consistency group. Snapshot data is acquired. At-Time Snapshot when Thin Image volume shared with UR and TC You can share HTI P-VOLs with UR or TC S-VOLs within a storage system, place the HTI pairs in a consistency group, and use the At-Time Snapshot function to maintain consistency for multiple HTI S-VOLs. The following figures illustrate these configurations. 4-6 Pair tasks

63 Figure 4-3 At-Time Snapshot configuration with UR Pair tasks 4-7

64 Figure 4-4 At-Time Snapshot configuration with TC The following table explains when you can run the At-Time Snapshot function. If HTI P-VOL is used as and the pair status is Can I run At-Time Snapshot? UR S-VOL COPY No PAIR PSUS Yes Yes TC S-VOL COPY No PAIR PSUS Yes Yes SI S-VOL COPY No PAIR COPY(SP) PSUS(SP) PSUS COPY(RS) COPY(RS-R) PSUE No No No Yes No No No 4-8 Pair tasks

65 You cannot maintain consistency for the HTI S-VOLs in the following cases: An HTI P-VOL is shared with SI S-VOLs, TC, and/or UR S-VOLs, and the status of those pairs are not the same. An HTI P-VOL is shared with a UR S-VOL and the journal group is not the same. Notes on using Thin Image P-VOLs as TrueCopy or Universal Replicator pair volumes If you are using the CCI to run commands and you cannot change the pair status in an HTI consistency group, running the raidcom modify snapshot - snapshot_data create CCI command to split pairs can return the following error code and terminate abnormally: EX_EWSTOT (timeout) The following are possible reasons why you cannot change the pair status: The HTI P-VOL is used as an UR S-VOL, and the capacity of the UR journal volume is running short. The HTI license is invalid. The HTI pair volumes are blocked. The current status of the HTI pair does not allow you to run the raidcom modify snapshot -snapshot_data create CCI command on the pair. The current status of the TC or UR pair does not allow you to run the raidcom modify snapshot -snapshot_data create CCI command on the pair. After resolving these error conditions, complete the following: 1. Ensure that all pairs in the consistency group are in PAIR status. 2. Run the following raidcom command: raidcom modify snapshot -snapshot_data create Notes on acquiring snapshot data (If you are using the CCI to run the raidcom modify snapshot - snapshot_data create CCI command to split pairs and the consistency group includes a pair in a status other than PAIR ) The command can terminate abnormally, as follows: The command is rejected. Timeout occurs. The error code is EX_EWSTOT. The pair is suspended. The error code is EX_EWSUSE. To maintain the consistency of snapshot data while running the raidcom modify snapshot -snapshot_data create CCI command, do not run other commands on pairs in the consistency group. If you run other commands, this CCI command can end abnormally as follows: Pair tasks 4-9

66 Timeout (Error code EX_EWSTOT). The pair is suspended (Error code EX_EWSUSE). The restoration of an HTI pair can end abnormally in either of the following conditions: Snapshot data for a consistency group including the HTI pair is being acquired. The P-VOL of the HTI pair is also used as the P-VOL of another HTI pair. In addition, snapshot data for a consistency group including the latter HTI pair is being acquired. Notes on when the host is down If the host is down, some consistency group might not contain any HTI pair. In this case, if you use CCI to create a pair that should be a target of the At- Time Snapshot function, the command can be rejected. If this occurs, you should locate the consistency group in the Consistency Group tab of the Local Replications window, and then create a pair where this consistency group is specified. Restoring pairs To restore an HTI pair, the pair status must be PSUS. If the pair is restored, the HTI pair status changes to PAIR. To restore an HTI pair, use the Resync pairs window. Caution: When restoring a pair (reverse) resync, if a failure occurs, pair status changes to PSUE. To restore the pair, delete the snapshot data. Deleting the snapshot data does not guarantee the pair's P-VOL data. To assure the data, overwrite the backup data to the P-VOL or format the P-VOL. Prerequisites You have the Storage Administrator (Local Copy) role. The HTI pair status is PSUS. 1. In the Storage Systems tree, click Replications > Local Replications. 2. In the Pairs tab, select the pairs you want to resynchronize, then click Resync Pairs. 3. In the Resync Pairs window, for Resync Type, select Reverse Copy (Secondary > Primary) to reverse resynchronize the volumes from the S-VOL to the P-VOL. All differential data is updated to the P-VOL. 4. Click Finish. 5. In the Confirm window, for Task Name, type a name for the task and then click Apply. The pair is restored Pair tasks

67 Related topics Resync Pairs wizard on page B-29 Deleting snapshot data Deleting only the snapshot data maintains the relationship between the P- VOL and S-VOLs. If you only delete the snapshot data, you can assign the MU number of the deleted snapshot data when you store the snapshot data for the HTI pair. You can store a maximum of 1,024 snapshots for a P-VOL. If you have reached the maximum, delete the unneeded or unused snapshots. You must have the Storage Administrator (Local Copy) role to delete snapshot data. 1. In the Storage Systems tree, click Replications > Local Replications. 2. In the Pairs tab, select the pairs you want to resynchronize, then click Resync Pairs. 3. In the Resync Pairs window, for Resync Type, select Normal Copy (Primary > Secondary) to resynchronize the volumes from the P-VOL to the S-VOL. All differential data is updated to the S-VOL. 4. Click Finish. 5. In the Confirm window, for Task Name, type a name for the task and then click Apply. The snapshot data is deleted. The pair status changes to PAIR. Related topics Resync Pairs wizard on page B-29 Snapshot data storage methods on page 1-9 Deleting HTI pairs Deleting an HTI pair deletes snapshot data from the pool and cancels the relationship between the P-VOL and S-VOLs. You can delete snapshot data but not also release the HTI pair. To do this, delete the snapshot data for the pair in PFUS status. Caution: After deleting the HTI pair, if the number of pairs shown on the Summary tab and on the list is different, the configuration is still being processed. To reload the configuration information, wait for a while and then click File > Refresh All. Pair tasks 4-11

68 Prerequisites You have the Storage Administrator (Local Copy) role. The HTI pair status is PAIR, PSUS, or PSUE. 1. In the Storage Systems 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 then click Apply. While the pair is in the process of being deleted, the P-VOL and S-VOLs status is SMPL(PD). After the HTI pair is deleted, the status changes to SMPL. Related topics Delete Pairs window on page B Pair tasks

69 5 Monitoring and maintenance This topic provides information and instructions for monitoring and maintaining the HTI system. Monitoring pair information Monitoring consistency groups Monitoring pair operation history Monitoring licensed capacity Monitoring the number of cache management devices Managing pools and V-VOLs Viewing snapshot data capacity Maintenance requirements Monitoring and maintenance 5-1

70 Monitoring pair information You can monitor pair information in the following ways: Viewing the number of pairs and a list of pairs on page 5-2. Monitoring pair properties on page 5-3. Monitoring synchronous rates on page 5-3. Viewing the number of pairs and a list of pairs Pair status definitions 1. In the Storage Systems tree, click Replications > Local Replications. 2. View the number of pairs and a list of pairs. When checking the pair status, click Refresh View to ensure the data is current. The following table shows the HTI pair status definitions. Status Description S-VOL access CCI shows the status as SMPL(PD) The pair is being deleted. You cannot perform pair tasks when the pair is in this status. Deleting the pair changes the status to SMPL. Read/write disabled SMPL COPY The paircreate command has been accepted. P-VOLs accept read/write operations, but S-VOLs do not. Read/write disabled COPY PAIR The volumes are paired. S-VOLs cannot accept read/ write operations. Read/write disabled PAIR PFUL The data pool threshold is exceeded while the volumes were paired ( PAIR status). Read/write disabled PFUL PFUS The data pool threshold is exceeded in PSUS status. Read/write enabled PFUS PSUS The pairsplit command has completed. Update copy operations are stopped. S-VOLs accept read/write operations. The system records differential data between the P-VOL and S-VOLs so that you can immediately resynchronize the pair. Read/Write enabled. Can be mounted. PSUS for P- VOLs SSUS for S- VOLs RCPY A reverse resync operation is in progress. S-VOLs do not accept read/write operations. Only S-VOL differential data is copied to the P-VOL. Update copy operations are not performed during Reverse Copy or Quick Restore. Read/write disabled RCPY PSUE The pair is suspended by the system. P-VOLs accept read/write operations. Read/write disabled PSUE S-VOLs do not accept read/write operations. 5-2 Monitoring and maintenance

71 Monitoring pair properties You must have the Storage Administrator (Local Copy) role to monitor pair properties. 1. In the Storage Systems tree, click Replications > Local Replications. 2. Select the pair in the Pairs tab and then click More Actions > View Pair Properties. Related topics View Pair Properties window on page B-10 Monitoring synchronous rates You can check on the percentage of data that is synchronized between the P- VOL and S-VOLs. You must have the Storage Administrator (Local Copy) role to monitor synchronous rates. The HTI synchronous rate shows the rate that S-VOL data matches that of the S-VOL s next new generation. If the S-VOL is the latest one, the synchronous rate is computed by comparing the S-VOL with the P-VOL. The synchronous rate is a rough value and can have a large margin of error. If the P-VOL is written in the configuration of multiple generation (the configuration between the P-VOL and S-VOLs is 1:N), the synchronous rates for only the S-VOL of the newest generation decrease. If the S-VOL is written to, only the synchronous rates of written generation decrease. The following figure shows an example for synchronous rates in the configuration between the P-VOL and S-VOLs is 1:N. 1. In the Storage Systems tree, click Replications > Local Replications. 2. Select the pair in the Pairs tab and then click More Actions > View Pair Synchronous Rate. 3. In the View Pair Synchronous Rate window, click Refresh View. Monitoring and maintenance 5-3

72 The latest synchronous rate is shown. Caution: To ensure that this rate is up to date when you view the rate while restoring an HTI pair, ensure that the pair task has completed. If you close the window, information in the Local Replications window may not be the latest. Click Refresh View again. Related topics View Pair Synchronous Rate window on page B-12 Monitoring consistency groups You monitor consistency groups in the following ways: Viewing the number of consistency groups on page 5-4. Viewing a list of consistency groups on page 5-4. Viewing consistency group properties on page 5-5. Viewing the number of consistency groups 1. In the Storage Systems tree, click Replications > Local Replications > Consistency Group. 2. View the number of consistency groups. You can also view the number of consistency groups in the following windows: Consistency Group Properties window In SI, in the Pair Operation window, in the Volume list. Related topics Local Replications window on page B-3 Requirements for consistency groups on page 2-6 Viewing a list of consistency groups 1. In the tree, click Replications > Local Replications. View a list of consistency groups in the Consistency Groups tab. Related topics Local Replications window on page B Monitoring and maintenance

73 Viewing consistency group properties You must have the Storage Administrator (Local Copy) role to view consistency group properties. 1. In the Storage Systems tree, click Replications > Local Replications. 2. On the Consistency Groups tab, click CTG ID. 3. In the Consistency Group Properties window, view consistency group properties. Related topics Consistency Group Properties window on page B-15 Monitoring pair operation history You can review the operations that have been performed on a pair. You must have the Storage Administrator (Local Copy) role to monitor pair operation history. If you use 1,000 or more pairs concurrently, some operation history might not be recorded. 1. Click Replications in the tree. 2. Click View Histories. 3. In the View Histories window, for Copy Type, select TI. The following table shows HTI tasks that are shown in the View Histories window. The Description column indicates which tasks ran. Code Description Explanation 2001 PAIR The pair was created PSUS The pair was split SMPL The pair was deleted COPY(RS-R) START Pair restoration task began COPY(RS-R) END Pair restoration task completed COPY(RS-R) ENDED ABNORMAL Pair restoration task failed INITIALIZE START Initialization processing began INITIALIZE END Initialization processing terminated normally INITIALIZE ENDED ABNORMAL Initialization processing terminated abnormally COPY(RS) Snapshot data was deleted PSUE(ABNORMAL END) A failure occurred. The pair status changed to PSUE. Monitoring and maintenance 5-5

74 Related topics View Histories window on page B-13 Monitoring pair operation history using secondary window Use the History window to view the history of tasks and associated data. The upper pane shows SI history. The lower pane shows SS and HTI history. To view HTI history, click the Thin Image tab. For details about SS history, see the Hitachi Copy-on-Write Snapshot User Guide. 1. In SN, click Actions > Local Replications > SI/SS > History. If some of the pairs include LUSE volumes or if the total number of the following pairs and migration plans is 500 or more in the subsystem, you may need to wait until the History window shows the operation history. SI pairs SS pairs SIz pairs FCv2 Volume Migration 5-6 Monitoring and maintenance

75 HTI pairs 2. In the History window, see HTI information in the bottom part of the window. The list sorts based on the column heading you click. 3. To change the order of the items in the list, click a column in the list. The list is sorted based on the items in the clicked column. If there are more than 16,384 records of tasks, the list is divided into multiple pages and only the list that is currently shown is sorted. If you click the same column again, you can switch the sorting order (Ascending or Descending). 4. If the information on the list is not updated, click File > Refresh to update with the latest information. For tasks involving the copying process, the History window does not show information about the tasks until the copying process starts. If you perform an task on a pair before the copying process starts, the History window does not show information about the task. 5. If there are many records of tasks, scroll the list to see the task history that is not currently shown. If you click and drag down the frame border that divides the History window into upper and lower panes, you can expand the display area of the list. 6. If there are more than 16,384 records of tasks, click Next. The list shows subsequent records of tasks. If you click Previous, the list switches to the previous page. If there are 16,384 or fewer records of tasks, Previous and Next are unavailable. The storage system saves up to 512,000 records of latest tasks. See the following table for items that are shown for HTI pairs. Item Previous button Next button Date P-VOL Description Shows the previous page of the task history list when the total number exceeds 16,384. If the number of the task history pages is less than 16,384, this item is unavailable. Shows the next page of the task history list when the total number exceeds 16,384. If the number of the task history entries is less than 16,384, this item is unavailable. The date and time of the task in the YYYY / MM / DD hh:mm:ss format. YYYY: year MM: month DD: day hh: hour mm: minute ss: second The task's P-VOL, identified by LDKC:CU:LDEV. Monitoring and maintenance 5-7

76 Item S-VOL MU Pool ID Code Message Description A device ID ending in #, such as 00:00:3C #, indicates that the LDEV is an external volume. For more information about an external volume, see the Hitachi Universal Volume Manager User Guide. A device ID ending in X, such as 00:00:3C X, indicates that the LDEV is an HDP V-VOL. For more information about V-VOLs, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. The task's S-VOL (V-VOL), identified by LDKC:CU:LDEV. A device ID ending in V, such as 00:00:01 V, indicates that the LDEV is a V-VOL. HTI ID. ID of the related data pool. HTI reference code, which indicates the kind of task that was performed. For more information about the codes, see Monitoring pair operation history on page 5-5. Describes the task. Related to the reference code. For more information about the codes, see Monitoring pair operation history on page 5-5. Monitoring licensed capacity 1. In the Storage Systems tree, select Replications. 2. View the licensed capacity. Related topics Replications window on page B-2 Monitoring the number of cache management devices You can monitor the number of cache management devices, such as the current number of devices and maximum amount allowed in the storage system, in the View Management Resource Usage window. 1. On the menu bar, select Actions > View Management Resource Usage. 2. From the View Management Resource Usage window, view the number of cache management devices in Number of Cache Management Devices. Related topics The View Management Resource Usage window in the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. 5-8 Monitoring and maintenance

77 Thin Image cache management device requirements on page 2-10 Managing pools and V-VOLs You can complete the following to manage pools and V-VOLs: Monitoring pool information on page 5-9. Increasing pool capacity on page Monitoring pool information 1. In the Storage Systems tree, select Pools. 2. View information about a pool. Related topics The top window when you select Pools. For more information about this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Viewing used pool capacity You can view used pool capacity by pool or by HTI P-VOL. Viewing used capacity by pool 1. In the Storage System tree, select Pools. 2. The used capacity of the pools appears in the Used column of the Pools tab. Related topics The Pools window after selecting a pool in the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems Viewing used pool capacity by HTI P-VOL 1. In the Storage System tree, select Pools. 2. In the Pools table, click the name of the pool for which you want to see the used capacity. 3. Select the Primary Volumes tab. 4. The used pool capacity of the HTI P-VOLs appears in the Used Pool Capacity column. Related topics The top window when selecting a pool under Pools in the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Monitoring and maintenance 5-9

78 Viewing formatted pool capacity The following are the cases that the free pool capacity is not formatted. In these cases, the free capacity may not increase: Pools other than the selected pool are being formatted. The pool usage level reaches up to the warning threshold. The selected pool is blocked. I/O loads to the storage system are high. The cache memory is blocked. Pool-VOLs in the selected pool are blocked. Pool-VOLs which are external volumes in the selected pool are blocked. Correction access executes to the pool-vol in the selected pool. The format function for a free space of a pool is not operating. The following are the cases that the formatted pool capacity may decrease: The system is allocating new pages. The system is performing a correction copy. 1. In the Storage Systems tree, select Pools. 2. In the Pools window, complete the following: Increasing pool capacity a. From the Pools table, click the row for the pool you want to confirm free pool capacity. b. Click More Actions > View Pool Management Status. View the formatted pool capacity in the View Pool Management Status window. You can increase the pool capacity by adding pool-vols to the pool. The pool capacity is calculated by subtracting the capacity of V-VOL management areas from the total capacity of pool-vols in the pool. Check the capacity of available free space in the pool and expand the pool as needed. 1. In the Storage System tree, select Pools. 2. From the list, click the pool that has a capacity you want to increase and then click Expand Pool. Note: You cannot select multiple pools to expand. 3. In the Expand Pool window, click Select Pool VOLs. 4. In the Select Pool VOLs window, complete the following, and then click OK: In the Available Pool Volumes table, select the LDEV you want to expand, and then click Add. The LDEV is moved to the Selected Pool Volumes table Monitoring and maintenance

79 You can add up to 1,024 volumes (including volumes already in a pool). To filter rows, select ON in the Filter component. To select all the pool-vols in the list, click Select All Pages. To specify the capacity unit and the number of rows to be shown, click Options. 5. In the Expand Pool window, the number of selected pool volumes and the total capacity is shown. Click Finish. 6. In the Confirm window, complete the following and then click Apply. For Task Name, type the name of the task. Character limit: 32 Allowable characters and symbols: All alphanumeric except \ / :, ; *? " < > Default: date-task Name For Go to tasks window for status, select to open the Tasks window. The pool capacity is increased. Changing pool threshold Use the following procedure to change the pool threshold. Prevent the pool from reaching full capacity by monitoring the pool usage rate. Caution: For example, when the actual pool usage rate is 50.1%, you round the value down to the closest integer 50, and 50% is shown in the Edit Pools window. If you set 50% as the pool threshold, even though the value shown on the window does not exceed the threshold, the excessive pool usage in SIM and SNMP is reported. 1. In the Storage System tree, select Pools. 2. From the list, click the pool with the threshold that you want to change. 3. Click More Actions > Edit Pools. 4. In the Edit Pools window, check the Warning Threshold, and click Finish: For Warning Threshold, type a new threshold. The range is shown below the text box. 5. In the Confirm window, complete the following and then click Apply. For Task Name, type a name for the task. Character limit: 32 Allowable characters and symbols: All alphanumeric except \ / :, ; *? " < > Default: date-task name For Go to tasks window for status, select to open the Tasks window. The pool threshold is changed. Monitoring and maintenance 5-11

80 Related topics The Expand Pool wizard in the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. The Edit Pools wizard in the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Changing pool names 1. In the Storage System tree, select Pools. 2. From the list, click the pool for which you want to change the name. To select more than one pool, hold down the Shift key and click multiple adjacent pools. Hold down the Ctrl key and click pools that are not adjacent. 3. Click More Actions > Edit Pools. 4. In the Edit Pools window, check the Pool Name, and then click Finish: For Pool Name, type a new pool name. Character limit: 32 (for the Pool Name and Initial Number combined.) - For Prefix, type alphanumeric characters Case-sensitive: Yes - For Initial Number, type a number Limit: 9 digits 5. In the Confirm window, complete the following and then click Apply: For Task Name, type a name for the task. Character limit: 32 Allowable characters and symbols: All alphanumeric except \ / :, ; *? " < > Default: date-task name For Go to tasks window for status, select to open the Tasks window. The pool name is changed. Related topics The Edit Pools wizard in the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Recovering pools Recover pools for disaster recovery purposes. Normally, do not perform this task. Note: The recovery time for pools depends on pool or V-VOL usage. Calculate roughly 20 minutes of recovery time for every 100 TB of pool or V-VOL usage. Recovery time also depends on system workload. 1. In the Storage System tree, select Pools Monitoring and maintenance

81 2. From the list, select one or more pools that you want to recover. Hold down the Shift key when clicking multiple adjacent pools. Hold down the Ctrl key when clicking pools that are not adjacent. 3. Click More Actions > Restore Pools. 4. In the Restore Pools window, complete the following and then click Apply: For Task Name, type a name for the task. Character limit: 32 Allowable characters and symbols: All alphanumeric except \ / :, ; *? " < > Default: date-task name For Go to tasks window for status, select to open the Tasks window. The pool is recovered. Related topics The Restore Pools window in the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Deleting pools You can delete one of more pools in a single operation. 1. In the Storage System tree, select Pools. 2. In the Pools window, from the list, select the pool you want to delete, and then click More Actions > Delete Pools. 3. In the Delete Pools window, click Finish. 4. In the Confirm window, complete the following, and then click Apply: For Task Name, type a name for the task. Character limit: 32 Allowable characters and symbols: All alphanumeric except \ / :, ; *? " < > Default: date-task name For Go to tasks window for status, select to open the Tasks window. (Optional) Click Next to perform volume shredding to erase data from the volume. For more information about volume shredding tasks, see the Hitachi Volume Shredder User Guide. The pool is deleted. Related topics The Delete Pools wizard in the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Monitoring and maintenance 5-13

82 Changing V-VOL names 1. In the Storage System tree, select Logical Devices. 2. In the list, select the rows for V-VOLs you want to change, and then click Edit LDEVs. 3. In the Edit LDEVs window, select the LDEV Name and type the prefix and the initial number, and then click Finish. 4. In the Confirm window, complete the following and then click Apply: For Task Name, type the name of the task. Character limit: 32 Allowable characters and symbols: All alphanumeric except \ / :, ; *? " < > Default: date-task name For Go to tasks window for status, select to open the Tasks window. The V-VOL name is changed. Related topics The Edit LDEVs wizard in the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Deleting V-VOLs To delete V-VOLs and V-VOL groups that are specified for HTI S-VOLs, first release the pairs. 1. In the Storage System tree, select Logical Devices. 2. In the list, click the rows for the V-VOLs that you want to delete. Hold down the Shift key when clicking multiple adjacent pools. Hold down the Ctrl key when clicking pools that are not adjacent. 3. Click More Actions > Delete LDEVs. 4. In the Delete LDEVs window, complete the following, and then click Apply: For Task Name, type the name of the task. Character limit: 32 Allowable characters and symbols: All alphanumeric except \ / :, ; *? " < > Default: date-task name For Go to tasks window for status, select to open the Tasks window. The V-VOL is deleted Monitoring and maintenance

83 Related topics The Delete LDEVs window in the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Viewing snapshot data capacity You can use the raidcom command to view the snapshot data capacity for each P-VOL. This capacity indicates the pool capacity which is used as snapshot data stored from the P-VOL, but it does not include all of the information required to manage snapshot data. Although snapshot data is assigned from the pool in 42MB blocks, HTI stores snapshot data from a P-VOL in 256KB blocks. Therefore, the snapshot data capacity is not always consistent with each pool s used capacity. The following example shows how to use the raidcom command to view snapshot data capacity. #raidcom get ldev -ldev_id 640 Serial# : LDEV : 640 SL : 0 CL : 0 VOL_TYPE : OPEN-V-CVS VOL_Capacity(BLK) : VOL_Capacity(cyl) : NUM_LDEV : 1 LDEVs : 640 NUM_PORT : 1 PORTs : CL2-E-0 14 Linux_X86 F_POOLID : NONE VOL_ATTR : CVS : VVOL : QS : TIER_Alloc_level : H TIER#1_Alloc_rate : MAX : 50 : MIN : 30 TIER#3_Alloc_rate : MAX : 50 : MIN : 30 Snap_Used_Pool(MB) : 2181 For more information about the raidcom command, see the Command Control Interface Command Reference. Maintenance requirements This topic explains points to be noted regarding powering-off when HTI is up and running. This topic also explains points to be noted regarding offline microcode replacement. Replacing the microcode offline Microcode is usually replaced online. In the cases when it is replaced offline (for example, when configuration of shared memory needs changing), pool Monitoring and maintenance 5-15

84 Powering-off and pair information in shared memory is lost, and pools and pairs must be recreated. Use the following process to power off: 1. Stop the host I/O. 2. Switch off the power supply. When you restore the power, HTI's behavior depends on whether data that was in shared memory before powering off is present after powering on. If information in shared memory before powering off is present after powering on If information in the shared memory is present after switching off the power supply, the pools and pairs can usually be used. However, since the storage system checks the status of the pools and the pool volumes, if the pool volumes are blocked at that moment, the pool will be blocked and the status of the pairs changes to PSUE. When this occurs, do the following: 1. Switch the power on. 2. Recover the pools. Switching off the power supply while you are storing snapshot data by consistency group and the status of all the pairs in the consistency group have not changed completely does not resume the storing of snapshot data. Switching on the power supply does not guarantee a status change for some pairs. If information in shared memory is lost after switching off the power supply If you lose power and the data in SM is lost, the storage system saves the data to SSD at the time the power supply is switched off. You can still use the pool and HTI pairs, because the data is restored to SM from SSD after switching the power supply back on Monitoring and maintenance

85 6 Troubleshooting This topic provides HTI troubleshooting information. General troubleshooting Calling the Hitachi Data Systems customer support Troubleshooting 6-1

86 General troubleshooting The following table shows HTI troubleshooting information. Problem Pool information is not shown. A pool is blocked. Pool usage rate exceeds the threshold. Cannot add pool-vols. Cause: The pool is blocked. Solution: Recover the blocked pool. Causes and solutions For more information about recovering blocked pools, see The workflow for recovering blocked pools workflow on page 6-4. Cause: The pool-vols are blocked. The pool reaches full capacity. Solution: 1. Recover the blocked pool. For more information about recovering blocked pools, see The workflow for recovering blocked pools workflow on page Complete the SIMs. For more information about completing SIMs, see The workflow for processing pool-related SIMs on page 6-5. Causes: You have too much snapshot data stored in the pool. The pool s capacity is insufficient. The pool threshold is too low. Solutions: 1. Complete one or more of the following: Decrease the pool s usage rate. To do this, delete all of the snapshot data in the P-VOL. Increase the pool s capacity. To do this, add more pool volumes. Increase the pool s threshold. To do this, set a larger value for the pool threshold. 2. Complete the SIMs. For more information about completing SIMs, see The workflow for processing pool-related SIMs on page Ensure that you have enough unused volumes to add the pool volumes. If you do not have unused volume, create new volumes or call the Support Center to have a representative add the hard disks. Causes: Note: This problem can take time to solve. The maximum 1,024 pool-vols are already set in the pool. Available pool management block in the V-VOL management area in the shared memory is insufficient. Pool-VOL requirements were not followed. Solutions: Add pool-vols to another pool. Initialize the V-VOL management area. Check pool-vols requirements. 6-2 Troubleshooting

87 Problem You cannot create HTI pairs. HTI pairs are not shown in the volume list. An error occurred while restoring the pair. A volume is blocked. A problem occurred in the host application for monitoring the volumes. Causes: Causes and solutions There are not enough cache management devices. There are not enough resources depending on cache management devices. The conditions to create the pair are not fulfilled. The status of the specified volume is not shown because an HTI pair is being deleted. Solutions: Ensure that there are enough cache management devices to create the pairs. For more information, see Thin Image cache management device requirements on page If cache management devices are running out, delete the unnecessary external volumes, V-VOLs, or all the HTI pairs related to the P-VOL. Fulfill the conditions to create the pair and try creating the pair again. Increase the resources depending on cache management devices. To do this, delete the unnecessary external volumes, V-VOLs, or all the HTI pairs related to the P-VOL. Delete them until the following formula is satisfied: The number of external volumes + the number of V-VOLs + the number of P-VOLs of HTI pair <= 59,136. Complete the following: a. In the Local Replications window, confirm that the volume status has changed to SMPL (the status is not shown). b. Try the pair creation again. Run CCI's inqraid command and verify that the volume is not used by HTI, and then try the pair creation again. Causes: The pairs are not created. Displaying of the pairs is prohibited by the filtering function. Solutions: Create the pairs. Change the settings in the Display Filter dialog box. Cause: A volume is blocked because a failure occurred in the hard disk drive. Solution: Delete the pair that is blocked, and call the Support Center. Causes: A failure occurred in two or more hard disk drives. The breaker was turned off once and then the power supply switched on. Solution: Ask the Hitachi Data Systems customer support for assistance. Cause: Access to the volume is rejected. Solution: 1. Stop the host application monitoring the volumes. 2. Change all pair statuses to PSUS. 3. Start the monitoring application on the host. Troubleshooting 6-3

88 Problem Causes and solutions To check whether the host has access to pair volumes, see Pair status on page You booted/rebooted the host server or ran the command for recognizing a device, but the V-VOL is not correctly recognized. Cause: Access to the volume is rejected. Solution: 1. Stop the host application monitoring the volumes. 2. Split the pairs ( PSUS status). 3. Reboot the host server or run a command that causes the system to recognize the device. 4. Start the host application monitoring the volumes. To check whether the host has access to pair volumes, see Pair status on page When the host computer tries to access the port, an error occurs and the host cannot access the port. SN frequently times out. The pair information in Local Replications window is not updated. The date and time for Last Updated is not updated. By the write operation from the host, the used pool capacity shown on the Summary tab in the Pool window and on the list in the Primary Volumes tab may be different. Cause: A port may go offline because access to a volume on another port has been rejected. Solutions: Wait awhile, then retry the task. If a host application is installed to monitor the volume, stop the application. Causes: The load on SN is too heavy and it cannot respond to the SVP. The time-out period is not long enough. Solutions: Wait awhile, then retry the task. Verify the SN RMI time-out period. For information about how to set RMI time-out period, see the Hitachi Storage Navigator User Guide. HTI processing may be in progress. After the HTI processing finishes, the update will be complete. The write operation from the host is running the copy processing. The copy processing must finish before the used pool capacity shown on the summary tab in the Pool window and on the list in the Primary Volumes tab match. If the solutions in this table do not work, or if your problem is not included in this table, call the Support Center. The workflow for recovering blocked pools workflow Use the following process to recover blocked pools: 6-4 Troubleshooting

89 1. Recover the blocked pool-vols. For more information about recovering blocked pool-vols, call the Support Center. 2. Recover the pool. Do one of the following: Add additional pool-vols to the pool. Increase the unused capacity. To do this, delete all snapshot data from the P-VOLs. For more information about recovering a blocked pool, see Recovering pools on page Recover the pairs. To do this, delete the pair. If the pool is blocked, the status of all pairs with snapshot data in the pool changes to PSUE. To recover the pairs in this status, delete them. 4. Recover the V-VOLs. For more information about recovering V-VOLs, call the Support Center. The workflow for processing pool-related SIMs Completing SIMs Use the following workflow to process pool-related SIMs: 1. Correct pool-related Service Information Messages (SIMs) for the following, if they occur: Reference code 601XXX: Pool usage rate exceeds the threshold. Reference code 602XXX: Pool is blocked. XXX indicates the pool ID. Check SIMs using the System Information/ Status window in SN. Reference code 602FFE: Multiple pools are blocked. Reference code : The snapshot estimated manageable capacity is less than 128TB. Reference code : There is no space available in the shared memory. 2. Complete the SIM and change the SIM status to completed. For more information about completing SIMs, see Completing SIMs on page Complete one of the following: For reference code 601XXX or 602XXX, recover the pool in the normal status. For more information about countermeasures of these codes, see General troubleshooting on page 6-2. For reference code * or , perform one of the following tasks: a. Delete unused pools. Troubleshooting 6-5

90 b. Delete unused HTI pairs. c. Delete the unused V-VOLs, created by using HDP or HDT. d. Shrink the capacity of the HDP pool or HDT pool. * In this case, you do not need to perform these tasks. However, if a long time has passes since you have performed the task, reference code is reported. 2. In the Pool window, click More Actions > Complete SIM Action. 3. In the Confirmation window, complete the following and then click Apply. For Task Name, type a name for the task. Character limit: 32 Allowable characters and symbols: All alphanumeric except \ / :, ; *? " < > Default: date-task name For Go to tasks window for status, select to open the Tasks window. Completing warning SIMs before depletion of cache management devices The following SIM occurs if the number of the remaining cache management devices goes below 4,096: Reference code For more information about SIM reference codes, call the Support Center. In an SN window, you can see SIMs that occur in the storage system. For more information about the window, see the Hitachi Storage Navigator User Guide. Calculating the number of remaining cache management devices Use the following process to calculate the number of remaining cache management devices: 1. Calculate the remaining number of the remaining cache management devices. To do this, use the following formula: number-of-cache-management-devices = 65,280 - number-of-cachemanagement-devices-being-used For more information about how to confirm the number of cache management devices being used, see Monitoring the number of cache management devices on page 5-8. If a warning SIM is issued before you deplete the cache management devices, that does not mean a problem occurs immediately. However, if you continue to use the storage system and then cache management devices are depleted, the HTI pair status becomes PSUE and you cannot store the snapshot data. In addition, you cannot create additional HTI 6-6 Troubleshooting

91 pairs using other P-VOLs. It is important that you reserve enough cache management devices. 2. Correct the problems related to a SIM. For more information about correcting problems, see General troubleshooting on page Complete the SIM and change the SIM status to completed. For more information about completing SIMs, see Completing SIMs on page 6-5. SIMs related to cache management devices completion Use the following process to complete SIMs related to cache management devices: 1. Confirm the number of the remaining cache management devices. For more information about how to confirm the number of the remaining cache management devices, see Calculating the number of remaining cache management devices on page Complete the following to make sure that the number of the remaining cache management devices is 4,096 or more: Remove unneeded V-VOLs. Remove all snapshots in unneeded P-VOLs. 3. Complete the SIM. For more information about completing SIMs, see Completing SIMs on page (Optional) Verify whether a SIM has been completed normally using the SN window. For more information about this window, see the Hitachi Storage Navigator User Guide. Calling the Hitachi Data Systems customer support If you need to call the Hitachi Data Systems customer support, provide as much information about the problem as possible, including: The circumstances surrounding the error or failure. The content of any messages displayed in SN. The SN configuration information (use the FD Dump Tool). The SIMs, including reference codes and severity levels, displayed in SN. HDS customer support staff is available 24 hours a day, seven days a week. If you need technical support, log on to HDS Support Portal for contact information: Troubleshooting 6-7

92 6-8 Troubleshooting

93 A CCI command reference This topic describes CCI commands corresponding to actions in the SN GUI. Statuses required for CCI tasks Troubleshooting with Command Control Interface CCI command reference A-1

94 Statuses required for CCI tasks You can use CCI to perform pair tasks. You can also use SN. To perform tasks using CCI, you run existing commands for pair tasks or the raidcom commands. Use raidcom commands to store 65 or more snapshot data or use 64 or more MU numbers. You can use the existing commands for pair tasks only for the pairs which have 0 to 63 MU numbers. The following table shows the CCI existing commands and raidcom commands you can use to perform pair tasks, as well as the SN tasks. Pair task The CCI command SN task Create pair paircreate Create pairs (using the raidcom add snapshot Create Pair wizard) Create and split pair paircreate split Split pairs (using the Split Pairs wizard) Split pair pairsplit Split pairs (using the Split raidcom modify snapshot - Pairs wizard) snapshot_data create raidcom modify snapshot - snapshot_data split Normal copy pairresync Resynchronize pairs (using raidcom modify snapshot - the Resync Pairs wizard) snapshot_data resync Reverse copy pairresync -restore Resynchronize pairs (using raidcom modify snapshot - the Resync Pairs wizard) snapshot_data restore Delete pair pairsplit -S Delete pairs (using the raidcom delete snapshot Delete Pairs window) CCI pair status names Running a command for a pair with a different status than the one required can give you mixed results. The following table shows results for tasks run with statuses other than those that are required. CCI command Status paircrea te paircrea te -split pairsplit pairresy nc pairresy nc - restore pairsplit -S pairsplit -E SMPL Ok Ab Ab Ab Ab Np Ab COPY Np Ab Ab Np Np Ab Ab A-2 CCI command reference

95 CCI command Status paircrea te paircrea te -split pairsplit pairresy nc pairresy nc - restore pairsplit -S pairsplit -E PAIR/ PFUL PSUS/ PFUS Np Ok Ok Np Np Ok Ab Ab Np Np Ok Ok Ok Ab RCPY Np Ab Ab Np Np Ab Ab PSUE Ab Ab Ab Ok Ab Ok Np Ok: ends normally Np: not performed but ends normally Ab: the command is rejected, ends abnormally You cannot use the noread mode (-m noread) for S-VOLs if you are using CCI. If the noread mode is specified for a S-VOL when creating a pair, the command ends normally but the noread mode does not take effect. If a CCI command is rejected and ends abnormally, sense bytes (SSB) are output to the CCI error log file if the host is running the HP-UX operating system. Sense bytes indicate the cause of the error. For more information about SSB and error causes, see Troubleshooting with Command Control Interface on page A-3. Troubleshooting with Command Control Interface When an error occurs using CCI, you can identify the cause of the error by referring to the following: The log shown on the CCI window The CCI operation log file 1. Find the error code from the logs displayed in the CCI window. The following figure shows an example of a log displayed in the CCI window: 2. Locate the SSB1 and SSB2 codes. In the previous figure the error codes appear to the right of "SSB=". The last four digits to the left of the comma (,) are the SSB1 code (B9E1). The last four digits to the right of the comma (,) are the SSB2 code (B901). CCI command reference A-3

96 3. Locate the description of the SSB1/SSB2 error code combination in the next table. For error codes not described in this table, call the Support Center. 1. Open the CCI log file in the following default location: /HORCM/log*/curlog/horcmlog_HOST/horcm.log where: The asterisk (*) is the instance number. HOST is the host name. 2. Find the error code. An example error code string is: 11:06: SSB = 0xB901,4A96 3. Locate the SSB1 and SSB2 codes. In the example error code above: Error codes appear to the right of "SSB=". The last four digits to the left of the comma (,) are the SSB1 code (B901). The characters to the right of the comma (,) are the SSB2 code (4A96). 4. Locate the description of the SSB1/SSB2 error code combination in the following table. For details about error codes that are not described in the following table, call the Support Center. The following table shows the CCI error codes for SSB1: 2E31, B901, B9A8, B9A9, B9AD, B9AE). SSB2 CCI command Cause of error 9100 All commands You cannot run the command because the user authentication is not performed paircreate You cannot create the HTI or SS pair because of a shortage of pair tables paircreate You cannot create the HTI or SS pair because the pool is not available paircreate You cannot create the HTI or SS pair because you specified a pool ID different from the pool ID used by existing pairs with the specified P-VOL paircreate You cannot create the HTI or SS pair because the volume you specified as the P-VOL is already used by another HTI or SS S-VOL paircreate You cannot create the HTI or SS pair because the volume you specified as the S-VOL is already used by another HTI or SS P-VOL paircreate You cannot create the HTI or SS pair because the volume you specified as the S-VOL is already used by another HTI or SS S-VOL. A-4 CCI command reference

97 SSB2 CCI command Cause of error 9706 paircreate You cannot create the HTI or SS pair because the specified snapshot ID is already used by another HTI or SS pair paircreate You cannot create the HTI or SS pair because the capacity of the pair that you are trying to create exceeds the licensed capacity All commands The command ended abnormally. You tried to use a command other than paircreate for the volume in the pair other than the HTI or SS pair. This error also can occur if you run the command specifying an unsupported parameter All commands The command ended abnormally because the pair is in a status that the command does not accept. This error also can occur if you run the command specifying an unsupported parameter. 971A paircreate You cannot create the HTI or SS pair because the capacity of shared memory is insufficient. 971F pairresync - restore You cannot restore the HTI or SS pair because the volume you specified as the P-VOL has an S-VOL Disable attribute All commands An error occurred for one of the following reasons: The LDEV number that is specified for the P-VOL or S- VOL is not correct. The specified P-VOL or S-VOL has not been paired. The pair that is specified by the P-VOL or S-VOL is not ready for the specified task. The specified snapshot identifier (MU number) is not correct. The specified snapshot identifier (MU number) is already in use. The specified pool is unusable. The license capacity is exceeded. Control tables for HTI or SS are running out paircreate, pairsplit, pairresync, pairresync - restore The command ended abnormally because you have not installed SS or SI All commands The command ended abnormally because there is no additional shared memory (FCv2, TPF, Extension1) All commands The command ended abnormally because there is no additional shared memory (more than SM 1) All commands The command ended abnormally because the LDEV number of the volume you specified as the HTI or SS P-VOL is beyond the specified range All commands The command ended abnormally because you specified the unmounted volume as the HTI or SS P-VOL. CCI command reference A-5

98 SSB2 CCI command Cause of error 9727 paircreate, pairsplit, pairresync, pairresync - restore 9728 paircreate, pairsplit, pairresync, pairresync - restore 9729 paircreate, pairsplit, pairresync, pairresync - restore The command ended abnormally because you specified a blocked volume as the HTI or SS P-VOL. The command ended abnormally because you specified a volume that is in the process of being formatted as the HTI or SS P-VOL. The command ended abnormally because you specified a volume as the HTI or SS P-VOL and that volume has an emulation type other than OPEN-V. 972A paircreate You cannot create the HTI or SS pair because the volume you specified as the HTI or SS P-VOL has the command device setting. 972C paircreate You cannot create the HTI or SS pair because you have exceeded the allowable HTI P-VOL capacity, which is 4 TB. 972E paircreate You cannot create the HTI or SS pair because you have exceeded the allowable HTI S-VOL capacity, which is 4 TB. 972F paircreate You cannot create the HTI or SS pair because you specified a V-VOL as the HTI or SS P-VOL paircreate You cannot create the HTI or SS pair because you specified a pool-vol as the HTI or SS P-VOL pairresync - restore 9732 pairresync - restore 9733 pairresync - restore 9734 pairresync - restore You cannot restore the HTI or SS pair because the HTI or SS P-VOL and TC P-VOL share the volume, and the status of the TC pair is not PSUS or PSUE. You cannot restore the HTI or SS pair because the HTI or SS P-VOL and UR P-VOL share the volume, and the status of the UR pair is not PSUS or PSUE. You cannot restore the HTI or SS pair because the HTI or SS P-VOL and TC S-VOL share the volume. You cannot restore the HTI or SS pair because the HTI or SS P-VOL and UR S-VOL share the volume paircreate You cannot create the HTI or SS pair because you specified UR's journal volume as the HTI or SS P-VOL paircreate, pairsplit, pariresync, pairresync - restore The command ended abnormally because the LUSE volumes you specified as the P-VOL and S-VOL do not have the same structure. 973A paircreate You cannot create the HTI or SS pair because you specified a volume with the VMA setting as the HTI or SS P-VOL. A-6 CCI command reference

99 SSB2 CCI command Cause of error 973B All commands The command ended abnormally because the LDEV number of the volume you specified as the HTI or SS S-VOL is beyond the specified range. 973C All commands The command ended abnormally because you specified an unmounted volume as the HTI or SS S-VOL. 973D 973E 973F paircreate, pairsplit, pairresync, pairresync - restore paircreate, pairsplit, pairresync, pairresync - restore paircreate, pairsplit, pairresync, pairresync - restore The command ended abnormally because you specified a blocked volume as the HTI or SS S-VOL. The command ended abnormally because you specified a volume that is in process of formatting as the HTI or SS S- VOL. The command ended abnormally because you specified a volume that has an emulation type other than OPEN-V as the HTI or SS S-VOL paircreate You cannot create the HTI or SS pair because the volume you specified as the HTI or SS S-VOL has the command device setting paircreate You cannot create the HTI or SS pair because you specified an external volume as the HTI or SS S-VOL paircreate You cannot create the HTI or SS pair because you specified a volume other than V-VOLs as the HTI or SS S-VOL paircreate You cannot create the HTI or SS pair because you specified a pool-vol as the HTI or SS S-VOL paircreate You cannot create the HTI or SS pair because you specified a TC P-VOL as the HTI or SS S-VOL paircreate You cannot create the HTI or SS pair because you specified TC S-VOL as the HTI or SS S-VOL paircreate You cannot create the HTI or SS pair because you specified a UR data volume or journal volume in the intermediate site of 3DC cascading configuration as the HTI or SS S-VOL, You cannot create the HTI or SS pair. 974A paircreate You cannot create the HTI or SS pair because you specified a UR P-VOL as the HTI or SS S-VOL. 974B paircreate You cannot create the HTI or SS pair because you specified a UR S-VOL as the HTI or SS S-VOL. 974C paircreate You cannot create the HTI or SS pair because you specified a UR journal volume as the HTI or SS S-VOL. 974F All commands The command ended abnormally because the volume you specified as the HTI or SS S-VOL has an S-VOL Disable attribute. CCI command reference A-7

100 SSB2 CCI command Cause of error 9750 paircreate You cannot create the HTI or SS pair because you specified a volume with the VMA setting as the HTI or SS S-VOL paircreate, pairsplit, pairresync, pairresync - restore 9753 paircreate, pairsplit, pairresync, pairresync - restore The command ended abnormally because the Max LBA size of the volumes you specified as the HTI or SS P-VOL and S- VOL is different. The command ended abnormally because the number of slots of the volumes you specified as the HTI or SS P-VOL and S-VOL is different paircreate You cannot create the HTI or SS pair because you specified a HDP V-VOL as the HTI or SS S-VOL All commands The command ended abnormally because you specified a SI reserved volume as the HTI or SS P-VOL All commands The command ended abnormally because you specified a Volume Migration source volume as the HTI or SS P-VOL. For information about using Volume Migration, call the Support Center All commands The command ended abnormally because you specified a Volume Migration target volume as the HTI or SS P-VOL. For information about using Volume Migration, call the Support Center All commands The command ended abnormally because you specified a Volume Migration reserved volume as the HTI or SS P-VOL. For information o about n using Volume Migration, call the Support Center. 975A All commands The command ended abnormally because you specified a SI P-VOL as the HTI or SS S-VOL. 975B All commands The command ended abnormally because you specified a SI S-VOL as the HTI or SS S-VOL. 975C All commands The command ended abnormally because you specified a SI reserved volume as the HTI or SS S-VOL. 975D All commands The command ended abnormally because you specified a Volume Migration source volume as the HTI or SS S-VOL. For information about using Volume Migration, call the Support Center. 975E All commands The command ended abnormally because you specified a Volume Migration target volume as the HTI or SS S-VOL. For information about using Volume Migration, call the Support Center. 975F All commands The command ended abnormally because you specified a Volume Migration reserved volume as the HTI or SS S-VOL. For information about using Volume Migration, call the Support Center. A-8 CCI command reference

101 SSB2 CCI command Cause of error 9763 paircreate You cannot create the HTI or SS pair because you do not have enough shared memory or the initialization is in process. 976A paircreate An unavailable parameter (unsupported parameter) is specified in the command. 976C pairsplit You cannot store snapshot data because you ran the command with the PSUE option. 976E pairsplit You cannot store snapshot data because the HTI or SS P- VOL and TC S-VOL share the volume, and the status of the TC pair is COPY. 976F pairsplit You cannot store snapshot data because the HTI or SS P- VOL and UR S-VOL share the volume, and the status of the UR pair is COPY paircreate You cannot create the HTI or SS pair because you specified UR delta resync pair volume as the HTI or SS S-VOL paircreate You cannot create the HTI or SS pair because the HTI or SS P-VOL and SI P-VOL share the volume, and the MU number you specified for the HTI or SS pair is already used by the SI pair paircreate You cannot create the HTI or SS pair because the HTI or SS P-VOL and SI S-VOL share the volume, and you specified MU number zero (0) for the HTI or SS P-VOL. 977A 977B paircreate, pairsplit paircreate, pairsplit The command ended abnormally because the HTI or SS P- VOL and SI P-VOL share the volume, and the SI pair was in the process of resynchronization. The command ended abnormally because the HTI or SS P- VOL and SI S-VOL share the volume, and SI pair status is not PSUS. 977C pairresync - restore 977D pairresync - restore You cannot restore the HTI or SS pair because the HTI or SS P-VOL and SI P-VOL share the volume, and SI pair status is not PSUS or PSUE. You cannot restore the HTI or SS pair because the HTI or SS P-VOL and SI S-VOL share the volume, and SI pair status is not PSUS. 977E pairsplit You cannot store snapshot data because the pool or the pool-vol is blocked pairresync - restore 9786 paircreate, pairsplit, pairresync, You cannot restore the HTI or SS pair for one of the following reasons: A snapshot for the HTI or SS pair to be restored is being stored per consistency group. The P-VOL of the HTI or SS pair to be restored is used as the P-VOL of another HTI or SS pair, and the snapshot data of the latter pair is being stored per consistency group. The command ended abnormally because quorum disks are specified as P-VOLs of HTI or SS pairs. CCI command reference A-9

102 SSB2 CCI command Cause of error pairresync - restore 9787 paircreate, pairsplit, pairresync, pairresync - restore The command ended abnormally because quorum disks are specified as S-VOLs of HTI or SS pairs. 978A paircreate You cannot create the HTI or SS pair using the consistency group number for one of the following reasons: The specified consistency group number is in use for SI. You have reached the maximum number of pairs that you can create for a consistency group. A pair that uses the same P-VOL exists already in the specified consistency group. 978B paircreate You cannot create the HTI or SS pair because the specified consistency group number is out of the range of the number that you can specify paircreate You cannot create the HTI or SS pair because the HDP V- VOL, which is undergoing capacity expansion, is specified as the HTI or SS P-VOL paircreate You cannot create the HTI or SS pair because an HDP V- VOL that is undergoing Unmap command operation with system option mode 905 ON is specified as the HTI or SS P- VOL paircreate, pairsplit, pairresync, pairresync - restore 9797 paircreate, pairsplit, pairresync, pairresync - restore The command ended abnormally because a volume without path definition is specified as the HTI or SS P-VOL. The command ended abnormally because a volume without path definition is specified as the HTI or SS S-VOL. 97A1 paircreate If you have already created the maximum number of HTI or SS pairs, you cannot create additional pairs. 97A2 97A3 paircreate, pairsplit, pairresync, pairresync-restore paircreate, pairsplit, pairresync, pairresync-restore The command ended abnormally because the volume specified as the P-VOL uses two mirrors in a 3 UR data center configuration. The command ended abnormally because the volume specified as the S-VOL uses two mirrors in a 3 UR data center configuration. 97A4 paircreate You cannot create the HTI or SS pair because the DP-VOL in the initialization process is specified as the HTI or SS P- VOL. A-10 CCI command reference

103 SSB2 CCI command Cause of error 97A5 97A6 paircreate, pairsplit, pairresync, pairresync - restore paircreate, pairsplit, pairresync, pairresync - restore The command ended abnormally because the external volume that is mapped for online data migration is specified as HTI or SS P-VOL. The command ended abnormally because the external volume that is mapped for online data migration is specified as the HTI or SS S-VOL. 97B4 paircreate You cannot create the pair specified with a consistency group because the maximum number of the consistency groups are defined. 97B5 paircreate You cannot create the HTI or SS pair for the specified P-VOL because the maximum number of snapshot ID (MU number) was used. 97B6 paircreate You cannot create the HTI or SS pair because of one of the following reasons: The new snapshot group was being created, but the maximum number of snapshot groups were defined. The maximum number of pairs are defined in the specified snapshot group. 97B7 paircreate You cannot create the HTI or SS pair because the HDP pool is being initialized. 97B9 paircreate, pairsplit, pairresync, or pairresync - restore The command ended abnormally because the status of all pairs using the specified P-VOL is PSUE. 97BF paircreate You cannot create the HTI or SS pair by using the consistency group to which the specified snapshot group belongs because of one of the following reasons: The specified consistency group is being used for SI. You have reached the maximum number of pairs that you can created in a consistency group. A pair that uses the same P-VOL exists already in the specified snapshot group. 97C2 All commands The command ended abnormally because the specified MU number is outside the allowable range. 97C3 paircreate, pairsplit, pairresync, or pairresync - restore The command ended abnormally because microprograms that support HTI and other microprograms are mixed. 97C4 All commands The command ended abnormally because of one of the following reasons: The specified pool is neither an HTI pool nor an SS pool. CCI command reference A-11

104 SSB2 CCI command Cause of error The specified pool does not exist. 97C6 paircreate, pairsplit, pairresync, or pairresync - restore The command ended abnormally because HTI is not installed. 97C7 paircreate You cannot create the HTI or SS pair because the capacity of cache management devices is insufficient. 97C8 paircreate You cannot create the HTI or SS pair because the capacity of the volume you specified as the P-VOL or the S-VOL of the HTI pair is more than the supported size, which is 4 TB. 97C9 paircreate You cannot create the HTI or SS pair because you specified the LUSE volume for the P-VOL. 97CB All commands The command ended abnormally because the pool you specified is not an HTI pool. 97CE paircreate You cannot create the HTI or SS pair because of one of the following: You created an HTI pair using the consistency group number that you used for SS. You created an SS pair using the consistency group number that you used for HTI. 97CF paircreate You cannot create the pair because the specified consistency group number is being used by a snapshot group. B912 paircreate, pairsplit, pairresync The HTI or SS pair task failed because the specified S-VOL is wrong. B9A7 All commands You cannot obtain the consistency group information because HTI is not installed. A-12 CCI command reference

105 B Thin Image GUI reference This appendix describes HTI windows and dialog boxes. 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 Delete Pairs window Edit Local Replica Option wizard Thin Image GUI reference B-1

106 Replications window The following image shows this window. Summary tab Item Licensed Capacity Number of Replica LDEVs Number of FCv2/FCSE Relationships Number of Differential Tables View Histories button Description Used and licensed capacity of each product Number of LDEVs used for SI, SIz, HTI, SS, FCv2, and Compatible Software for IBM FlashCopy SE Number of FCv2 and Compatible Software for IBM FlashCopy SE relationships in use Number of differential tables in use. The number of differential tables is not increased or decreased by HTI pair tasks because differential tables are not used for HTI pairs. Click to open the View History window. B-2 Thin Image GUI reference

107 Replica LDEVs tab Only pairs that consist of the P-VOL and S-VOLs (the source and target volumes for FCv2 or FCSE) allocated to each user are shown. Item Description LDEV ID LDEV Name Emulation Type Capacity Copy Type Export button Selected LDEV's identifier Selected LDEV's name Selected LDEV's emulation type Selected LDEV's capacity The copy type and volume. Values: SI-L1: SI first cascade layer (L1) pair SI-L2: SI second cascade layer (L2) pair TI: HTI pair SS: SS pair SIMF SIz pair FCv2: Compatible FlashCopy relationship FCSE: Compatible Software for IBM FlashCopy SE relationship Status of SI, HTI, SS, and SIMF volumes: Primary: P-VOL Secondary: S-VOL Status of FCv2 and FCSE volumes: S means a source volume. T means a target volume. S-Normal: Source volume in the normal status T-Normal: Target volume in the normal status ST-Normal: Normal volume which is set for the source volume and the target volume S-Failed, S-Full, S-Full & Failed: Source volume in the abnormal status T-Failed, T-Full, T-Full & Failed: Target volume in the abnormal status ST-Failed, ST-full, ST-full & Failed: Abnormal volume which is set for the source volume and the target volume Click to open a dialog for downloading table information to a file. Local Replications window The following image shows this window. Thin Image GUI reference B-3

108 Summary tab Item Number of Pairs Number of Reserve Volumes Number of Consistency Groups Snapshot Estimated Manageable Capacity* Description The number of pairs for each local replication software application type. The number of reserved volumes: Open: The number of open system reserved volumes. Mainframe: The number of mainframe system reserved volumes. Total: The total amount of reserved volumes. Total including Secondary Volumes: This value includes the number of reserve volumes and number of S-VOLs for SI, SIz, HTI and SS. The number of consistency groups in use. The number of estimated manageable capacity for HTI pair. When this item is less than TB, icon is shown. B-4 Thin Image GUI reference

109 Item Number of Pair Tables Number of Differential Tables Edit Local Replica Options button Edit SCP Time button Description This value is the estimated HTI pair capacity that you can create using the remaining SM capacity. Use the following formula to calculate the remaining SM: The remaining SM = the whole SM capacity - (the SM area used by HTI pools + HTI pairs) This value is a rough estimation, and the value does not guarantee that HTI pairs of the indicated capacity are created successfully. If you add or delete an HTI pool volume or an HTI pair, this value changes. The number of pair tables for the following combinations of software applications: SI/SIMF/Volume Migration: Number of SI, SIz, and Volume Migration pair tables in use. HTI/SS: Number of HTI and SS pair tables in use. The number of differential tables in use. The number of differential tables is not increased or decreased by HTI pair tasks because differential tables are not used for HTI pairs. Click to open the Edit Local Replica Options window. Click to open the Edit SCP Time window. Pairs tab This tab only shows pairs that have P-VOL and/or S-VOLs to which you are allocated. Item Primary Volume Copy Type P-VOL information. Values: Description LDEV ID: The P-VOL's LDEV identifier. Click to open the LDEV Properties window. 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 identifier of the P-VOL LDEV's LUN path. Capacity: The P-VOL's capacity. CLPR: The P-VOL's CLPR number. The copy type. Values: SI-L1: SI L1 pair SI-L2: SI L2 pair TI: HTI pair Thin Image GUI reference B-5

110 Item SS: SS pair SIMF SIz pair Description Snapshot Group Status The snapshot group name. If you do not configure a snapshot group for an HTI pair, this item is blank. The following icons and pair status names. ( SIMPLEX and SMPL statuses do not shown in SN.) The SI pair or HTI pair is being deleted. Status names are: (SI or HTI) SMPL(PD) (SIz) Deleting/TRANS This icon is used for the following: The pair is being copied. Status names are: (SI) COPY(PD)/COPY (SIz) PENDING (HTI) COPY (SS) COPY The pair is being resynchronized. Status names are: (SI) COPY(RS)/COPY (SIz) Resync/PENDING (HTI) RCPY (SS) RCPY The pair is being resynchronized from secondary to P-VOL. Status names are: (SI) COPY(RS-R)/RCPY (SIz) Resync-R/REVRSY (HTI) RCPY (SS) RCPY The pair is being split in normal mode. Status names are: (SI) COPY(SP)/COPY (SIz) SP-Pend/TRANS This icon is used for the following: The volumes are paired. Status names are: (SI) PAIR (SIz) DUPLEX The pool has exceeded the threshold. Status name is: (HTI) PFUL (SS) PFUL B-6 Thin Image GUI reference

111 Item Status, continued Description This icon is used for the following: The pair is split. Status names are: (SI) PSUS (SIz) Split/SUSPOP The pair is being split in high-speed mode. Status names are: (SI) PSUS(SP)/PSUS (SIz) V-Split/SUSPVS The data pool threshold is exceeded in PSUS status. Status name is: (HTI) PFUS (SS) PFUS The pair is suspended. Status names are: (SI) PSUE (SIz) Suspend/SUSPER For more information about HTI pair status, see Pair status definitions on page 5-2. For more information about pair status definitions for other software applications, see the appropriate user guide. Secondary Volume Snapshot Date Pool Name (ID) Copy Pace CTG ID Mirror Unit Topology ID Create Pairs Split Pairs S-VOL information. Values: LDEV ID: The S-VOL's LDEV identifier. Click to open the LDEV property window. LDEV Name: The S-VOL's LDEV name. Port ID: The S-VOL LDEV's LUN path port name. Host Group Name: The S-VOL s host group name. LUN ID: The S-VOL s LUN ID LDEV's LUN path. Capacity: The S-VOL's capacity. CLPR: The S-VOL's CLPR number The date and time the snapshot was acquired. The pool name and identification number. The copy speed. A hyphen (-) is shown for HTI and SS pairs. The consistency group identification number. The mirror unit number. LDEV's topology identifier. Click to open the Create Pairs window. Click to open the Split Pairs window of the Split Pairs wizard. Thin Image GUI reference B-7

112 Resync Pairs Item View Pair Synchronous Rate* View Pair Properties* Suspend Pairs* Delete Pairs* Export* Description Click to open the Resync Pairs window of the Resync Pairs wizard. Click to open the View Pair Synchronous Rate window. Click to open the View Pair Properties window. Click to open the Suspend Pairs window. Click to open the Delete Pairs window. Click to open a dialog for downloading table information to a file. *Available when you click More Actions. Reserve Volumes tab The reserved volume for SI and SIz. Only LDEVs that are allocated to each user are shown. Item Description LDEV ID LDEV Name Emulation Type Capacity Number of Paths Add Reserve Volumes Remove Reserve Volumes Reserved volume LDEV's identifier. Click to open the LDEV property window Reserved volume LDEV's name Reserved volume's emulation type Reserved volume's capacity Displays number of paths to reserved volume Displays Add Reserve Volumes window Displays Remove Reserve Volumes window B-8 Thin Image GUI reference

113 Item Description Export Click to open a dialog for downloading table information to a file. Consistency Groups tab Item Description CTG ID Status Number of Pairs Reserve Mainframe CTGs The consistency group identification number. Click to open the Consistency Group Properties window. The status of consistency group. SI Used: Consistency group used by SI. SI Used (RAID Manager)MF Consistency group used for SIz pairs and managed with CCI. SI Used (PPRC/BCM)MF Consistency group used for SIz pairs and managed with PPRC or Business Continuity Manager. TI Used: Consistency group used for HTI pairs. SS Used: Consistency group used for SS pairs. Mainframe Reserved: Consistency group reserved for use with PPRC or Business Continuity Manager. Free: Consistency group not being used and is not reserved. (Changing...): Status is in the process of changing. Number of pairs for the consistency group in use. Click to open the Reserved Mainframe CTGs window. Thin Image GUI reference B-9

114 Item Release Reserved Mainframe CTGs Export Description Click to open the Release Reserved Mainframe CTGs window. Click to open a dialog for downloading table information to a file. View Pair Properties window Pair Properties tab Item Description Copy Type The copy type. Values: ShadowImage: SI pair Thin Image: HTI pair COW Snapshot: SS pair SIz: SIz pair B-10 Thin Image GUI reference

115 Item Pool Name (ID) Description The pool name and identification number. Most Recent Snapshot Date The date and time the latest snapshot data was acquired. LDEV ID LDEV Name The P-VOL and S-VOL LDEV identification numbers. The P-VOL and S-VOL LDEV names. Pairs table All pairs, which are related to a pair shown on the Pair Property table, are shown. Item Primary Volume Snapshot Group Status Secondary Volume Snapshot Date CTG ID COPY Pace P-VOL information. Values: Description 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. The snapshot group name. If you do not configure a snapshot group for an HTI pair, this item is blank. The pair status. For more information, see Pair status definitions on page 5-2. S-VOL 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. Mode: Indicates whether the S-VOL has been written to. (For HTI and SS) W is shown if the S-VOL was written to when its pair status is PSUS(SP)/PSUS or PSUS. A hyphen (-) indicates that the S-VOL has not been written to. The date and time the snapshot was acquired. The consistency group identification number. The copy speed. Thin Image GUI reference B-11

116 Mirror Unit Item Description A hyphen (-) is shown for HTI and SS pairs. The mirror unit number. View Pair Synchronous Rate window Pairs table Item Primary Volume Copy Type Snapshot Group Description P-VOL information. Values: LDEV ID: The P-VOL's LDEV identifier. LDEV Name: The P-VOL's LDEV name. CLPR: The P-VOL's CLPR number. The copy type. Values: SI-L1: SI L1 pair SI-L2: SI L2 pair TI: HTI pair SS: SS pair SIMF SIz pair The snapshot group name. B-12 Thin Image GUI reference

117 Item Description If you do not configure a snapshot group for an HTI pair, this item is blank. Status Synchronous Rate (%) Secondary Volume Copy Pace Mirror Unit Refresh Pair status. For more information, see Pair status definitions on page 5-2. The synchronous rate that the S-VOL matches the S-VOL s next new generation. If the S-VOL is the latest one, the synchronous rate is computed by comparing the S-VOL with the P-VOL. S-VOL information. Values LDEV ID: The S-VOL's LDEV identifier. LDEV Name: The S-VOL's LDEV name. CLPR: The S-VOL's CLPR number. The copy speed. A hyphen (-) is shown for HTI pairs or SS pairs. The mirror unit number. Click to update the information in the Pairs table. View Histories window Setting fields Item Description Copy Type The copy type. Values: Thin Image GUI reference B-13

118 Item SI: SI TI: HTI SS: SS SIMF SIz Description FCv2/FCSE: Compatible FlashCopy and Compatible Software for IBM FlashCopy SE Histories table Only the task on the pairs that consist of the P-VOL and/or S-VOLs (the source and/or target volumes for FCv2/FCSE) allocated to each user are shown. Item Description Date Primary Volume (Source Volume for FCv2/FCSE) Secondary Volume (Target Volume for FCv2/FCSE) Mirror Unit Pool ID The task date and time. The information about the P-VOL (the source volume for / FCSE). Values: LDEV ID: The P-VOL/source volume's LDEV identifier. Provisioning Type: The P-VOL s type (source volume). Values: Basic: Internal volume DP: DP-VOL External: External volume External MF: Migration volume The information about the S-VOL (the target volume for FCv2/FCSE) is shown. Values: LDEV ID: The S-VOL/target volume's LDEV identifier. Provisioning Type: The S-VOL's type (target volume for FCv2/FCSE). If you specify TI or SS as the copy type, this value is not shown. Otherwise, LDEV ID is shown as the S- VOL. Values: Basic: Internal volume DP: DP-VOL External: External volume The mirror unit number. This item is shown only if you select TI or SS as the copy type. The pool identifier. B-14 Thin Image GUI reference

119 Item Relationship ID Description Code Description Export Description This item is shown only if you select TI or SS as the copy type. The relationship identifier. This item is shown only when you select FCv2/FCSE as the copy type. The code for the type of task performed. The description of the task. For more information about HTI tasks, see Monitoring pair operation history on page 5-5. For more information about monitoring pair task history for other software applications, see the appropriate user guide. Click to open a dialog for downloading table information to a file. Consistency Group Properties window Consistency Group Properties table Item Description CTG ID Status The consistency group identification number. The consistency group status. Thin Image GUI reference B-15

120 Item Number of Pairs Values: Description SI Used: The consistency group is in use by SI. SIMF Used (RAID Manager): SIz uses the consistency group and CCI manages the consistency group. SIMF Used (PPRC/BCM): SIz uses the consistency group and PPRC and Business Continuity Manager manages the consistency group. TI Used: HTI uses the consistency group. SS Used: SS uses the consistency group. Mainframe Reserved: PPRC and Business Continuity Manager uses the consistency group. Free: The consistency group is not being used and is not reserved. (Changing...): Status is in the process of changing. The number of pairs assigned to the consistency group. Pairs table This table shows pairs with P-VOL and/or S-VOLs allocated to you. Item Primary Volume Copy Type Snapshot Group Status Secondary Volume P-VOL information. Values: Description 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. The copy type. Values: SI-L1: SI L1 pair SI-L2: SI L2 pair TI: HTI pair SS: SS pair SIMF: SIz pair Snapshot group name. If you do not configure a snapshot group for an HTI pair, this item is blank. Pair status. For more information, see Pair status definitions on page 5-2. S-VOL information. Values: B-16 Thin Image GUI reference

121 Item Snapshot Date Pool Name (ID) Copy Pace Mirror Unit Detail button Description 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. The date and time the snapshot was acquired. The pool name and identification number. The copy speed. A hyphen (-) is shown for HTI and SS pairs. The mirror unit number. Click to open the Pair Properties window. Create Pairs wizard Use this wizard to create pairs. See Creating Thin Image pairs on page 4-2 for information. Select Pair Configuration window Item Description Copy Type Emulation Type The copy type. Values: Copy-on-Write Snapshot ShadowImage for Mainframe HTI COW Snapshot Emulation type. Values: OPEN-V For HTI or SS, you can only specify OPEN-V. Thin Image GUI reference B-17

122 Item Number of Secondary Volumes Description Specify the total number of S-VOLs assigned to one P-VOL. Includes volumes for pairs being created, volumes in existing pairs, and volumes in L2 pairs (SI only). Select Primary Volumes window Item Use Primary Volumes of Snapshot Pairs Port ID Host Group Name Select Pool button Add button Remove button Description Specifies whether you will use the P-VOL of snapshot pair. Values: Yes: The storage system shows only P-VOLs of the pair that is already created in the Available LDEVs table. No: The storage system shows only the LDEV of the pair that is not created yet in the Available LDEVs table. Port name of the LDEV's LUN path. Host group name of the LDEV's LUN path. Any is shown by default. Selected pool name and identifier. Click to open the Select Pool window. If you selected Yes for Use P-VOLs of Snapshot Pairs, this button is unavailable. Click to add the selected LDEVs from the Available LDEVs table to the Selected LDEVs table. Click to move the selected LDEVs from the Selected LDEVs table back to the Available LDEVs table. B-18 Thin Image GUI reference

123 Available LDEVs table Item Description LDEV ID The identifier of the LDEV which can be specified as the P- VOL. LDEV Name Port ID Host Group Name LUN ID Provisioning Type Emulation Type Capacity CLPR Number of Secondary Volumes Primary Volumes Mirror Unit Pool Name (ID) LDEV's name Port name of the LDEV's LUN path. Host group name of the LDEV's LUN path. LUN ID of the LDEV's LUN path. LDEV provisioning type. Values: Basic: Internal volume DP: HDP volume External: External volume Emulation type of the LDEV Capacity of the LDEV CLPR number of the LDEV The number of S-VOLs. The number for an L1 pair does not include the number of L2 S-VOLs (SI only). If you use the LDEV as an S-VOL for an existing pair, shows information about the P-VOL: 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. The mirror unit number. If the LDEV is not used as a S-VOL for an existing pair, a hyphen (-) is shown. HTI or SS only. The pool name and ID. Selected LDEVs table Item Description LDEV ID LDEV Name The selected P-VOL's LDEV identifier. The selected P-VOL's LDEV name. Thin Image GUI reference B-19

124 Item Description Port ID Host Group Name LUN ID Provisioning Type Emulation Type Capacity CLPR Number of Secondary Volumes The port name of the LDEV's LUN path. The host group name of the LDEV's LUN path. The LUN ID of the LDEV's LUN path. The LDEV provisioning type. Values: Basic: Internal volume DP: HDP volume External: External volume The emulation type of LDEV. The capacity of LDEV. The CLPR number. The total number of S-VOLs assigned to the P-VOL. Primary Volume Information about the P-VOL is shown if the LDEV is the S- VOL of the existing pair. 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: Host group name of the P-VOL LDEV's LUN path LUN ID: 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 Pool Name (ID) The mirror unit number. If the LDEV is not used as a S-VOL for an existing pair, a hyphen (-) is shown. The pool name and identifier. B-20 Thin Image GUI reference

125 Select Pool window Available Pools table Item Pool Name (ID) RAID Level Description The nickname and ID of the pool. The RAID level of the pool. Capacity Total: The total pool capacity. Used: The amount of pool capacity that is used. Used (%): The percentage of pool capacity that is used. Note: The number truncated to an integer is shown. Drive Type/RPM User-Defined Threshold (%) CLPR Detail button The hard disk drive type and RPM. The threshold you configure. The ID and name of the CLPR in the CLPR-name format (ID:CLPR). Click to open the Pool Properties window. Thin Image GUI reference B-21

126 Select Secondary Volumes window Capacity list Item The remaining number you have to select Port ID list Host Group Name list Snapshot Group Set button Clear button Description Select to filter the available LDEVs according to the capacity you select. This item refers to the selected P-VOLs in the Selected Pairs table with no assigned S-VOL. Filters LDEVs in the Available LDEVs table by the Port ID. Filters LDEVs in the Available LDEVs table by the Host Group Name. Any is selected by default. Select whether to create a new snapshot group or use the defined snapshot group. Values: Create New Snapshot Group: Type the new snapshot group name. Use Existing Snapshot Group: Select the desired snapshot group. This item is shown only when you select TI as the copy type. Click to move the selected LDEV to the Selected Pairs table. Click to return the selected S-VOL from the Selected Pairs table back to the Available LDEVs table. B-22 Thin Image GUI reference

127 Available LDEVs table Item Description LDEV ID LDEV Name Port ID Host Group Name LUN ID Emulation Type Capacity Provisioning Type CLPR Detail button Identifier of LDEV, which you can specify as the S-VOL. The LDEV's name. The port name of the LDEV's LUN path. The host group name of the LDEV's LUN path. LUN ID of the LDEV's LUN path. The LDEV's emulation type. The LDEV's capacity. Provisioning type of the LDEV. Values: Basic: Internal volume DP: DP-VOL External: External volume Snapshot: HTI or SS volume LDEV's CLPR number Click to open the LDEV Properties window, which contains additional information for the selected LDEV. Selected Pairs table Item Primary Volume Snapshot Group New Snapshot Group P-VOL information. Values: Description LDEV ID: The P-VOL's LDEV identifier. LDEV Name: The P-VOL's LDEV name. A hyphen (-) is shown for unallocated LDEV. Port ID: The port name of the P-VOL LDEV's LUN path. Host Group Name: Host group name of the P-VOL LDEV's LUN path LUN ID: LUN ID of the P-VOL LDEV's LUN path Emulation Type: The P-VOL's emulation type. Capacity: The P-VOL's volume capacity. Snapshot group name. For HTI, this item is blank. Indicates whether the Snapshot group is newly created or not. Yes: Newly created Snapshot group No: Already defined Snapshot group For HTI or SS, this item is blank. Thin Image GUI reference B-23

128 Item Secondary Volume Copy Type Pool Name (ID) Remove button S-VOL information. Values: Description LDEV ID: The S-VOL's LDEV identifier. If an LDEV is not allocated, this field is blank. LDEV Name: The S-VOL's LDEV name. If an LDEV is not allocated, a hyphen (-) is shown. Port ID: The S-VOL LDEV's LUN path port name. Host Group Name: The S-VOL LDEV's LUN path host group name. LUN ID: The S-VOL LDEV's LUN path LUN ID. Emulation Type: The S-VOL's emulation type. Capacity: The S-VOL's volume capacity. The copy type. Values: SI-L1: SI L1 pair SI-L2: SI L2 pair TI: HTI pair SS: SS pair SIMF: SIz pair The pool name and ID number. Click to remove a selected pair from the table. Confirm window B-24 Thin Image GUI reference

129 Selected Pairs table Item Primary Volume Copy Type Snapshot Group New Snapshot Group Secondary Volume Pool Name (ID) P-VOL information. Values: Description 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: Host group name of the P-VOL LDEV's LUN path. LUN ID: LUN ID of the P-VOL LDEV's LUN path. Emulation Type: The P-VOL's emulation type. Capacity: The P-VOL's volume capacity. CLPR: The P-VOL's CLPR number. The copy type. Values: SI-L1: SI L1 pair SI-L2: SI L2 pair TI: HTI pair SS: SS pair SIMF: SIz pair The snapshot group name. Indicates whether the snapshot group is newly created. Values: Yes: The snapshot group is new. No: The snapshot group has already been defined. S-VOL information. Values: LDEV ID: The S-VOL's LDEV identifier. LDEV Name: The S-VOL's LDEV name. Port ID: The S-VOL LDEV's LUN path port name. Host Group Name: The S-VOL LDEV's LUN path host group name. LUN ID: The S-VOL LDEV's LUN path LUN ID. Emulation Type: The S-VOL's emulation type. Capacity: The S-VOL's volume capacity. CLPR: The S-VOL's CLPR number. The pool name and ID number. Split Pairs wizard Use this wizard to split pairs. Thin Image GUI reference B-25

130 Split Pairs window This wizard includes the following windows: Split Pairs window Confirm window Selected Pairs table Item Primary Volume Copy Type Description P-VOL information. Values: 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. The copy type. Values: SI-L1: SI L1 pair SI-L2: SI L2 pair TI: HTI pair B-26 Thin Image GUI reference

131 Item SS: SS pair SIMF: SIz pair Description Snapshot Group Status Secondary Volume Pool Name (ID) Mirror Unit Split Type list Copy Pace list Snapshot group name. If you do not configure a snapshot group for the HTI pair, this item is blank. Pair status. For more information, see Pair status definitions on page 5-2. S-VOL 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. The pool name and ID number. The mirror unit number. The split type. Values: Quick Split: Splits the pair immediately. Specify this function when you want to split a pair then immediately write to or read from the S-VOL. After the pair is split, the remaining differential data is copied to the S-VOL in the background. Steady Split: Copies the differential data then splits the pair. If you have specified TI or Snapshot as the copy type, this is the only available option. Default: Steady Split The speed at which the pair is split. Values: Faster Medium Slower For HTI or SS, this list is not available. Thin Image GUI reference B-27

132 Confirm window Selected Pairs table Item Primary Volume Copy Type Snapshot Group P-VOL information. Values: Description 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. The copy type. Values: SI-L1: SI L1 pair SI-L2: SI L2 pair TI: HTI pair SS: SS pair SIMF: SIz pair Snapshot group name. If you do not configure a snapshot group for an HTI pair, this item is blank. B-28 Thin Image GUI reference

133 Item Description Status Split Type Copy Pace Secondary Volume Pool Name (ID) Mirror Unit Pair status. For more information, see Pair status definitions on page 5-2. The split type. Values: Quick Split: Immediately splits the pair. Steady Split: The differential data is copied and then the pair is split. The copy speed. A hyphen (-) is shown for HTI pairs or SS pairs. S-VOL information. Values: 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 The pool name and ID number. The mirror unit number. Resync Pairs wizard Use this wizard to resynchronize pairs. This wizard includes the following windows: Resync Pairs window Confirm window Thin Image GUI reference B-29

134 Resync pairs window Selected Pairs table Item Primary Volume Copy Type Snapshot Group Description P-VOL information. Values: 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. The copy type. Values: SI-L1: SI L1 pair SI-L2: SI L2 pair TI: HTI pair SS: SS pair SIMF: SIz pair The snapshot group name. B-30 Thin Image GUI reference

135 Item Description If you do not configure a snapshot group for the HTI pair, this item is blank. Status Secondary Volume Snapshot Date Pool Name (ID) Mirror Unit Resync Type Copy Pace The pair status. For more information, see Pair status definitions on page 5-2. S-VOL 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. The date and time the snapshot was acquired. The pool name and identification number. The mirror unit number. The type of resynchronization. Values: Normal Copy (Primary > Secondary): All differential data is updated on the S-VOL. Reverse Copy (Secondary > Primary): All differential data is updated on the P-VOL. You cannot use this option for the following pairs: SI L2 pair SIz pair, which shares the P-VOL with FCv2/FCSE pair Quick Resync (Primary > Secondary): (SI or SIz pairs only.) Changes the pair status to PAIR immediately. The differential data is copied during the updating copy. Quick Restore (Secondary > Primary): (SI or SIz pairs only.) Replaces the P-VOL and the S-VOL. The differential data between the volumes is copied during the update copying. You cannot use this option for the following pairs: SI L2 pair. A pair containing DP-VOL as either one of the P- VOL or the S-VOL. SI pair containing HTI pair as the P-VOL and/or the S-VOL. SIz pair, which shares the P-VOL with FCv2/FCSE pair. For more information, see Hitachi ShadowImage User Guide. The speed at which to task is performed. Faster Thin Image GUI reference B-31

136 Item Description Medium Slower A hyphen (-) is shown for HTI pairs or SS pairs. Confirm window Selected Pairs table Item Primary Volume Copy Type Description P-VOL information. Values: 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. The copy type. Values: SI-L1: SI L1 pair B-32 Thin Image GUI reference

137 Item SI-L2: SI L2 pair TI: HTI pair SS: SS pair SIMF: SIz pair Description Snapshot Group Status Resync Type Copy Pace Secondary Volume Snapshot Date Pool Name (ID) Mirror Unit Snapshot group name. If you do not configure a snapshot group for an HTI pair, this item is blank. Pair status. For more information, see Pair status definitions on page 5-2. The type of resynchronization is specified: Normal Copy (Primary > Secondary): All differential data is updated on the S-VOL. Reverse Copy (Secondary > Primary): All differential data is updated on the P-VOL. Quick Resync (Primary > Secondary): Immediately changes the pair status to PAIR. The differential data is copied during the updating copy. Quick Restore (Secondary > Primary): Replaces the P-VOL and the S-VOL. The differential data between the volumes is copied during the update copying. The speed at which the task is performed. A hyphen (-) is shown for HTI pairs or SS pairs. S-VOL 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. The date and time the snapshot was acquired. The pool name and identification number. The mirror unit number. Delete Pairs window Use this window to delete pairs. For full information, see Deleting HTI pairs on page Thin Image GUI reference B-33

138 Selected Pairs table Item Primary Volume Copy Type Snapshot Group Status Secondary Volume P-VOL information. Values: Description 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. The copy type. Values: SI-L1: SI L1 pair SI-L2: SI L2 pair TI: HTI pair SS: SS pair SIMF: SIz pair The snapshot group name. If you do not configure a snapshot group for an HTI pair, this item is blank. The pair status. For more information, see Pair status definitions on page 5-2. S-VOL information. Values: B-34 Thin Image GUI reference

139 Item Snapshot Date Pool Name (ID) Mirror Unit Description 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. The date and time the snapshot was acquired. The pool name and identification number. The mirror unit number. Edit Local Replica Option wizard Edit Local Replica Option window Use this window to specify options that affect performance. For more information about systems options that affect performance, see Hitachi ShadowImage User Guide. SI/TI/SS System Options table Item System Option Description The system options that you can change. Values: Thin Image GUI reference B-35

140 Item Description Swap & Freeze: Quick Restores and then immediately saves the data. Note: Enabling this option with Quick Restore inhibits the update copy operation and the paired S-VOL is not updated. Host I/O Performance: Gives weight to I/O response rather than the copy time. This option controls the copy operation and improves the host I/O response. Copy Pace Ext. Slower1 Copy Pace Ext. Slower2 Copy Pace Ext. None Reducing the copy volume in PAIR status curbs the influence to the I/O performance of the host server. This item is available to all pairs in PAIR status. The order of Copy Pace Ext. Slower1, Copy Pace Ext. Slower2, and Copy Pace Ext. None determines the host server s I/O performance. Status Enable button Disable button Shows whether the option is currently enabled or disabled. Click to enable the selected option. Click to disable the selected option. System Type: Mainframe Select when you want to change the system option of SIz, Compatible FlashCopy V2, and Compatible Software for IBM FlashCopy SE. SIMF/FCv2/FCSE System Options table Item System Option Options that you can change. Values: Description Swap & Freeze: Quick Restores and then immediately saves the data. Note: Enabling this option with Quick Restore inhibits the update copy operation and the paired S-VOL (T- VOL for FCv2 or FCSE) is not updated. Host I/O Performance: Gives weight to I/O response rather than the copy time. This option controls the copy operation and improves the host I/O response. FC Slower Copy1 (FCv2 or FCSE only): Reduces the multiplicity of background copy into half. FC Slower Copy 2 (FCv2 or FCSE only): Reduces the multiplicity of background copy into quarter. FC Ext. Slower Copy1: Inhibits background copy and improves host I/O response when the operating ratio of the MP blade (FCv2 or FCSE S-VOL or T-VOL is allocated) exceeds 65%. B-36 Thin Image GUI reference

141 Item Description FC Ext. Slower Copy2: inhibits background copy and improves host I/O response when the operating ratio of the MP blade (FCv2 or FCSE S-VOL or T-VOL is allocated) exceeds 50%. Copy Pace Ext. Slower1 Copy Pace Ext. Slower2 Copy Pace Ext. None Reducing the copy volume in DUPLEX status curbs the influence to the I/O performance of the host server. This item is available to all pairs in DUPLEX status. The I/O performance of the host server is improved in order of Copy Pace Ext. Slower1, Copy Pace Ext. Slower2,and Copy Pace Ext. None. Status Enable button Disable button Shows whether the option is currently enabled or disabled. Click to enable the selected option. Click to disable the selected option. Confirm window SI/HTI/SS System Options table Item System Option Status Description The system options that you can change. Shows whether the option is currently enabled or disabled. Thin Image GUI reference B-37