Hitachi Virtual Storage Platform

Transcription

1 Hitachi Virtual Storage Platform Hitachi Copy-on-Write Snapshot User Guide Document Organization Product Version Getting Help Contents MK-90RD December 2016

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... ix Intended audience... x Product version...x Document revision level...x Referenced documents... xi Changes in this revision... xi Document organization...xi Document conventions...xii Convention for storage capacity values...xiii Accessing product documentation...xiv Getting help... xiv Comments... xiv 1 Overview of Copy-on-Write Snapshot Copy-on-Write Snapshot software How Copy-on-Write Snapshot works Volume pairs: P-VOLs and V-VOLs Data pools Components Licenses and capacity Consistency groups Interfaces for performing Copy-on-Write Snapshot operations The Storage Navigator Command Control Interface Pair status Copy-on-Write Snapshot planning and design Consistency group system requirements Data pool requirements and restrictions Planning pair volumes Planning V-VOLs and data pools Sizing the data pool workflow Calculating the number of Copy-on-Write Snapshot pairs Calculating SS pairs when creating external volumes or V-VOLs Calculating maximum SS pairs based on differential tables workflow iii

4 Calculating maximum SS pairs based on shared memory workflow Calculate the capacity of the pool management block Capacity of pool association information Calculating maximum pairs based on pair tables Determining maximum pairs allowed on your system Planning for splitting pairs in consistency groups Requirements and restrictions for the At-Time Split operation Pair inclusion in At-Time Split operations workflow Consistency maintenance workflow when sharing SS P-VOLs with UR or TC volumes Snapshot secondary volume consistency maintenance External volumes External-volume failures Copy-on-Write Snapshot installation and configuration Installing and removing Copy-on-Write Snapshot Configuration workflow Creating data pools Creating V-VOLs Setting up the Command Control Interface command device Sharing Copy-on-Write Snapshot volumes Interoperability with other software applications and functions Data Retention Utility and access attributes Dynamic Provisioning Resource Partition Manager ShadowImage Restrictions when sharing P-VOLs TrueCopy and Universal Replicator TC and UR volume backup in 3DC multi-target configuration Volume Migration Thin Image Pair operations Pair operations Checking the pair status Pair creation workflow Pair creation Configuring pairs Removing and moving volumes Creating pairs Pair split Splitting pairs Splitting pairs in consistency groups at a pre-determined time Pair resynchronization and restoration Resynchronizing and restoring pairs Pair deletion Deleting pairs iv

5 6 Copy-on-Write Snapshot monitoring and maintenance Monitoring the storage system Monitoring pair information, license capacity, status Pair status definitions Monitoring pair properties Monitoring synchronous rates Monitoring consistency groups Monitoring pair operations history Monitoring pool information Maintaining the storage system Managing data pools Increasing data pool volume capacity Changing pool volume threshold Changing pool volume names Recovering pool volumes Deleting pool volumes Managing virtual volumes Changing virtual volume names Deleting virtual volumes Switching off the storage system power and replacing the microcode Switching off the power supply Replacing the microcode offline Copy-on-Write Snapshot troubleshooting General troubleshooting Recovering from failure during pairresync -restore operation Recovering a terminated HP-UX host server Recovering a blocked pool workflow Pool-related SIM entry removal workflow Completing Service Information Messages Troubleshooting with Command Control Interface Identifying errors using the log on the CCI window Identifying errors using the Command Control Interface operation log file A Command Control Interface command reference... A-1 Command Control Interface commands for Storage Navigator operations... A-2 Storage Navigator and Command Control Interface pair status names... A-2 Statuses required for Command Control Interface pair operations... A-3 B Copy-on-Write Snapshot GUI reference...b-1 Pools window... B-2 Selected pool volume window...b-6 Create Pools wizard...b-15 Create Pools window...b-15 Confirm window... B-20 Expand Pool wizard...b-21 Expand Pool window...b-21 Confirm window... B-23 Edit Pools wizard...b-24 Edit Pools window...b-24 v

6 Confirm window... B-26 Delete Pools wizard...b-28 Delete Pools window...b-28 Confirm window... B-30 Restore Pools window... B-31 Complete SIMs window... B-32 Select Pool window... B-34 Select Pool Volumes window...b-35 Pool Property window...b-39 Create Pairs wizard... B-40 Select Pair Configuration window... B-41 Select Primary Volumes window...b-42 Select Pool window...b-45 Select Secondary Volumes window...b-46 Edit Mirror Units window... B-48 Confirm window... B-49 C Pair operations (secondary window)... C-1 Pair operations workflow... C-2 Checking pair status...c-2 Creating a pair... C-2 Creating pairs in a consistency group...c-3 Splitting pairs... C-4 Resynchronizing pairs... C-4 Restoring pairs... C-5 Deleting pairs...c-5 Deleting a single pair... C-5 Deleting multiple pairs related to a port or host group...c-5 Deleting multiple pairs related to a pool... C-6 D Copy-on-Write Snapshot monitoring and maintenance (secondary window)... D-1 Monitoring the system in the secondary window... D-2 Monitoring pair status...d-2 Pair status definitions...d-3 Statuses required for pair operations...d-3 Monitoring pair volume details... D-3 Monitoring S-VOL path information...d-5 Monitoring number of pairs and license information...d-6 Monitoring pair operation history...d-7 Maintaining the system... D-8 E Copy-on-Write Snapshot GUI reference (secondary window)... E-1 Pair Operation window... E-2 Volume list...e-3 Preview list... E-5 Command menu...e-6 History window...e-7 Reference codes...e-8 C.O.W. Snapshot window... E-9 vi

7 Glossary Index vii

8 viii

9 Preface This guide provides instructions for performing Copy-on-Write Snapshot (SS) tasks on Hitachi Virtual Storage Platform (VSP) storage systems. Notice: The use of the features and/or software applications described in this guide and all other Hitachi Data Systems software applications is governed by the terms of your agreements with Hitachi Data Systems. Intended audience Product version Document revision level Referenced documents Changes in this revision Document organization Document conventions Convention for storage capacity values Accessing product documentation Getting help Comments Preface ix

10 Intended audience This document is intended for system administrators, Hitachi Data Systems representatives, and authorized service providers who are involved in installing, configuring, and operating the Hitachi Virtual Storage Platform storage system. Readers of this document should meet the following requirements: Have a background in data processing and understand RAID storage systems and their basic functions. Be familiar with the Hitachi Virtual Storage Platform storage system, and have read the Hitachi Virtual Storage Platform User and Reference Guide. Be familiar with the Storage Navigator (SN) software for the Hitachi Virtual Storage Platform storage system and have read the Hitachi Storage Navigator User Guide. Product version This document revision applies to Hitachi Virtual Storage Platform microcode x or later. You must have Storage Administrator (Local Copy) role to perform Compatible FlashCopy V2 operations in the SN. Document revision level Revision Date Description MK-90RD October 2010 Initial release. MK-90RD December 2010 Supersedes and replaces MK-90RD MK-90RD April 2011 Supersedes and replaces MK-90RD MK-90RD August 2011 Supersedes and replaces MK-90RD MK-90RD November 2011 Supersedes and replaces MK-90RD MK-90RD March 2012 Supersedes and replaces MK-90RD MK-90RD June 2012 Supersedes and replaces MK-90RD MK-90RD November 2012 Supersedes and replaces MK-90RD MK-90RD January 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 Supercedes and replaces MK-90RD MK-90RD August 2015 Updated for ITPD, not published by HDS. MK-90RD December 2016 Supercedes and replaces MK-90RD x Preface

11 Referenced documents Hitachi Virtual Storage Platform documentation: Command Control Interface Installation and Configuration Guide, MK-90RD7008 Command Control Interface User and Reference Guide, MK-90RD7010 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 Storage Navigator Messages, MK-90RD7028 Hitachi Universal Volume Manager User Guide, MK-90RD7032 Hitachi Virtual Storage Platform User and Reference Guide, MK-90RD7042 Changes in this revision Added support for 6588-A emulation type functionality. Document organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the Chapter 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 Copy-on-Write Snapshot on page 1-1 Chapter 2, Copy-on-Write Snapshot planning and design on page 2-1 Chapter 3, Copy-on-Write Snapshot installation and configuration on page 3-1 Chapter 4, Sharing Copyon-Write Snapshot volumes on page 4-1 Chapter 5, Pair operations on page 5-1 Chapter 6, Copy-on-Write Snapshot monitoring and maintenance on page 6-1 Provides an overview of SS. Description Describes the storage system and operational requirements. Provides instructions for installing and configuring SS. Provides information about sharing SS volumes with other Hitachi Data Systems features and software applications. Provides instructions for pair operations. Provides instructions for monitoring and maintaining pairs. Preface xi

12 Chapter Chapter 7, Copy-on-Write Snapshot troubleshooting on page 7-1 Appendix A, Command Control Interface command reference on page A-1 Appendix B, Copy-on- Write Snapshot GUI reference on page B-1 Appendix C, Pair operations (secondary window) on page C-1 Appendix D, Copy-on- Write Snapshot monitoring and maintenance (secondary window) on page D-1 Appendix E, Copy-on- Write Snapshot GUI reference (secondary window) on page E-1 Description Provides troubleshooting information. Provides command line interface (CLI) commands for SS operations. Describes SS windows and dialog boxes in SN. Provides instructions for pair operations using the previous SN graphical user interface (GUI), which opens in a secondary window. Provides information for checking status and other information using the previous SN GUI, which opens in a secondary window. Describes SS windows and dialog boxes in the previous SN GUI, which opens in a secondary window. Document conventions This document uses the following typographic conventions: Convention Description Bold Italic screen/code Indicates text on a window or dialog box, including window and dialog box names, menus, menu options, buttons, items, 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 entered by the user. Example: # pairdisplay -g oradb < > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: # pairdisplay -g <group> Note: Italic font is also used to indicate variables. [ ] square brackets Indicates optional values. Example: [ a b ] indicates that you can choose a, b, or nothing. { } braces Indicates required or expected values. Example: { a b } indicates that you must choose either a or b. xii Preface

13 Convention Description vertical bar Indicates that you have a choice between two or more options or arguments. Examples: [ a b ] indicates that you can choose a, b, or nothing. { a b } indicates that you must choose either a or b. Underline Indicates the default value. Example: [ a b] This document uses the icons in the following table to draw attention to information: Icon Meaning Description Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Note Calls attention to important and/or additional information. Caution Warns users of adverse conditions and consequences, such as disruptive operations. WARNING Warns users of severe conditions and consequences, such as destructive operations. Convention for storage capacity values Physical storage capacity values (such as disk drive capacity) are calculated based on the following values: Physical capacity unit Value 1 KB 1,000 bytes 1 MB 1, 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: Preface xiii

14 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 Accessing product documentation Product documentation is available on Hitachi Data Systems Support Connect: Check this site for the most current documentation, including important updates that may have been made after the release of the product. Getting help Hitachi Data Systems Support Connect is the destination for technical support of products and solutions sold by Hitachi Data Systems. To contact technical support, log on to Hitachi Data Systems Support Connect for contact information: Hitachi Data Systems Community is a new global online community for HDS customers, partners, independent software vendors, employees, and prospects. It is the destination to get answers, discover insights, and make connections. Join the conversation today! Go to community.hds.com, register, and complete your profile. Comments Please send us your comments on this document: doc.comments@hds.com. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation. Thank you! xiv Preface

15 1 Overview of Copy-on-Write Snapshot With Copy-on-Write Snapshot (SS), you can create virtual copies of a data volume in the Hitachi Virtual Storage Platform storage system. This chapter provides instructions for planning and designing, configuring, operating, monitoring, and troubleshooting SS. Copy-on-Write Snapshot software How Copy-on-Write Snapshot works Components Licenses and capacity Consistency groups Interfaces for performing Copy-on-Write Snapshot operations Pair status Overview of Copy-on-Write Snapshot 1-1

16 Copy-on-Write Snapshot software SS creates a virtual, point-in-time copy, or snapshot, of a data volume. Since only changed data blocks are stored in the SS storage pool, storage capacity is substantially less than the source volume. This results in significant savings compared with full cloning methods. The most probable types of target applications for SS are: Database copies for decision support and database inquiries. Non-disruptive backups from an SS secondary volume (S-VOL). Periodic point-in-time disk copies for rapid restores in the event of a corrupted data volume. How Copy-on-Write Snapshot works You create a volume pair when you complete the following: 1. Select the volume that you want to replicate. 2. Identify another volume that will contain the copy. 3. Associate the primary volume (P-VOL) and S-VOLs. 4. Set up a data pool. 5. Create the pair. The P-VOL is updated. The virtual volume (V-VOL) points to the point-intime data in the P-VOL and data pool and mirrors it. The V-VOL contains a virtual copy of the P-VOL; it does not contain actual data. For more information about creating pairs, see Pair creation on page Split the pair. The storage system continues to update the P-VOL. The V-VOL stops mirroring the current P-VOL. Instead, the V-VOL maintains a snapshot from the time of the split. For more information about splitting pairs, see Pair split on page Write data to the P-VOL. SS maintains the point-in-time image by copying the existing data to the data pool. 8. Resume the pair. The pool data is deleted. Volume pairs: P-VOLs and V-VOLs A volume pair consists of a P-VOL, which contains the original and actual data, and at least one and up to 64 V-VOLs. The V-VOL is made up of pointers to the data in the P-VOL. The P-VOL and its V-VOLs are located in the same storage system. A V-VOL is also referred to as an S-VOL. Although you must set up V-VOLs with the same capacity as the paired P- VOL, the capacity is not actually used and remains available as free storage 1-2 Overview of Copy-on-Write Snapshot

17 capacity. This V-VOL sizing requirement is necessary for SS and the storage system logic. The V-VOL pointers to data in the data pool and P-VOL reside in cache memory. Enabling your system s cache reserves part of your system s cache for SS. Splitting the volume pair moves the original data to the data pool as the P- VOL is updated. The following figures show SS volumes and data pool interaction when you split the pair. The following figure shows how the V-VOL maintains the point-in-time data when you split the pair. The following figure shows how the V-VOL maintains the point-in-time data when you split the pair. The following image shows how the V-VOL maintains point-in-time data when you split the pair. Overview of Copy-on-Write Snapshot 1-3

18 Data pools When you replace data in the P-VOL, the data pool holds the data. After you split a pair, the V-VOL maintains pointers to point-in-time data. If updates are written to the P-VOL before you update the block, the data that is being replaced is first copied to the data pool. The V-VOL pointer to this block is updated to the new address in the data pool. All pairs sharing the same P- VOL use a data pool. Components An SS system typically consists of the following components: The SN SS and ShadowImage (SI) software Command Control Interface (CCI) A pair of volumes (P-VOL and S-VOL) A data pool A consistency group Licenses and capacity To use SS, SI must be installed on the same system. You must provide sufficient licensed capacity for both SS and SI. SS uses a V-VOL management area for managing V-VOLs and data pools. The V-VOL management area is created when additional shared memory is installed. The V-VOL management area consists of the following: Pool management block 1-4 Overview of Copy-on-Write Snapshot

19 Pool association information The following table shows the volumes and capacities for calculating the usable capacity for SS. The total applicable capacity must be less than the capacity you have licensed for SS. If you need more licensed capacity, call the Support Center. Software Volumes to be added Volume type Normal VOL or DP- VOL Applicable capacity SS P-VOL Normal VOL Volume capacity Pool volume (pool- VOL) DP-VOL Normal VOL Pool capacity used by the volume Volume capacity Related topics Calculating maximum SS pairs based on shared memory workflow on page 2-9. Consistency groups Define SS pair operations in consistency groups to perform the operations on multiple pairs at the same time. Set up consistency groups during pair creation. For more information about creating pairs, see Pair creation on page 5-3. Interfaces for performing Copy-on-Write Snapshot operations You perform setup and pair operations using a combination of the following: The SN. For more information about the SN, see The Storage Navigator on page 1-5. Command Control Interface (CCI). For more information about CCI, see Command Control Interface on page 1-6. The Storage Navigator The Storage Navigator (SN) is connected to the Hitachi Virtual Storage Platform storage system through the TCP/IP local-area network (LAN). The SN communicates and exchanges data directly with the service processor (SVP) of the connected storage system. Use the SN to do the following: Overview of Copy-on-Write Snapshot 1-5

20 Create the data pools and V-VOLs. For more information: About creating data pools, see Creating data pools on page 3-2. About creating V-VOLS, see Creating V-VOLs on page 3-4. View pair and data pool status. For more information: About viewing pair status, see Monitoring pair information, license capacity, status on page 6-2. About viewing data pool status, see Monitoring pool information on page 6-5. Command Control Interface Use CCI to perform pair operations. CCI is set up on the host server. SS commands are sent from CCI to a command device on the storage system and is volume dedicated to CCI communications. Other Hitachi Data Systems software applications cannot use this volume. Pair status The status of a pair is an indicator of its condition. You check the status to see when an operation is completed or when an operation can be done. For more information about monitoring pair information, license capacity, and status, see Monitoring pair information, license capacity, status on page Overview of Copy-on-Write Snapshot

21 2 Copy-on-Write Snapshot planning and design This chapter describes requirements for setting up and using SS and includes data pool sizing information. Consistency group system requirements Data pool requirements and restrictions Planning pair volumes Calculating the number of Copy-on-Write Snapshot pairs Planning for splitting pairs in consistency groups External volumes Copy-on-Write Snapshot planning and design 2-1

22 Consistency group system requirements The following table includes a list of consistency group system requirements. Note: Many of these requirements are augmented with restrictions. Item Requirement Software License capacity Shared memory CCI Volume type SI is required to operate SS. Install and enable the Virtual Storage Platform (VSP) storage system hardware, microcode, and software required for SI operations. Consider the capacity of the volume when purchasing licensed capacity. Capacity for SS is part of the licensed capacity for SI. Ensure that the licensed capacity for SI is more than the combined capacity needed for both software applications. The number of software applications using a volume does not increase the amount of licensed capacity that you must purchase. Required: SS/VFS1: MB (RACK model is supported up to VFS1.) SS/VFS2: 1,021 MB (VFS MB) SS/VFS3: 2,045 MB (VFS1, MB) SS/Extension 1: 4,096 MB (SS/VFS MB) VSP storage systems can handle a 7.15 TB database with seven generations. Verify that your system is installed with the appropriate SS V-VOL management area. Restriction: You cannot share the V-VOL management area memory with Dynamic Provisioning (HDP). CCI is required for you to perform SS pair operations. CCI requires that you use one volume as a command device. For more information about setting up the CCI, see the Command Control Interface Command Reference. The P-VOL, V-VOL, and volumes must be logical volumes (LDEVs). For more information about volume type, see the following: Data pool requirements and restrictions on page 2-4 External volumes on page 2-16 To maintain performance levels, use the following configurations: Do not mix normal volumes and data pool-vols in the same parity group. Ensure that the data pool-vols consist of LDEVs from multiple parity groups. 2-2 Copy-on-Write Snapshot planning and design

23 Item Emulation type Requirement Assign different processor blade identifiers to LDEVs that make up data pool-vols. For more information about assigning the processor blade identifier, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. (For P-VOL, V-VOL, and data pool-vols) OPEN-V Pair configuration V-VOL limit per P-VOL: 64 RAID level LUSE CLPR Number of P-VOLs and V- VOLs Maximum number of data pools Pool-VOL capacity Maximum number of pool- VOLs in a data pool Expansion of data pool-vol capacity Deletion of data pool Use of external volumes in pool Data drive type Operating system restrictions Supported: RAID1, RAID1+0, RAID5, and RAID6 Restriction: You cannot add a different RAID level to the data pool. Supported: P-VOL and V-VOL Not supported: pool-vol The data pool must contain pool-vols belonging to the same cache logical partition. P-VOL: 16,384 V-VOL: 16,384 For more information about calculating the number of SS pairs, see Calculating the number of Copy-on-Write Snapshot pairs on page (HDP, Dynamic Tiering (HDT), and Dynamic Provisioning for Mainframe (HDPz) pools) Creating pools for HDP, HDT, and HDPz reduces the number of usable pools for SS. 8 GB to 4 TB 1,024 Restriction: You cannot register volumes that are already registered in a pool as pool-vols to another pool. Allowed, even if snapshots are using the pool. Allowed. You must first use the pool to delete the pairs. For more information about deleting pairs, see Deleting pairs on page Allowed. For more information about external volumes, see External volumes on page SAS, SATA, and SSD (Internal and external volumes) You can use pool-vols with different drive types in the same pool. For optimum performance, use volumes with the same drive types. (For HP-UX host servers only) Copy-on-Write Snapshot planning and design 2-3

24 Item Consistency groups (CG) Requirement Restriction: Create the SS pair before running the command for recognizing the device or V-VOL on the host server. Important! Do not use a volume already recognized by the host server as a V-VOL. If you do, an error can occur and the HP-UX host server can terminate. For more information about recovering terminated HP-UX host servers, see Recovering a terminated HP-UX host server on page 7-6. The consistency group number. You define this number during the paircreate command. Note: If you do not specify a number, an unused number is assigned. Values: (80 to FF). Maximum number of SS pairs per CG: 8,192 Maximum number of CGs per storage system: 256 including SI and ShadowImage for Mainframe (SIz) CGs. Restrictions: Do not combine pairs with the same P-VOL in the same CG. Do not combine SI, SIz, and SS pairs in the same CG. For more information about consistency groups, see the Command Control Interface User and Reference Guide. For more information about creating pairs using the paircreate command, see Creating pairs in a consistency group on page C-3. Data pool requirements and restrictions To use a volume as a data pool, the volume s LDEV status must be Normal or Normal (Quick Format). You cannot use the following volumes as data pools: LUSE or Cache Residency Manager (CRM) volumes, system disks, command devices, quorum disks. Volumes in Block status or volumes in copying process. SS P-VOLs or V-VOLs. Volumes which are already being used as data pools for SS or HDP (including HDT). Volumes used by another software application pair or migration plan. Volumes with Protect or Read Only attribute, or the S-VOL Disable setting. Note: Set the access attributes using the Data Retention Utility (DRU). 2-4 Copy-on-Write Snapshot planning and design

25 For more information about setting the access attributes, see Data Retention Utility and access attributes on page 4-3. The following are rules and restrictions regarding volumes: You cannot use external and internal volume pool-vols in the same data pool. You must use the same pool for all pairs sharing the same P-VOL. For example, if you pair one P-VOL with three V-VOLs, the three pairs must use the same data pool. You cannot use volumes that are in the different resource groups in the same data pool. Planning pair volumes You must set up the pair volumes and data pools before creating the pair. For more information about planning pair volumes, see the following: Planning V-VOLs and data pools on page 2-5 Sizing the data pool workflow on page 2-6 Planning V-VOLs and data pools When you plan an SS implementation, keep the following considerations in mind: The frequency in which you will create snapshots of the P-VOL. The lifespan for each snapshot (V-VOL). The number of snapshots (V-VOLs) you will create and the V-VOL limit per P-VOL. For more information about the V-VOL limit per P-VOL, see Consistency group system requirements on page 2-2. Use copy frequency and V-VOL lifespan to determine the number of V- VOLs your system requires per P-VOL. For example: If your data must be copied every 12 hours, and business use of the V-VOL requires holding it 48 hours, set up four V-VOLs. The size of the data pool. Copy frequency, V-VOL lifespan, and the number of V-VOLs are factors in determining data pool size. The more time that elapses between snapshots, the longer a snapshot is held, and the more snapshots that exist all result in more data accumulating in the data pool. For more information about data pool sizing, see Sizing the data pool workflow on page 2-6. Copy-on-Write Snapshot planning and design 2-5

26 Sizing the data pool workflow Updating the P-VOL replaces and holds the P-VOL data in the data pool. The original data in the data pool is held to maintain the image of the P-VOL at the time of the snapshot. To determine the size of the data pool, do the following: 1. Measure write workload over time from the host software application to the P-VOL. Write workload is the megabytes-per-second that are written to the P-VOL over a specific amount of time. 2. Calculate the amount of data that would accumulate during the lifespan of your V-VOLs. 3. Multiply the amount of data that accumulates by the number of V-VOLs. The following figure shows the basic factors for data pool sizing. When you finalize the capacity for a data pool, factor in the following: A safety factor of 20 percent. Having a safety factor calculated in minimizes the chances of over-filling the data pool. To factor in a safety factor of 20 percent, multiply the base data pool size by 1.2. Annual increase in data transactions. Your business data is likely to grow. Multiply the base pool size by the percentage of expected annual growth. The unit size of 256 KB. Data is copied to a pool in units of 256 KB. This is true even when the actual write data is smaller than 256 KB. In such a case, the write consumes 256 KB of the pool-vol capacity. 2-6 Copy-on-Write Snapshot planning and design

27 Calculating the number of Copy-on-Write Snapshot pairs The available system resources for copying pairs limits the number of SS pairs that you can create in the storage system. Confirm with your service provider that additional shared memory for differential tables and the V-VOL management area are installed on your system. The maximum number of SS pairs supported on a system is the lowest value based on the following calculations: The number of differential tables. For more information about calculating based on differential tables, see Calculating maximum SS pairs based on differential tables workflow on page 2-7. The shared memory capacity for the V-VOL management area. For more information about calculating based on shared memory, see Calculating maximum SS pairs based on shared memory workflow on page 2-9. Number of pair tables. For more information about calculating based on pair tables, see Calculating maximum pairs based on pair tables on page If you are creating external volumes or Thin Image (HTI), HDP, or HDT V- VOLs in the storage system, see Calculating SS pairs when creating external volumes or V-VOLs on page 2-7. Calculating SS pairs when creating external volumes or V-VOLs If you are creating external volumes or HTI, HDP, or HDT V-VOLs in the storage system, the maximum number of SS pairs you can create is the lowest value based on the following calculations and no more than 63,232 pairs: The value of the calculations for calculating the number of SS pairs. For more information about calculating the number of SS pairs, see Calculating the number of Copy-on-Write Snapshot pairs on page 2-7. Max. num. SS pairs = Num. of external volumes + Num. of HTI, HDP, HDT, and SS V-VOLs Calculating maximum SS pairs based on differential tables workflow Differential tables keep track of the updates that take place in pairs. The number of these tables a pair requires depends on the size of the volumes. 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 is installed on your system. For more information about determining this amount, see Determining maximum pairs allowed on your system on page When you use SS, the shared memory level is COW 1 with Extension 1 and Extension 2. The following table shows the shared memory level Copy-on-Write Snapshot planning and design 2-7

28 combinations and the number of differential tables that are associated with them. Combination Base with no shared memory Extension 1 Extension 2 Differential tables required 26,176 tables 104,768 tables 209,600 tables The following software applications also use differential tables: SI SIz Compatible FlashCopy V2 Volume Migration Using differential tables, use the following workflow to find the maximum number of pairs allowed on your system: 1. The number of differential tables required for each pair. 2. The maximum number of pairs your system supports based on the number of differential tables in the storage system. To calculate the number of differential tables that are unused and available for SS pairs on the storage system, use the following calculation: (The number of differential tables used by all other software applications on the storage system) - (The total number of differential tables that are available on the storage system) 1. Calculate the number of differential tables required for one SS pair (O) using the following formula: Note: ceil indicates that you must round up the result within the parenthesis () that follows. ceil((x 256) Z) where: X = Capacity of the volume in kilobytes. Z = Number of slots that a differential table can manage (639 32). Round up to the nearest whole number. Example: (16,777,216 kb 256) (639 x 32)= , which rounds up to four. In this example, you must create four differential tables to create one SS pair. 2. Calculate the maximum number of SS pairs using the following formula: T D = M where: 2-8 Copy-on-Write Snapshot planning and design

29 T = Total number of differential tables. D = Number of differential tables required for one SS pair. M = Maximum number of SS pairs. Example: This example assumes that no other software application is using differential tables, and that the number of differential tables is 57, ,00 4 = 14,400 In this example, the maximum number of pairs allowed for SS is 14,400 pairs. Note: For an SS pair, one pair consists of a P-VOL and up to 64 V-VOLs. Generations of snapshots do not apply when you perform differential table calculations. On the example system, you can create a maximum of 6,544 SS pairs based on differential tables. Calculating maximum SS pairs based on shared memory workflow Shared memory capacity for the V-VOL management area depends on additional shared memory. You can check the pool management block and pool association shared memory capacity in the C.O.W. Snapshot window. For more information about this window, see C.O.W. Snapshot window on page E-9. The following table shows a system s shared memory capacity based on the amount of additional shared memory. This table also shows the V-VOL management area s memory capacity. Shared memory Shared memory capacity SS SS Extension 1 751,619,276 bytes 4,294,967,296 bytes You can calculate the maximum number of SS pairs that you can create based on the amount of additional shared memory in the V-VOL management area. Use the following workflow to calculate the maximum number of pairs: 1. Calculate the capacity of the pool management block, which is the total capacity of shared memory used by the pool-vol (see Calculate the capacity of the pool management block on page 2-11). 2. Calculate the capacity of pool association information, which is the total capacity of shared memory used by the P-VOL (see Capacity of pool association information on page 2-11). Note: ceil in the formulas indicates that you must round up the result within the parenthesis () that follows. Copy-on-Write Snapshot planning and design 2-9

30 floor in the formulas indicates that you must round down the result within the parenthesis () that follows. Example This example assumes the following: The V-VOL management area s shared memory has a capacity of 716 MB (751,619,276 bytes). There are four pool-vol pools, each having a capacity of 1 TB (1,073,741,824 KB). Each P-VOL has a capacity of 10 GB (10,485,760 KB). Use the following formula to calculate the maximum number of SS pairs (P- VOLs) you can create in a storage system: The capacity (bytes) of shared memory used by the pool-vol = ceil (floor (1,073,741,824 (KB)/256 (KB)) X 32/8,640) X 8,736 + ceil (ceil (floor (1,073,741,824 (KB)/256 (KB)) X 32/8,640) X 8,736 + ceil (ceil (ceil (floor (1,073,741,824 (KB)/256 (KB)) X 32/8,640) X 8,736 = 135,713, , ,736 = 135,792,384 (bytes) The capacity of the pool management block = 135,792,384 X 4 = 543,169,536 bytes The capacity (bytes) of shared memory used by the P-VOL = ceil (ceil (10,485,760 (KB)/256 (KB))/2,048) X 8,736 + ceil (ceil (ceil (10,485,760 (KB)/256 (KB))/2,048) X 8,736 = 17,472 +8,736 = 26,208 (bytes) Maximum number of SS pairs (P-VOLs) = (751,619, ,169,536) / 183,456 = 208,449,740 / 183,456 = 1,136 Using these examples, the maximum number supported based on additional shared memory in the V-VOL management area is 1,136 pairs. The following table shows the pool capacity for shared memory and the P- VOL capacity that you can create. Shared memory Pool capacity (GB) 2,048 4,096 6,144 8,192 10, , , , ,720 SS 26 (TB) 11 (TB) SS Extension (TB) 209 (TB) 194 (TB) 179 (TB) 163 (TB) 148 (TB) 133 (TB) 88 (TB) 12 (TB) The total capacity of pool-vols registered in a pool is the capacity of that pool. The capacity of the pool you want to create depends on the shared memory extension status Copy-on-Write Snapshot planning and design

31 The following graph roughly shows the relationship between the allowable pool capacity and the P-VOL capacity depending on the shared memory extension status. Calculate the capacity of the pool management block The capacity of the pool management block is the total capacity of shared memory used by the pool-vol. Use the following formula to calculate the capacity: Capacity (bytes) of shared memory used by the pool-vol = ceil (floor (pool-vol capacity (KB)/256 (KB)) X 32/8,640) X 8,736 + ceil (ceil (floor (pool-vol capacity (KB)/256 (KB)) X 32/8,640)/2,048) X 8,736 + ceil (ceil (ceil (P-VOL capacity (KB)/256 (KB)) X 32/8,640)/2,048)/1,024) X 8,736 Copy capacity and creating pools Estimate the copy capacity (the capacity of SS data to be copied to the pool) and then set the pool capacity large enough to accommodate the copy capacity. If the copy capacity varies according to time, use the maximum copy capacity in your calculation. Creating a pool when the pool capacity is insufficient can suspend the SS pairs ( PSUE status). Pool capacity and copying SS data Copying SS data to the pool consumes the pool capacity in units of 256 KB. You must allow for this amount of pool capacity even in situations where less than that amount is consumed. Capacity of pool association information The capacity of the pool association information is the total capacity of shared memory used by the P-VOL. Copy-on-Write Snapshot planning and design 2-11

32 Use the following formula to calculate the capacity: Capacity (bytes) of shared memory used by the P-VOL = ceil (ceil (P-VOL capacity (KB)/256 (KB))/2,048) X 8,736 + ceil (ceil (ceil (P-VOL capacity (KB)/256 (KB))/2,048)/1,024) X 8,736 Calculating maximum pairs based on pair tables SS and Compatible FlashCopy V2 (FCv2) pairs use pair tables. A pair table keeps track of the status for a pair. You use one pair table for each pair. To calculate the maximum number of SS pairs you can create, use the following formula: Max. num. SS pairs = The number of pair tables - The number of FCv2 pairs on the storage system A storage system contains 1,048,575 pair tables. On the example system, you can create a maximum of 1,048,575 SS pairs based on pair tables. Determining maximum pairs allowed on your system To determine the maximum number of SS pairs your system supports, use the example calculations described in the following sections: Calculating maximum SS pairs based on differential tables workflow on page 2-7. Calculating maximum SS pairs based on shared memory workflow on page 2-9. Calculating maximum pairs based on pair tables on page Planning for splitting pairs in consistency groups At-Time Split to split pairs in a consistency group at a pre-determined time. You can At-Time Split multiple pairs and multiple pairs whose P-VOLs are shared with TrueCopy (TC) or Universal Replicator (UR) S-VOLs. Use the following list to plan for splitting pairs in consistency groups: 1. Note the requirements in Requirements and restrictions for the At-Time Split operation on page Before defining consistency groups for the pairsplit operation, read the information in Pair inclusion in At-Time Split operations workflow on page To share SS P-VOLs with UR or TC S-VOLs within a storage system, read the information in Consistency maintenance workflow when sharing SS P- VOLs with UR or TC volumes on page Copy-on-Write Snapshot planning and design

33 Requirements and restrictions for the At-Time Split operation Note the following requirements and restrictions when setting up to perform an At-Time Split operation: You must include the pairs in the same consistency group. The pairs must have a status of PAIR. For more information about pair status, see Pair status definitions on page 6-3. If you want to make changes to the pair, make the change in the same consistency group according to the copy group. Registering the At-Time Split operation: You can split or delete pairs while registering the At-Time Split. If you create a pair, split a pair, or resynchronize a pair, the split time is rejected. To perform one of these operations, reset the registration of the At-Time Split. Switching off the power resets the pre-determined split time. Performs the At-Time Split operation when a read/write request with a time stamp past the specified Split time is received. Run a read/ write request to prevent delays in the Split operation. When I/O does not occur, the storage system timer performs the Split operation. If the split operation fails, the status all volumes in the consistency group remains the same as before the At-Time Split operation. If the consistency group contains a pair whose status cannot be changed, the pairsplit command can terminate abnormally (with error code EX- EWSTOT (Timeout)). The following are possible reasons: The SS P-VOL is also used as an UR S-VOL and the UR journal capacity is insufficient. The SS license is invalid. An SS pair volume is blocked. The SS pair has a status that does not allow you to perform the pairsplit operation. For more information about SS pair status, see Statuses required for Command Control Interface pair operations on page A-3. The SS pair has a status that does not allow UR to run the pairsplit command. Pair inclusion in At-Time Split operations workflow Use the following workflow to include pairs in an At-Time Split operation: 1. Review the requirements for consistency groups in Consistency group system requirements on page Place the pairs in a consistency group. Specify only one consistency group for a group defined in the CCI configuration file. Copy-on-Write Snapshot planning and design 2-13

34 Note: Performing the pairsplit operation when the pairs are placed in a consistency group does not guarantee the acquired snapshot data to be the P-VOL data. To guarantee that the acquired snapshot data is the P-VOL data, include pairs that do not share the same P-VOL in the consistency group. To avoid a pairsplit operation failure, include only pairs that are in consistency groups in a group (not a consistency group) that you have defined in the CCI configuration file. When creating a pair using a group that you defined in the CCI configuration file, if another pair in the group is part of a consistency group, place the pair you are creating in the same consistency group. If you want to specify multiple consistency groups, define a group for each consistency group. To avoid a command rejection and a generating a consistency group number that does not include the SS pair, create a pair for an At-Time Split operation when the host server is running. If the host server is down, create the pair using the consistency number. In the SN, use the Consistency Groups tab in the Local Replications window. For more information about creating pairs using the paircreate command, see Creating pairs in a consistency group on page C-3. Consistency maintenance workflow when sharing SS P-VOLs with UR or TC volumes Use the following workflow to share SS P-VOLs with UR or TC S-VOLs within a storage system and to maintain consistency: 1. Place the SS pairs in a consistency group. 2. Split the pair in a consistency group. For more information about splitting pairs in consistency groups, see Splitting pairs in consistency groups at a pre-determined time on page The following figure shows the At-Time Split configuration with UR Copy-on-Write Snapshot planning and design

35 The following figure shows the At-Time Split configuration with TC. Copy-on-Write Snapshot planning and design 2-15

36 Snapshot secondary volume consistency maintenance If you are sharing the SS P-VOL with one of the following S-VOLs, ensure the following to maintain SS S-VOL consistency: (SI, TC, and/or UR) The pair status must be the same. For more information: About sharing SI P-VOLs and S-VOLs with SS P-VOLs, see ShadowImage on page 4-6. About sharing TC and/or UR pair volumes with SS P-VOL, see TrueCopy and Universal Replicator on page 4-9. (UR) The journal group must be the same. For more information about sharing UR pair volumes with SS P-VOLs, see TrueCopy and Universal Replicator on page 4-9. For more information about sharing Hitachi Data Systems software application volumes with SS P-VOL and S-VOLs, see Interoperability with other software applications and functions on page 4-2. External volumes External volumes are volumes on external systems. You can connect multiple external storage systems to a VSP storage system. You can use external volumes as pool-vols, but this blocks the pool-vols and the pool Copy-on-Write Snapshot planning and design

37 External-volume failures To minimize the effects of the external-volume failure, specify one kind of volume as data pool-vols in a particular pool, either internal volumes or external volumes. For more information about external systems and the solutions for the errors related to external volumes, see the Hitachi Universal Volume Manager User Guide. Copy-on-Write Snapshot planning and design 2-17

38 2-18 Copy-on-Write Snapshot planning and design

39 3 Copy-on-Write Snapshot installation and configuration This chapter provides instructions and information for installing and configuring SS. Installing and removing Copy-on-Write Snapshot Configuration workflow Creating data pools Creating V-VOLs Setting up the Command Control Interface command device Copy-on-Write Snapshot installation and configuration 3-1

40 Installing and removing Copy-on-Write Snapshot 1. In the SN, install SI. 2. Install the SS license key. To remove SS, complete the following: 1. Delete the SS pairs, pools, and V-VOLs. For more information about deleting SS pairs, pools, and V-VOLs, see: Deleting pairs on page Deleting pool volumes on page 6-9. Deleting virtual volumes on page In the SN, remove SS. Configuration workflow Use the following workflow to set up SS: 1. Create the data pool. For more information, see Creating data pools on page Create the V-VOL. For more information, see Creating V-VOLs on page (Optional) Set up the CCI command device. For more information, see Setting up the Command Control Interface command device on page 3-5. Creating data pools Splitting the pair replaces data in the P-VOL and stores data in the data pool. The V-VOL maintains a point-in-time image. To create data pools, use the Create Pools window. Define the required items, as indicated with an asterisk (*). From this window, you can create the data pool and then continue to the next page where you can create LDEVs for the pools. Size the pool according to the write workload and within the range for pool- VOL capacity. For more information about sizing data pools, see Sizing the data pool workflow on page 2-6. For more information about the pool-vol capacity, see Consistency group system requirements on page 2-2. Prerequisite information Before creating the data pool, determine what is needed to assign pool- VOLs. 3-2 Copy-on-Write Snapshot installation and configuration

41 For more information about consistency group system and data pool requirements, see Consistency group system requirements on page 2-2 and Data pool requirements and restrictions on page 2-4. Caution: You cannot delete pool-vols that you have added. Before adding the pool-vol, ensure that the pool-vol settings are correct. Note: For item descriptions, including character limits, see Create Pools window on page B In the Storage Systems tree, select Pools > Create Pools. 2. In the Create Pools window, for Pool Type, select COW Snapshot. 3. In the Pool Volume Selection area of the Create Pools window, complete the following items: For Drive Type/RPM, select your system s data drive type and RPM. Values: - Mixable - External Storage For RAID Level, select your system s RAID level. Note: If you select External Storage as the drive type/rpm, a single dash (-) is shown as the RAID level, which indicates that you cannot select the RAID level. 4. In the Pool Volume Selection area of the Create Pools window, click Select Pool VOLs, and complete the following: a. In the Select Pool Volumes window, in the Available Pool Volumes table, select the pool-vols you want and click Add. b. Complete the following and then click OK: - To select all pool-vols in the list, click Select All Pages. - To filter the rows, for Filter, click ON. - To specify the number of rows to show, click Options and make the selection. - To select pool-vols, select the pool-vol from the Available Pool Volumes table and move it to the Selected Pool Volumes table. 5. In the Create Pools window, for Pool Name, type a name for the pool and then click Options. 6. In the Options area of the Create Pools window, complete the following items and then click Add: For Initial Pool ID, enter a number. For Warning Threshold, select a data pool capacity threshold. The new pool is added to the Selected Pools table. 7. Click Finish. Note: To create the data pool and then continue to the next page where you can create LDEVs for the pools, click Next. Copy-on-Write Snapshot installation and configuration 3-3

42 8. In the Confirm window, click Apply. The data pool is created. Creating V-VOLs For more information about V-VOLs and P-VOLs, see Volume pairs: P-VOLs and V-VOLs on page 1-2. Prerequisite Information The data pool must exist. For more information about creating data pools, see Creating data pools on page 3-2. The V-VOL must be the same size as the P-VOL. The V-VOL recognized by the host server must have a status of PSUS. You can create a maximum of 64 V-VOLs per P-VOL. For HP-UX/Solaris and other operating systems: Do not use a volume that is already recognized by the host server as a V-VOL. For more information about the HP-UX host servers operating system restrictions and the V- VOL requirements, see Consistency group system requirements on page 2-2. For more information about determining how many V-VOLs you must create, how long to hold an SS, and other planning considerations, see Planning V- VOLs and data pools on page 2-5. Note: For item descriptions, including character limits, see Appendix B, Copyon-Write Snapshot GUI reference on page B In the Storage Systems tree, select Logical Devices > LDEVs > Create LDEVs. 2. On the Create LDEVs window of the Create LDEVs wizard, for Provisioning Type, confirm that COW Snapshot is selected. 3. Complete the following items: For System Type, confirm OPEN is selected. For Emulation Type, confirm OPEN-V is selected. For LDEV Capacity, type the capacity for the new V-VOL. Enter the capacity within the range of figures shown below the text box. Enter the number with two digits after the decimal point. For Number of LDEVs, type the number of V-VOLs (LDEVs) you want to create. For LDEV Name, type a name for the new V-VOL. For Prefix, type alphanumeric characters. Case-sensitive: Yes For Initial Number, type a number. Limit: 9 digits 3-4 Copy-on-Write Snapshot installation and configuration

43 Character limit: Click Option and complete the following items and then click Add: For Initial LDEV ID, ensure that the LDEV ID is set. Caution: You cannot change the LDEV ID. It is automatically registered. To confirm the used number and unavailable number, click View LDEV IDs, which opens the View LDEV IDs window. For Initial SSID, enter the (storage) subsystem identifier (SSID). Characters/digits: 4-digit representation of a hexadecimal number Values: 0004 to FFFE To confirm the created SSID, click View SSID to open the View SSID windows. For Cache Partition, select the CLPR. For Processor Blade, assign a processor blade. To assign a specific processor blade, click the ID for the processor blade. To assign the next available processor blade, click Auto. The new V-VOLs are added to the Selected LDEVs table. 5. Do one of the following: To open the next page where you can create LDEVs, click Next to open the Create LDEVs window. To confirm this operation, click Finish. 6. In the Confirm window, do the following and then click Apply: For Task Name type a name for the task. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. For Go to tasks window for status, select to open the Tasks window. More information For more information about the tasks you can perform using the Create LDEVs wizard and window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. For more information about creating LDEVs and about the tasks you can perform from this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Setting up the Command Control Interface command device You must set up a volume on the storage system for the CCI and dedicate it as the CCI command device. This device acts as the interface between the CCI and the storage system. Copy-on-Write Snapshot installation and configuration 3-5

44 For more information about how to set up the command device, see the Command Control Interface Command Reference. 3-6 Copy-on-Write Snapshot installation and configuration

45 4 Sharing Copy-on-Write Snapshot volumes This chapter discusses the Hitachi Data Systems software application volumes that you can share with SS P-VOLs. Interoperability with other software applications and functions Data Retention Utility and access attributes Dynamic Provisioning Resource Partition Manager ShadowImage TrueCopy and Universal Replicator Volume Migration Thin Image Sharing Copy-on-Write Snapshot volumes 4-1

46 Interoperability with other software applications and functions You can share the following Hitachi Data Systems software application volumes with SS P-VOLs: Dynamic Provisioning For more information about sharing volumes with HDP, see Dynamic Provisioning on page 4-6. Resource Partition Manager For more information about sharing volumes with Res Par, see Resource Partition Manager on page 4-6. ShadowImage or more information about sharing volumes with SI, see ShadowImage on page 4-6. TrueCopy and Universal Replicator For more information about sharing volumes with TC and UR, see TrueCopy and Universal Replicator on page 4-9 Volume Migration For more information about sharing volumes with Volume Migration, see Volume Migration on page Thin Image For more information about sharing volumes with HTI, see Thin Image on page Use the following table to determine the interoperability of other HDS software applications and function volumes with SS P-VOL and S-VOLs. Software application and function volume types Used as SS P-VOL Used as SS S-VOL HTI P-VOL No No HTI S-VOL No No SI P-VOL Yes No SI S-VOL Yes No TC P-VOL Yes No TC S-VOL Yes No UR P-VOL Yes No UR S-VOL Yes No Volume Migration source volume Yes No Volume Migration target volume No No Read Only volume Yes Yes Protect volume Yes Yes S-VOL Disable volume Yes Yes 4-2 Sharing Copy-on-Write Snapshot volumes

47 Software application and function volume types Used as SS P-VOL Used as SS S-VOL Zero Read Capacity volume Yes Yes Invisible volume Yes Yes Note: Use the CCI to set the Zero Read Capacity and Invisible attributes. Data Retention Utility and access attributes In Copy-on-Write Snapshot, you can use a volume with access attributes set by using the Data Retention Utility to create a pair. You can set any access attributes for Copy-on-Write Snapshot virtual volumes. However, you might not be able to perform Copy-on-Write Snapshot pair or pool operations depending on the access attribute of the P-VOL, S-VOL and pool volumes by using Storage Navigator. Furthermore, the pair operations that you can perform vary depending on whether you used Storage Navigator or CCI to set the access attribute of Data Retention Utility. There is no difference in pool operations. You can also set SS pair P-VOLs and S-VOLs access attributes. Note: The SS volume access attributes do not change as a result of an SS operation. For example, even though the reverse resync operation reverses the P-VOL and S-VOL, the P-VOL access attribute is not overwritten to that S- VOL. The following table shows the SS pair operations that you can perform for volumes based on the access attributes that you set by using Storage Navigator. SS pair P-VOL access attribute SS pair S-VOL access attribute SS pair operation Create, Split, Suspend, Delete, Resync (forward) Resync (reverse) Read/Write Read/Write YES YES Read Only, Protect, S-VOL Disable NO NO Read Only Read/Write YES NO Read Only, Protect, S-VOL Disable NO NO Protect Read/Write YES NO Read Only, Protect, S-VOL Disable NO NO S-VOL Disable Read/Write YES NO Sharing Copy-on-Write Snapshot volumes 4-3

48 SS pair P-VOL access attribute SS pair S-VOL access attribute SS pair operation Create, Split, Suspend, Delete, Resync (forward) Resync (reverse) Read Only, Protect, S-VOL Disable NO NO The following table shows the SS pair operations that you can perform for volumes based on the access attributes that you set by using CCI. SS pair P-VOL access attribute SS pair S-VOL access attribute SS pair operation Create, Split, Suspend, Delete, Resync (forward) Resync (reverse) Read/Write Read/Write, Read Only, Protect YES YES S-VOL Disable NO NO Read Only Read/Write, Read Only, Protect YES YES S-VOL Disable NO NO Protect Read/Write, Read Only, Protect YES YES S-VOL Disable NO NO S-VOL Disable Read/Write, Read Only, Protect YES NO S-VOL Disable NO NO The following table shows the SS pool operations that you can perform for volumes based on the access attributes that you set. SS volume access attribute SS pool operation Pool-VOL setting Read/Write Read Only Protect S-VOL Disable YES NO NO NO The SS pair status determines whether you can set access attributes for the SS P-VOL and S-VOL. Furthermore, the access attributes that you can set vary depending on whether you used Storage Navigator or CCI to set the access attribute of Data Retention Utility. The following table shows the access attributes that you can set for SS P-VOL and S-VOL by using Storage Navigator. 4-4 Sharing Copy-on-Write Snapshot volumes

49 Access attribute setting SS pair status SS pair volume Read Only, Protect, S-VOL Disable Read/Write COPY P-VOL YES YES S-VOL NO YES PAIR, PFUL P-VOL YES YES S-VOL YES YES PSUS, PFUS P-VOL YES YES S-VOL YES YES SMPL P-VOL YES YES S-VOL NO YES RCPY P-VOL NO YES S-VOL NO YES PSUE P-VOL YES YES S-VOL NO YES The following table shows the access attributes that you can set by using CCI for SS P-VOL and S-VOL. Access attribute setting SS pair status SS pair volume S-VOL Disable Read/Write, Read Only, Protect COPY P-VOL YES YES S-VOL NO YES 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 NO YES RCPY P-VOL NO YES S-VOL NO YES PSUE P-VOL YES YES S-VOL NO YES Sharing Copy-on-Write Snapshot volumes 4-5

50 Dynamic Provisioning You can share HDP volumes with SS P-VOLs. You can use a maximum HDP volume size of 4 TB ( bytes) as an SS P-VOL. You cannot use TB, GB, or MB specifications for SS volumes. For example, to create a 4 TB P-VOL, use the block specification. The block-size equivalent to 4 TB is blocks. Note the following regarding pools: You cannot use HDP pools (including Dynamic Tiering (HDT) pools) as SS pools. The number of available pools for SS decreases according to the number of HDP pools (including HDT pools) and HDPz pools in the storage system. You can create a maximum of 128 pools in the storage system. If you specify an HDP V-VOL as the SS P-VOL and the capacity of the HDP V-VOL is increasing, you cannot create the SS pair. Performing an SS paircreate operation while zero pages are being reclaimed (including operations by Writesame, Unmap, and Rebalance) results in the zero-page operation being interrupted. An SS create pair operation may be rejected if the Unmap command operation is in progress with system option mode 905 ON. Retry the SS operation after a while. If the operation still fails, set system option mode 905 to OFF and retry. Resource Partition Manager You can create an SS pair if the P-VOL and S-VOL are allocated to the same resource group or different resource groups. Allocate the pool you want to use to the same resource group as the P-VOL or the resource group that has an authority to create an SS pair. For more information about resource groups, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. ShadowImage You can share SI P-VOLs and S-VOLs with SS P-VOLs. The SI and SS pair s status determines the pair operations you can perform. For more information about SI pair status and operations, see the Hitachi ShadowImage User Guide. The following tables list the relationship between SS pair operations and SI status. 4-6 Sharing Copy-on-Write Snapshot volumes

51 SI status SS pair operation COPY( PD) / COPY PAIR COPY( SP) / COPY PSUS( SP) / PSUS PSUS COPY (RS) / COPY COPY (RS-R) / RCPY PSUE Create pair Yes Yes Yes Yes Yes Yes No Yes Split pair Yes Yes Yes Yes Yes Yes No Yes Restore pair No No No No Yes No No Yes Delete SS data Yes Yes Yes Yes Yes Yes Yes Yes Delete pair Yes Yes Yes Yes Yes Yes Yes Yes The following tables list the relationship between SS operations and SI status. SI status SS operation COP Y(PD) / COPY PAIR COPY( SP) / COPY PSUS (SP) / PSUS PSUS COPY (RS) / COPY COPY (RS-R) / RCPY PSUE Create pair No No No No Yes No No No Split pair N/A No No No Yes No No No Split pair in a consistency group N/A No No No Yes* No No No Restore pair N/A No No No Yes No No No Delete SS data N/A Yes Yes Yes Yes Yes Yes Yes Delete pair N/A Yes Yes Yes Yes Yes Yes Yes * The SI pair status must be PSUS from the time you split the pairs in a consistency group until the time the status of all SS pairs in the consistency group change to PSUS. If the SI pair status changes while splitting pairs in a consistency group, the SS data cannot maintain consistency. The following tables list the relationship between SI operations and SS status. SS status SI operation COPY 1 PAIR, PFUL PSUS, PFUS COPY 2 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 Forward pair resynchronization Normal backward pair resynchronization Yes Yes Yes Yes No Yes Yes Yes Yes Yes No Yes Sharing Copy-on-Write Snapshot volumes 4-7

52 SS status SI operation COPY 1 PAIR, PFUL PSUS, PFUS COPY 2 RCPY PSUE Quick backward pair resynchronization No No No No No No Suspend pair Yes Yes Yes Yes Yes Yes Delete pair Yes Yes Yes Yes Yes Yes 1. COPY status during initial copy. 2. COPY status during resynchronization. The following tables list the relationship between SI operations and SS status. SS status SI operation COPY 2 PAIR, PFUL PSUS, PFUS COPY 3 RCPY PSUE 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 Forward pair resynchronization Normal backward pair resynchronization Quick backward pair resynchronization Yes Yes Yes Yes No Yes Yes Yes Yes Yes No Yes No No No No No No Suspend pair Yes Yes Yes Yes No Yes Delete pair Yes Yes Yes Yes Yes Yes 1. You can perform SI operations while splitting pairs in a consistency group. However, the SS data consistency is not maintained. 2. COPY status during initial copy. 3. COPY status during resynchronization. Restrictions when sharing P-VOLs The SS S-VOL uses the data in the P-VOL. The following are restrictions when sharing an SS pair P-VOL with an SI P-VOL or S-VOL: The SS pair P-VOL cannot have the same mirror unit (MU) number as the SI pair. You cannot perform the SI Quick Restore operation. You cannot share the SI volume that is in a consistency group with SS. You cannot share the SS volume that is in a consistency group with SI. 4-8 Sharing Copy-on-Write Snapshot volumes

53 TrueCopy and Universal Replicator You can share TC and UR pair volumes with SS P-VOLs. If you share pair volumes with these software applications, the pair operation you can perform are restricted based on the shared pair status. The following table shows the relationship between SS pair operations and TC/UR status. SS operation TC/UR status COPY PAIR PSUS PSUE Suspending Deleting Create pair Yes Yes Yes Yes Yes Yes Split pair Yes Yes Yes Yes Yes Yes Restore pair No No Yes Yes No No Delete SS data Yes Yes Yes Yes Yes Yes Delete pair Yes Yes Yes Yes Yes Yes The following table shows the relationship between SS pair operations and TC/UR status. SS operation TC/UR status COPY PAIR PSUS PSUE SSWS Suspending Deleting Create pair Yes Yes Yes Yes Yes Yes Yes Split pair No Yes Yes Yes Yes Yes Yes Restore pair* No No No No No No No Delete SS data Yes Yes Yes Yes Yes Yes Yes Delete pair Yes Yes Yes Yes Yes Yes Yes * When restoring an SS pair whose P-VOL is used as a TC or UR S-VOL, switch operations to the remote site by running the horctakeover command. The following table shows the relationship between TC/UR pair operations and SS status. SS status TC/UR operation COPY 1 PAIR, PFUL PSUS, PFUS COPY 2 RCPY PSUE Create pair Yes Yes Yes Yes No Yes Split pair Yes Yes Yes Yes N/A Yes Resync pair Yes Yes Yes Yes No Yes Delete pair Yes Yes Yes Yes Yes Yes Switch operations to the remote site Yes Yes Yes Yes No Yes Sharing Copy-on-Write Snapshot volumes 4-9

54 SS status TC/UR operation COPY 1 PAIR, PFUL PSUS, PFUS COPY 2 RCPY PSUE 1. COPY is the status during the initial copy. 2. COPY is the status during a resynchronization. The following table shows the relationship between TC/UR pair operations and SS status. SS status TC / UR operations COPY 1 PAIR, PFUL PSUS, PFUS COPY 2 RCPY PSUE Create pair 3 No No No No No No Split pair Yes Yes Yes Yes N/A Yes Resync pair Yes Yes Yes Yes N/A Yes Delete pair Yes Yes Yes Yes N/A Yes Switch operations to the remote site Yes Yes Yes Yes N/A Yes 1. COPY is the status during the initial copy. 2. COPY is the status during a resynchronization. 3. To use a TC or UR S-VOL as the SS P-VOL, you must first create the TC or UR pair then create the SS pair. To view a list of the corresponding CCI pair status names, see Storage Navigator and Command Control Interface pair status names on page A-2. TC and UR volume backup in 3DC multi-target configuration You can use SS to back up TC and UR volumes on the remote sites in a 3DC multi-target configuration. The following figure shows how to back up the volumes Sharing Copy-on-Write Snapshot volumes

55 Pair 1 is the TC pair. Pair 2 is the UR pair. Pair 3 is the UR pair for a delta resynchronization. Pair 4, pair 5, and pair 6 are the SS pairs. To back up the volumes, complete the following: 1. Create the 3DC multi-target and delta resynchronize pairs (pairs 1, 2, and 3). 2. Create pair Create pairs 5 and 6. Note: You cannot share SS volumes in 3DC UR/UR configurations. Volume Migration To share the source Volume Migration pair with an SS P-VOL, complete the following: 1. Create the SS pair. 2. Perform the migration plan. To share SS P-VOL, the SS pair status must be PAIR. You can delete and cancel the migration plan at any time. For more information about using Volume Migration, call the Support Center. Thin Image You can share HTI pair volumes with SS, HDP, and HDPz pairs. Note the following regarding pools: You cannot use HTI pools for SS. You cannot use SS pools for HTI. Sharing Copy-on-Write Snapshot volumes 4-11

56 The more pools that you create for HTI, the less pools that are available for SS Sharing Copy-on-Write Snapshot volumes

57 5 Pair operations This chapter provides instructions for performing pair operations. Pair operations Checking the pair status Pair creation workflow Pair split Pair resynchronization and restoration Pair deletion Pair operations 5-1

58 Pair operations You can perform the following operations on pairs: Checking the pair status on page 5-2. Pair creation on page 5-3. The V-VOL becomes a virtual duplicate of the PVOL. Pair split on page 5-9 A point-in-time snapshot of the P-VOL is established in the V-VOL, allowing another software applications to use the V-VOL. Pair resynchronization and restoration on page SS data is discarded and the V-VOL is again a virtual copy of the P-VOL. Pair deletion on page The pair relationship between the pair volumes is ended. Checking the pair status Each pair operation requires a pair to have a specific status. Check the pair status before performing a pair operation and to ensure that an operation completes successfully. For more information about checking pair status, see Monitoring the storage system on page 6-2. For the more information about the statuses that are required for specific operations, see Pair status definitions on page 6-3. Pair creation workflow Use the following workflow to create a pair: 1. (If you are sharing SS P-VOLs with other Hitachi Data Systems software application volumes and you want to use the volumes to create the SS pair) Set the access attributes using the SN DRU. For more information about setting access attributes, see Data Retention Utility and access attributes on page Create the data pool. For more information about creating data pools, see Creating data pools on page Create the V-VOL for the pair. For more information about creating V-VOLs, see Creating V-VOLs on page Check the pair status. For more information about checking the pair status, see Checking the pair status on page Do the following: 5-2 Pair operations

59 If you are creating pairs with different numbers of S-VOLs, configure the pairs. For more information about configuring pairs, see Configuring pairs on page 5-4. If you are creating pairs with the same number of S-VOLs, create the pairs. For more information, see Creating pairs on page 5-5. Pair creation When you create a pair, the V-VOL becomes a virtual copy of the P-VOL. Updates you make to the P-VOL are reflected in the V-VOL until you split the pair. Related topics Prerequisite information on page 5-3 Configuring pairs on page 5-4 Creating pairs on page 5-5 Note: After you create the pair, if the number of pairs and other information shown in the Summary tab differs from the number of pairs in the list on the window, configuration changes may be in progress. If configuration changes are in progress, wait until they have completed and then click File > Refresh All to read the configuration information. Prerequisite information The data pool must exist. For more information about creating data pools, see Creating data pools on page 3-2. The V-VOL for the pair must exist. For more information about creating V-VOLs, see Creating V-VOLs on page 3-4. The P-VOLs 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, or for a secondary window, look at the Capacity (blocks) area of the Detail window. Review the pair volume requirements. For more information, see Planning pair volumes on page 2-5. The pair volumes must be in SMPL status. You must use the same pool for all pairs sharing a single P-VOL. Example: Three pairs with the same P-VOL must use the same pool. In the Create Pairs wizard, specify the pair configuration settings. Pair operations 5-3

60 Configuring pairs For more information about setting up pair configuration, see Configuring pairs on page 5-4. If you are creating pairs with different numbers of S-VOLs, do the following to create the pair: 1. Specify the maximum number of secondary pairs, even if a pair will not have that many S-VOLs. 2. Remove volumes or move volumes to the correct location. For more information about removing and moving volumes, see Removing and moving volumes on page 5-5. Example 1 You want to create a pair using one P-VOL and one S-VOL. For Number of Secondary Volumes, type 1. You want to create a pair using one P-VOL and 64 S-VOLs (the maximum). For Number of Secondary Volumes, type 64. Example 2 You want to add a new S-VOL to an existing pair, as shown in the following diagram. For Number of Secondary Volumes, type 2. Example 3 You want to create one pair with two S-VOLs and another pair with one S- VOL. For Number of Secondary Volumes, type 2. In this case, the storage system assumes that you are creating two pairs, each having two S-VOLs, as shown in the following figure. 5-4 Pair operations

61 Removing and moving volumes Creating pairs 1. In the Storage Systems tree, click Replications > Local Replications > Pairs. 2. In the Pairs tab of the Local Replications window, click Create Pairs. 3. In the Select Pair Configuration window, for Number of Secondary Volumes, type the number of S-VOLs that you want to pair, and then click Next. 4. In the Select Primary Volumes window, select two LDEVs as P-VOLs, and then click Next. 5. In the Select Secondary Volumes window, complete the following and then click Next: a. Select three LDEVs from the Available LDEVs table as the S-VOLs. b. In the Selected Pairs table, delete the unwanted row by selecting it and clicking Remove. The volumes are removed and moved. Use this procedure if you are creating pairs with the same number of S-VOLs. Use the Create Pairs wizard to create pairs. Note: If you are using SS, Split Type, Copy Pace, and Pair Topology Type are unavailable. Note: If the pair is in SMPL (PD) status, you cannot create the pair. To shorten the period when the pair is in SMPL (PD) status, do the following: 1. Resynchronize the pair. For more information about resynchronizing pairs, see Resynchronizing and restoring pairs on page Wait until the pair status changes to PAIR. 3. Delete the pair. For more information about deleting pairs, see Deleting pairs on page Open the Create Pairs wizard. Complete one of the following: Click General Tasks > Create Pairs. In the Storage Systems tree, click Replications > Local Replications > Pairs > Create Pairs. Pair operations 5-5

62 2. In the Select Pair Configuration window of the Create Pairs wizard, complete the following items and then click Next: For Copy Type, select COW Snapshot. For Emulation Type, OPEN-V is selected by default. Note: If you are using SS, this item is unavailable. For Number of Secondary Volumes, type the number of S-VOLs according to the pair configuration with the largest amount of S-VOLs that you are creating. For more information about setting up the pair configuration, see Configuring pairs on page 5-4. For Initial MU Number, type an MU number. 3. In the Select Primary Volumes window, for Use Primary Volumes of Snapshot Pairs, select the kind of volumes you want to populate from the Available LDEVs table. Values: Yes. The LDEVs that are already used as P-VOLs are shown. No. The LDEVs that are not used as P-VOLs are shown. 4. To create pairs with LDEVs that are not paired and are not listed in the Available LDEVs table, add an available pool. Do the following: a. Click Select Pool. b. In the Select Pool window, select a pool and click OK. The LDEV is added and is listed in the Available LDEVs table. 5-6 Pair operations

63 5. In the Available LDEVs table, select the LDEV that you want to be the P- VOL and click Add. The LDEV moves to the Selected LDEVs table. 6. Click Next. 7. In the Select Secondary Volumes window, pair the LDEV to the P-VOL LDEV. Repeat this step until all LDEVs are paired with a P-VOL LDEV: a. Select the S-VOL LDEV ID from the Available LDEVs table. b. (If you specified multiple P-VOLs) From the Selected Pairs table, select the LDEV ID for the P-VOL to which you want the S-VOL to be paired, and click Set. Note: If you do not select a P-VOL, the selected S-VOL is paired to P- VOLs in the order they are listed in the table. Pair operations 5-7

64 8. Sort the Available LDEVs and Selected Pairs tables according to the capacity you select in the Capacity list. 9. You can do the following from this window: Correct mirror unit numbers by selecting the line in the Selected Pairs table and clicking Edit Mirror Unit. Remove a configuration. To do this, select the line you want to remove from the Selected Pairs table and click Remove. For more information about creating unequal pair configurations and removing configurations, see Example 3 on page 5-4. The following figure shows the right-side of the Select Secondary Volumes window. 5-8 Pair operations

65 10. Click Next. 11. In the Confirm window, for Task Name, type a name and then click Apply. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. Pair split Splitting a pair creates a virtual point-in-time copy of the P-VOL and stores SS data in the pool. Splitting a pair does the following to the P-VOL: It continues receiving updates from the host, but updates are not reflected in the V-VOL. The data blocks are copied to the data pool. Pointers in the V-VOL follow this original data to the data pool, maintaining the point-in-time copy. You can do the following to split pairs: Split a pair. For more information about splitting pairs, see Splitting pairs on page Split multiple pairs in a consistency group. Pair operations 5-9

66 Splitting pairs For more information about splitting pairs in a consistency group, see Splitting pairs in consistency groups at a pre-determined time on page Split multiple pairs in a consistency group at a pre-determined time. For more information about splitting pairs in a consistency group, see Splitting pairs in consistency groups at a pre-determined time on page For more information about the consistency group requirements for splitting pairs, see Consistency group system requirements on page 2-2. Related topics Prerequisite information on page 5-10 Splitting pairs on page 5-10 Splitting pairs in consistency groups at a pre-determined time on page 5-11 Note: If you are performing the pairsplit operation on a pair that shares the same P-VOL, do not run the pairresync -restore command on the pair. Running the command during this operation can result in the pairsplit operation ending abnormally. Prerequisite information The pair status must have a status of PAIR. If you pair a P-VOL with two or more V-VOLs, the pairs must have a status other than RCPY. If the status is RCPY, the pairsplit operation can end abnormally. SS does not support Quick Split mode. You can also split pairs in consistency groups. For more information about splitting pairs in a consistency group, see Splitting pairs in consistency groups at a pre-determined time on page In the Storage Systems tree, click Replications > Local Replications > Pairs. 2. In the Pairs tab, select the pair you want to split, click Split Pairs, and then click Finish. 3. In the Confirm window, for Task Name, type a name for the task and then click Apply. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. The pairs are split. The pair status changes to PSUS Pair operations

67 Splitting pairs in consistency groups at a pre-determined time Use the At-Time Split operation to split pairs in a consistency group at a predetermined time. Prerequisite information The CCI must be installed. 1. From a command prompt, run the following command, specifying a consistency group number in the command option: paircreate The At-Time SS function is enabled. 2. (Optional) Create more pairs specifying the same consistency group number. 3. From a command prompt, run the following command on the consistency group: pairsplit The VSP storage system receives the command. Running a subsequent write requests from the host to the P-VOL of a pair in the consistency group acquires SS data. Related topics Planning for splitting pairs in consistency groups on page 2-12 Pair resynchronization and restoration Resynchronizing a pair does the following: Increases capacity in the data pool. Deletes data in the pool. Mirrors the V-VOL with the current data in the P-VOL. Reverse resynchronizing a pair restores the P-VOL using data from the V- VOL. Related topics Prerequisite information on page 5-10 Resynchronizing and restoring pairs on page 5-12 Prerequisite information The pair must be in PSUS status. SS does not support high speed mode, even if you specify it. If a failure occurs when you reverse resynchronize a pair, the pair status changes to PSUE. To restore the pair, you must delete the SS data. However, when you do this, the pair s P-VOL data cannot be guaranteed. Pair operations 5-11

68 Therefore, take appropriate measures, such as overwriting the backup data to the P-VOL or formatting the P-VOL. Resynchronizing and restoring pairs 1. In the Storage Systems tree, click Replications > Local Replications > Pairs. 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 one of the following and then click Finish: If you have split or deleted the pool data, to resynchronize the pair, select Normal Copy (Primary > Secondary). To reverse resynchronize the volumes from the S-VOL to the P-VOL, select Reverse Copy (Secondary > Primary). All differential data is updated to the P-VOL. 4. On the Confirm window, for Task Name, type a name for the task and then click Apply. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. The pair is resynchronized and restored. Pair deletion Deleting a pair ends the SS relationship between the P-VOL and V-VOL. The following also occurs: SS data for the pair is deleted from the data pool. The status changes to SMPL (PD). When the operation is complete, the status changes to SMPL. Note: The time required to delete a pair or pairs can be from several seconds to more than ten minutes. The time increases when you delete multiple pairs at the same time or if you use a large area of the pool for SS data. Related topics Prerequisite information on page 5-10 Deleting pairs on page 5-13 Note: After you delete the pair, if the number of pairs and other information shown in the Summary tab differs from the number of pairs in the list on the window, configuration changes may be in progress. If configuration changes are in progress, wait until they have completed and then click File > Refresh All to read the configuration information. Prerequisite information 5-12 Pair operations

69 Deleting pairs The pair status must be PAIR, PSUS, or PSUE. 1. In the Storage Systems tree, click Replications > Local Replications > Pairs. 2. In the Pairs tab, select the pair you want to delete, and click More Actions > Delete Pairs. 3. In the Delete Pairs window, for Task Name, type a name for the task and then click Apply. Note: For more information about character and symbol limits and default values, see Complete SIMs window on page B-32. The pair is deleted. Pair operations 5-13

70 5-14 Pair operations

71 6 Copy-on-Write Snapshot monitoring and maintenance This chapter provides information and instructions for monitoring and maintaining SS. Monitoring the storage system Maintaining the storage system Copy-on-Write Snapshot monitoring and maintenance 6-1

72 Monitoring the storage system Monitoring the storage system helps you to keep track of pairs and volumes in current and past conditions. Monitoring is an ongoing activity. Monitoring the storage system includes the following activities: Monitoring pair information, license capacity, status on page 6-2 (status definitions included) Monitoring pair properties on page 6-3 Monitoring synchronous rates on page 6-4 Monitoring consistency groups on page 6-4 Monitoring pair operations history on page 6-4 Monitoring pool information on page 6-5 Monitoring pair information, license capacity, status You can view basic pair information, license capacity, and pair statuses from the Local Replications window. Monitor pair status before and after performing pair operations. Each operation requires a specific status or statuses. To do a pair command, first check the pair s status. Check the pair status to ensure that the pairs are operating correctly and that status is changing to the appropriate state during and after an operation. Monitor pair information, license capacity, and status frequently using the SN GUI. You can set up notifications for problems that occur in pair operations using SN. 1. In the Storage Systems tree, click Replications > Local Replications. 2. In the Pairs tab, locate the pair whose status you want to review. Review pair status in the Status column. Note: Both SS and SI pairs are shown in the Pairs tab. Use the Copy Type column to find SS pairs. SS V-VOLs are shown in the Secondary Volume column. Caution: (Using monitoring software applications on a host server) If you have installed and are running a software application on a host server to monitor the volumes of SS pairs, the following problems can occur: An S-VOL whose status is not PSUS (or PFUS ) rejects access from the host server, possibly causing problems for the monitoring software application whose access is rejected. If the host server connects to more than one port, other ports may also go offline when the S-VOL rejects host server access. To solve these problems, stop the monitoring software application. 6-2 Copy-on-Write Snapshot monitoring and maintenance

73 Pair status definitions Click Refresh View to ensure the pair status data is current. For more information about the corresponding CCI pair status names, see Storage Navigator and Command Control Interface pair status names on page A-2. The following table shows the pair status and descriptions. The P-VOL and V- VOL access columns in the following table indicate whether the volumes accept read/write. Status Description P-VOL access V-VOL access SMPL(PD) The pair is in the process of being deleted. You cannot perform pair operations while the pair is in this status. After the pair is deleted, the status changes to SMPL. Yes R/W disabled COPY The storage system has accepted the paircreate initial copy. The storage system accepts read/write operations to the P-VOL, but does not accept read/write operations to the S-VOL. Yes R/W disabled PAIR The volumes are paired. The storage system does not accept read/write operations to the S-VOL. Yes R/W disabled PSUS The snapshot is split. The storage system accepts read/ write operations to the S-VOL. Differential data between the P-VOL and S-VOL is retained. You can immediately perform the resync operation. Yes R/W enabled. Can be mounted. PFUL The data pool threshold is exceeded in PAIR status. Yes R/W disabled PFUS The data pool threshold is exceeded in PSUS status. Yes R/W enabled RCPY* The pair is in the process of reverse pairresync. The storage system does not accept read/write operations to the S-VOL. Only the S-VOL differential data is copied to the P-VOL. Yes R/W disabled PSUE The storage system has suspended the pair. The storage system accepts read/write operations to the P- VOL, but does not accept read/write operations to the S-VOL. Yes R/W disabled * Starting time of the copy depends on numbers of pairs and your system environment. Caution: When you run DEVSERVE to a read/write disabled volume, the message INTERVENTION REQUIRED appears. If you have created pairs with the volumes online, and then run DEVSERVE to a read/write disabled volume, a normal value is returned. Monitoring pair properties You can view data related to pairs and their volumes, including volume capacity, status, P-VOLs and S-VOLs, identifiers, and several other details. 1. In the Storage Systems tree, click Replications > Local Replications. Copy-on-Write Snapshot monitoring and maintenance 6-3

74 2. In the Local Replications window, select the pair and then click More Actions > View Pair Properties. The pair properties are shown in the View Tier Properties window. Monitoring synchronous rates You can check on the percentage of data that is synchronized between the P- VOLs and S-VOLs. Note: You can show the latest synchronous rate by clicking Refresh View. If you close the window, information in the Local Replications window may not be the latest. Click Refresh View again. 1. In the Storage Systems tree, click Replications > Local Replications. 2. In the Local Replications window, select the pair and click More Actions > View Pair Synchronous Rate. The synchronous rates are shown in the View Pair Synchronous Rate window. Monitoring consistency groups You can check the number and individual properties for consistency groups. 1. In the Storage Systems tree, click Replications > Local Replications. 2. In the Local Replications window, view the number of consistency groups in the Summary table. 3. To view a list of consistency groups with status and number of pairs, click the Consistency Groups tab. 4. On the Consistency Groups tab, click the CTG ID link to view a consistency group s properties. Monitoring pair operations history You can review the operations that have been performed on a pair using the View History window. Prerequisite information If you use 1,000 or more pairs concurrently, some operation history might not be recorded. 1. In the Storage Systems tree, click Replications > View Histories. 2. In the View Histories window, for Copy Type, select COW Snapshot. The Description column indicates which operations ran. The following table contains descriptions and explanations of the code. Code Description Explanation 2001 PAIR The pair has been created PSUS The pair has been split. 6-4 Copy-on-Write Snapshot monitoring and maintenance

75 Code Description Explanation 2021 SMPL The pair has been deleted COPY(RS-R) START The pair restoration operation has begun COPY(RS-R) END The pair restoration operation is completed COPY(RS-R) ENDED ABNORMAL The pair restoration operation has failed COPY(RS) The pair has been resynchronized and SS data has been deleted PSUE(ABNORMAL END) A failure occurred. The pair has been suspended INITIALIZE START Initialization processing began INITIALIZE END Initialization processing terminated normally INITIALIZE ENDED ABNORMAL Initialization processing terminated abnormally. Monitoring pool information 1. In the Storage Systems tree, click Pools. 2. From the names that appear on the Pools tab, click the pool that you want to review. 3. In the Pools window on the right pane, review the desired pool information. Copy-on-Write Snapshot monitoring and maintenance 6-5

76 You can do the following to monitor pool information: Chapter 3, Copy-on-Write Snapshot installation and configuration on page 3-1 Chapter 6, Copy-on-Write Snapshot monitoring and maintenance on page 6-1 Changing pool volume names on page 6-8 Managing data pools on page 6-7 Maintaining the storage system You can maintain the storage system while monitoring it. Some of the maintenance tasks you will do are in response to a particular behavior in the storage system. Other maintenance tasks are in response to requirements changes, which you can do by changing the storage system settings. Maintaining the storage system, data pools, and V-VOLs includes the following activities: Managing data pools on page 6-7 Managing virtual volumes on page 6-9 Switching off the storage system power and replacing the microcode on page Copy-on-Write Snapshot monitoring and maintenance

77 Managing data pools You can perform the following maintenance operations to manage data pools: Increasing data pool volume capacity on page 6-7 Changing pool volume threshold on page 6-7 Changing pool volume names on page 6-8 Recovering pool volumes on page 6-8 Deleting pool volumes on page 6-9 Increasing data pool volume capacity If the pool threshold is reached more than once or twice, increase the data pool-vol capacity. The best practice is to prevent the pool from reaching full capacity by monitoring the pool usage rate. You increase the data pool-vol capacity by adding pool-vols to the data pool. You can check the capacity in the Pools window. For more information about monitoring pool information, see Monitoring pool information on page 6-5). 1. In the Storage Systems tree, click Pools. 2. From the names that appear on the Pools tab, click the pool with the capacity you want to increase. 3. In the Pools window, click Expand Pool. 4. In the Expand Pool window, click Select Pool VOLs. 5. In the Available Pool Volumes table that is shown in the Select Pool Volumes window, select the LDEV you want and then click Add. The LDEV is moved to the Selected LDEVs table. 6. Click OK. In the Expand Pool window, the number of selected pool-vols and total capacity is shown. 7. Click Finish. 8. In the Confirm window, complete the following and click Apply: For Task Name, type a name for the task. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. For Go to tasks window for status, select to open the Tasks window. Changing pool volume threshold 1. In the Storage Systems tree, click Pools. 2. From the names that appear on the Pools tab, click the pool with the threshold that you want to change and click More Actions > Edit Pools. Copy-on-Write Snapshot monitoring and maintenance 6-7

78 3. In the Edit Pools window, complete the following items and then click Finish: Select Warning Threshold. For Warning Threshold, type a new threshold. Note: The possible range is shown below the item name. 4. In the Confirm window, complete the following and then click Apply: Changing pool volume names For Task Name, type the task name. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. For Go to tasks window for status, select to open the Tasks window. The pool-vol threshold is changed. 1. In the Storage Systems tree, click Pools. 2. From the names that appear on the Pools tab, select the pool with the name that you want to change and click More Actions > Edit Pools. 3. In the Edit Pools window, select Pool Name. 4. For Pool Name, type a name for the pool and click Finish. Note: For item descriptions, including character limits, see Create Pools window on page B In the Confirm window, complete the following and then click Apply: Recovering pool volumes For Task Name, enter the task name. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. For Go to tasks window for status, select to open the Tasks window. The pool-vol name is changed. 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 Systems tree, click Pools. 2. From the names that appear on the Pools tab, select one or more pools with volumes you want to recover and click More Actions > Restore Pools. 6-8 Copy-on-Write Snapshot monitoring and maintenance

79 3. In the Restore Pools window, for Task Name, type a name and then click Apply. Note: For more information about character and symbol limits and default values, see Complete SIMs window on page B-32. The pool-vol is recovered. Deleting pool volumes 1. In the Storage Systems tree, click Pools. 2. From the names that appear on the Pools tab, select the pool-vol that you want to delete and click More Actions > Delete Pools. 3. In the Delete Pools window, click Finish. 4. In the Confirm window, complete the following and click Apply: For Task Name, enter the task name. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. For Go to tasks window for status, select to open the Tasks window. The pool-vol is deleted. Managing virtual volumes You can perform the following operations to manage V-VOLs: Changing virtual volume names on page 6-9 Deleting virtual volumes on page 6-10 Within the resulting list on the Logical Devices window, you can do the following: To select all pool-vols in the list, click Select All Pages. To filter the rows, for Filter, click ON. To specify the number of rows to show, click Options and make the selection. Changing virtual volume names 1. In the Storage Systems tree, click Logical Devices. 2. From the names that appear, select one or more V-VOL rows with names that you want to change and then click More Actions > Edit LDEVs. 3. In the Edit LDEVs window of the Edit LDEVs wizard, complete the following: For LDEV Name, type a new name for the LDEV. Character limit: 32 For Prefix, type alphanumeric characters. Copy-on-Write Snapshot monitoring and maintenance 6-9

80 Case-sensitive: Yes For Initial Number, type a number. Limit: 9 digits 4. Click Finish. 5. In the Confirm window of the Edit LDEVs wizard, complete the following and click Apply: For Task Name, type the task name. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. For Go to tasks window for status, select to open the Tasks window. The LDEV name is changed. Deleting virtual volumes Note: You cannot make a V-VOL part of an SS pair. You must delete the pair before you can delete the V-VOL. For more information about deleting pairs, see Deleting pairs on page In the Storage Systems tree, click Logical Devices. 2. From the names that appear, select one or more V-VOL rows with V-VOLS that you want to delete, click More Actions > Delete LDEVs. 3. In the Delete LDEVs window, complete the following and then click Apply: For Task Name, type the task name. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. or Go to tasks window for status, select to open the Tasks window. The V-VOL is deleted. Switching off the storage system power and replacing the microcode This topic explains how to maintain pairs when you switch off the storage system power and when you replace the microcode. For more information, see: Switching off the power supply on page 6-10 Replacing the microcode offline on page 6-11 Switching off the power supply Note: Stop the host I/O to the P-VOL before switching off the power supply for the storage system Copy-on-Write Snapshot monitoring and maintenance

81 When you restore the power, SS s behavior depends on the following: If data in shared memory existed after switching off the power supply If information in the shared memory exists after you have switched off the power supply, you can use the pools and pairs. However, since the storage system checks the status of the pools and the pool-vols, if the pool-vols are blocked at the time you switch off the power supply, the pool will be blocked and the status of the pairs changes to PSUE. When this occurs, you must restore the power and then recover the pools. When you store snapshot data by consistency group, if you switch off the power supply before the status of all the pairs in a consistency group has changed completely, the snapshot data will not resume storing. When you restore the power, the status of some pairs may remain unchanged. If information in shared memory is lost after switching off the power supply If information in the shared memory is lost after switching off the power supply, the information about pools and pairs is also lost. If this occurs, complete the following: 1. Restore the power. 2. Recreate the pools and pairs. For more information about creating pairs, see Creating pairs on page 5-5. For more information about creating pools, see Creating data pools on page 3-2. Replacing the microcode offline You usually replace the microcode online. If you replace it offline, the pool and pair information in shared memory is lost and you must recreate it. For example, when you need to change the configuration of shared memory. Copy-on-Write Snapshot monitoring and maintenance 6-11

82 6-12 Copy-on-Write Snapshot monitoring and maintenance

83 7 Copy-on-Write Snapshot troubleshooting This chapter provides Snapshot troubleshooting information. General troubleshooting Troubleshooting with Command Control Interface Copy-on-Write Snapshot troubleshooting 7-1

84 General troubleshooting The following table shows general SS troubleshooting information. Problem You cannot install SS. Pool information is not shown. A pool is blocked. Pool usage rate exceeds the threshold. Cannot add pool-vols. Causes: Causes and solutions Shared memory for the V-VOL management area is not installed. Shared memory is not set for the V-VOL management area. Shared memory for the differential tables is not installed. Solutions: Check if the shared memory for the V-VOL management area and the differential tables is installed. Check if the shared memory for the V-VOL management area is correctly set. To check installation and settings, call the Support Center. Cause: The pool is blocked. Solution: Recover the blocked pool. For more information, see Recovering a blocked pool workflow on page 7-6. Cause: The pool-vols are blocked. Solution: 1. Recover the blocked pool. For more information, see Recovering a blocked pool workflow on page Complete the SIMs. For more information, see Pool-related SIM entry removal workflow on page 7-7. Causes: An excess of SS data is being stored in the pool. Capacity of the pool is insufficient. Threshold of the pool is too low. Solutions: 1. Complete one or more of the following: Delete old or less important SS data to decrease the usage rate of the pool. Add more pool-vols to increase the capacity of the pool. Note: You need unused volumes to add the pool-vols. If you do not have unused volume, you must create new volumes or call the Support Center to have them add the hard disks. The solution to this problem may take time. Set a larger value for the pool threshold. 2. Complete the SIMs. For more information, see Pool-related SIM entry removal workflow on page 7-7. Causes: The maximum number of pool-vols are set in the pool. For more information about the maximum number of pool-vols, see Consistency group system requirements on page 2-2. Available pool management block in the V-VOL management area in the shared memory is insufficient. 7-2 Copy-on-Write Snapshot troubleshooting

85 Problem You cannot create the SS pairs. SS pairs are not shown in the volume list. An error occurred while restoring the pair. A volume is blocked. A problem occurred with the software application on the host server that is monitoring the volumes of SS pairs. Causes and solutions You did not following the Pool-VOL requirements. Solutions: Add pool-vols to another pool. Initialize the V-VOL management area. Check pool-vols requirements. For more information, see Data pool requirements and restrictions on page 2-4. Causes: There are not enough differential tables to create the pairs. The conditions to create the pair are not fulfilled. The volumes that are specified to create the pair are in SMPL (PD) status and are in the process of being deleted. Solutions: Secure enough differential tables to create the pairs. Fulfill the conditions to create the pair and try the pair creation again. In the SI Pair Operation window, verify that the status of the volume changes to SMPL, and then try the pair creation again. Using the CCI, do the following: Causes: a. Run the inqraid command. b. Verify that SS is not using the volume. c. Create the pair. The pairs are not created. The filtering function is prohibiting you from showing the pairs. Solutions: Create the pairs. Open the Display Filter dialog box and change the settings. 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 and then the power was restored. Solution: Contact the Hitachi Data Systems customer support for assistance. Cause: Access to the volume is rejected. Solution: 1. On the host server, stop the monitoring software application. 2. Change all pair statuses to PSUS. 3. On the host server, start the monitoring software application. To check whether the host has access to pair volumes, view the P-VOL/S- VOL access columns. For more information about the pair status definitions, see Pair status definitions on page 6-3. Copy-on-Write Snapshot troubleshooting 7-3

86 Problem A V-VOL cannot be recognized correctly after you boot or reboot the host server or after you run the command for recognizing the device or V-VOL on the host server. When the host server tries to access the port, an error occurs and the host cannot access the port. SN frequently times out. Running the Pairsplit command on a consistency group terminates abnormally. Running the Pairsplit command on a consistency group terminates abnormally when P-VOL shared with UR or TC. Causes and solutions Cause: Access to the volume is rejected. Solution: 1. On the host server, stop the monitoring software application. 2. Change all pair statuses to PSUS. 3. Do one of the following: Reboot the host server. Run the command for recognizing the device or V-VOL on the hose server. 4. On the host server, start the monitoring software application. To check whether the host server has access to pair volumes, view the P- VOL/S-VOL access columns. For more information, see Pair status definitions on page 6-3. Cause: A port may go offline because access to a volume on another port is rejected. Solutions: Retry the operation. If you have installed and are running a software application on a host server to monitor the volumes of SS pairs, stop the monitoring software 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: Retry the operation. Verify the SN RMI time-out period. For more information about how to set RMI time-out period, see the Hitachi Storage Navigator User Guide. Causes: All pairs in the consistency group are not in PAIR status. This may result in rejection of the command, Timeout (Error code: EX_EWSTOT), or suspension of the pair (Error code: EX_EWSUSE). During the operation, you run the pairresync or pairsplit-s command on another pair or pairs in the consistency group. This can result in a timeout (Error code: EX_EWSTOT), or suspension of the pair (Error code: EX_EWSUSE) Solutions: Ensure all pairs in the consistency group are in PAIR status and run the pairsplit command. Perform only one operation on the pairs in a consistency group at one time. Error code EX_EWSTOT is generated, and you cannot change the status of some SS pairs in a consistency group. Possible causes: If you use an UR S-VOL as an SS P-VOL, the capacity of the journal volumes for this UR pair is insufficient. 7-4 Copy-on-Write Snapshot troubleshooting

87 Problem Restore pair operation terminates abnormally. Creating consistency groups when host server is down or failed. When you select the data pool, the pool capacity and other information shown in the Summary table is different than the information in the Primary Volumes tab. You cannot resynchronize an SS pair that is in PSUE status. The SS license is invalid. Causes and solutions The SS pair volumes are blocked. The SS pair is in a status for which you cannot run the pairsplit command. For more information about the status that is required for CCI operations, see Statuses required for Command Control Interface pair operations on page A-3. The TC or UR pair status is not PAIR. Solution: 1. Change all of the pairs to the PAIR status. 2. From a command prompt, run the pairsplit command. Causes: The pair s SS data is being stored per consistency group. The P-VOL is also a P-VOL in another pair, and the SS data in the second pair is stored per consistency group. You can create a consistency group that does not contain pairs. However, if the host server is down or failed and you create pairs using the At-Time Split operation, the consistency group may be rejected. Solution: 1. Find the consistency group number. Use the COW Snapshot or Pair Operation window in SN. 2. Create a pair specifying the consistency group number. Cause: The host is copying the pair and writing data. Solution: Wait until the pair is copied and the information shown in the Summary table and the Primary Volumes tab is the same. Cause: The host did not define the SS pair because the pair status changed to PSUE while the host was creating the pair. Solution: 1. Delete all SS pairs associated with the P-VOL. 2. Recreate the SS pairs. For more information about resolving this problem, see Recovering from failure during pairresync -restore operation on page 7-5. Recovering from failure during pairresync -restore operation If a failure occurs while you restore a pair and the pair status changes to PSUE, data in the P-VOL cannot be ensured. Establish consistency in the P- VOL. 1. Delete the pair. 2. Do one of the following: Create a new pair. Copy-on-Write Snapshot troubleshooting 7-5

88 Resynchronize the pair. 3. Overwrite the P-VOL with backup data. For more information about the cause and solution to errors when resynchronizing SS pairs that are in PSUE status, see General troubleshooting on page 7-2. Recovering a terminated HP-UX host server Errors can occur and the HP-UX host server can terminate if you use a volume in a paircreate command that has already been recognized by the host server as a V-VOL. You can recover the terminated HP-UX host server. 1. Force the command process and its parent process to terminate. 2. Create the SS pair. Ensure the emulation type is 0 (OPEN-0V) for both the V-VOL and the VDEV for the V-VOL group. For more information about creating pairs, see Pair operations on page Split the pair. For more information about splitting pairs, see Splitting pairs on page Run the command for recognizing the device or V-VOL on the host server. Recovering a blocked pool workflow When a pool is blocked, recover the pool. Use the following workflow to recover the pool: 1. Recover the pool-vols. To recover a blocked pool-vol, call the Support Center. 2. Recover the pool. To recover the pool, do one of the following: Add additional pool-vols to the pool. Increase unused capacity by deleting the SS data from the pool. Lower the pool s usage by deleting the pairs. 3. Recover the pairs by deleting the pairs. You must delete the pairs because the status of all pairs with SS data in a blocked pool changes to PSUE. To recover the pairs in this status, do the following: a. Delete the pair. b. Recreate the pair. For more information about creating pairs, see Creating pairs on page Recover the V-VOLs. To do this, call the Support Center. 7-6 Copy-on-Write Snapshot troubleshooting

89 Pool-related SIM entry removal workflow Use the following workflow to remove Service Information Messages (SIM) entries from the storage system: 1. Correct the problem related to the SIM. In the System Information/ Status window in SN, check the SIM and correct pool-related SIMs for the following: Reference code 601XXX: The pool usage rate exceeds the threshold. Reference code 602XXX: The pool is blocked. Note: XXX indicates the pool ID. 2. Complete the SIM. The pool status is normal. 3. Change the SIM status to Completed. 4. Complete the SIM. For more information about completing SIMs, see Completing Service Information Messages on page 7-7. Completing Service Information Messages 1. In the Storage Systems tree, click Pools. 2. From the names that appear on the Pools tab, click the pool that you want to complete SIMs. 3. On the Pools tab of the Pools window, select More Actions > Complete SIMs. 4. In the Confirmation window, for Task Name, type a name for the task, and then click Apply. Note: For character and symbol limits and default values, see Complete SIMs window on page B-32. The pool-related SIM is processed. Troubleshooting with Command Control Interface To identify the cause of errors while using CCI, you can use the following logs: The log is shown in the CCI window. For more information, see Identifying errors using the log on the CCI window on page The CCI operation log file. For more information, see Identifying errors using the Command Control Interface operation log file on page 7-15 Copy-on-Write Snapshot troubleshooting 7-7

90 The following table lists the error codes for SSB1: B901, B9A8, B9A9, B9AD, B9AE, and 2E31. For more information about the error codes that are not described in this table, call the Support Center. SSB2 CCI command Cause of error 9100 All commands You cannot run the command because the storage system did not perform user authentication paircreate You cannot create the pair because of a shortage of pair tables paircreate You cannot create the pair because of a shortage of differential tables paircreate You cannot create the pair because the pool is not available paircreate You cannot create the pair because a pair using a pool ID that is different from the specified pool ID exists in the specified P-VOL paircreate You cannot create the pair because another HTI or SS S- VOL is using the volume you specified as the P-VOL paircreate You cannot create the pair because another HTI or SS P- VOL is using the volume you specified as the S-VOL 9705 paircreate You cannot create the pair because another HTI or SS S- VOL is using the volume you specified as the S-VOL paircreate You cannot create the pair because another SS pair is using the specified SS ID paircreate You cannot create the pair because the capacity of the pair that you are trying to create exceeds the licensed capacity All commands The command ends abnormally. You tried to use a command other than the paircreate command for the volume in the pair other than the SS pair. This error can also occur when you run the command with an unsupported parameter All commands The command ends abnormally because the pair is in a status that the command does not accept, or because you ran the command with an unsupported parameter. 971A paircreate You cannot create the pair because you do not have a sufficient amount of shared memory. 971F pairresync - restore The pair cannot be restored 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: You specified an LDEV number for the P-VOL or S-VOL that is not correct. You specified a P-VOL or S-VOL that is not paired. The P-VOL or S-VOL is specifying a pair that is not ready for the specified operation. You specified an MU number (SS ID) that is not correct. You specified an MU number (SS ID) that is already in use. 7-8 Copy-on-Write Snapshot troubleshooting

91 SSB2 CCI command Cause of error You specified a pool that is unusable. You have exceeded the license capacity. The control tables for SS are running out paircreate, pairsplit, pairresync, pairresync - restore The command ends abnormally because SS or SI is not installed All commands The command ends abnormally because additional shared memory (FCv2, TPF, Extension1) does not exist All commands The command ends abnormally because additional shared memory (more than COW1) does not exist All commands The command ends abnormally because the LDEV number of the volume you specified as the P-VOL exceeds the range All commands The command ends abnormally because you specified the unmounted volume as the SS P-VOL paircreate, pairsplit, pairresync, pairresync - restore 9728 paircreate, pairsplit, pairresync, pairresync - restore 9729 paircreate, pairsplit, pairresync, pairresync - restore The command ends abnormally because you specified a blocked volume as the SS P-VOL. The command ends abnormally because you specified a volume that is in the process of being formatted as the SS P-VOL. The command ends abnormally because you specified a volume as the SS P-VOL and that volume has an emulation type other than OPEN-V. 972A paircreate You cannot create the pair because the volume you specified as the SS P-VOL has the command device setting. 972C paircreate You cannot create the pair because the capacity of the volume you specified as the SS P-VOL exceeds the supported size (4TB). 972E paircreate You cannot create the pair because the capacity of the volume you specified as the SS S-VOL exceeds the supported size (4TB). 972F paircreate You cannot create the pair because you specified a V-VOL as the SS P-VOL paircreate You cannot create the pair because you specified a pool- VOL as the SS P-VOL pairresync - restore You cannot create the pair because the SS P-VOL and TC P- VOL share the volume, and the status of the TC pair is not PSUS or PSUE. Copy-on-Write Snapshot troubleshooting 7-9

92 SSB2 CCI command Cause of error 9732 pairresync - restore 9733 pairresync - restore 9734 pairresync - restore You cannot restore the pair because the 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 pair because the SS P-VOL and TC S-VOL share the volume. You cannot restore the pair because the SS P-VOL and UR S-VOL share the volume paircreate You cannot create the pair because you specified UR s journal volume as the SS P-VOL paircreate, pairsplit, pairresync, pairresync - restore The command ends abnormally because the LUSE volumes you specified for the P-VOL and S-VOL do not have the same structure. 973A paircreate You cannot create the pair because you specified a volume with the VMA setting as the SS P-VOL. 973B All commands The command ends abnormally because the LDEV number of the volume you specified as the S-VOL exceeds the range. 973C All commands The command ends abnormally because you specified an unmounted volume as the SS S-VOL. 973D 973E 973F paircreate, pairsplit, pairresync, pairresync - restore paircreate, pairsplit, pairresync, pairresync - restore paircreate, pairsplit, pairresync, pairresync - restore The command ends abnormally because you specified a blocked volume as the SS S-VOL. The command ends abnormally because you specified a volume that is in process of being formatted as the SS S- VOL. The command ends abnormally because you specified a volume whose emulation type is other than OPEN-V as the SS S-VOL paircreate You cannot create the pair because the volume you specified as the SS S-VOL has the command device setting paircreate You cannot create the pair because you specified an external volume as the SS S-VOL paircreate You cannot create the pair because you specified a volume other than V-VOLs as the SS S-VOL paircreate You cannot create the pair because you specified a pool- VOL as the SS S-VOL paircreate You cannot create the pair because you specified a TC P- VOL as the SS S-VOL Copy-on-Write Snapshot troubleshooting

93 SSB2 CCI command Cause of error 9748 paircreate You cannot create the pair because you specified TC S-VOL as the SS S-VOL paircreate You cannot create the pair because you specified a UR data volume or journal volume in the intermediate site of 3DC cascading configuration as the SS S-VOL, the SS pair cannot be created. 974A paircreate You cannot create the pair because you specified a UR P- VOL as the SS S-VOL. 974B paircreate You cannot create the pair because you specified a UR S- VOL as the SS S-VOL. 974C paircreate You cannot create the pair because you specified a UR journal volume as the SS S-VOL. 974F All commands The command ends abnormally because the volume you specified as the S-VOL has an S-VOL Disable attribute paircreate You cannot create the pair because you specified a volume with the VMA setting as the SS S-VOL paircreate, pairsplit, pairresync, pairresync - restore 9753 paircreate, pairsplit, pairresync, pairresync - restore The command ends abnormally because the Max LBA size for the volumes you specified as the SS P-VOL and S-VOL are different. The command ends abnormally because the number of slots of the volumes you specified as the SS P-VOL and S-VOL are different paircreate You cannot create the pair because you specified an HDP V- VOL as the SS S-VOL All commands The command ends abnormally because you specified an SI reserved volume as the SS P-VOL All commands The command ends abnormally because you specified a Volume Migration source volume as the SS P-VOL. For more information about using Volume Migration, call the Support Center All commands The command ends abnormally because you specified a Volume Migration target volume as the SS P-VOL. For more information about using Volume Migration, call the Support Center All commands The command ends abnormally because you specified a Volume Migration reserved volume as the SS P-VOL. For more information about using Volume Migration, call the Support Center. 975A All commands The command ends abnormally because you specified an SI P-VOL as the SS S-VOL. Copy-on-Write Snapshot troubleshooting 7-11

94 SSB2 CCI command Cause of error 975B All commands The command ends abnormally because you specified an SI S-VOL as the SS S-VOL. 975C All commands The command ends abnormally because you specified an SI reserved volume as the SS S-VOL. 975D All commands The command ends abnormally because you specified a Volume Migration source volume as the SS S-VOL. For more information about using Volume Migration, call the Support Center. 975E All commands The command ends abnormally because you specified a Volume Migration target volume as the SS S-VOL. For more information about using Volume Migration, call the Support Center. 975F All commands The command ends abnormally because you specified a Volume Migration reserved volume as the SS S-VOL. For more information about using Volume Migration, call the Support Center paircreate The pair cannot be created for one of the following reasons: The shared memory is not increased. Initialization is in process. 976A paircreate You specified an unavailable parameter (unsupported parameter) in the command. 976C pairsplit SS data cannot be stored because you ran the command when the pair status was PSUE. 976E pairsplit SS data cannot be stored because the SS P-VOL and TC S- VOL share the volume, and the status of the TC pair is COPY. 976F pairsplit SS data cannot be stored because the SS P-VOL and UR S- VOL share the volume, the status of the UR pair is COPY paircreate You cannot create the pair because you specified a UR delta resynchronization pair volume as the SS P-VOL paircreate You cannot create the pair because you specified a UR delta resynchronization pair volume as the SS S-VOL paircreate You cannot create the pair because the SS P-VOL and SI P- VOL share the volume, and the SI pair is using the MU number (SS ID) you specified for the SS pair paircreate You cannot create the pair because the SS P-VOL and SI P- VOL share the volume, and the SI P-VOL you specified for the SS P-VOL has consistency group settings paircreate You cannot create the pair because the SS P-VOL and SI S- VOL share the volume, and you specified MU number zero (0) for the SS P-VOL paircreate You cannot create the pair because the SS P-VOL and SI S- VOL share the volume, and the SI S-VOL you specified for the SS P-VOL has consistency group settings Copy-on-Write Snapshot troubleshooting

95 SSB2 CCI command Cause of error 977A 977B paircreate, pairsplit paircreate, pairsplit The command ends abnormally because the SS P-VOL and SI P-VOL share the volume, and the SI pair was in the process of resynchronization. The command ends abnormally because the SS P-VOL and SI S-VOL share the volume, and SI pair status is not PSUS. 977C pairresync - restore 977D pairresync - restore The command ends abnormally because the SS P-VOL and SI P-VOL share the volume, and SI pair status is not PSUS or PSUE. The command ends abnormally because the SS P-VOL and SI S-VOL share the volume, and SI pair status is not PSUS. 977E pairsplit SS data cannot be stored because the pool or the pool-vol is blocked pairresync - restore 9786 paircreate, pairsplit, pairresync, pairresync - restore 9787 paircreate, pairsplit, pairresync, pairresync - restore The pair cannot be restored for one of the following reasons: The pair s snapshot you want to restore is stored in a consistency group. The pair s P-VOL you want to restore is used as the P- VOL for another SS pair, and the SS data of the latter pair is stored in a consistency group. The command ends abnormally because quorum disks are specified as P-VOLs of SS pairs. The command ends abnormally because quorum disks are specified as S-VOLs of SS pairs. 978A paircreate The pair cannot be created using the consistency group number for one of the following reasons: The specified consistency group number is in use for SI. The number of pairs has already exceeded the maximum number of pairs that can be created for one consistency group. A pair that uses the same P-VOL exists already in the specified consistency group. 978B paircreate You cannot create the pair because the specified consistency group number is out of the range of the number that can be specified. 978C pairsplit SS data cannot be stored because the TC asynchronous pair status is other than PSUS or PSUE when SS (P-VOL) and TC asynchronous (S-VOL) share the volume. Copy-on-Write Snapshot troubleshooting 7-13

96 SSB2 CCI command Cause of error 978E paircreate You cannot create the pair for which you specified the consistency group. The P-VOL or S-VOL of the SI pair is already specified as the P-VOL of the SS pair paircreate You cannot create the pair because you specified an HDP V- VOL that is undergoing capacity expansion as the SS P-VOL paircreate You cannot create the pair because you specified an HDP V- VOL that is undergoing an Unmap command operation with system option mode 905 set to ON paircreate, pairsplit, pairresync, pairresync - restore 9797 paircreate, pairsplit, pairresync, pairresync - restore The command ends abnormally because you specified a volume without path definition as the SS P-VOL. The command ends abnormally because you specified a volume without path definition as the SS S-VOL. 97A1 paircreate If you have already made the maximum number of SS pairs, you cannot create new pairs. 97A2 97A3 paircreate, pairsplit, pairresync, pairresync-restore paircreate, pairsplit, pairresync, pairresync-restore The command ends abnormally because the volume specified as the P-VOL uses two mirrors in a 3 UR data center configuration. The command ends 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 pair because the DP-VOL specified as the SS P-VOL is being initialized. 97A5 97A6 paircreate, pairsplit, pairresync, pairresync - restore paircreate, pairsplit, pairresync, pairresync - restore The command ends abnormally because you specified an external volume that is mapped for online data migration as the SS P-VOL. The command ends abnormally because you specified an external volume that is mapped for online data migration as the SS S-VOL. 97C2 All commands The command ends abnormally because the specified MU number (SS ID) is outside the allowable range. 97C4 paircreate The SS pair cannot be created because the specified pool is not an HTI or SS pool, or the specified pool does not exist. 97CB All Commands You cannot create the SS pair because the specified pool is an HTI pool. 97CE paircreate You cannot create the pair using the command. One of the following can be the reason: 7-14 Copy-on-Write Snapshot troubleshooting

97 SSB2 CCI command Cause of error You specified a consistency group number in HTI that SS is using. You specified a consistency group number in SS that HTI is using. 97D6 97D7 B912 paircreate, pairsplit, pairresync, pairresync - restore paircreate, pairsplit, pairresync, pairresync - restore paircreate, pairsplit, pairresync The command ended abnormally because you specified an LDEV number other than the beginning of a LUSE volume as the SS P-VOL. The command ended abnormally because you specified an LDEV number other than the beginning of a LUSE volume as the SS S-VOL. The pair operation fails because you specified the wrong S- VOL. B9A7 All commands The consistency group information cannot be obtained because SS is not installed. Identifying errors using the log on the CCI window 1. Find the error code from the logs shown on the CCI window. The following figure shows an example of a log shown on the CCI window: Figure 7-1 Example of a log shown on 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). Note: You can view the description of the SSB1/SSB2 error code combination in the table that lists the error codes, above. Identifying errors using the Command Control Interface operation log file 1. Open the CCI log file. The default location is /HORCM/log*/curlog/ horcmlog_host/horcm.log, where: Copy-on-Write Snapshot troubleshooting 7-15

98 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 following figure: 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). Note: You can view the description of the SSB1/SSB2 error code combination in the table that lists the error codes, above Copy-on-Write Snapshot troubleshooting

99 A Command Control Interface command reference This appendix describes Command Control Interface (CCI) commands corresponding to actions in SN. Command Control Interface commands for Storage Navigator operations Storage Navigator and Command Control Interface pair status names Statuses required for Command Control Interface pair operations Command Control Interface command reference A-1

100 Command Control Interface commands for Storage Navigator operations The following table lists a mapping of the operations for logical device and pool that you can perform in SN to the CCI commands. Item SN Operation CCI command Logical Device Create LDEVs raidcom add ldev Delete LDEVs Edit LDEVs raidcom delete ldev raidcom modify ldev Pool Create Pools raidcom add snap_pool Expand Pool Delete Pools Edit Pools Restore Pools raidcom add snap_pool raidcom delete pool raidcom modify pool raidcom modify pool Storage Navigator and Command Control Interface pair status names The CCI pair status name may be different than the SN pair status name. The following table shows a mapping of SN pair status names to CCI pair status names. SN pair status name CCI pair status name SMPL (is not shown) COPY PAIR PSUS RCPY PFUL PFUS PSUE SMPL COPY PAIR SSUS RCPY PFUL PFUS PSUE For more information about the pair status definitions, see Pair status definitions on page 6-3. A-2 Command Control Interface command reference

101 Statuses required for Command Control Interface pair operations The pair must have a specific status to perform pair operations. The following table lists the CCI pair operations and the required status to perform the operation. CCI pair operation Required status paircreate paircreate split pairsplit pairresync pairresync -restore pairsplit -S SMPL PAIR/PFUL PAIR/PFUL PSUS/PFUS, PSUE PSUS/PFUS PAIR/PFUL, PSUS/PFUS, PSUE If you run a command for a pair with a status other than the one required, you can get mixed results. The following table lists the results for CCI commands that you run that have statuses other than those that are required. CCI command Status pair create pair createsplit pair split pair resync pair resyncrestore pair split-s pair split-e SMPL Ok Ab Ab Ab Ab Np Ab COPY Np Ab Ab Np Np Ab Ab PAIR/PFUL Np Ok Ok Np Np Ok Ab PFUS 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 * If you run the pairresync to a pair in PSUE status because you cannot reserve shared memory for the S-VOL management area, the command is rejected and ends abnormally. Command Control Interface command reference A-3

102 A-4 Command Control Interface command reference

103 B Copy-on-Write Snapshot GUI reference This appendix describes SS windows and dialog boxes. Pools window Selected pool volume window Create Pools wizard Expand Pool wizard Edit Pools wizard Delete Pools wizard Restore Pools window Complete SIMs window Select Pool window Select Pool Volumes window Pool Property window Create Pairs wizard Copy-on-Write Snapshot GUI reference B-1

104 Pools window Use the Pools window to view information about pools in your system. You can do the following from this window: Chapter 3, Copy-on-Write Snapshot installation and configuration on page 3-1 Chapter 6, Copy-on-Write Snapshot monitoring and maintenance on page 6-1 Increasing data pool volume capacity on page 6-7 Changing pool volume threshold on page 6-7 Changing pool volume names on page 6-8 Recovering pool volumes on page 6-8 Deleting pool volumes on page 6-9 For more information, see: Summary table on page B-3 Pools tab on page B-3 B-2 Copy-on-Write Snapshot GUI reference

105 Summary table Item Pool Capacity* Description The capacity for the pool. Used/Total For SS: The SS pool capacity (used/total). For each value, if Pool Capacity Estimated Configurable is zero, Estimated Configurable is shown. For SS: The remaining physical pool capacity that is configurable in SS. V-VOL Capacity* Licensed Capacity (Used/ Licensed) Number of Pools Edit Tiering Policies button Shows information about DP-VOL capacity. For SS, a hyphen (-) is shown. For SS, the total licensed system capacity for SI and SS, including the capacities of LDEVs and other resources assigned to other users. The value shown for Licensed Capacity Used can differ from the value shown for Pool Capacity Total. The total number of pools that SS, HDP, HDPz, HDT, and Dynamic Tiering for Mainframe (HDTz) are using. Click to open the Edit Tiering Policies window. For more information about the tasks you can perform from this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. * The total value of Total for Capacity for each pool type in the Pools window and the total Used capacity for Pool Capacity in the Summary table are almost the same, but small differences might occur. Pools tab Use this tab of the Pools window to view specific pool information. Item Pool Name (ID) Status Description The pool s name and identifier. Clicking this link shows additional pool information. Information about the pool status. Values: Normal: The pool is in a normal status and is accessible. Warning: The pool-vol in the pool is blocked. Exceeded Threshold: The pool s used capacity exceeds the pool threshold. Shrinking: Reducing the pool-vol. Copy-on-Write Snapshot GUI reference B-3

106 Item Number of pool volumes Number of V-VOLS Number of Primary VOLs RAID Level Capacity User-Defined Threshold(%) Subscription (%) Pool Type Drive Type/RPM Description Blocked: The pool is full, or an error occurred in the pool, therefore the pool is blocked and cannot be used. If the pool is in both Warning and Blocked status, only Blocked is shown. The number of pool-vols. The number of V-VOLs associated with the pool. For SS, a hyphen (-) is shown. The number of SS P-VOLs. If you are not using the pool for SS, a hyphen (-) is shown. The RAID level. If multiple RAID levels exist in a pool, Mixed is shown. Information about pool capacity. Values: Total: The pool s total capacity Unit of capacity: Click Option to select the unit of capacity. One block equals 512 bytes and one page equals 256 kilobytes in SS pool capacity. Used: The amount of pool capacity that is used. Used (%): The percentage of pool capacity that is used. If you clicked Option to change the unit of capacity to Cylinder, a hyphen (-) is shown. Information about the pool threshold. Values: Warning: Warning threshold is shown. Depletion: Depletion threshold is shown. For SS, a hyphen (-) is shown. Caution: You must define both user-defined thresholds. Defining only one of the user-defined pool thresholds enables the system threshold (fixed at 80%). If the pool s used capacity exceeds the user-defined threshold, SIM code 620XXX is reported. You cannot set the system threshold. Shows the following information about the pool s subscription: Current: Current subscription. For SS, a hyphen (-) is shown. Limit: Subscription limit. For SS, a hyphen (-) is shown. Shows the type of pool. Value: COW Snapshot The pool s hard disk drive type and RPM. B-4 Copy-on-Write Snapshot GUI reference

107 Item Tier Management CLPR Shrinkable Monitoring Mode Monitoring Status Recent Monitor Data Pool Management Task Recent Relocation Progress Mixable* Create Pools button Create LDEVs button Expand Pool button Description If multiple drive types or RPMs exist in a pool, Mixed is shown. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. Shows whether HDT is enabled or disabled. For SS, a hyphen (-) is shown. The CLPR (cache logical partition) set for the pool-vol. For pools other than for SS, a hyphen (-) is shown. Shows whether you can delete the pool-vol. For SS, a hyphen (-) is shown because its pool is not shrinkable. The monitoring mode set for the pool, Continuous Mode or Period Mode. The status of pool monitoring. Conditions: In Progress: Monitoring is being performed. During Computation: Calculating is being processed. If a condition is not present, a hyphen (-) is shown. The latest monitoring data. Values: If monitoring data exists, the monitoring period of time is shown. Example: 2010/11/15 00: /11/15 23:59 If monitoring data is being obtained, only the starting time is shown. Example: 2010/11/15 00:00 - If the latest monitoring data does not exist, a hyphen (-) is shown. The pool management task being performed on the pool. For SS and HTI pools, a hyphen (-) is shown. The rate for recent tier relocation processing. Shows whether pool-vols whose RAID levels are different can coexist in the pool. For SS, a hyphen (-) is shown. Click to open the Create Pools window. Click to open the Create LDEVs window of the Create LDEVs wizard. For more information about the tasks you can perform from this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Click to open the Expand Pool window. Copy-on-Write Snapshot GUI reference B-5

108 Item More Actions > Delete Pools More Actions > Restore Pools More Actions > Edit Pools More Actions > Monitor Pools More Actions > Stop Monitoring Pools More Actions > Start Tier Relocation More Actions > Stop Tier Relocation More Actions > Complete SIMs More Actions > View Tier Properties More Actions > View Pool Management Status More Actions > Export More Actions > Tier relocation log Description Click to open the Delete Pools window. Click to open the Restore Pools window. Click to open the Edit Pools window. Click to open the Monitor Pools window. Click to open the Stop Monitoring Pools window. Click to open the Start Tier Relocation window. Click to open the Stop Tier Relocation window. Click to open the Complete SIMs window. (HDT or HDTz only) Click to open the View Tier Properties window. Click to open the View Pool Management Status window. Click to open a window to export table information. Click to open the download screen for tier relocation operation results. * Does not appear in the default view. Selected pool volume window Use the selected pool volume window to view information about the pool-vol you have selected and its associated P-VOL. The following image shows this window. B-6 Copy-on-Write Snapshot GUI reference

109 Summary table Item Description Status Pool Name (ID) Pool VOL with System Area (Name) Pool Type Shows the following information about the pool status: Values: Normal: The pool is in a normal status and is accessible. Warning: The pool-vol is blocked. Exceeded Threshold: The pool s used capacity exceeds the pool threshold. Shrinking: Reducing the pool-vol. Blocked: The pool is full, or an error occurred in the pool, therefore the pool is blocked and cannot be used. If the pool is in both Warning and Blocked status, only Blocked is shown. The pool s name and identifier. The pool s LDEV ID and LDEV name. For SS, a hyphen (-) is shown. The pool s type. Value: COW Snapshot Copy-on-Write Snapshot GUI reference B-7

110 Item Description RAID Level Drive Type/RPM CLPR Cache Mode Number of Pool VOLs Number of V-VOLs Number of Primary VOLs Pool Capacity (Used/Total) V-VOL Capacity (Used/ Total) Subscription (Current/Limit) User-Defined Threshold (Warning/Depletion) Tier Management Cycle Time Monitoring Period Monitoring Mode Monitoring Status The pool s RAID level. For multiple RAID levels in a pool, Mixed is shown. The pool s data drive type and RPM. For multiple Drive Type/RPMs in a pool, Mixed is shown. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. The CLPR configured in SS pool-vol in ID:CLPR name form. For pool-vols other than for SS, a hyphen (-) is shown. Shows whether cache mode is enabled or disabled. For non-external volume configurations, a hyphen (-) is shown. The number of pool-vols set for the pool, and the maximum number of pool-vols that you can set. The number of V-VOLs associated with the pool. For SS, a hyphen (-) is shown. The number of SS P-VOLs. For pools other than for SS, a hyphen (-) is shown. The used and total pool capacity. If the pool consists of multiple pool-vols, the sum of their capacities is shown for Total. The used and total V-VOL capacity. For SS, a hyphen (-) is shown. The subscription rate. For SS, a hyphen (-) is shown. Information about the pool threshold. Values: Warning and Depletion For SS, a hyphen (-) indicates a depletion. Shows whether HDT is enabled or disabled. For SS, a hyphen (-) is shown. The cycle of performance monitoring and tier relocation. If HDT is disabled, a hyphen (-) is shown. The starting and ending of performance monitoring times. If HDT is disabled, a hyphen (-) is shown. The monitoring mode set for the pool, Continuous Mode or Period Mode If HDT or HDTz is disabled, a hyphen (-) is shown. Pool monitoring status. If the monitoring is being performed, In Progress is shown; otherwise a hyphen (-) is shown. B-8 Copy-on-Write Snapshot GUI reference

111 Item Recent Monitor Data Pool Management Task Relocation Result Description The latest monitoring data is shown, as follows: If the monitoring data exists, the monitoring period of time is shown. Example: 2010/11/15 00: /11/15 23:59 If the monitoring data is being obtained, only the starting time is shown. Example: 2010/11/15 00:00 - If the latest monitoring data does not exist, a hyphen (-) is shown. The pool management task being performed on the pool. For SS, a hyphen (-) is shown. The status of the tier relocation processing. For pools other than for HDT or HDTz, a hyphen (-) is shown. Pool Volumes tab Use the Pool Volumes tab to view specific pool-vol information. Item Description LDEV ID LDEV Name Status Parity Group ID Usable Capacity RAID Level Emulation Type Drive Type/RPM The pool-vol s LDEV identifier. The pool-vol s LDEV name. Shows the following information about the pool status. Values: Normal: The pool-vol is in normal status and is accessible. Shrinking: Reducing the pool-vol. Blocked: The pool-vol is blocked and cannot be accessed. The parity group ID. Shows available capacity of page boundaries in a pool-vol by the specified unit. For a pool-vol with system area, the shown capacity does not include the capacity of the management area For HDP, HDT, and SS pools, if you change the unit of capacity to Cylinder, a hyphen (-) is shown. The pool-vol s RAID level. If multiple RAID levels exist in a pool, Mixed is shown. The pool-vol s emulation type. The pool-vol s data drive type and RPM. Copy-on-Write Snapshot GUI reference B-9

112 Item Description (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. Tier ID Provisioning Type Shrinkable Resource Group Name (ID) Expand Pool Shrink Pool Stop Shrinking Pools More Actions > Edit External LDEV Tier Rank More Actions > Export The tier ID. For SS, a hyphen (-) is shown. The pool-vol LDEV s provisioning type. Basic: Internal volume External: External volume Shows whether you can delete the pool-vol. For SS, a hyphen (-) is shown. The resource group name and identifier of the LDEV. The ID is in parentheses. Click to open the Expand Pool window. Click to open the Shrink Pool window. Click to open the Stop Shrinking Pools window. Click to open the Edit External LDEV Tier Rank window. For more information about the tasks you can perform from this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. You can performs tasks on HDP, HDPz, HDT, and HDTz pools. Click to open the window to export table information. Virtual Volumes tab This tab is shown for all pools except HTI and SS pools. Item Description LDEV ID LDEV Name Status The LDEV s identifier. The LDEV s name. The LDEV s status. Values: Normal: The P-VOL s LDEV is in normal status and is accessible. Blocked: The P-VOL s LDEV is blocked. The host cannot access the volume. Warning: The host has detected a problem in the P-VOL LDEV. Formatting: The host is formatting the P-VOL s LDEV. B-10 Copy-on-Write Snapshot GUI reference

113 Item Emulation Type Capacity - Total Capacity - Used Capacity - Used(%) Number of Paths CLPR Tiering Policy Tiering Policy - New Page Assignment Tier Tier Relocation Description Preparing Quick Format: The host is preparing to quick format the P-VOL s LDEV. Quick Formatting: The host is quick formatting the P-VOL s LDEV. Correction Access: The host is correcting the access attribute for the P-VOL s LDEV. Copying: The host is copying data in the P-VOL s LDEV. Read Only: The P-VOL s LDEV data is read-only. The host cannot write data. Shredding: The host is shredding the P-VOL s LDEV data. -: The P-VOL s LDEV has a status other than the ones listed. The LDEV s emulation type. The total V-VOL capacity. Note: This amount might be larger than the Capacity - Used amount. The V-VOL used capacity, which is the rounded-up amount on each page. If the emulation type is 3390-A, this amount includes the control cylinder capacity (7 Cyl is required per 1,113 Cyl). The V-VOL usage level. The number of alternate paths. The CLPR in the format, ID:CLPR. The tiering policy name and ID. Values: All(0): The policy for which you are using all of the tiers in the pool. Level1(1) - Level31(31): The user definition policy for any V-VOL Level1 to Level31 tier. A hyphen (-) is shown if the V-VOL is not an HDT or HDTz V-VOL. The new page assignment tier. Values: High, Middle, or Low A hyphen (-) is shown if the V-VOL is not an HDT or HDTz V-VOL. The tier relocation status. Values: Enabled or Disabled Copy-on-Write Snapshot GUI reference B-11

114 Item Relocation Priority Pool Management Task V-VOL Management Task Page Status Attribute Resource Group Name (ID) Create LDEVs button Add LUN Paths button Expand V-VOLs button More Actions > Format LDEVs Description A hyphen (-) is shown if the V-VOL is not an HDT or HDTz V-VOL. The tier relocation priority. Values: Prioritized: You have set the V-VOL priority. Blank: You have not set the V-VOL priority. A hyphen (-) is shown if the tier relocation functionality is disabled or if the V-VOL is not an HDT or HDTz V-VOL. The pool management task being performed on the pool. For SS and HTI pools, a hyphen (-) is shown. The V-VOL management task that you are performing. Values: Reclaiming Zero Pages: You are reclaiming zero pages. Waiting for Zero Page Reclaiming: The storage system has not started the process to reclaim zero pages. A hyphen (-) is shown if you are not performing a V-VOL management task. Shows the status of reclaiming zero pages. If you are reclaiming zero pages, Reclaiming Zero Pages is shown. If not, this item is blank. The LDEV s attribute. Value: TSE is shown if the volume is a TSE-VOL. A hyphen (-) is shown if you have not defined the volume. The resource group names and identifiers of the LDEV. The ID is provided in parentheses. Click to open the Create LDEVs window of the Create LDEVs wizard. For more information about the tasks you can perform from this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Click to open the Add LUN Paths window. For more information about the tasks you can perform from this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. This item is not available if you select Dynamic Provisioning for Mainframe or Dynamic Tiering for Mainframe as the Pool Type. Click to open the Expand V-VOLs window. For more information about the tasks you can perform using this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Click to open the Format LDEVs window. B-12 Copy-on-Write Snapshot GUI reference

115 Item More Actions > Delete LDEVs More Actions > Shred LDEVs More Actions > Delete LUN Paths More Actions > Block LDEVs More Actions > Restore LDEVs More Actions > Edit LDEVs More Actions > Reclaim Zero Pages More Actions > Stop Reclaiming Zero Pages More Actions > View Tier Properties More Actions > Export Description For more information about the tasks you can perform using this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Click to open the Delete LDEVs window. Click to open the Shred LDEVs window. Click to open the Delete LUN Paths window. For more information about the tasks you can perform using this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Click to open the Block LDEVs window. For more information about this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Click to open the Restore LDEVs window. For more information about this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Click to open the Edit LDEVs window. Click to open the Reclaim Zero Pages window. For more information about this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Click to open the Stop Reclaiming Zero Pages window. For more information about this window, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. Click to open the View Tier Properties window. Click to open the window to export table information. Primary Volumes tab Use the Primary Volumes tab to view specific P-VOL information for an LDEV. Copy-on-Write Snapshot GUI reference B-13

116 Item Description LDEV ID LDEV Name Status The P-VOL s LDEV identifier. The P-VOL s LDEV name. The LDEV s status. Values: Normal: The P-VOL s LDEV is in normal status and is accessible. Blocked: The P-VOL s LDEV is blocked. The host cannot access the volume. Warning: The host has detected a problem in the P- VOL LDEV. Formatting: The host is formatting the P-VOL s LDEV. Preparing Quick Format: The host is preparing to quick format the P-VOL s LDEV. Quick Formatting: The host is quick formatting the P-VOL s LDEV. Correction Access: The host is correcting the access attribute for the P-VOL s LDEV. Copying: The host is copying data in the P-VOL s LDEV. Read Only: The P-VOL s LDEV data is read-only. The host cannot write data. Shredding: The host is shredding the P-VOL s LDEV data. B-14 Copy-on-Write Snapshot GUI reference

117 Item Emulation Type Used Pool Capacity Pool Usage (%) Number of Paths CLPR Export button Description -: The P-VOL s LDEV has a status other than the ones listed. The LDEV s emulation type. The pool s used capacity. The ratio of the pool s used capacity to its full capacity. The number of alternate paths. The CLPR in the format, ID:CLPR. Click to open the Export window to output P-VOL information to a file. Create Pools wizard Use this wizard to create pools. For more information about creating pools, see Creating data pools on page 3-2. Create Pools window Copy-on-Write Snapshot GUI reference B-15

118 Setting items In the following table, items that are marked with an asterisk (*) require configuration. Item Description Pool Type* System Type The pool s type. Value: COW Snapshot The system type. Value: Open B-16 Copy-on-Write Snapshot GUI reference

119 Item Multi-Tier Pool Drive Type/RPM* RAID Level* Select Pool VOLs button* Total Selected Pool Volumes Total Selected Capacity Pool Name* Initial Pool ID Subscription Limit (%) Warning Threshold Depletion Threshold Tier Management Monitoring Mode Description You can only select Open if the pool type is COW Snapshot. HDP/HDT only. The pool-vol s hard disk drive type and RPM. Values: Mixable: This value is shown if the volume is nn HDT volume. External Storage: This value is shown if the volume is an external volume. The pool-vol s RAID level. Values: Hyphen (-): If you select External Storage as the Drive Type/RPM, a hyphen (-) is shown. Mixable: This value is shown if the volume is an HDP/HDT volume. Click to open the Select Pool Volumes window. You must select a pool-vol. The total number of the selected pool-vols. The total capacity of the selected pool-vols. Set the pool name: Prefix: Type the alphanumeric characters, which are fixed characters before the pool name. Case-sensitive: Yes Initial Number: Type the initial number following the prefix name. Limit: 9 digits Character limit: 32 Entering the registered pool ID, adds the smallest available pool ID automatically registered among the subsequent pool ID that you entered. Default: The smallest available number Limit: 0 to 127 If an available pool ID does not exist, this item is blank. The pool s subscription limit. For SS, this item is unavailable. The pool s warning threshold. Limit: 20% to 95%, in 5% increments Default: 80% For SS, this item is unavailable. HDP/HDT only. HDP/HDT only. Copy-on-Write Snapshot GUI reference B-17

120 Item Description Buffer Space for New page assignment (%) Buffer Space for Tier relocation (%) HDP/HDT only. HDP/HDT only. Selected pools table Item Pool Name (ID) Description The pool s nickname and identifier. B-18 Copy-on-Write Snapshot GUI reference

121 RAID Level Capacity Pool Type Item Drive Type/RPM User-Defined Threshold (%) Subscription Limit (%) Number of Pool VOLs Multi-Tier Pool Buffer Space for New page assignment (%) Buffer Space for Tier relocation (%) Detail Remove The pool s RAID level. Description If multiple RAID levels exist in a pool, Mixed is shown. The pool s maximum capacity. The pool s type. Value: COW Snapshot The data drive type and RPM. If multiple types of drives exist in a pool, Mixed is shown. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. Information about the pool threshold. Values: Warning: The warning threshold is shown. Depletion: The depletion threshold is shown. For SS, a hyphen (-) is shown. The pool s subscription limit. For SS, a hyphen (-) is shown. The number of pool-vols. HDP/HDT only. HDP/HDT only. HDP/HDT only. When you select a line, the Pool Properties window opens. You must select a line. If you do not select a line or if you select multiple lines, an error window opens. Deletes the pool selected in the Selected Pools window. You must select a line. If you do not select a line, an error window opens. Copy-on-Write Snapshot GUI reference B-19

122 Confirm window Create Pools table Item Pool Name (ID) RAID Level Capacity Pool Type Drive Type/RPM User-Defined Threshold (%) Description The pool s nickname and identifier. The pool s RAID level. The pool s capacity. The type of pool. Value: COW Snapshot The data drive type and RPM. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. Information about the pool threshold. Values: Warning: Warning threshold is shown. Depletion: Depletion threshold is shown. For SS pools, a hyphen (-) is shown. B-20 Copy-on-Write Snapshot GUI reference

123 Item Subscription Limit (%) Number of Pool VOLs Multi-Tier Pool Buffer Space for New page assignment (%) Buffer Space for Tier relocation (%) Detail Total The pool s subscription limit. Description For SS, a hyphen (-) is shown. The number of pool-vols. HDP/HDT only. HDP/HDT only. HDP/HDT only. When you select a line, the Pool Properties window opens. You must select a line. If you do not select a line or if you select multiple lines, an error window opens. The total number of pools. Expand Pool wizard The Expand Pool wizard consists of the Expand Pool window and the Confirm window. Use the Expand Pool wizard to increase data pool capacity. For more information about increasing data pool capacity, see Increasing data pool volume capacity on page 6-7. Expand Pool window The Expand Pool window is the first window in the Expand Pool wizard. This window shows the Pool Volume Selection area. Copy-on-Write Snapshot GUI reference B-21

124 Pool Volume Selection area Use the Pool Volume Selection area of the Expand Pool window to define the drive type and RAID level for LDEVs you are adding to increase the pool capacity. Item Drive Type/RPM RAID Level Select Pool VOLs button Total Selected Pool Volumes Description The drive type and RPM of the selected pool. Values: Mixable External Storage: Shows if the volume is an external volume. For SS whose RAID level is fixed, this item is unavailable. Click to open the Select Pool Volumes window. The total number of selected pool-vols. B-22 Copy-on-Write Snapshot GUI reference

125 Item Total Selected Capacity Description The total capacity of the selected pool-vols. Confirm window The Confirm window is the second window in the Expand Pool wizard. This window shows the Selected Pool table and the Selected Pool Volumes table. Use this window to do the following: 1. Type a name for the task. 2. Confirm the settings in the list. 3. Add the task to the Tasks queue so that the operation is performed. Selected Pool table Use the Selected Pool table to view the list of pools that are selected. Copy-on-Write Snapshot GUI reference B-23

126 Item Pool Name (ID) Description The pool s nickname and identifier. Selected Pool Volumes table Use the Selected Pool Volumes table to view the list of pool-vols that are selected. Item Description LDEV ID LDEV Name Capacity Parity Group ID RAID Level Drive Type/RPM Emulation Type Total The pool-vol s LDEV identifier. The pool-vol s LDEV name. The pool-vols's capacity. The pool-vol s parity group ID. Does not apply to SS, whose RAID level is fixed. The hard disk drive type and RPM. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. The pool-vol s emulation type. The total number of pool-vols. Edit Pools wizard Edit Pools window The Edit Pools wizard consists of the Edit Pools window and the Confirm window. Use the Edit Pools wizard to change a pool name and threshold. For more information about editing pools, see: Changing pool volume names on page 6-8 Changing pool volume threshold on page 6-7 The Edit Pools window is the first window in the Edit Pools wizard. This window shows the Setting items area. B-24 Copy-on-Write Snapshot GUI reference

127 Setting items area Use this area of the Edit Pools window to edit the pool s properties. Item Multi-Tier Pool Options for Multi-Tier Pool Subscription Limit Pool Name Description For SS, this item is unavailable. For SS, this item is unavailable. For SS, this item is unavailable. Select the Pool Name check box to enter the pool name: If the check box is not selected, the setting is not applied. Prefix: Type the alphanumeric characters, which are fixed characters before the pool name. Case-sensitive: Yes Initial Number: Type the initial number for the pool name. Copy-on-Write Snapshot GUI reference B-25

128 Item Warning Threshold Depletion Threshold Limit: 9 digits Character limit: 32 Description Default: When you select one pool, for Prefix, the pool name is shown. When multiple pools are selected, the numbers ranging from the specified Initial Number to the maximum number of the same digits are automatically set to the pool name. Examples: If you set the Initial Number at 1, a number from 1 to 9 is automatically added to each pool name. If you set the Initial Number at 08, a number from 08 to 99 is added to each pool name. If you set the Initial Number to 098, a number from 098 to 999 is added to each pool name. Information about the pool s warning threshold. Select and type the threshold value. Minimum threshold: Pool usage rate plus one percent (1%) Maximum threshold: 95 percent (95%) For SS, this item is unavailable. Confirm window The Confirm window is the second window in the Edit Pools wizard. This window shows the Selected Pools table. Use this window to do the following: 1. Type a name for the task. 2. Confirm the settings in the list. 3. Add the task to the Tasks queue so that the operation is performed. The following image shows the Selected Pools table. B-26 Copy-on-Write Snapshot GUI reference

129 Selected Pools table Use the Selected Pools table to view the list of pools that are selected. The following tables provides descriptions of the items in the Selected Pools table. Item Pool Name (ID) RAID Level Capacity Pool Type Drive Type/RPM Description The pool s nickname and identifier. The RAID level. If multiple RAID levels exist in a pool, Mixed is shown. The pool capacity. The type of pool. Value: COW Snapshot The data drive type and RPM. Copy-on-Write Snapshot GUI reference B-27

130 Item User-Defined Threshold (%) Subscription Limit (%) Number of Pool VOLs Multi-Tier Pool Buffer Space for New page assignment (%) Buffer Space for Tier relocation (%) Total Description If multiple types of drives exist in a pool, Mixed is shown. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. Information about the pool threshold. For SS, a hyphen (-) is shown. The subscription limit. For SS, a hyphen (-) is shown. The number of pool-vols. HDT information. For SS, this item is unavailable. For SS, this item is unavailable. For SS, this item is unavailable. The total number of pools. Delete Pools wizard The Delete Pools wizard consists of the Delete Pools window and the Confirm window. Use the Delete Pools wizard to delete a pool-vol and make the pool-vol available for other use. For more information about deleting pools, see Deleting pool volumes on page 6-9. Delete Pools window The Delete Pools window is the first window in the Delete Pools wizard. This window shows the Selected Pools table. You can do the following from this window: Go to the next page where you can shred the LDEVs for the selected pool. To do this, click Next. Confirm the deletion. Click Finish. The following image shows the Delete Pools window of the Delete Pools wizard. B-28 Copy-on-Write Snapshot GUI reference

131 Selected Pools table Use this table on the Delete Pools window to view the list of pools that are selected. Item Pool Name (ID) RAID Level Capacity Pool Type Drive Type/RPM User-Defined Threshold (%) Description The pool s nickname and identifier. The pool s RAID level. If multiple RAID levels exist in a pool, Mixed is shown. The pool capacity. For LUSE, shows the LUSE capacity. The type of pool. Value: COW Snapshot The pool s hard disk drive type and RPM. If multiple types of drives exist in a pool, Mixed is shown. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. Information about the pool threshold. Values: Warning: Warning threshold is shown. Depletion: Depletion threshold is shown. Copy-on-Write Snapshot GUI reference B-29

132 Item Number of Pool VOLs Detail Description For SS, a hyphen (-) is shown. The number of pool-vols. When you select a line, the Pool Properties window opens. You must select a line. If you do not select a line or if you select multiple lines, an error window opens. Confirm window The Confirm window is the second window in the Delete Pools wizard. This window shows the Selected Pools table. Use this window to do the following: 1. Type a name for the task. 2. Confirm the settings in the list. Note: Ensure that you want to delete the listed pool-vols. 3. Add the task to the Tasks queue so that the operation is performed. B-30 Copy-on-Write Snapshot GUI reference

133 Selected Pools table Use this table on the Confirm window of the Delete Pools wizard to view the list of pools that are selected. Item Pool Name (ID) RAID Level Capacity Pool Type Drive Type/RPM User-Defined Threshold (%) Number of Pool VOLs Detail button Total Description The pool s nickname and identifier. The pool s RAID level. If multiple RAID levels exist in a pool, Mixed is shown. The pool capacity. In LUSE, shows the LUSE capacity. The type of pool. Value: COW Snapshot The hard disk drive type and RPM. If multiple types of drives exist in a pool, Mixed is shown. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. Information about the pool threshold. For SS, a hyphen (-) is shown. The number of pool-vols. Select a line and click to open the Pool Properties window. The total number of pools. Restore Pools window Use the Restore Pools window to recover a blocked pool. For more information about recovering pools, see Recovering pool volumes on page 6-8. This window shows the Selected Pools table. Copy-on-Write Snapshot GUI reference B-31

134 Selected Pools table Use the Selected Pools table to view the list of pools that are selected. Item Pool Name (ID) RAID Level Capacity Pool Type Drive Type/RPM User-Defined Threshold (%) Number of Pool VOLs Description The pool s nickname and identifier. The pool s RAID level. If multiple RAID levels exist in a pool, Mixed is shown. The pool capacity. If the pool is blocked and the pool-vols that belong to the pool cannot be identified, 0 is shown. The type of pool. Value: COW Snapshot The hard disk drive type and RPM. If multiple types of drives exist in a pool, Mixed is shown. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. Information about the pool threshold. For SS, a hyphen (-) is shown. The number of pool-vols. Complete SIMs window Use the Complete SIMs window to remove the SIM entry from the system. For more information about removing SIMs, see Pool-related SIM entry removal workflow on page 7-7. B-32 Copy-on-Write Snapshot GUI reference

135 This window shows the Setting items area. Setting items area Use the Setting items area of the Complete SIMs window to type the task name and add the task to the Tasks queue so that the operation is performed. Item Description Task Name The task name. Character and symbol limit: 32 Allowable characters and symbols: All alphanumeric except / :, ; *? < > Case-sensitive: Yes Default: date-window name Copy-on-Write Snapshot GUI reference B-33

136 Select Pool window Available Pools table Item Pool Name (ID) RAID Level Capacity Drive Type/RPM User-Defined Threshold (%) CLPR Description The pool s nickname and identifier. The pool s RAID level. The pool s capacity. Values: Total: The total pool capacity. Used: The amount of pool capacity that is used. Used (%): The percentage of pool capacity that is used. The hard disk drive type and RPM. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. Information about the pool threshold. The ID and name of the CLPR in the CLPR-name format. B-34 Copy-on-Write Snapshot GUI reference

137 Select Pool Volumes window Copy-on-Write Snapshot GUI reference B-35

138 Available Pool Volumes table The following table shows descriptions of the items in the Available Pool Volumes table. Item Description LDEV ID LDEV Name Capacity Parity Group ID RAID Level Drive Type/RPM Emulation Type Provisioning Type The LDEV s identifier. The LDEV s name. The pool-vol capacity. The parity group ID. The RAID level. The hard disk drive type and RPM. (External LDEVs) External Storage is shown. The LDEV s emulation type. The LDEV type. Values: Basic: Internal volume B-36 Copy-on-Write Snapshot GUI reference

139 Item Description External: Shows if the LDEV is an external volume. CLPR Cache Mode Resource Group Name (ID) Shows cache logical partition. Shows whether the cache mode is enabled or disabled. For non-external volumes, a hyphen (-) is shown. The resource group names and identifiers of the LDEV. The ID is provided in parentheses. The External LDEV Tier Rank specifies the external LDEV tier rank. If an external LDEV does not exists in the Available Pool Volumes table or Selected Pool Volumes table, you cannot select the tier rank. Selected Pool Volumes table You can add a maximum of 1,024 volumes, including volumes that already exist in the pool. For more information about the maximum number of volumes, see Consistency group system requirements on page 2-2. Copy-on-Write Snapshot GUI reference B-37

140 Item Description LDEV ID LDEV Name Capacity Parity Group ID RAID Level Drive Type/RPM External LDEV Tier Rank Emulation Type Provisioning Type CLPR Cache Mode Resource Group Name (ID) The LDEVs identifier. The LDEV s name. The pool-vol capacity. The parity group ID. Show the RAID level. The data drive type and RPM. (External LDEVs) External Storage is shown. The external volume tier rank. For non-external volume, a hyphen (-) is shown. The LDEV s emulation type. The LDEV type. Values: Basic: Internal volume External: External volume Shows cache logical partition. Shows the cache mode. Values: Enabled or Disabled For non-external volumes, a hyphen (-) is shown. The resource group names and identifiers of the LDEV. The ID is provided in parentheses. B-38 Copy-on-Write Snapshot GUI reference

141 Pool Property window Pool Properties table Item Description Pool Name (ID) Pool Type Capacity User-Defined Threshold (Warning/Depletion) Subscription Limit RAID Level CLPR The pool s name and identifier. The pool s type. Value: COW Snapshot The pool capacity by the specified unit. Information about the pool threshold. Values: Warning and Depletion The subscription limit. For SS, a hyphen (-) is shown. The RAID level. Shows the CLPR configured in SS pool- VOL in ID:CLPR name form. For pool-vols other than for SS, a hyphen (-) is shown. Copy-on-Write Snapshot GUI reference B-39

142 Item Pool VOL with System Area (Name) Description The pool-vol s LDEV ID and LDEV name that contains the pool s management area. For SS, a hyphen (-) is shown. Pool Volumes table Item Description LDEV ID LDEV Name Capacity Parity Group ID RAID Level Drive Type/RPM Emulation Type Provisioning Type Resource Group Name (ID) The pool-vol s LDEV identifier. The pool-vol s LDEV name. The pool-vol capacity by the specified unit. The pool-vol s parity group ID. The pool-vol s RAID level. The hard disk drive type and RPM. (External LDEVs) External Storage and the value of the external LDEV tier rank is shown. The pool-vol s emulation type. The pool-vol s provisioning type. Values: Basic: Internal volume External: External volume The resource group names and identifiers of the LDEV. The ID is provided in parentheses. Create Pairs wizard The Create Pairs wizard consists of the Create Pairs window. Use the Create Pairs wizard in this window to create pairs. B-40 Copy-on-Write Snapshot GUI reference

143 Select Pair Configuration window Item Description Copy Type Emulation Type Pair Topology Type The copy type. Values: ShadowImage ShadowImage for Mainframe Thin Image COW Snapshot The emulation type. Value: OPEN-V For HTI or SS, you can only specify OPEN-V. This item is shown only when you specify SI as the copy type. Specify the SI pair configuration. If you specify the existing pair to open this window, the pair topology type is shown as the pair configuration. The checkbox is: Not selected, but available: You can set a pair configuration. Selected, but not available: The SI pair exists. Neither selected nor available: You cannot set a pair configuration. Number of secondary volumes Specify the total number of S-VOLs assigned to one P- VOL. This includes existing pairs. For SI, this item is blank. Initial MU number The initial MU number. Limits: 0 to 63 For SI and HTI, zero (0) is shown. Copy-on-Write Snapshot GUI reference B-41

144 Select Primary Volumes window Item Use Primary Volumes of Snapshot Pairs Port ID Host Group Name Select Pool button Add Remove Description Specifies whether the SS pair s P-VOL is used or not. Values: Yes: Only the existing pair s P-VOLs are shown in the Available LDEVs table. No: Only the pair s LDEV that have not yet been created are shown in the Available LDEVs table. For SI and ShadowImage for Mainframe, this item is blank. Port name of the LDEV s LUN path. For ShadowImage for Mainframe, this item is blank. Host group name of the LDEV s LUN path. Default: Any For ShadowImage for Mainframe, this item is blank. Click to open the Select Pool window. Use this window to name and identify the pool. If you select Yes as the Use Primary Volumes of Snapshot Pairs, this button in unavailable. In SI or in ShadowImage for Mainframe, data is not shown. Adds the selected LDEVs from the Available LDEVs table to the Selected LDEVs table. Returns the selected LDEVs from the Selected LDEVs table back to the Available LDEVs table. B-42 Copy-on-Write Snapshot GUI reference

145 Available LDEVs table Item Description LDEV ID LDEV Name Port ID LUN ID Host Group Name Provisioning type Emulation type Capacity CLPR Number of Secondary Volumes Primary Volumes Mirror unit Pool Name (ID) The identifier of the LDEV. You can specify the LDEV identifier as the P-VOL. The name of the LDEV. The port name of the LDEV s LUN path. For ShadowImage for Mainframe, this item is blank. LUN ID of the LDEV's LUN path. For ShadowImage for Mainframe, this item is blank. Host group name of the LDEV s LUN path. For ShadowImage for Mainframe, this item is blank. Provisioning type of the LDEV. Values: Basic: Internal volume HDP: DP-VOL External: External volume The emulation type of the LDEV. The capacity of the LDEV. The CLPR number of the LDEV. Shows the number of S-VOLs. If you use the LDEV as an S-VOL for an existing pair, shows information about the P-VOL. Values: LDEV ID: LDEV identifier LDEV Name: LDEV name Port ID: Port name of the LDEV s LUN path Host Group Name: Host group name of the LDEV s LUN path LUN ID: 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 For SI or SIz, this item is blank. The mirror unit number. If you are not using the LDEV as a S-VOL for an existing pair, a hyphen (-) is shown. For SI or SIz, this item is blank. The pool s name and identifier. For SI or SIz, this item is blank. Copy-on-Write Snapshot GUI reference B-43

146 Selected LDEVs table Item Description LDEV ID LDEV Name Port ID Host Group Name LUN ID Provisioning type Emulation type Capacity CLPR Number of Secondary Volumes Primary volume Mirror unit Pool Name (ID) Selected P-VOL s LDEV identifier Selected P-VOL s LDEV name Port name of the LDEV s LUN path. For SIz, this item is blank. Host group name of the LDEV s LUN path. For SIz, this item is blank. LUN ID of the LDEV's LUN path. For SIz, this item is blank. Type of LDEV Values: Basic: Internal volume HDP: DP-VOL External: External volume Emulation type of LDEV Capacity of LDEV CLPR number Shows the number of S-VOLs. The information about the P-VOL is shown if the LDEV is the S-VOL of the existing pair. Values: LDEV ID: P-VOL s LDEV identifier: LDEV Name: P-VOL s LDEV name Port ID: 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: P-VOL s emulation type Capacity: P-VOL s capacity CLPR: P-VOL s CLPR number. For SI or SIz, this item is blank. Mirror unit number. If you are not using the LDEV as a S-VOL for an existing pair, a hyphen (-) is shown. For SI or SIz, this item is blank. The pool s name and identifier. For SI or SIz, this item is blank. B-44 Copy-on-Write Snapshot GUI reference

147 Select Pool window Available Pools table Item Pool Name (ID) RAID Level Capacity Drive Type/RPM User-Defined Threshold (%) CLPR Detail Description The pool s name and identifier. The pool s RAID level. Values: Total: The total pool capacity. Used: The amount of pool capacity that is used. Used (%): The percentage of pool capacity that is used. *For Used (%), the number truncated to an integer is shown. The hard disk drive type and RPM. Information about the pool threshold. The ID and name of the CLPR (ID:CLPR). Click to open the Pool Properties window. Copy-on-Write Snapshot GUI reference B-45

148 Select Secondary Volumes window Item Description Capacity The remaining number you have to select Exclude Paired Volumes Port ID Host Group Name Set button Clear button Allows you to filter the available LDEVs according to the capacity you select. Refers to the selected P-VOLs in the Selected Pairs table with no assigned S-VOL. When checked, volumes already in a pair are not shown. This item is shown only when SI is specified. Filters LDEVs in the Available LDEVs table by the Port ID. For SIz, this item is blank. Filters LDEVs in the Available LDEVs table by the Host Group Name. Default: Any For SIz, this item is blank. 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. Available LDEVs table Item Description LDEV ID LDEV Name The identifier of LDEV, which you can specify as the S-VOL. LDEV s name B-46 Copy-on-Write Snapshot GUI reference

149 Item Description Port ID Host Group Name LUN ID Emulation type Capacity Provisioning type CLPR Detail Port name of the LDEV s LUN path. For SIz, this item is blank. Host group name of the LDEV s LUN path. For SIz, this item is blank. LUN ID of the LDEV's LUN path. For SIz, this item is blank. LDEV s emulation type 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 dialog box, which contains additional information for the selected LDEV. Selected Pairs table Item Primary Volume Secondary Volume Description Defines the P-VOL information. Values: LDEV ID: P-VOL s LDEV identifier LDEV Name: P-VOL s LDEV name. For unallocated LDEVs, a hyphen (-) is shown. Port ID: Port name of the P-VOL LDEV s LUN path For SIz, this item is blank. Host Group Name: Host group name of the P-VOL LDEV s LUN path For SIz, this item is blank. LUN ID: LUN ID of the P-VOL LDEV's LUN path For SIz, this item is blank. Emulation type: P-VOL s emulation type Capacity: P-VOL s volume capacity Defines the S-VOL information. Values: LDEV ID: S-VOL s LDEV identifier. If an LDEV is not allocated, this item is blank. LDEV Name: S-VOL s LDEV name. If an LDEV is not allocated, a hyphen (-) is shown. Copy-on-Write Snapshot GUI reference B-47

150 Item Description Port ID: Port name of the S-VOL LDEV s LUN path. For SIz, this item is blank. Host Group Name: Host group name of the S-VOL LDEV s LUN path. For SIz, this item is blank. LUN ID: LUN ID of the S-VOL LDEV's LUN path. For SIz, this item is blank. Emulation type: S-VOL s emulation type. Capacity: S-VOL s volume capacity. Copy type Mirror unit Pool name (ID) Edit Mirror Units button Remove button Shows 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 s mirror unit number. In HTI, this item is blank. The pool s name and identifier. In SI or SIz, this item is blank. Click to open the Edit Mirror Units window where you change mirror unit numbers. In HTI, this item is blank. Click to remove the pair from the table. Edit Mirror Units window Edit Mirror Units table Item Description Mirror Unit Specifies the mirror unit number. B-48 Copy-on-Write Snapshot GUI reference

151 Confirm window Selected Pairs table Item Primary volume Copy type Secondary volume Description Defines the P-VOL information. Values: LDEV ID: P-VOL s LDEV identifier LDEV Name: P-VOL s LDEV name Port ID: Port name of the P-VOL LDEV s LUN path For SIz, this item is blank. Host Group Name: Host group name of the P-VOL LDEV s LUN path For SIz, this item is blank. LUN ID: LUN ID of the P-VOL LDEV's LUN path For SIz, this item is blank. Emulation type: P-VOL s emulation type Capacity: P-VOL s volume capacity CLPR: 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 Defines the S-VOL information. Values: LDEV ID: S-VOL s LDEV identifier Copy-on-Write Snapshot GUI reference B-49

152 Item Pool Name (ID) Mirror Unit Description LDEV Name: S-VOL s LDEV name Port ID: Port name of the S-VOL LDEV s LUN path For SIz, this item is blank. Host Group Name: Host group name of the S-VOL LDEV s LUN path For SIz, this item is blank. LUN ID: LUN ID of the S-VOL LDEV's LUN path For SIz, this item is blank. Emulation type: S-VOL s emulation type Capacity: S-VOL s volume capacity CLPR: S-VOL s CLPR number The pool s name and identifier. In SI or SIz, this item is blank. The pool s mirror unit number. In HTI, this item is blank. B-50 Copy-on-Write Snapshot GUI reference

153 C Pair operations (secondary window) This appendix provides instructions on using the previous version of the SN GUI, which opens in a secondary window, and CCI. You can do all pair operations in the new SN GUI. For more information about the pair operations, see Chapter 5, Pair operations on page 5-1. Pair operations workflow Checking pair status Creating a pair Splitting pairs Resynchronizing pairs Restoring pairs Deleting pairs Pair operations (secondary window) C-1

154 Pair operations workflow Use the following workflow to perform pair operations: Check the pair status. The pairs must have a specific status before you can do a pair operation. Check the pair status to confirm an operation completed successfully. Create the pair. The V-VOL is transformed as a virtual copy of the P-VOL. Split the pair. A point-in-time snapshot of the P-VOL in the V-VOL is created. This allows another software application to use the V-VOL. Resume the pair. The SS data is discarded. The V-VOL is returned to a virtual copy of the P-VOL. Delete the pair. The pair relationship between the pair volumes ends. Restore the pair. The pair is restored to the point-in-time data of the last snapshot. Checking pair status Pair operations require a specific status. Check the pair status before performing an operation. For more information about checking pair status, see Monitoring the system in the secondary window on page D-2. For the operations allowed for specific statuses, see Pair status definitions on page D-3. Creating a pair Creating a pair changes the V-VOL to a virtual copy of the P-VOL. Updates to the P-VOL are reflected in the V-VOL until you split the pair. Prerequisite Information The data pool and V-VOL for the new pair must exist. For more information about installing and configuring data pools and V-VOLs, see Chapter 3, Copy-on-Write Snapshot installation and configuration on page 3-1. Review the pair volume requirements. For more information, see Chapter 2, Copy-on-Write Snapshot planning and design on page 2-1. The pair volumes must be in SMPL status. Use the same data pool for all pairs sharing a single P-VOL. For example: Three pairs with the same P-VOL must use the same data pool. C-2 Pair operations (secondary window)

155 Run the paircreate command when the data pool capacity is within the threshold. Running the paircreate command immediately after deleting previous SS data takes a longer time to complete. The CCI hide mode (-m noread) is not supported for S-VOLs (V-VOLs). If you specify it, the paircreate completes normally, but the hide mode is ignored. When using an HP-UX host server, you must create the SS pair before you run the command for recognizing the device or V-VOL on the host server. Caution: If a volume is recognized by the HP-UX host server, do not use the volume as a V-VOL. Otherwise an error occurs and the host server can terminate. For more information about recovering a terminated HP-UX host server, see Recovering a terminated HP-UX host server on page 7-6. From a command prompt, run the CCI paircreate command. The pair status changes to PAIR. For more information, see the Command Control Interface Installation and Configuration Guide. Creating pairs in a consistency group This topic provides a summary of the steps needed to create pairs in a consistency group. For more information about creating pairs, see the Command Control Interface Installation and Configuration Guide. Prerequisite information Use different consistency groups for each pair sharing a P-VOL. Review the system requirements for consistency groups. For more information, see Consistency group system requirements on page 2-2. Review the consistency group information. For more information, see the Command Control Interface Installation and Configuration Guide. In the same CCI configuration file consistency group, do not mix pairs that you have created using the At-Time Split operation with other pairs. If you mix these pairs, the pairsplit command terminates abnormally and the integrity of stored SS data cannot be ensured. 1. From a command prompt, run the paircreate command. Include the option for specifying the consistency group number. Note: Specifying a consistency group number automatically enables the At-Time Split operation. 2. Add more pairs to the same consistency group by running the paircreate command and specifying the same consistency group number defined in Step 1. Pair operations (secondary window) C-3

156 Splitting pairs Splitting a pair creates a virtual point-in-time copy of the P-VOL. The following occurs when you split a pair: The P-VOL continues receiving updates from the host, but updates are not reflected in the V-VOL. The current P-VOL data blocks are copied to the data pool. Pointers in the V-VOL follow this original data to the data pool, maintaining the point-intime copy. You can split one pair or multiple pairs belonging to a consistency group. Prerequisite information The pair must be in PAIR status. If you the P-VOL is paired with two or more V-VOLs, the pairs cannot be in COPY(RS-R)/RCPY status. Running the pairsplit operation while the pair is in this status can abnormally end the operation. Do not run the pairresync -restore command on a pair while a pairsplit operation is being performed on a related pair (a pair that shares the same P-VOL). Running this command can abnormally end the pairsplit operation. SS does not support Quick Split mode. For more information about the requirements for consistency group operations, see Consistency group system requirements on page 2-2. To split a pair, from a command prompt, run the CCI pairsplit command. For more information about this command, see the Command Control Interface Installation and Configuration Guide. To split pairs in a consistency group, from a command prompt, run the CCI pairsplit command on the consistency group that is a target of the At-Time Split operation. When the pairsplit completes, the pair status changes to PSUS. Resynchronizing pairs Resynchronizing pairs deletes the SS data in the data pool and transforms the V-VOL as a mirror of the current data in the P-VOL. Resynchronizing a pair increases the capacity in the data pool. Prerequisite information The pair status must be PSUS. If a related pair is using the SS data in the data pool, then only the SS ID is deleted for the resynchronized pair; the data is not deleted from the pool. To resynchronize a pair, use the CCI pairresync command. The pair status changes to PAIR. C-4 Pair operations (secondary window)

157 For more information about this command, see the Command Control Interface Installation and Configuration Guide. Restoring pairs When you restore a pair, the SS data in the data pool is copied back to the P- VOL. This restores P-VOL data to the point when the pair was split. Prerequisite information The pair must be in PSUS status. SS does not support the Quick Restore operation. To restore a pair, from a command prompt, run the CCI pairresync - restore command. The pair status changes to PAIR. Deleting pairs Deleting pairs ends the relationship between the P-VOL and V-VOL. SS data for the pair is deleted from the pool. Prerequisite information The pair must be in PAIR, PSUS, or PSUE status. It can take several seconds to ten minutes for the pair to delete. If you are using a large area of the pool for SS data or if you are deleting more than one pair, it can take ten minutes for the pair to delete. Deleting a single pair To delete a single pair, use the CCI pairsplit -S command. Deleting multiple pairs related to a port or host group Use the SN to delete multiple pairs from a port or host group. 1. In the SN, click Actions > Local Replications > SI/SS > Pair Operation. 2. Change to Modify mode by clicking the icon. 3. In the Pair Operations window tree, select the port or host group that contains the pairs you want to delete. 4. In the Volume list, select the SS pairs you want to delete, right-click, and select Pairsplit-S from the menu. Pair operations (secondary window) C-5

158 Figure C-1 Pairsplit-S Dialog box 5. In the Pairsplit-S dialog box, confirm that the pairs you want to delete are shown and selected, then click OK. The selected pairs are shown in the Preview list. 6. In the Pair Operations window, click Apply. 7. Click OK on the confirmation message. The pairs are deleted. Deleting multiple pairs related to a pool Use the SN to delete multiple pairs from a pool. 1. In the SN, click Actions > Local Replications > SI/SS > COW Snapshot. 2. Change to Modify mode by clicking the icon. 3. In the C.O.W. Snapshot window tree, complete the following: a. Select the pool containing the pairs you want to delete. b. From the list of pairs or volumes that are shown in the volume list, select all the pairs you want to delete, right-click and select the Pairsplit-S command. 4. In the Pairsplit-S dialog box, review the pairs you have selected and click OK. The dialog box closes. The list of pairs you want to delete are shown in the Preview list. 5. Click Apply, then click OK on the confirmation message. C-6 Pair operations (secondary window)

159 The pairs are deleted. Pair operations (secondary window) C-7

160 C-8 Pair operations (secondary window)

161 D Copy-on-Write Snapshot monitoring and maintenance (secondary window) This appendix provides instructions for monitoring SS using the previous version of the SN GUI, which opens in a secondary window. You can do maintenance and similar monitoring operations in the new SN GUI. For more information about maintenance on the new SN GUI, see Chapter 6, Copy-on-Write Snapshot monitoring and maintenance on page 6-1. Monitoring the system in the secondary window Maintaining the system Copy-on-Write Snapshot monitoring and maintenance (secondary window) D-1

162 Monitoring the system in the secondary window Monitoring helps you to keep track of your pairs and volumes in their current and past conditions. Monitoring is an ongoing activity. You can monitor the following SS elements: Monitoring pair information, license capacity, status on page 6-2 (status definitions included) Monitoring pair volume details on page D-3 Monitoring S-VOL path information on page D-5 Monitoring number of pairs and license information on page D-6 Monitoring pair operation history on page D-7 Monitoring pair status Monitor pair status before and after performing pair operations. Each operation requires a specific status or statuses. To do a pair command, first check the pair s status. Pair status changes when you do an operation. Check the status to ensure that the pairs are operating correctly and that the status is changing to the appropriate state during and after the operation. You can monitor the pair status manually using the SN. Repeat the monitoring process frequently. You can use the SN to set up notifications when you experience problems during a pair operation. To monitor pair status 1. In the SN, click Actions > Local Replications > SI/SS > Pair Operation. Note: Both SS and SI pairs are shown in the Pair list. SS V-VOLs are shown in the S-VOL column. 2. In the Pair Operation window, locate the pair whose status you want to review. Review pair status in the Status column. Caution: (Using monitoring software applications on a host server) If you have installed and are running a software application on a host server to monitor the volumes of SS pairs, the following problems can occur: An S-VOL whose status is not PSUS (or PFUS ) rejects access from the host, possibly causing problems for the monitoring software application whose access is rejected. If the host computer connects to more than one port, other ports may also go offline when the S-VOL rejects host access. To solve these problems, stop the monitoring software application. You can view more details by right-clicking a pair and selecting Detail. For more information about monitoring pair volume, see Monitoring pair volume details on page D-3. D-2 Copy-on-Write Snapshot monitoring and maintenance (secondary window)

163 Pair status definitions For more information about pair status descriptions, see Pair status definitions on page 6-3. Click File/Refresh to ensure the pair status data is current. The status names are slightly different in the new SN GUI than in the previous GUI version showing in the secondary window. The following table shows the new and previous status names. Current SN pair status names SMPL (is not shown) COPY PAIR PSUS PFUS PFUL RCPY PSUE Previous SN pair status names SMPL COPY, COPY(RS)/COPY PAIR PSUS PSUS PAIR COPY(RS-R)/RCPY PSUE Statuses required for pair operations To perform a pair operation, the pair must have a specific status. The following table shows the CCI pair operations and the required statuses to complete the pair operation. CCI pair operation Required status paircreate paircreate split pairsplit pairresync pairresync -restore pairsplit -S SMPL PAIR/PFUL PAIR/PFUL PSUS/PFUS, PSUE PSUS/PFUS PAIR/PFUL, PSUS/PFUS, PSUE Monitoring pair volume details You can review more details for a pair and pair-volumes than are available on the Pair Operation window. This includes volume capacity, related pool ID, pool usage, and so on. 1. In the SN, click Actions > Local Replications > SI/SS > Pair Operation. 2. In the Pair Operation window, select the desired SS pair on the Volume list, right-click and select Detail. Copy-on-Write Snapshot monitoring and maintenance (secondary window) D-3

164 3. In the Detail dialog box, check pair and volume details. The following table shows descriptions of the items in the Detail dialog box. Items Descriptions P-VOL Emulation Capacity (MB) Capacity (blocks) CLPR (P) Pool ID Amount of pool used by P-VOL (GB) Pool usage rate by P- VOL Snapshot Pair Detail list P-VOL LDKC number, control unit (CU) number, and LDEV number. P-VOL emulation type. P-VOL capacity in megabytes. P-VOL capacity in blocks. P-VOL cache logical partition. The pool s pool ID in which the P-VOL is registered. The amount of pool capacity the P-VOL is using. Pool usage rate of the P-VOL. Shows the SS pair details. Values: MU: SS ID. S-VOL: LDKC number, CU number, and LDEV number. Status: The pair s status. Date: Time when the SS data was stored in the pool. Pool used(gb): The amount of the pool s capacity the S-VOL is using. Sync.: Consistency rate of data of the P-VOL and the S-VOL. CLPR (S): S-VOL s cache logical partition (CLPR). CTG: The pair s consistency group number. D-4 Copy-on-Write Snapshot monitoring and maintenance (secondary window)

165 Items Refresh the window after this dialog box is closed. check box Refresh Close Descriptions Note: When the consistency group is not specified, dotted lines (---) are shown. SvolMode: Shows the status of the S-VOL. For more information about SvolMode, see the SvolMode item in Volume list on page E-3. If you select the check box, the information shown in the SI Pair Operation window is updated after the Detail dialog box closes. If you do not select the check box, the information stays the same when you close the dialog box. Updates the information in the Detail dialog box. Closes the Detail dialog box. Monitoring S-VOL path information You can view path information for the S-VOL. 1. In the SN, click Actions > Local Replications > SI/SS > Pair Operation. 2. In the Pair Operation window, select a pair in the Volume list, rightclick and select S-VOL Path. Figure D-1 S-VOL Path dialog box Copy-on-Write Snapshot monitoring and maintenance (secondary window) D-5

166 3. In the S-VOL Path dialog box, check S-VOL information as desired. The following table shows descriptions of the items in the S-VOL Path dialog box. Items Pair Information box S-VOL Path Information box Close Descriptions Path information for the selected pairs. P-VOL and S-VOL volumes are shown in the AAA-BB-CCC(XX:YY:ZZ) format. AAA: Port ID (cluster name and channel number) BB: Group number (GID) of host group CCC: LU number XX:YY:ZZ: LDKC number:cu number: LDEV number Path information for the S-VOLs selected in the Pair Information box. Port: The port ID GID: The group number of host group LUN: LU number Closes the S-VOL Path dialog box. Monitoring number of pairs and license information You can review information related to pairs and license capacity using the Information dialog box. 1. In the SN, click Actions > Local Replications > SI/SS > Pair Operation. 2. In the Pair Operation window, right-click and select Information. Figure D-2 Information dialog box D-6 Copy-on-Write Snapshot monitoring and maintenance (secondary window)

167 3. In the Information dialog box, review pair and license information as desired. The following table shows descriptions of the items in the Information dialog box. Items ShadowImage pair(s) C.O.W. Snapshot pair(s) Reserved volume(s) Remaining pair table(s) Remaining differential table(s) Used volume (TB) C.O.W. Snapshot Used volume (TB) Close Descriptions Number of SI pairs in the XXXX / YYYY format, where XXXX is SI pairs and YYYY is the number of SI and SIz pairs. Number of SS pairs. Maximum number of pairs: 16,384 If you create SI, Volume Migration, and Compatible FlashCopy V2 pairs in the same storage system, the maximum number of pairs that you can create may be less than 16,384 minus YYYY. YYYY is the number of SI and SIz pairs. The number of reserved volumes of SI is shown in the format of XXXX / YYYY. XXXX is the number of reserved SI volumes. YYYY is the total number of reserved SI and SIz volumes.reserved volumes include S-VOLs of SI and SIz. Number of usable pair tables in the storage system shown in XXXXX / YYYYY format. XXXXX is the number of usable pair tables. YYYYY is the maximum number of pair tables. Number of usable differential tables in the storage system in the XXXXXX / YYYYYY format. XXXXXX is the number of usable differential tables. YYYYYY is the maximum number of differential tables. For more information about calculating maximum number of pairs based on differential tables, see Calculating maximum SS pairs based on differential tables workflow on page 2-7. SI license information in the X(Y) format, where X is license capacity SI is using and Y is total license capacity reserved for SI. If there is no limit on license capacity, Unlimited is shown. SS license information in the X(Y) format, where X is license capacity SS is using and Y is total license capacity reserved for SS. If there is no limit on license capacity, Unlimited is shown. Closes the Information dialog box. Monitoring pair operation history You can review the operations that have been performed on a pair using the History window. The History window shows information about copying pairs. The storage system saves up to 512,000 records of the latest operations. If there are more than 16,384 records of pair operations, the list in the History window is divided into multiple pages and only the list that is currently shown is sorted. 1. In the SN, click Actions > Local Replications > SI/SS > History. Note: If some of the pairs include LUSE volumes or if the subsystem includes 500 or more of the following pairs and migration plans, you may need to wait until the History window shows the operation history. In Copy-on-Write Snapshot monitoring and maintenance (secondary window) D-7

168 addition, if you use 1,000 or more pairs concurrently, some operation history might not be recorded. SI pairs SS pairs SIz pairs Compatible FlashCopy V2 Volume Migration HTI pair SS and HTI pair information is shown in the bottom part of the History window. The list sorts based on the column heading you click. 2. In the History window, click the C.O.W. Snapshot tab. 3. In the History window, in the C.O.W. Snapshot tab, perform the following in the COW Snapshot History list. To change the displaying order, click a column in the list. The list is sorted based on the items in the clicked column. If multiple pages of pair operations exist, click Next to move to the next page. To move to the previous page, click Previous. Note: If only one page of pair operations exists, the Previous and Next buttons are unavailable. Click the same column again to switch the sorting order (Ascending or Descending). To update the window with the latest information, click File > Refresh. If there are many records of tasks, use the scroll icons. The list scrolls and the operation history that has not been shown is shown. To expand the display area of the list in the History window, click and drag down the frame border that divides the History window into upper and lower panes. Maintaining the system You can make changes to the storage system, data pools, and V-VOLs to fit your requirements. For more information about maintaining the SN, see Maintaining the storage system on page 6-6. D-8 Copy-on-Write Snapshot monitoring and maintenance (secondary window)

169 E Copy-on-Write Snapshot GUI reference (secondary window) This appendix describes SS windows and dialog boxes in the previous version of the SN GUI, which opens in a secondary window. Note: The P-VOL and S-VOLs listed in the SN may end in special symbols. An LDEV number that ends with a pound or gate symbol (#) indicates an external volume (for example, 00:00:01#). An LDEV number that ends with the letter X indicates that HDP is using a V-VOL. For example, 00:00:01X. Pair Operation window History window C.O.W. Snapshot window Copy-on-Write Snapshot GUI reference (secondary window) E-1

170 Pair Operation window Use the Pair Operation window to view SS and SI pair and volume information for the selected port or host group. Note: This section references only the items related to SS pairs. For more information about SI, see the Hitachi ShadowImage User Guide. You can do the following from the Pair Operation window: Monitoring pair information, license capacity, status on page 6-2 Monitoring pair volume details on page D-3 Monitoring S-VOL path information on page D-5 Monitoring number of pairs and license information on page D-6 Item Display Filter button Tree Pair/volume list Description Click to open the Display Filter dialog box. Use this dialog box to filter to display specific volumes in the Pair list. Shows port and host group. When you click one of these, associated pairs show in the pair/volume list. If you select Storage System, pair or volumes are not listed. Shows volume and pair information. You can sort this list by column in ascending or descending order. For more information, see Volume list on page E-3. E-2 Copy-on-Write Snapshot GUI reference (secondary window)

171 Icons Item Description The following are the SS icons and their meanings: : Storage system : Port : Host group : LUN or SMPL volume : SS pair For more information about the SI icons, see the Hitachi ShadowImage User Guide. Preview Apply Shows the operations you have specified but have not yet applied to the storage system. You can change or delete the operations by rightclicking the item in the Preview list. Applies the operations shown in the Preview list to the storage system. If the specified operations are applied successfully, the Preview list will be cleared. If an error occurs during an operation, the failed operation will remain in the Preview list with an error icon ( ) shown in front. The error dialog box shows the details of the error (error code and message). For more information about the SS error code list, see the Hitachi Storage Navigator Messages. Cancel Cancels all the operations set in the Preview list. Volume list The main list in the Pair Operation window is the Volume list. This list shows SS and SI volume and pair information. You can filter the list to show only SS volumes. To do this, click Display Filter. P-VOL Item Description P-VOL information in AAA-BB-CCC(XX:YY:ZZ) format. Values: AAA: Port ID (cluster and channel number) BB: Group number of host group CCC: LU number XX:YY:ZZ: LDKC number:cu number:ldev number A device ID ending in # (e.g., 00:00:3C #), indicates the LDEV is an external volume. For more information about external volume, see the Hitachi Universal Volume Manager User Guide. Copy-on-Write Snapshot GUI reference (secondary window) E-3

172 Item Description A device ID ending in X (e.g., 00:00:3C X) indicates the LDEV is an HDP V-VOL. For more information about V-VOL, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. MU Status S-VOL CTG SvolMode Copy Pace Sync. Emulation Capacity (MB) CLPR (P) CLPR (S) Mirror unit (MU) number of the SS pair, formed with the P-VOL. The storage system assumes the same numbers of P-VOLs as S-VOLs. For example, when a P-VOL is paired with three S-VOLs, though just one P- VOL exists, the system assumes that there are three P-VOLs. These virtual P-VOLs are mirror units, MUs. The MU numbers identify the virtual P-VOLs seen only by the system. Note: If the pair is in SMPL status, three hyphens (---) are shown. Pair status. S-VOL information in AAA-BB-CCC(XX:YY:ZZ) format. Values: AAA: Port ID (cluster and channel number) BB: Group number of host group CCC: LU number XX:YY:ZZ: LDKC number:cu number: LDEV number Only one path is listed, which is the path connected to the first port in the tree view. A device ID ending in # (e.g., 00:00:3C #), indicates that the LDEV is an external volume. For more information about external volume, see the Hitachi Universal Volume Manager User Guide. A device ID ending in X (e.g., 00:00:3C X) indicates that the LDEV is an HDP V-VOL. For more information about V-VOL, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. The pair s consistency group number. When the consistency group is not specified, three hyphens (---) are shown. Shows the status of the S-VOL. When data is not written in the S-VOL, three hyphens (---) are shown. When the data is written in the S-VOL, W is shown. Not for SS, three hyphens (---) are shown. Indicates the percentage of pair synchronization, and changes based on the pair status. Values: For volumes or pairs in SMPL or SMPL (PD) status, dashes (---) are shown. The percentage (%) of data in the S-VOL and P-VOL for volumes in COPY, PAIR, COPY(RS)/COPY, COPY(RS-R)/RCPY, PSUS, or PSUE status. Emulation type of the volume. Volume storage capacity in megabytes. P-VOL cache logical partition. S-VOL cache logical partition. E-4 Copy-on-Write Snapshot GUI reference (secondary window)

173 Item Right-click command menu Previous Next Message Description Commands you can perform. If you select and right click the SS pair volumes in the volume list, the menus in the following table are shown. For more information about the command descriptions, see the following table. If the total number of the volumes in the storage system has exceeded the maximum number of volumes, multiple pages exist. Click to open the previous page in the list. Note: If only one page exists, this button is unavailable. For more information about the maximum number of pool-vols allowed in a data pool, see Consistency group system requirements on page 2-2. If the total number of the volumes in the storage system has exceeded the maximum number of volumes, multiple pages exist. Click to open the next page of the volume list. Note: If only one page exists, this button is unavailable. For more information about the maximum number of pool-vols allowed in a data pool, see Consistency group system requirements on page 2-2. If a volume or pair does not exist, Message is shown. If Message is shown in the Volume list, click a different icon in the tree in the left area of the Pair Operation window. Preview list The Preview list shows the operations and changes you have made from the Pair Operation window. You can review your changes, modify the operation or your changes, and apply them to the storage system: To modify an operation, right-click the row and select Delete or Modify. To display error messages, click Error. The Preview list opens below the Volume list. The following table shows descriptions of the items in the Preview list. Item Description P-VOL MU S-VOL P-VOL information in AAA-BB-CCC(XX:YY:ZZ) format. Values: AAA: Port ID (cluster and channel number) BB: Group number of host group CCC: LU number XX:YY:ZZ: LDKC number:cu number:ldev number The MU number of the SI pair formed with the P-VOL. S-VOL information in AAA-BB-CCC(XX:YY:ZZ) format. Values: Copy-on-Write Snapshot GUI reference (secondary window) E-5

174 Item Copy Pace CLPR (P) CLPR (S) Error Code Menu Preview X(Y) Description AAA: Port ID (cluster and channel number) BB: Group number of host group CCC: LU number XX:YY:ZZ: LDKC number:cu number:ldev number Indicates the speed that data is copied according to the pair status. P-VOL cache logical partition is shown. S-VOL cache logical partition is shown. If you click Apply and then the operations in the Preview list fail, an error code indicates the cause of the error. Select and right-click items in the Preview list to show the menu. Options: Detail: Opens the error message dialog box, which shows the error code and message. For SS error codes, see Hitachi Storage Navigator Messages. Delete: Cancels the selected task and removes the task from the Preview list on the Pair Operation window. The unavailable commands are for SI pairs. For more information about the SI commands, see the Hitachi ShadowImage User Guide. X denotes the total number of operations that are shown in the Preview list. Y denotes the type of operation. Command menu Data in the status bar below the Preview list indicate the number of changes, the type of change (the operation), and any command options. When you right-click a row or other item, a menu opens and shows commands. The following table lists the commands. Command Detail Pairsplit-S S-VOL Path Information Grayed-out commands Function Opens the Detail dialog box, which shows detailed information for the selected volume or pair. Opens the Pairsplit-S dialog box, in which you delete SS pairs. Opens the S-VOL Path dialog box, in which you view information about the S-VOL path. Opens the Information dialog box, which shows the number of pairs or reserved volumes. Reserved for SI. E-6 Copy-on-Write Snapshot GUI reference (secondary window)

175 Command Paircreate, Pairsplit Function Opens the Paircreate and Pairsplit dialog boxes. These dialog boxes are reserved for SI. You cannot create or split SS pairs from these dialog boxes. Use CCI to create or split SS pairs. History window You can view your operation history and its associated data in the History window. The upper pane shows SI history. To show the SS or HTI history in the lower pane, click the C.O.W. Snapshot or Thin Image tab. For more information about SI history, see the Hitachi ShadowImage User Guide. Item Previous Next Description If the total number exceeds 16,384 of operations, multiple pages exist. Click to open the previous page of the operation history list. Note: If only one page exists, this button is unavailable. If the total number exceeds 16,384 of operations, then multiple pages exist. Click to open the next page of the operation history list. Copy-on-Write Snapshot GUI reference (secondary window) E-7

176 Item Description Note: If only one page exists, this button is unavailable. Date P-VOL S-VOL MU Pool ID Code Message Shows date and time of the operation in the YYYY / MM / DD hh:mm:ss format. YYYY: year MM: month DD: day hh: hour mm: minute ss: second The operation s P-VOL, identified by LDKC:CU:LDEV. A device identifier ending in the pound sign (#) (e.g., 00:00:3C #), indicates that the LDEV is an external volume. For more information about external volumes, see the Hitachi Universal Volume Manager User Guide. Note: A device identifier ending in X (e.g., 00:00:3C X) indicates that the LDEV is an HDP V-VOL. For more information about V-VOL, see the Hitachi Virtual Storage Platform Provisioning Guide for Open Systems. The operation s S-VOL (V-VOL), identified by LDKC:CU:LDEV. A device ID ending in V (e.g., 00:00:01 V) indicates that the LDEV is a V-VOL. The SS ID. ID of the related data pool. SS reference code, which indicates the kind of operation that was performed. For more information, see Reference codes on page E-8. Describes the operation. Related to the reference code. Reference codes Reference code and message information about SS and HTI operations is shown in the Code and Message columns in the History window. The following table lists descriptions for the columns. Code Message Description 2001 PAIR The pair was created PSUS The pair was split SMPL The pair was deleted COPY(RS-R) START Pair restoration started COPY(RS-R) END Pair restoration ended normally COPY(RS-R) ENDED ABNORMAL Pair restoration ended abnormally. E-8 Copy-on-Write Snapshot GUI reference (secondary window)

177 Code Message Description 2051 COPY(RS) The SS data was deleted PSUE(ABNORMAL END) A failure occurred and the status of the pair changed to PSUE INITIALIZE START Initialization started INITIALIZE END Initialization ended normally INITIALIZE ENDED ABNORMAL Initialization ended abnormally. C.O.W. Snapshot window The C.O.W. Snapshot window shows SS pool information. Item Description Tree The pools in the storage system are shown with the following icons: : Storage system Pool:X: Pool in normal status (X indicates pool ID) Pool:X: Pool whose usage rate exceeds the threshold (X indicates pool ID) Copy-on-Write Snapshot GUI reference (secondary window) E-9