hitachi unified storage vm block module hitachi thin image ... · product version contents getting...

Product Version

Contents

Getting Help

FASTFIND LINKS

Hitachi Unified Storage VM Block ModuleHitachi Thin Image User Guide

MK-92HM7010-05

Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

ii

© 2012-2014 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. (hereinafter referred to as "Hitachi") and Hitachi Data Systems Corporation (hereinafter referred to as "Hitachi Data Systems").

Hitachi and Hitachi Data Systems reserve the right to make changes to this document at any time without notice and assume no responsibility for its use. This document contains the most current information available at the time of publication. When new and/or revised information becomes available, this entire document will be updated and distributed to all registered users.

Some of the features described in this document may not be currently available. Refer to the most recent product announcement or contact your local Hitachi Data Systems sales office for information about feature and product availability.

Notice: Hitachi Data Systems products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems agreements. The use of Hitachi Data Systems products is governed by the terms of your agreements with Hitachi Data Systems.

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

ShadowImage and TrueCopy are registered trademarks of Hitachi Data Systems.

AIX and IBM are registered trademarks or trademarks of International Business Machines Corporation.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

All other trademarks, service marks, and company names are properties of their respective owners.

Microsoft product screen shots reprinted with permission from Microsoft Corporation.

iiiHitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixIntended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xProduct version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xRelease notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xDocument revision level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xChanges in this revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xReferenced documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiDocument conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiConvention for storage capacity values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiResources performing operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiAccessing product documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiGetting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiComments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

1 Overview of Thin Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Thin Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Components of Thin Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Components of volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Consistency and snapshot groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Thin Image overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Dynamic Provisioning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4The Command Control Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

How Thin Image works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Thin Image Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Virtual volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Releasing V-VOL definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Thin Image pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Storing snapshot data for a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Snapshot data storage methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Differences in methods to storing snapshots depending on volumes . . . . . 1-10Restoring Thin Image pairs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Deleting snapshot data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11


iv

Deleting Thin Image pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11HTI pair status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Copy threshold option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Interoperability with other software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Data Retention Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Volume Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17ShadowImage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17TrueCopy and Universal Replicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19Dynamic Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21Resource Partition Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22

Software application acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . 1-22

2 Planning and design requirements . . . . . . . . . . . . . . . . . . . . . . . . 2-1System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Requirements for Thin Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Installing Thin Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Uninstalling Thin Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Requirements for licensed capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Shared memory requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Volume requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Consistency group requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Snapshot group requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Requirements for Thin Image operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Calculating the number of virtual volumes that the storage system can create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Calculating the number of Thin Image pairs that you can create . . . . . . . . 2-7Calculating the number of Thin Image pairs based on pair tables . . . . . . 2-8

Calculating the number of Thin Image pairs based on the snapshot estimated manageable capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Calculating the number of Thin Image pairs workflow . . . . . . . . . . . . . . . . 2-8Calculating the number of cache management devices . . . . . . . . . . . . . . . 2-9

The number of cache management devices required for Thin Image pair operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Effects on I/O performance of the storage system . . . . . . . . . . . . . . . . . . 2-9Notes on assigning the pool capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Estimating the capacity of snapshot data to be copied to the pool . . . . 2-10Using external volumes as pool-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

3 Performing configuration operations. . . . . . . . . . . . . . . . . . . . . . . 3-1Configuration workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Creating pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Creating V-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Changing the V-VOL settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Removing V-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Setting up command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

vHitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

4 Pair operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Creating HTI pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Using Storage Navigator to create HTI pairs workflow . . . . . . . . . . . . . . . . 4-3Acquiring snapshot data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Acquiring snapshot data using the At-Time Snapshot function . . . . . . . . . . 4-6At-Time Snapshot when Thin Image volume shared with UR and TC. . . . . . 4-6

Notes on using Thin Image primary volumes as TrueCopy or Universal Replicator pair volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Notes on acquiring snapshot data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Restoring pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Deleting snapshot data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Deleting pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

5 Monitoring and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Monitoring pair information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Viewing the number of pairs and a list of pairs . . . . . . . . . . . . . . . . . . . . . 5-2Checking pair status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Monitoring pair properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Monitoring synchronous rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Monitoring consistency groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Viewing the number of consistency groups. . . . . . . . . . . . . . . . . . . . . . . . 5-4Viewing a list of consistency groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Viewing properties of a consistency group . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Monitoring pair operation history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Viewing the operation run history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Monitoring pair operation history using the secondary window. . . . . . . . . . 5-5

Monitoring licensed capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Monitoring the number of cache management devices . . . . . . . . . . . . . . . . . . 5-8Managing pools and V-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Monitoring pool information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Viewing used pool capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Viewing used capacity by pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Viewing used pool capacity by HTI P-VOL . . . . . . . . . . . . . . . . . . . . . . 5-9

Pool capacity and formatting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Viewing formatted pool capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Increasing pool capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Changing the pool threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Changing the pool name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Recovering pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Deleting pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Changing V-VOL names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Deleting V-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Viewing snapshot data capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Maintenance requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Replacing the microcode offline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15


vi

Switching off the power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1General troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Blocked pool recovery workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Processing pool-related SIMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Completing warning SIMs before depletion of cache management devices . 6-6

Contacting the Hitachi Data Systems Support Center . . . . . . . . . . . . . . . . . . . 6-7

A Command Control Interface command reference. . . . . . . . . . . . . . A-1Statuses required for CCI operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Pair status names in the CCI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Troubleshooting with the Command Control Interface . . . . . . . . . . . . . . . . . . . A-3

Identifying errors using the log on the CCI window. . . . . . . . . . . . . . . . . A-10Identifying errors using the CCI operation log file . . . . . . . . . . . . . . . . . . A-10

B Thin Image GUI reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Replications window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2Local Replications window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3View Pair Properties window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10View Pair Synchronous Rate window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12View Histories window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13Consistency Group Properties window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15Create Pairs wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16

Select Pair Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17Select Primary Volumes window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18Select Pool window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21Select Secondary Volumes window . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22Confirm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26

Split Pairs wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-28Split Pairs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-28Confirm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-30

Resync Pairs wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-32Resync Pairs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-32Confirm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-34

Delete Pairs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36Edit Local Replica Options wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38

Edit Local Replica Options window . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38Confirm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-39

SI/TI System Options table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-40

Glossary

viiHitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Index


viii

Preface ixHitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Preface

This document describes and provides instructions for using Hitachi Thin Image (HTI) to plan, configure, and perform pair operations on the Hitachi Unified Storage VM (HUS VM) storage system.

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

This preface includes the following information:

□ Intended audience

□ Product version

□ Release notes

□ Document revision level

□ Changes in this revision

□ Referenced documents

□ Document conventions

□ Convention for storage capacity values

□ Resources performing operations

□ Accessing product documentation

□ Getting help

□ Comments


x Preface

Intended audienceThis 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.

This document is for users who are familiar with the following:• Data processing and RAID storage systems and their basic functions.• The Hitachi Virtual Storage Platform storage system, and have read the

Hitachi Virtual Storage Platform User and Reference Guide.• The Storage Navigator (SN) software for the HUS VM and have read the

Hitachi Storage Navigator User Guide.• Hitachi Dynamic Provisioning, Hitachi Dynamic Tiering software, Hitachi

LUN Manager, Hitachi LUN Expansion, Virtual LUN, and the Hitachi Data Retention Utility.

Product versionThis document revision applies to HUS VM microcode 73-03-3x or later.

Release notesThe Hitachi Unified Storage VM Release Notes provide information about the HUS VM microcode (DKCMAIN and SVP), including new features and functions and changes. The release notes are available on the Hitachi Data Systems Portal: https://portal.hds.com

Document revision level

Changes in this revision• Updates regarding pair operations during zero-page reclamation.• Updates regarding pair operation rejection when system option mode

905 is ON.

Revision Date Description

MK-92HM7010-00 December 2012 Initial release.

MK-92HM7010-01 January 2013 Supersedes and replaces MK-92HM7010-00.

MK-92HM7010-02 March 2013 Supersedes and replaces MK-92HM7010-01.

MK-92HM7010-03 May 2013 Supersedes and replaces MK-92HM7010-02.

MK-92HM7010-04 October 2013 Supersedes and replaces MK-92HM7010-03.

MK-92HM7010-05 September 2014 Supersedes and replaces MK-92HM7010-04.

https://portal.hds.com

Preface xiHitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

• Updates to ShadowImage on page 1-17 and Creating HTI pairs on page 4-2 regarding MU numbering.

• Update to Switching off the power supply on page 5-15 regarding shared memory.

• Added section Viewing used pool capacity on page 5-9.• Added section Viewing snapshot data capacity on page 5-14.

Referenced documentsHitachi Unified Storage VM documentation:• Hitachi Storage Navigator User Guide, MK-92HM7016• Hitachi Universal Volume Manager User Guide, MK-92HM7020• Hitachi Volume Shredder User Guide, MK-92HM7021• Hitachi Unified Storage VM Block Module Provisioning Guide, MK-

92HM7012• Hitachi TrueCopy® User Guide, MK-92HM7018• Hitachi Universal Replicator User Guide, MK-92HM7019• Command Control Interface User and Reference Guide, MK-90RD7010• Hitachi Command Control Interface Command Reference, MK-

90RD7009

Document conventionsThe following table lists the typographical conventions used in this document.

Convention Description

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

Italic Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file

Monospace Indicates text that is shown on screen or the user types. 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

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

Convention for storage capacity valuesPhysical storage capacity values (for example, disk drive capacity) are calculated based on the following values.

Logical storage capacity values (for example, logical device capacity) are calculated based on the following values.

| 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.

Convention Description

Icon Meaning Description

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

Note Calls attention to important and/or additional information.

Caution Warns the user of adverse conditions and/or consequences (for example, disruptive operations).

WARNING Warns the user of severe conditions and/or consequences (for example, destructive operations).

Physical capacity unit Value

1 KB 1,000 bytes

1 MB 1,0002 bytes

1 GB 1,0003 bytes

1 TB 1,0004 bytes

1 PB 1,0005 bytes

1 EB 1,0006 bytes

Logical capacity unit Value

1 KB 1,024 bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

Preface xiiiHitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Resources performing operationsThe resources for each operation must satisfy the specific conditions to use the functions described in this document.

The SN main window shows only the resources that are assigned to a user who logs into the SN. The window may also show the related resources that are required to manage the assigned resources.

The SN secondary window shows all of the resources in the storage system. To perform an operation in the SN secondary window, verify the resource group ID in the Basic Information Display dialog boxes and then perform the operations for the resources assigned to the user account.

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

Accessing product documentationThe HUS VM user documentation is available on the Hitachi Data Systems Portal: https://portal.hds.com. Check this site for the most current documentation, including important updates that may have been made after the release of the product.

Getting helpThe Hitachi Data Systems Support Center staff is available 24 hours a day, seven days a week. If you need technical support, log on to the Hitachi Data Systems Portal for contact information: https://portal.hds.com

CommentsPlease send us your comments on this document: [email protected]. Include the document title and number, including the revision level (for example, -03), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems.

Thank you!

1 block 512 bytes

Logical capacity unit Value

https://hdssupport.hds.com



xiv Preface

1

Overview of Thin Image 1–1Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Overview of Thin Image

This document provides an overview of Thin Image (HTI). Use HTI to perform cost-effective duplication by storing differential data between primary volumes (P-VOLs) and secondary volumes (S-VOLs) of virtual volumes (V-VOLs).

This chapter includes the following information:

□ Thin Image

□ Components of Thin Image

□ How Thin Image works

□ HTI pair status

□ Copy threshold option

□ Interoperability with other software

□ Software application acronyms and abbreviations


1–2 Overview of Thin Image

Thin ImageUse HTI to create duplicated data in your storage system for data in open-system volumes. Splitting HTI pairs stores snapshot data. HTI stores snapshots of data in your storage system. You can store a maximum of 1,024 snapshots. If a data failure occurs in your storage system, use the snapshot data to restore the data.

The following figure shows an overview of HTI.

Snapshot data is a copy of updated data in HTI P-VOL. Before the P-VOL is updated, only the updated data is copied as snapshot data in pool volumes (pool-VOLs). This processing is referred to as the storing of snapshot data.

Create HTI pairs to store snapshot data. The P-VOL of an HTI pair is a logical volume. The S-VOL of an HTI pair is a V-VOL.

Use the following process to store snapshot data:1. Create an HTI pair.2. The host updates the P-VOL.3. You split the HTI pair.

The P-VOL snapshot data is stored (Snapshot A in the following figure).4. The host updates the P-VOL again.5. You split the HTI pair.

The updated data in the P-VOL is stored as snapshot data (Snapshot B in the following figure).The following image shows the workflow to store snapshot data.


In the figure above, the host can reference the P-VOL, snapshot data A, and Snapshot data B. Snapshots A and B are handled as HTI S-VOLs.

Required software applications

Dynamic Provisioning (DP) is required to use HTI. DP accesses data in pool-VOLs by way of V-VOLs, and can handle data in open-system servers such as UNIX and PC servers.

Components of Thin ImageAn HTI system typically consists of the following components:• HTI pairs:

Components of P-VOL, S-VOL, and pool-VOLs• Groups:

A consistency group A snapshot group

• Software applications: HTI DP Command Control Interface (CCI)



Components of volumesHTI manages logical volumes of P-VOLs and V-VOLs of S-VOLs as HTI pairs. Logical volumes of P-VOLs include V-VOLs whose provisioning type is DP. You can only use the V-VOL used by an HTI pair as an S-VOL. The differential data of P-VOLs are stored as snapshot data in pool-VOLs.

The following volumes are required for using HTI:• At least one P-VOL• At least one S-VOL (V-VOL)• At least one HTI pool-VOL, as a container for snapshot data

Consistency and snapshot groupsTo use HTI to create new pairs and perform HTI pair operations per group, add pairs to a consistency group or a snapshot group.

Using the CCI, you can create multiple HTI pairs as a consistency group. To store snapshot data per consistency group, first define the consistency group. Use consistency groups to assure the data from the time when HUS VM receives the request of storing data.

The following table lists the differences between consistency groups and snapshot groups.

For more information about storing snapshot data for a group, see Storing snapshot data for a group on page 1-7.

For more information about consistency group requirements, see Consistency group requirements on page 2-6.

Thin Image overviewYou use the HTI on your SN computer.

The use of HTI, DP, and all other VSP products requires license agreements with Hitachi.

Dynamic Provisioning overviewInstall DP on the SN computer to perform HTI pair operations. DP license is required. You must reserve license capacity enough to accommodate pairs or pools that should be created.

Item Consistency group Snapshot group

Maximum number of pairs in a group 8,192 8,192

Maximum number of groups you can create

256* 512

Data consistency Guaranteed Not guaranteed

* You can create up to 256 consistency groups in a storage system, with ShadowImage (SI) and HTI consistency groups combined.


The licensed capacity for DP is calculated based on the capacity of pool-VOLs for HTI and DP. These volumes are referred to as used volumes. Make sure that the licensed capacity exceeds the total capacity of used volumes.

The Command Control InterfaceYou use the CCI from a host and run commands to perform HTI pair operations.

For more information about the commands you can run to perform HTI pair operations, see Command Control Interface command reference on page A-1 and the Hitachi Command Control Interface Command Reference.

How Thin Image worksThis topic explains how HTI works and includes the following:• Thin Image Pools on page 1-5• Virtual volumes on page 1-6• Thin Image pairs on page 1-6• Storing snapshot data for a group on page 1-7• Snapshot data storage methods on page 1-9• Differences in methods to storing snapshots depending on volumes on

page 1-10• Restoring Thin Image pairs on page 1-10• Deleting snapshot data on page 1-11• Deleting Thin Image pairs on page 1-11

Thin Image PoolsHTI stores snapshot data in pools. A pool consists of multiple pool-VOLs, which contain snapshot data. A pool can contain up to 1,024 pool-VOLs. You can create up to 128 pools in a storage system including DP, Dynamic Tiering (HDT), and HTI pools.

The following figure illustrates the relationship between an HTI pair and a pool.



You must create pools to use HTI. If you are using HTI to perform a pair operation, you can add pool-VOLs but you cannot delete pool-VOLs. To delete a pool, delete all HTI pairs.

Virtual volumesV-VOLs do not have any physical storage space. You must create the V-VOLs before you create HTI pairs because HTI uses V-VOLs as S-VOLs.

Releasing V-VOL definitions

Release V-VOL definitions only if the V-VOL is not being used as an HTI S-VOL. To release definitions of V-VOLs, release the HTI pairs that are using the V-VOLs.

Thin Image pairsUse the following process to create HTI pairs:1. Create the V-VOLs. You can specify up to 1,024 S-VOLs for a single P-

VOL.You cannot use volumes that have recently changed to “SMPL” status to create HTI pairs. Releasing an HTI pair changes the volume status to “SMPL”.

Caution: The pool capacity is the total capacity of pool-VOLs in the pool. If data is written to HTI pair volumes and therefore the amount of pool usage exceeds the pool capacity, the status of the HTI pair changes to “PSUE”, which means that a failure occurs, and then you cannot store snapshot data. Also, you cannot create new HTI pairs. You must reserve a sufficient amount of pool capacity for the pools you plan to create.


For more information about releasing HTI pairs, see Deleting pairs on page 4-11.To create HTI pairs using volumes that are in “SMPL” status, wait to create the pairs.

2. Create the HTI pairs. Specify the pool to be used for the HTI pair.If multiple HTI pairs share the same P-VOL, the pairs must also share the same pool. For example, if you specify three S-VOLs for one P-VOL, you must specify the same pool for the three HTI pairs.For more information about creating HTI pairs, see Creating HTI pairs on page 4-2.

Storing snapshot data for a groupUse the CCI to define a consistency group or a snapshot group and store snapshot data for the group. The following figure illustrates how snapshot data for a group is stored.

For more information about the differences between snapshot groups and consistency groups, see Consistency and snapshot groups on page 1-4.

The following figure shows how snapshot data is stored for a group.



Snapshot data is stored in the following steps:1. Request to store snapshot data for a group. To do this, run the following

CCI command:raidcom modify snapshot -snapshot_data create

Note: Use the CCI to store snapshot data for consistency groups or snapshot groups. Use the SN to reference consistency groups and snapshot groups.


2. The host issues a write request to each P-VOL in the group.3. Snapshot data for the volumes are stored.

Snapshot data storage methodsUse the Copy-On-Write (COW) method or the Copy-After-Write (CAW) method to store snapshot data. In the COW method, after the P-VOL snapshot data is acquired, the status changes to the write completion status. In the CAW method, after writing data to the P-VOL the status changes to the write completion status. Therefore, the CAW method’s waiting time is shorter than that of the COW method.

The following image shows the CAW method.

In the CAW method, store snapshot data in the following steps:1. The host writes data to a P-VOL.2. The write completion status is returned to the host before the snapshot

data is stored.3. Snapshot data for the P-VOL is stored in the background.

The following image shows the COW method.



In the COW method, store snapshot data in the following steps:1. The host writes data to a P-VOL.2. Snapshot data for the P-VOL is stored.3. The write completion status is returned to the host after the snapshot

data is stored.

Differences in methods to storing snapshots depending on volumes

If the write pending rate is less than 60% in the cache memory, use the CAW method to store the snapshot data. Otherwise, use the COW method to store the snapshot data.

For more information about the write pending rate, see the Hitachi Unified Storage VM Block Module Performance Guide.

If a P-VOL is an external volume

Use the COW method to store snapshot data.

Restoring Thin Image pairsYou can use HTI to overwrite snapshot data in pools to P-VOLs. Overwriting snapshot data returns the P-VOL content to the condition it was when you stored the snapshot data. Overwriting snapshot data to P-VOLs is referred to as restoring HTI pairs.

If you write data to an S-VOL, this particular data (not the snapshot data) is overwritten to the P-VOL when you restore the HTI pair.

If a problem occurs with a P-VOL due to a failure, restore the pair so that data in the P-VOL is returned to the condition it was when you stored the snapshot data.


For more information about restoring pairs, see Restoring pairs on page 4-10.

Deleting snapshot dataIf the capacity of snapshot data exceeds the pool capacity because of data being written to HTI pair volumes, the pair changes to “PSUE”. An HTI pair in “PSUE” status shows that a failure has occurred. You cannot create new HTI pairs in “PSUE” status. You must delete unneeded snapshot data.

Use one of the following methods to delete snapshot data:• Delete the HTI pairs.

Deleting an HTI pair deletes the snapshot data from the pool and unpairs the P-VOL and S-VOLs.

• Delete only the snapshot data.To delete snapshot data, use the Resync pairs window. If you only delete the snapshot data, the relationship between the P-VOL and S-VOLs is maintained. If you only delete the snapshot data, assign the MU number of the deleted snapshot data when snapshot data for the HTI pair is stored.

For more information about deleting snapshot data, see Deleting snapshot data on page 4-10.

After you delete snapshot data, the pair status changes to “PAIR” and you cannot store a snapshot even when the hosts update P-VOLs. To resume storing snapshot data, split the pair again.

Deleting snapshot data or HTI pair takes time. The more pool capacity the pair uses, the longer it takes to split the pair. The more pairs are operated concurrently, the longer it takes to split the pair.

Deleting Thin Image pairsTo delete HTI pairs, use the Delete Pairs window. Delete a pair when you no longer need it or you want to delete snapshot data. Deleting a pair changes the P-VOL and S-VOLs status to “SMPL(PD)” and then to “SMPL”. When the pair status changes to “SMPL”, the HTI pair is removed from SN. After you have deleted the HTI pairs, you can use the volumes in another pair.

You cannot create pairs when the status is “SMPL (PD)”. To shorten the time when the pair status is “SMPL (PD)”, complete the following:1. Delete the snapshot data.

The pair status changes to “PAIR”.2. Delete the pair.

If you have defined a snapshot group, when all of the pairs in the snapshot group change to “SMPL” status, the snapshot group is deleted. Make sure that the snapshot group is deleted, and then perform the next pair operation.

For more information about deleting pairs, see Deleting pairs on page 4-11



HTI pair statusThe status of an HTI pair changes as you create, split, or perform other pair operations on the pair, as illustrated in the following figure.

1. The volumes are not paired. The volumes are in “SMPL” status.2. You create a pair. The initial copy is in progress. The pair status changes

to “COPY”.The pair is created. The pair status changes to “PAIR”.

3. Split the pair in “PAIR” status. The snapshot data is stored. The pair status changes to “PSUS”.

Note: Creating HTI pairs can take more time than usual if you create a pair immediately after deleting the last snapshot data for the P-VOL.

If you exceed the pool threshold while the HTI pair is in “PAIR” status, the pair status changes to “PFUL”. You cannot create additional HTI pairs when you have exceeded the pool threshold.

Note: If you exceed the pool threshold while the HTI pair is in “PSUS” status, the pair status changes to “PFUS”.


4. If you only want to delete snapshot data but you do not want to release the HTI pair, delete the snapshot data for the pair in “PFUS” status. If you want to release the HTI pair, delete the pairs.For more information about deleting pairs, see Deleting Thin Image pairs on page 1-11.

5. Restore the HTI pair in “PSUS” status. The snapshot data is overwritten to the P-VOL. While the pair is being restored, the pair status is “RCPY”.The restore process finishes. The pair status changes to “PAIR”.The pool can only contain data of predetermined capacity. If the total capacity of snapshot data in the pool exceeds the pool capacity, a failure occurs during the restore process, or if the pool usage rate reaches 100%, the status of the HTI pair changes to “PSUE”. Even if the restore process is not in progress, the pair status may change to “PSUE” if a failure occurs.

Hosts can read from or write to the HTI pair’s P-VOL or S-VOLs depending on the status of HTI pairs. The following table explains the details.

Copy threshold optionI/O performance of the host server might be lowered as the workload on the storage system increases. If you perform HTI restore operations when the workload on the storage system is high, I/O performance of the host server is more likely to be lowered because replication processes for the P-VOLs are triggered.

HTI pair statusP-VOL S-VOL

Read Write Read Write

SMPL Yes Yes No No

SMPL(PD) Yes Yes No No

COPY Yes Yes No No

PAIR/PFUL Yes Yes No No

PSUS/PFUS Yes Yes Yes Yes

RCPY Yes Yes No No

PSUE Yes Yes No No

LegendYes: Hosts can access the volumeNo: Hosts cannot access the volume

Caution: If a host uses an application to monitor HTI pair volumes, abnormal termination may occur depending on the status of an S-VOL. For example, a monitoring application may terminate abnormally if access from the application is rejected, because S-VOLs in a status other than “PSUS” and “PFUS” reject access from hosts. If a host connects to two or more ports, an abnormality may occur with ports that are not connected to S-VOLs rejecting access from hosts. To resolve these issues, you must terminate the application that monitors volumes.



Use the copy threshold option to temporarily stop the replication processes triggered by the restore operations when the workload on the storage system is high. The copy threshold option can contribute to minimizing the decline in I/O performance of the host server.

The copy threshold option is applicable only when the workload on the storage system is excessively heavy. If you apply the copy threshold option, all of the replication processes triggered by restore operations are stopped.

Replication processes stopped by the copy threshold option are restarted as the workload on the storage system is lowered. Enabling the copy threshold option stops replication processes for HTI and the following software applications when the storage system is overloaded:• SI• Volume Migration

For more information about the copy threshold option, call the Support Center.

Interoperability with other softwareCreate HTI pairs using pair volumes for replication software applications such as SI and TrueCopy (TC), or using volumes to which attributes are defined by Data Retention Utility or Command Control Interface.

The following table explains whether you can share pair volumes by HTI and other software applications.

Software application volume types Used as HTI P-VOL Used as HTI S-VOL

SI P-VOL Yes3 No

SI S-VOL Yes No

SI reserve volume No No

TC P-VOL Yes No

TC S-VOL Yes No

Universal Replicator (UR) P-VOL Yes No

UR S-VOL Yes No

UR journal volume No No

Volume Migration source volume No No

Volume Migration target volume No No

Volume Migration reserve volume No No

High Availability Manager (HAM) P-VOL No No

HAM S-VOL No No

HAM quorum disk No No

Nondisruptive Migration No No

Read Only volume1, 4, 6 Yes Yes

Protect volume1, 4, 6 Yes Yes

"S-VOL Disable" volume4, 6 Yes No


Data Retention UtilityCreate HTI pairs using volumes that have access attributes assigned by Data Retention Utility. The access attributes determines the pair operations and pool operations that you can perform using HTI.

The following tables explain whether you can perform HTI pair operations and pool operations on volumes that have access attributes assigned by Data Retention Utility.

Also, you can assign access attributes to HTI P-VOL and S-VOLs. The tables below also explain HTI pair operations and pool operations after access attributes are assigned.

Zero Read Capacity volume2, 5 Yes Yes

Invisible volume2, 5 Yes Yes

Reserve volume Yes Yes

DP-VOL Yes No

1. (If you use SN to share the volume with other software applications) The pair status determines whether you can share the volume.

2. Use the CCI to share the volume with other software applications.Note: You cannot use the SN to do share volumes.

3. You cannot Quick Restore.4. The Data Retention Utility is required to set Read Only, Protect, and S-VOL Disable

attributes.5. The CCI is required to set the Zero Read Capacity and Invisible attributes.6. Use Data Retention Utility to confirm whether Read Only, Protect, S-VOL Disable,

Zero Read Capacity and Invisible attributes are set to volumes.Yes: You can share the volumeNo: You cannot share the volume

Software application volume types Used as HTI P-VOL Used as HTI S-VOL

P-VOL access

attribute

S-VOL access

attribute

HTI pair operation

Create pair Split pair Suspend

pair

Resync pair

(Normal Copy)

Resync pair

(Reverse Copy)

Delete pair

Read/Write

Read/Write

Yes Yes Yes Yes Yes Yes

Read Only

No No No No No No

Protect No No No No No No

S-VOL Disable

No No No No No No



The following table show when Data Retention Utility can assign access attributes to HTI P-VOL and S-VOLs based on the HTI pair status.

Read Only, Protect, S-VOL Disable

Read/Write

Yes Yes Yes Yes No Yes

Read Only

No No No No No No

Protect No No No No No No

S-VOL Disable

No No No No No No

LegendYes: You can perform the pair operationNo: You cannot perform the pair operation

Access attribute of volume specified by HTI

HTI pool operation

Pool-VOL setting

Read/Write Yes

Read Only No

Protect No

S-VOL Disable No

LegendYes: You can perform the pair operationNo: You cannot perform the pair operation

Note: HTI pair operations do not change volume access attributes. Performing a reverse resynchronization does not copy S-VOLs to P-VOLs access attributes when writing snapshot data to P-VOLs.

P-VOL access

attribute

S-VOL access

attribute

HTI pair operation

Create pair Split pair Suspend

pair

Resync pair

(Normal Copy)

Resync pair

(Reverse Copy)

Delete pair

HTI volume Access attribute to be assigned

Pair status Volume Read/WriteRead Only

ProtectS-VOL Disable

COPY P-VOL Yes Yes

S-VOL Yes No

PAIR, PFUL P-VOL Yes Yes

S-VOL Yes Yes

PSUS, PFUS P-VOL Yes Yes

S-VOL Yes Yes


Volume MigrationYou cannot perform HTI pair operations on volumes in migration plans, regardless of the status of the migration plans. Also, you cannot use HTI pair volumes or pool-VOLs for Volume Migration migration plans.

ShadowImageYou can share HTI P-VOLs with SI P-VOL and S-VOLs. The following tables list the relationship between pair operations and status.

The following table shows the HTI pair operations that you can perform based on the SI pair status.

The following table shows the HTI pair operations that you can perform based on the SI pair status.

SMPL(PD) P-VOL Yes Yes

S-VOL Yes No

RCPY P-VOL Yes No

S-VOL Yes No

PSUE P-VOL Yes Yes

S-VOL Yes No

LegendYes: You can perform the settingNo: You cannot perform the setting

HTI volume Access attribute to be assigned

Pair status Volume Read/WriteRead Only

ProtectS-VOL Disable

HTI pair operation

SI pair status

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

Store Snapshot data

Yes Yes Yes Yes Yes Yes No Yes

Restore pair No No No No Yes No No Yes

Delete Snapshot data

Yes Yes Yes Yes Yes Yes Yes Yes

Release pair Yes Yes Yes Yes Yes Yes Yes Yes

LegendYes: You can perform the pair operationNo: You cannot perform the pair operation (the command is rejected)



The following table shows the SI pair operations that you can perform based on the HTI pair status.

HTI pair operation

SI pair status

COPY(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

Store Snapshot data

N/A No No No Yes No No No

Store Snapshot data for a consistency group

N/A No No No Yes* No No No

Restore pair N/A No No No Yes No No No


N/A Yes Yes Yes Yes Yes Yes Yes

Release pair N/A Yes Yes Yes Yes Yes Yes Yes

* The status of the SI pair must be “PSUS” during the period between when HTI starts to store snapshot data for a consistency group and when the status of all pairs in the consistency group changes to “PSUS”. If the SI pair status changes to a status other than “PSUS” when snapshot data for the consistency group is being stored, the storage system cannot guarantee the consistency of the snapshot data.LegendYes: You can perform the pair operationNo: You cannot perform the pair operation (the command is rejected)N/A: Not applicable

SI pair operation

HTI pair status

COPY PAIR, PFUL

PSUS, PFUS SMPL(PD) RCPY PSUE

Create pair Yes Yes Yes Yes No Yes

Create and split pair


Split pair Yes Yes Yes Yes No Yes

Normal Copy Yes Yes Yes Yes No Yes

Reverse Copy Yes Yes Yes Yes No Yes

Quick Restore No No No No No No

Suspend replication


Delete pair Yes Yes Yes Yes Yes Yes



The following table shows the SI pair operations that you can perform based on the HTI pair status.

Even after snapshot data is stored, you can operate SI pairs. In this case, the storage system cannot maintain the consistency of the stored snapshot data.

Because an HTI S-VOL uses the data in the P-VOL, you cannot perform the SI Quick Restore pair operation.

For more information about SI pair operations and pair statuses, see the Hitachi ShadowImage® User Guide.

TrueCopy and Universal ReplicatorYou can share HTI P-VOLs with TC and UR pair volumes. The following tables list the relationship between pair operations and status.

The following table shows the HTI pair operations you can perform based on the TC/UR status.

SI pair operation

HTI pair status

COPY PAIR, PFUL

PSUS, PFUS

SMPL(PD) 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

Normal Copy Yes Yes Yes Yes No Yes

Reverse Copy Yes Yes Yes Yes No Yes

Quick Restore No No No No No No

Suspend replication




Caution: The MU numbers used by HTI are 0 to 1,023, and they are assigned in the order of 3 to 1,023, followed by 0 to 2. On the other hand, the MU numbers used by SI are 0 to 2. Therefore, if HTI uses the MU number 0 to 2, HTI cannot share the volume with SI. To share a volume with HTI and SI, delete the HTI pair of the MU number 0 to 2. Then, create SI pairs and HTI pairs.

HTI pair operation

TC/UR status

COPY PAIR PSUS PSUE Suspending Deleting

Create pair Yes Yes Yes Yes Yes Yes



The following table shows the HTI pair operations you can perform based on the TC/UR status.

The following table shows the TC/UR pair operations you can perform based on the HTI status.

Store Snapshot data


Restore pair No No Yes Yes No No





HTI pair operation

TC/UR status

COPY PAIR PSUS PSUE Suspending Deleting

HTI pair operation

TC/UR status

COPY PAIR PSUS PSUE SSW

SSuspendin

g Deleting

Create pair Yes Yes Yes Yes Yes Yes Yes

Store Snapshot data No Yes Yes Yes Yes Yes Yes

Restore pair* No No No No No No No

Delete Snapshot data Yes Yes Yes Yes Yes Yes Yes

Delete pair Yes Yes Yes Yes Yes Yes Yes

* If you want to restore an HTI pair whose P-VOL is used as a TC or UR S-VOL, switch pair operations to the remote site using the horctakeover command.LegendYes: You can perform the pair operationNo: You cannot perform the pair operation (the command is rejected)

TC/UR pair operation

HTI status

COPY PAIR, PFUL PSUS, PFUS RCPY PSUE

Create pair Yes Yes Yes No Yes

Split pair Yes Yes Yes N/A Yes

Resynchronize pair Yes Yes Yes No Yes

Delete pair Yes Yes Yes Yes Yes

Switch to remote site

Yes Yes Yes No Yes


The following table shows the TC/UR pair operations you can perform based on the HTI status.

Dynamic ProvisioningIf you use HTI, DP, and HDPz in one storage system, note the following:• While the storage system is expanding the DP V-VOL capacity, you

cannot create an HTI pair whose P-VOL is a DP V-VOL.• Performing an HTI paircreate operation while zero pages are being

reclaimed (including reclamation by Writesame, Unmap command, or rebalancing) results in the zero-page operation being interrupted.

• HTI pair creation might be rejected if the Unmap command operation is in progress with system option mode 905 ON. Wait a while and then retry the operation. If the operation still fails, set system option mode 905 to OFF and retry again.

• You can use a DP volume size up to 4 TB (4,398,046,511,104 bytes) as an HTI P-VOL.When creating a DP V-VOL, if you specify TB, GB, or MB as the unit, you cannot create a volume of 4 TB (4,398,046,511,104 bytes). To create a volume of 4 TB (4,398,046,511,104 bytes), specify block as the unit.

LegendYes: You can perform the pair operationNo: You cannot perform the pair operation (the command is rejected)N/A: Not applicable


HTI status



HTI status


Create pair No No No No No

Split pair Yes Yes Yes N/A Yes

Resynchronize pair Yes Yes Yes N/A Yes

Delete pair Yes Yes Yes N/A Yes

Switch to remote site Yes Yes Yes N/A Yes

* If you want use a TC/UR S-VOL as an HTI P-VOL, first create the TC/UR pair then create the HTI pair.For more information about TC pair operations and pair status, see the Hitachi TrueCopy® User Guide. For more information about UR pair operations and pair status, see the Hitachi Universal Replicator User Guide.LegendYes: You can perform the pair operationNo: You cannot perform the pair operation (the command is rejected)N/A: Not applicable



The following table shows how the maximum LDEV capacity differs depending on the unit you specify.

For more information about creating V-VOLs and about specifying LDEV capacity and capacity unit, see Creating V-VOLs on page 3-5.

Resource Partition ManagerYou can create an HTI pair regardless of whether the P-VOL and S-VOLs are assigned to the same resource group or different resource groups. However, the pool to be used must be assigned to the resource group where the P-VOL is assigned or to the resource group where creation of HTI pairs is allowed.

For more information about resource groups, see the Hitachi Unified Storage VM Block Module Provisioning Guide.

Software application acronyms and abbreviationsThis document uses the following acronyms and abbreviations for software product names:• DP: Dynamic Provisioning• HDPz: Dynamic Provisioning for Mainframe• HUS VM: Hitachi Unified Storage VM• UVM: Universal Volume Manager• SI: ShadowImage• HTI: Hitachi Thin Image• TC: TrueCopy

Unit specification Maximum LDEV capacity

TB 3.99

GB 4,095.99

MB 4,194,303.75

block 8,589,934,592

2

Planning and design requirements 2–1Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Planning and design requirements

This topic discusses planning and design requirements for HTI. Read this topic before using HTI.

□ System requirements

□ Requirements for Thin Image operations


2–2 Planning and design requirements

System requirementsHTI operations require a HUS VM storage system with P-VOL and S-VOLs. HTI operations also require HTI and DP, which run on SN computers.

Requirements for Thin ImageTo use HTI, you must configure and set up the hardware and microcode and use SN to make sure that a license key for DP is installed.

For more information about license keys and installation, see the Hitachi Storage Navigator User Guide.

Installing Thin Image

The following procedure details how to install HTI:1. Install DP, which is prerequisite software for HTI.2. Install HTI.

Uninstalling Thin Image

The following procedure details how to uninstall HTI:1. Release all HTI pairs.2. Delete all pools.3. Uninstall HTI.

Requirements for licensed capacityIf you use HTI, the capacity licensed for the HTI P-VOLs and pools is needed. The capacity of pools which are used for HTI is subtracted from the licensed capacity for DP. Therefore, if you use HTI, secure the licensed capacity for DP more than the total capacity used for both DP and HTI.

The following table shows the HTI volumes and capacity calculated as the HTI usage. The total amount of these values must not exceed HTI license capacity.

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

The intended volumes

The intended capacitySoftware application The kind of

volumes

Normal volume or DP-

VOL

HTI P-VOL Normal volume The volume capacity

DP-VOL The pool capacity used by the volume

Pool VOL Normal volume The volume capacity


Shared memory requirementsHTI requires dedicated shared memory for the HTI pair management area. The HTI pair management area is used to store information of HTI pairs. This area is automatically created when shared memory is added.

HTI requires at least 16 GB shared memory that consists of 2 sections. If you are using HTI and you create a pool or V-VOL capacity, it is expanded depending on the status of the shared memory installed. If you use a pool or V-VOL that has a capacity of 1,700TB or more, you must install SI/VM/DP Extension2, TI Extension.

To remove SI/VM/DP Extension2, TI Extension, first delete all of the pools for DP, HDT, and HTI.

If you want to install the shared memory, contact Hitachi Data Systems service representative.

Volume requirementsHTI requires the following types of volumes:• P-VOLs• S-VOLs• pool-VOLs

The following tables explain requirements for HTI P-VOLs, S-VOLs, and pool-VOLs. HTI uses DP pool-VOLs.

The following table shows the requirements for HTI P-VOLs.

The following table shows the requirements for HTI S-VOLs.

Item Requirement

Volume type Logical volumes (LDEVs).You cannot specify the following volumes as HTI P-VOLs:• pool-VOLs• HTI S-VOLs• LUSE volumesFor more information about creating pairs using other software applications, see Interoperability with other software on page 1-14.

Emulation type OPEN-V

Maximum number of volumes 6,400Note: This value can be increased depending on your system configuration.

Maximum number of HTI pairs See Calculating the number of Thin Image pairs that you can create on page 2-7.

Path definitions Required.

Maximum volume capacity 4TB



The following table shows the requirements for HTI pool-VOLs.

Item Requirement

Volume type V-VOLsYou cannot specify the following volumes as HTI S-VOLs:• Volumes that are already used as S-

VOLs• Volumes that other software

applications are using for pairs or migration plans

• LUSE volumesFor more information about calculating the maximum number of V-VOLs, see Calculating the number of virtual volumes that the storage system can create on page 2-7.

Emulation type OPEN-VNote: If you use the CCI, Open-0V is shown.

Maximum number of volumes 12,800Note: This values can be increased depending on your system configuration.

Maximum number of pairs See Calculating the number of Thin Image pairs that you can create on page 2-7.

Path definitions Required


Item Requirement

Volume type Logical volumes (LDEV)The following configurations are recommended to maintain performance levels:• Do not mix normal volumes and pool-VOLs in a parity group.• Make sure that pool-VOLs consist of LDEVs from multiple parity

groups.• Assign different processor blade IDs* to LDEVs that make up pool-

VOLs.You cannot specify the following volumes as HTI pool-VOLs:• Volumes whose volume status is other than “Normal” or “Normal

(Quick Format)”. If the storage system is in the process of blocking or copying a volume, you cannot specify the volume.

• LUSE volumes• Volumes that are already being used as HTI primary or S-VOLs.• Volumes that are already contained in HTI, DP, or HDT pools.• Volumes used as migration plans or pair volumes for another

software application.• Volumes with Protect or Read Only attribute, or the S-VOL Disable

attribute setting (Data Retention Utility).• Hitachi Cache Residency Manager (CRM) volumes.• System disks• Command devices• HAM quorum disksAlso, note the following:• You combine external pool-VOLs whose cache mode is enabled with

those whose cache mode is disabled in the same data pool.• You cannot combine volumes in different resource groups in the

same data pool.• You cannot use internal volumes and external volumes whose

cache mode is disabled in the same data pool.

Emulation type

OPEN-V

RAID level All RAID levels are supported.

Hard disk drive type

You can use SAS and SSD.If you use internal and external volumes, you can use pool-VOLs with different drive types in the same pool. For best performance, use pool-VOLs with the same drive type in the same pool.

CLPR A data pool cannot contain pool-VOLs belonging to different cache logical partitions (CLPRs). You cannot change CLPRs in the parity group belonging to the pool-VOL.

Maximum number of pool-VOLs

You can add up to 1,024 pool-VOLs to a pool. You can create up to 128 pools in a storage system.If a volume is already contained in a pool, you cannot contain the pool-VOL in another pool. The number of available pools for HTI decreases according to the number of DP pools (including HDT pools).You can only add volumes that are assigned the same CLPRs to the same pool. One RAID level is permitted in the same pool.



Consistency group requirementsThis topic lists the requirements for consistency groups.

The following table explains requirements for consistency groups.

Notes on consistency groups

Note the following in regards to consistency groups:• You cannot define HTI pairs that share the same P-VOL in the same

consistency group. If you do, the raidcom add snapshot CCI command is rejected.

• Keep HTI pairs defined in consistency groups and pairs not defined in consistency groups separate in groups that are defined by the configuration definition file for the CCI. These groups are not consistency groups. If you mix these pairs, the pairsplit CCI command may finish abnormally. Also, if you store snapshot data from the P-VOL when HUS VM receives the pairsplit CCI command, the storage system cannot guarantee the data.

• Specify only one consistency group for a group defined by the configuration definition file for the CCI.

Volume capacity

8 GB to 4 TB

Path definition If you define unneeded paths to a volume, you cannot specify the volume as a pool-VOL.

* For more information about how to change processor blade IDs, see the Hitachi Unified Storage VM Block Module Provisioning Guide.

Item Requirement

Item Description

Consistency group number Assign a number from 0 to 255 when creating a pair. If you do not assign a number, an unassigned number is automatically assigned. Consistency group numbers appear in the following items in the GUI:• Consistency Group tab of the Local Replications

window• Consistency Group Properties window• Volume list in the Pair Operation window for SIYou can create up to 256 consistency groups in a storage system, with consistency groups for SI, and HTI combined.(For HTI only) You can also use consistency group numbers 128 to 255 (80 to FF).

Number of pairs You can create up to 8,192 pairs in a consistency group. You cannot mix SI and HTI pairs in a consistency group. HTI consistency groups can only contain HTI pairs.


To create pairs using a group defined by the configuration definition file for the CCI, and if a pair with a consistency group specified is already created in the group, the pair is added to the same consistency group even if you attempt to create a new pair in a different consistency group.To specify multiple consistency groups, you must define the same number of groups using the configuration definition file for the CCI.

Snapshot group requirementsThe following table explains requirements for snapshot groups.

Requirements for Thin Image operationsThis section discusses points you should consider when performing HTI pair operations.

Calculating the number of virtual volumes that the storage system can create

Use the following formula to calculate the maximum number of V-VOLs that the storage system can create:

The maximum number of V-VOLs = 12,800* - (The number of external volumes + The number of P-VOLs for HTI pairs)

* Your system configuration determines the maximum value in this formula.

Calculating the number of Thin Image pairs that you can createThe number of HTI pairs that you can create in a storage system depends on the shared memory capacity for V-VOL management areas, or the number of pair tables.

Use the following workflow to calculate the number of HTI pairs that you can create:1. Calculate this number using the shared memory capacity for V-VOL

management areas, and the number of pair tables, respectively.

Item Description

Name The name of the snapshot group.Character limit: 32 charactersOnce you create a snapshot group, you cannot change its name.

Maximum number • The maximum number of snapshot groups for one storage system is 512.

• The maximum number of HTI pairs for one snapshot group is 8,192.



2. Compare the three calculation results. The smallest of the two is the maximum number of HTI pairs that you can create in the storage system.

Calculating the number of Thin Image pairs based on pair tables

Pair tables contain information required for managing HTI pairs. Creation of one HTI pair requires one each table. You can use up to 1,048,575 pair tables in a storage system.

Use the following formula to calculate the number of HTI pairs you can create:

1,048,575 - (the number of HTI pairs that were created)

For example, if the number of HTI pairs that were created is 30,000, use the following formula to calculate the number of HTI pairs you can create:

1,048,575 - 30,000 = 1,018,575

The calculation result shows that you can create up to 1,018,575 HTI pairs.

An HTI pair consists of one P-VOL and up to 1,024 V-VOLs.

Calculating the number of Thin Image pairs based on the snapshot estimated manageable capacity

To view the snapshot estimated manageable capacity, in the Storage Systems tree, click Replications > Local Replications.

To calculate the number of HTI pairs you can create, use the following formula:

The number of HTI pairs you can create = the number of Snapshot estimated manageable capacity / the Snapshot management capacity per one P-VOL

To calculate the Snapshot management capacity per P-VOL, use the following formula:

The Snapshot management capacity per P-VOL = (the P-VOL capacity of HTI pairs [TB] / 2.6 [TB]) * 3,024 [GB] + (168GB * 2 (consumed shared memory))

Calculating the number of Thin Image pairs workflowUse the following process to calculate the number of HTI pairs based on the number of cache management devices:1. View the number of cache management devices. Click Action > View

Management Resource Usage.2. Calculate the number of HTI pairs that you can create. Use the following

formula to calculate the number:

Note: If DP volumes are already created in the storage system, you can create an even smaller number of HTI pairs.


(the Number of cache management devices / the P-VOL capacity of HTI pairs [TB]) / 2.6 [TB]

Calculating the number of cache management devicesThis section explains the number of cache management devices that are required to perform HTI pair operations.

Cache management devices are the unit for controlling the cache in association with LDEVs. Each LDEV requires at least one cache management device.

You can manage up to 65,280 cache management devices in a system. Use the View Management Resource Usage window to view the number of cache management devices.

For more information about LDEVs and cache management devices required for DP-VOLs, see the Hitachi Unified Storage VM Block Module Provisioning Guide.

The number of cache management devices required for Thin Image pair operations

HTI assigns 4,096 of the 8,192 cache management devices. 8,192 cache management devices must be available to create an HTI pool for the first time. 4,097 or more cache management devices must be available to create an HTI pair for a volume for the first time.

Use the following formula to calculate the number of cache management devices you need to create an HTI pair for a volume for the first time:

ceil(Size of P-VOL ÷ 2.6) (in terabytes)

If the amount of pool usage for the P-VOL exceeds 70 percent of the total capacity of the cache management devices reserved for the P-VOL, you must reserve an additional cache management device. Up to 256 cache management devices are required for a P-VOL.

Effects on I/O performance of the storage systemIf you perform HTI restore operations when the workload on the storage system is high, I/O performance of host servers can decline because replication processes for the P-VOLs are triggered. You can use the copy threshold option to lower the workload on the storage system.

For more information about using the copy threshold option, see Copy threshold option on page 1-13.

Notes on assigning the pool capacityYou can calculate the capacity of which to store snapshot data in the pool using the following formula:

Pool capacity = the total capacity of pool-VOLs in the pool - the capacity of V-VOL management areas



The capacity of V-VOL management areas is 3% of the pool capacity. If the pool capacity is insufficient, the status of HTI pairs may change to “PSUE”. Therefore, you must do the following:• Estimate the capacity of snapshot data to be copied to the pool.• Assign the pool capacity based on the estimate. If the capacity of

snapshot data to be copied to the pool varies hour by hour, make sure that the largest capacity is your pool capacity.

If snapshot data is copied to the pool, the pool capacity is always consumed in units of 42 megabytes. Even if snapshot data is smaller than 42 megabytes, at least 42 megabytes of pool capacity is needed.

It is recommended the capacity of a pool-VOL should be multiples of 42 megabytes. If the capacity of a volume specified as a pool-VOL is not multiples of 42 megabytes, the fraction of less than 42 megabytes is truncated.

Estimating the capacity of snapshot data to be copied to the pool

To decide the capacity of pools, estimate the capacity of snapshot data to be copied.

The capacity of snapshot data to be copied equals to the capacity of data written to the same area in the P-VOL during the period from when snapshot data is stored to when the snapshot data is deleted.

If multiple snapshot data are stored, the data may be shared in a pool. If there are the snapshot data containing the shared data, you can release HTI pairs, but you cannot delete the snapshot data from the pool. If you release all HTI pairs that have snapshot data containing the shared data, the snapshot data are also deleted from the pool.

To create a backup data using HTI, store snapshot data then use an S-VOL. In this case, the target for the backup is only the areas where the snapshot data is stored. You can create backup copies even when the pool capacity is small. While you are creating a backup copy, a large amount of data is read from the S-VOL. This may increase the accesses to the P-VOL and degrade the host I/O performance.

Although the pool capacity is decided according to the estimation, if the pool capacity exceeds the threshold, address the issue.

For more information about addressing exceeding pool capacity threshold issues, see General troubleshooting on page 6-2.

Using external volumes as pool-VOLsYou can use UVM to connect your HUS VM storage system to other storage systems. In UVM terminology, your HUS VM storage system is referred to as a local storage system, and the other storage systems are referred to as external storage systems. Volumes in external storage systems are referred to as external volumes. Volumes in a local storage system are referred to as internal volumes.


If UVM is installed, you can use external and internal volumes as pool-VOLs. However, if you use external volumes, the likelihood of failure increases and the disaster recovery is more complex and challenging.

If you use external volumes as pool-VOLs, use one pool for one external storage system to minimize adverse effect of failure.

You can use multiple external volumes as pool-VOLs in a pool. However, if external volumes are used, it increases the likelihood of a failure. For example, the pool might be blocked. If the external pool-VOLs are blocked due to a failure, the pool is also blocked.

For more information about how to restore a blocked pool, see Blocked pool recovery workflow on page 6-5.

For more information about external storage systems and disaster recovery methods for external volumes, see the Hitachi Universal Volume Manager User Guide.

3

Performing configuration operations 3–1Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Performing configuration operations

This topic describes creating pools, creating V-VOLs, and settings of the command device for configuring HTI.

□ Configuration workflow

□ Creating pools

□ Creating V-VOLs

□ Setting up command devices


3–2 Performing configuration operations

Configuration workflowUse the following configuration operations workflow to configure HTI. The following image shows the workflow.

You must create a V-VOL management area in the shared memory before you create pools. The V-VOL management area is created when additional shared memory is installed. For more information about the additional shared memory, contact the Hitachi Data Systems Support Center.

After you have create the HTI pairs and acquired the snapshot data, you can maintain the HTI pair status. Delete any unneeded snapshot data or HTI pairs. Releasing HTI pairs deletes the snapshot data, which are acquired with the HTI pair, from the pool.

When the recovery operation is performed after a failure occurred, you can write snapshot data over the P-VOL. While recovering an HTI pair, you cannot recover other HTI pairs.

For more information about operations on HTI pairs and pair statuses, see Pair operations on page 4-1.

Creating poolsThis topic describes how to create data pools using SN.

If you create pools, the new pool-VOL with system area is set automatically according to the priority of hard disk drive types explained in the following table.

Priority Hard disk drive type

1 SAS7.2K

2 SAS10K

3 SAS15K

4 SSD

5 External volume


If plural pool-VOLs of the same hard disk drive type exist, the priority of them is determined according to the internal index information of the storage system.

Related topics• Create Pools wizard in Hitachi Unified Storage VM Block Module

Provisioning Guide1. In the Storage Systems tree, select Pools.2. In the Pools window, click Create Pools.3. In the Create Pools window, complete the following and then click

Options: For Pool Type, select Thin Image.

Required: Yes Select a pool-VOL by completing the following:

- For Drive Type/RPM, select your system's data drive type and RPM.Values: External StorageMaximum volume: 3- For RAID Level, select the system's RAID level.

Values: Mixed4. Click Select Pool VOLs.5. In the Select Pool Volumes window, complete the following and then

click OK: For Pool Name, type the prefix and initial number for the pool name.

Required: YesCharacter limit: 32- For Prefix, type alphanumeric characters as the prefix. Case sensitive: Yes- For Initial Number, type a number.Digit limit: 9The information in the Selected Pool Volumes table is applied to Total Selected Pool Volumes and Total Selected Capacity.

From the Available Pool Volumes table, select the pool-VOLs that you want to assign and click Add.The selected pool-VOLs are registered to the Select Pool Volumes list.

6. (Optional) Complete the following:- To filter the rows, in the Filter component, select ON.- To select all pool-VOLs in the list, click Select All Pages.

Note: If you selected External Storage as the system’s data drive type and RPM, a dash (-) is shown for this item and this item is unavailable.



- To specify the capacity unit and the number of rows to be shown, click Options and make the selection.

Initial Pool ID and other items are shown on the page.7. Complete the following and then click Add:

For Initial Pool ID, type the identifier.Allowable characters: Integer numbersRange: 0 to 127Default: the smallest available number.If an available pool ID does not exists, a number does not appear. When you type the registered pool ID, the smallest available pool ID is automatically registered among the subsequent pool ID that you entered.

For Warning Threshold, type a data pool capacity threshold.Range: 20% and 95%Default: 80%

The created pool is added to the Selected Pools table. If you set invalid values, an error message appears.

8. Click Finish.9. In the Confirm window, complete the following and then click Apply:

For Task Name, type the name for the task. Character and symbol limit: All 32 alphanumeric except \ / : , ; * ? " < > |Default: date-task name

(Optional) For Go to tasks window for status, select to open the Tasks window.

The pool is created.

Caution: You cannot delete the added pool-VOL. Make sure that the pool-VOL settings are correct.


Creating V-VOLsThe V-VOL is the paired volume of the pool VOL. You must create a V-VOL before you can create the pair.

1. Click one of the following tabs and then click Create LDEVs: The LDEV tab when selecting Logical Devices The Pool tab when selecting Pool

2. In the Create LDEVs window, complete the following and then click Options: For Provisioning Type, confirm that Snapshot is selected. If it is

not selected, select it from the menu.Required: Yes

For LDEV capacity, type the capacity of the V-VOL.You can use decimals up to two decimal places.

Required: Yes

Caution: (If you boot or reboot a host server (such as HP-UX or Solaris) or when you use the host server to run the read command on a V-VOL to recognize a device) Keep the following in mind:• You cannot change the volume of the device recognized by the host

server to a V-VOL.• You must create the HTI pairs and acquire the snapshot data before you

boot or reboot the host server or you run the command for recognizing devices (The pair status of the V-VOL recognized by the host server must be “PSUS”).

If you do not fulfill all of the above conditions, the devices may not be recognized or failures can occur and the host server may stop. If you booted or rebooted the host server, or you ran commands to recognize devices and stopped the host server, run the commands:1. Forcibly stop the process of the command and its parent process.2. Create the HTI pair.3. Get the snapshot data.4. Rerun the command to recognize devices.• On the server (including the CCI), the V-VOL emulation type is shown

with a zero (0) (Example: OPEN-0V). If you create an HTI pair, specify a volume whose emulation type is shown with a zero (0) for the S-VOL, such as OPEN-0V.

• Define the V-VOL groups before you create V-VOLs. The emulation type of the VDEV for the V-VOL group is OPEN-V like the V-VOL type. This VDEV capacity is always 4 TB, and the maximum capacity of a V-VOL is 4 TB, too.

Note: You can change the LDEV capacity unit using the unit capacity menu.



For Number of LDEVs, type the number of V-VOLs (LDEVs) to be created.The range is shown below the item.Required: Yes

For LDEV Name, type the name for the V-VOL.- For Prefix, type the alphanumeric characters, which are fixed characters that precede the V-VOL name.Case-sensitive: Yes- For Initial Number, type the initial number for V-VOL.Limit: 9 digitsMaximum characters: 32 (for the Prefix and Initial number combined)

3. In the window, complete the following required items using valid values, click Add, and then click Finish: For LDEV ID, type the LDEV identifier. For Initial LDEV ID, set the initial LDEV ID.

To confirm the used number and unavailable number, click View LDEV IDs.

For Cache Partition, select the CLPR. From the MP Unit ID list, if an MP unit ID has been assigned, select

the MP unit ID for the LDEVs. If you have not yet assigned an MP unit ID, click Auto.

The created V-VOLs are added to the Selected LDEVs table.4. In the Confirm window, to continue to set the logical unit (LU) path and

define LUN, click Next.For more information about LU path settings, see the Hitachi Unified Storage VM Block Module Provisioning Guide.

5. (Optional) Change the V-VOL settings.For more information about changing the V-VOL settings, see Changing the V-VOL settings on page 3-7.

6. (Optional) Delete a row from the Selected LDEVs table.For more information about removing the V-VOL to be registered, see Removing V-VOLs on page 3-7.

7. Complete the following: For Task Name, type the task name and then click Apply.

Character limit and symbols: All 32 alphanumeric except \ / : , ; * ? " < > |Default: date-Task Name

(Optional) For Go to tasks window for status, select to open the task window.

The settings are registered to the task.


Related topics• Create LDEVs wizard in the Hitachi Unified Storage VM Block Module

Provisioning Guide.

Changing the V-VOL settingsUse this task to change the V-VOL settings. Before registering a V-VOL, you can optionally change V-VOL settings.1. In the Create LDEVs window, in the Selected LDEVs table, select

LDEV and click Change LDEV Settings.2. In the Change LDEV Settings window, change the following settings

and click OK: For LDEV Name, specify the prefix characters and the initial number

of LDEV. For Initial LDEV ID, specify the LDKC, CU, LDEV number and the

interval. To check used LDEVs, click View LDEV IDs to confirm the used LDEVs. The View LDEV IDs window opens.

For MP Unit ID, click the list and specify the MP unit ID. To specify an arbitrary MP unit, click Auto.

3. In the Create LDEVs window, click Finish.4. In the Confirm window, complete the following and then click Apply:


The settings are registered to the storage system.

Removing V-VOLsThis procedure describes how to remove the V-VOL that you want to register. If you do not want to register the V-VOL, remove it from the registering task queue.1. In the Selected LDEVs table in the Create LDEVs window, select the

LDEV you want to remove, and then click Remove.2. In the dialog box that displays, click OK to confirm that you want to

remove the V-VOL from the registering task queue.3. In the Create LDEVs window, click Finish.4. In the Confirm window, complete the following and then click Apply:


The V-VOL is removed from the registering task queue.

Setting up command devicesTo use the CCI and an in-band connection to perform HTI operations, reserve a volume for use as a command device. It is not necessary to reserve a volume for use as a command device to use the CCI and an out-of-band connection.



Running the CCI commands through an out-of-band connection can degrade the host I/O performance. Run the CCI commands through an in-band connection.

4

Pair operations 4–1Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Pair operations

This chapter provides instructions for performing pair operations.

□ Creating HTI pairs

□ Acquiring snapshot data

□ Restoring pairs

□ Deleting snapshot data

□ Deleting pairs


4–2 Pair operations

Creating HTI pairsThis topic explains how to create an HTI pair. You can create up to 1,024 pairs at the same time. To create more than 1,024 pairs, repeat the pair operation.

When specifying the P-VOL and S-VOLs, make sure that the size of the two volumes is the same. When specifying a P-VOL that is already used as the P-VOL of another HTI pair, make sure that the two HTI pairs share the same pool.

Prerequisite• You have the Storage Administrator (Local Copy) role.• To use the SI volumes as HTI volumes, first create the SI pair then

create the HTI pair.• To use an SI volume as an HTI P-VOL when an available MU number does

not exist, you must complete the following:a. Delete the HTI pairs that are associated with MU numbers 0 to 2.b. Create the SI pair.c. Recreate the HTI pair with an MU number of 3 or greater assigned.

1. Complete one of the following: In the Storage Systems tree, click Replications > Local

Replications. In the Pairs tab, click Create Pairs. In General Tasks, click Create Pairs.

2. In the Select Pair Configuration window of the Create Pairs wizard, complete the following and then click Next: For Copy Type, select Thin Image.

Default: Thin Image For Number of Secondary Volumes, type the total number of S-

VOLs (including the already configured pairs) that corresponds to the single P-VOL.Default: 1

3. In the Select Primary Volumes window of the Create Pairs wizard, complete the following and then click Next: For Use Primary Volumes of Snapshot Pairs, select the kind of

volumes you want to add the Available LDEVs table:- Yes shows LDEVs that are already used as P-VOLs.

Note: After creating an HTI pair, if the number of pairs shown on the summary tab and on the list are different, the system is still processing the information. If this is the case, wait until the configuration information has completed processing. If the numbers remain different, click File > Refresh All.

Caution: To prevent suspending the HTI pair (“PSUE” status), do not create HTI pairs while shutting down the storage system.


- No shows LDEVs that are not used as P-VOLs.If you select No, complete the following and then click OK:- Click Select Pool.- In the Select Pool window, select a pool.

From the Available LDEVs table, select an LDEV to be the P-VOL and click Add.The LDEV is moved to Selected LDEVs.

4. In the Select Secondary Volumes window of the Create Pairs wizard, complete the following and then click Finish: From the Available LDEVs table, select the LDEV that you want to

use as a S-VOL, and then select a snapshot group. If you need to create a new snapshot group, type the name and click Set.The selected LDEV is shown in the Selected Pairs table.To show the LDEVs that match the selected capacity in the Available LDEVs and Selected Pairs tables, for Capacity:, select a capacity.Select whether to create a new snapshot group or use the defined snapshot group. The snapshot group setting is necessary when you create a HTI pair.Values:- Create new snapshot group: Enter new snapshot group name.- Use defined snapshot group: Select the desired snapshot group.If you create pairs in a snapshot group by running the raidcom add snapshot CCI command, the pairs can also belong to the consistency group. An example of creating pairs with specifying the P-VOL (LDEV#10:10), the S-VOL (LDEV#20:20), and the pool (SnapPool00) in the snapshot group (db1) and add pairs in a consistency group is shown below.

raidcom add snapshot -ldev_id 0x1010 0x2020 -pool SnapPool00 -snapshotgroup db1 -snap_mode CTG

To delete the pair in the selected row, click Remove.To configure a pair, select a row in the Available LDEVs table and a row in the Selected Pairs table and then click Set.

5. In the Confirm window of the Create Pairs wizard, for Task Name, type a name for the task and then click Apply.

Related topics• Using Storage Navigator to create HTI pairs workflow on page 4-3

Using Storage Navigator to create HTI pairs workflowUse this procedure to create HTI pairs using SN.1. Select the pair configuration.2. Select the P-VOL.3. Select the S-VOL.



4. Perform confirmation.

The following points should be noted when you create the desired pair configuration.

In the main window, pairs are configured as shown in the following figure based on the number of S-VOLs corresponding to the P-VOL. S-VOLs are assigned in the order of 1 to 1,024.

The following figure shows the configuration showing a P-VOL with 1,024 S-VOLs assigned.

To add S-VOLs to an existing pair, the value for Number of Secondary Volumes must be larger than the current number of S-VOLs of the existing pair.

For example, if you add a pair to an existing pair of one P-VOL and one S-VOL as shown in the following figure, you must type 2 for Number of Secondary Volumes.

The following figure illustrates an S-VOL that you added to an existing pair made up of one P-VOL and one S-VOL.


If you simultaneously create multiple pairs among which the number of S-VOLs differs, make sure that the value for Number of Secondary Volumes is the largest number among those pairs. After that, you must perform deletion when selecting S-VOLs.

The following is an example of creating pairs of different configurations simultaneously. In this example, one pair of two S-VOLs and another pair of one S-VOL are created simultaneously.1. Type 2 as the number of S-VOLs, and select two P-VOLs.

The storage system assumes two pairs of two S-VOLs each are created.2. When selecting a S-VOL, select and delete the S-VOL MU#1 of the

second pair. By deleting a S-VOL, you can create multiple pairs of different configurations.The following image shows how to simultaneously create multiple pairs of different pair configurations.

Acquiring snapshot dataYou can acquire up to 1,024 snapshots from a single P-VOL. This topic explains how to acquire snapshot data.

Prerequisites• You have the Storage Administrator (Local Copy) role.• The HTI pair status is “PAIR”.1. In the Storage Systems tree, click Replications > Local

Replications.2. In the Pairs tab, select the pair you want to split, then click Split Pairs.3. In the Split Pairs window, click Finish.4. In the Confirm window, for Task Name, type a name for the task and

then click Apply.The snapshot data is acquired.



Acquiring snapshot data using the At-Time Snapshot functionUse the CCI’s At-Time Snapshot function to acquire snapshot data for a consistency group.1. Add pairs to the same consistency group. To do this, run the following

CCI command using an option to specify the consistency group number as the target of the At-Time Snapshot function:raidcom add snapshot

The At-Time Snapshot function is automatically enabled and a consistency group is created.Run this CCI command as many times as necessary.

2. Create the snapshot data. To do this, run the following CCI command on the consistency group that is the target of the At-Time Snapshot function:raidcom modify snapshot -snapshot_data create

3. Acquire the snapshot data. To do this, from a host, issue a write request to the P-VOL of an HTI pair in the consistency group.The snapshot data is acquired.

At-Time Snapshot when Thin Image volume shared with UR and TC

When HTI P-VOLs are shared with UR or TC S-VOLs within a storage system, you can place the HTI pairs in a consistency group and use the At-Time Snapshot function to maintain consistency for multiple HTI S-VOLs. The following figures illustrate these configurations.

The following figure shows the At-Time Snapshot configuration with UR.


The following figure shows the At-Time Snapshot configuration with TC.



The following table explains when you can perform the At-Time Snapshot function based on the pair status.

You cannot maintain consistency for the HTI S-VOLs in the following cases:

If HTI P-VOL is used as and the pair status is

Can you run the At-Time Snapshot?

UR S-VOL COPY No

PAIR Yes

PSUS Yes

TC S-VOL COPY No

PAIR Yes

PSUS Yes

SI S-VOL COPY No

PAIR No

COPY(SP) No

PSUS(SP) No

PSUS Yes

COPY(RS) No

COPY(RS-R) No

PSUE No


• An HTI P-VOL is shared with SI S-VOLs, TC, and/or UR S-VOLs, and the status of those pairs are not the same.

• You are sharing HTI P-VOLs with UR S-VOL. The journal group is not the same.

Notes on using Thin Image primary volumes as TrueCopy or Universal Replicator pair volumes

If you cannot change the status of a pair in an HTI consistency group, the CCI’s raidcom modify snapshot -snapshot_data create command can return the error code EX_EWSTOT (timeout) and terminate abnormally.

The following are possible reasons why you cannot change the pair status:• The HTI P-VOL is used as an UR S-VOL, and of the UR journal volume

does not have enough capacity.• The HTI license is invalid.• The HTI pair volumes are blocked.• You cannot run the raidcom modify snapshot -snapshot_data create

command on the pair because the HTI pair is not in the required status.• You cannot run the raidcom modify snapshot -snapshot_data create

command on the pair because the TC or UR pair is not in the required status.

After resolving these error conditions, make sure that all pairs in the consistency group are in “PAIR” status before running the raidcom modify snapshot -snapshot_data create command again.

Notes on acquiring snapshot dataThe following are notes on acquiring snapshot data:• The consistency group must include pairs in “PAIR” status to run the

raidcom modify snapshot -snapshot_data create CCI command. If the group contains pairs in a status other than “PAIR”, the command can terminate abnormally as shown below: The command is rejected. Timeout occurs. The error code is EX_EWSTOT. The pair is suspended. The error code is EX_EWSUSE.

• To maintain the consistency of snapshot data to be acquired and to avoid the raidcom modify snapshot -snapshot_data create command from ending abnormally, do not perform pair operations in the consistency group other than splitting a pair (for example, deleting snapshot data or deleting an HTI pair) while the command is running.Examples of abnormal ending includes: A timeout can occur. The error code is EX_EWSTOT. The pair can be suspended. The error code is EX_EWSUSE.

• The restoring of an HTI pair may end abnormally in either of the following conditions:



The system is acquiring snapshot data for a consistency group including the HTI pair.

The P-VOL of the HTI pair is also used as the P-VOL of another HTI pair. Also, snapshot data for a consistency group including the latter HTI pair is being acquired.

Notes on when the host is down

If the host is down, some consistency group might not contain any HTI pair. In this case, if you use the CCI to create a pair that should be a target of the At-Time Snapshot function, the command may be rejected. If this occurs, you should locate the consistency group in the Consistency Group tab of the Local Replications window, and then create a pair where this consistency group is specified.

Restoring pairsA pair is restored by reverse-resynchronizing.

Prerequisites• Pair status must be PSUS.• The user must have Storage Administrator (Local Copy) role.1. In the Storage Systems tree, click Replications > Local

Replications.2. In the Pairs tab, select the pairs you want to resynchronize, then click

Resync Pairs. 3. In the Resync Pairs window, for Resync Type, select Reverse Copy

(Secondary > Primary) to reverse resynchronize the volumes from the S-VOL to the P-VOL. The differential data is updated to the P-VOL.

4. Click Finish.5. In the Confirm window, for Task Name, type a name for the task and

then click Apply.The pairs are restored and the HTI pair status changes to PAIR.

Deleting snapshot dataYou can store up to 1,024 snapshots in a P-VOL. If you want to acquire new snapshot data for a P-VOL where 1,024 snapshots are already stored, delete the old snapshots. Resynchronizing the volumes from the P-VOL to the S-VOL deletes the snapshot data.

Caution: Pair status changes to PSUE if a failure occurs during pair restoration. You can also confirm a failure by checking the pair operation history (see Monitoring pair operation history on page 5-4).

To restore the pair, snapshot data must be deleted. However, when this is done, the storage system cannot guarantee the pair's P-VOL data. Therefore, take appropriate measures such as overwriting the backup data to the P-VOL or formatting the P-VOL.


Prerequisite• You have the Storage Administrator (Local Copy) role.1. In the Storage Systems tree, click Replications > Local

Replications.2. In the Pairs tab, select the pairs you want to resynchronize, then click

Resync Pairs.3. In the Resync Pairs window, for Resync Type, select Normal Copy

(Primary > Secondary) to resynchronize the volumes from the P-VOL to the S-VOL. The differential data is updated to the S-VOL.

4. Click Finish.5. In the Confirm window, for Task Name, type a name for the task and

then click Apply.The snapshot data is deleted.

Deleting pairsThis topic explains how to delete a HTI pair.

Prerequisites• You have the Storage Administrator (Local Copy) role.• The HTI pair status is “PAIR”, “PSUS”, or “PSUE”.1. In the Storage Systems tree, click Replications > Local

Replications.2. In the Pairs tab, select the pair you want to delete, and click More

Actions > Delete Pairs. 3. In the Delete Pairs window, for Task Name, type a name for the task

and then click Apply.

Caution: After deleting the pair, if the number of pairs shown on the summary tab and on the list is different, the system is changing the configuration. If this is occurring, to reload the configuration information, wait for a while and then click File > Refresh All.

5

Monitoring and maintenance 5–1Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Monitoring and maintenance

This topic provides information and instructions for monitoring and maintaining HTI.

□ Monitoring pair information

□ Monitoring consistency groups

□ Monitoring pair operation history

□ Monitoring licensed capacity

□ Monitoring the number of cache management devices

□ Managing pools and V-VOLs

□ Viewing snapshot data capacity

□ Maintenance requirements


5–2 Monitoring and maintenance

Monitoring pair information

Viewing the number of pairs and a list of pairsThis topic explains how to view the number of pairs and a list of pairs.

In the Storage Systems tree, click Replications > Local Replications. You can view the number of pairs and a list of pairs.

Checking pair status

When checking your pairs' status, click Refresh View to ensure the data is current.

The following table lists descriptions of the statuses.

Monitoring pair propertiesYou can monitor pair properties, such as confirming the status of a volume. Use the View Pair Properties window to monitor pair properties.

Prerequisite• You have the Storage Administrator (Local Copy) role.

Status Description S-VOL accessThe CCI

shows the status as

SMPL(PD) The pair is being deleted. Pair operations are not allowed in this status. Upon deletion, the status becomes “SMPL”.

Read/write disabled

SMPL

COPY The pair is being created. The initial copy is in progress. The storage system only accepts read/write operations to the P-VOL.

Read/write disabled

COPY

PAIR The volumes are paired. The storage system does not accept read/write operations to the S-VOL.

Read/write disabled

PAIR

PFUL The data pool threshold is exceeded in “PAIR” status. Read/write disabled

PFUL

PFUS The data pool threshold is exceeded in PSUS status. Read/write enabled

PFUS

PSUS The pair is split. The storage system accepts read/write operations to the S-VOL. The system records differential data between the P-VOL and S-VOLs so that you can immediately resynchronize the pair.

Read/Write enabled. Can be mounted.

PSUS for P-VOLsSSUS for S-VOLs

RCPY A Reverse Copy or Quick Restore is in progress. The storage system does not accept read/write operations to the S-VOL. Only S-VOL differential data is copied to the P-VOL.

Read/write disabled

RCPY

PSUE The storage system has suspended the pair. The storage system accepts read/write operations to the P-VOL. The storage system does not accept read/write operations to the S-VOL.

Read/write disabled

PSUE


1. In the Storage Systems tree, click Replications > Local Replications.

2. In the Local Replications window, in the Pairs tab, select the pair and then click More Actions > View Pair Properties.

Monitoring synchronous ratesYou can monitor synchronous rates, such as checking the percentage of data that is synchronized between the P-VOL and S-VOLs.

The synchronous rates for HTI is the data synchronous rate between the S-VOL and a newly created one. If the S-VOL is the newest, the S-VOL is compared with the P-VOL. Because the synchronous rates is an estimated value, it may have a large margin of error.

If the P-VOL is written to in the configuration of multiple generation (the configuration between the P-VOL and S-VOLs is 1:N), the synchronous rates for only the S-VOL of the newest generation decrease. If the S-VOL is written to, only the synchronous rates of written generation decrease.

The following figure shows an example of this process.


Replications.2. In the Local Replications window, in the Pairs tab, select the pair and

then click More Actions > View Pair Synchronous Rate.3. In the View Pair Synchronous Rate window, click Refresh View.

The latest synchronous rate shows.



If you close the View Pair Synchronous Rate window, information in the Local Replications window may not be the latest. Click Refresh View again.

Monitoring consistency groupsThis topic explains how to monitor consistency groups.

Viewing the number of consistency groupsThis topic explains how to view the number of consistency groups.

In the Storage Systems tree, click Replications > Local Replications. You can view the number of consistency groups.

Viewing a list of consistency groupsThis topic explains how to view a list of consistency groups.

In the tree, click Replications > Local Replications. You can view a list of consistency groups in the Consistency Groups tab.

Viewing properties of a consistency groupThis topic explains how to view properties of a consistency group.


Replications.2. On the Consistency Groups tab, click CTG ID.

The Consistency Group Properties window opens.

Monitoring pair operation historyThis topic explains how to monitor a pair’s operation history. You can review the operations that have been performed on a pair, including a description of the operations that have run.

You can view a maximum of 16,384 operations in the View Histories window.

Caution: When you restore an HTI pair, the synchronous rate between the P-VOL and the S-VOL may not be up to date. To view the updated synchronous rate, wait until the HTI pair restoration process has completed.

Note: You can view more than this maximum amount using the secondary window.

For more information about using the secondary window, see Monitoring pair operation history using the secondary window on page 5-5.


You can view the descriptions of the operations that have run in the Histories table.

For more information about the Histories table, see Viewing the operation run history on page 5-5.

Prerequisite• You have the Storage Administrator (Local Copy) role.1. In the tree, click Replications > View Histories.2. In the View Histories window, for Copy Type, select TI.

Default: TI3. View the information in the Histories table.

Viewing the operation run historyThe Description column in the Histories table on the View Histories window indicates which operations ran. This table shows only the operation on the pairs that consist of the P-VOL and S-VOLs allocated to each user.

The following tables show descriptions and explanations of the codes.

Monitoring pair operation history using the secondary windowYou can monitor a pair’s operation history using the secondary window. The storage system saves up to 512,000 records of the most recent operations.

Code Description Explanation

2001 PAIR The pair has been created.

2011 PSUS The pair has been split.

2021 SMPL The pair has been deleted.

2030 COPY(RS-R) START Pair restoration operation has begun.

2031 COPY(RS-R) END Pair restoration operation completed.

2032 COPY(RS-R) ENDED ABNORMAL

Pair restoration operation has failed.

2040 INITIALIZE START Initialization processing has begun.

2041 INITIALIZE END Initialization processing terminated normally.

2042 INITIALIZE ENDED ABNORMAL

Initialization processing terminated abnormally.

2051 COPY(RS) The snapshot data has been deleted.

2070 PSUE(ABNORMAL END) A failure occurred. The pair status has changed to PSUE.



Use the History window to view the history of operations and associated data. The upper pane of the window shows a list of SI records of operations in the ShadowImage History table. The lower pane shows a list of HTI records of operations in the Thin Image History table. The list sorts based on the column heading you click.

If some of the pairs include LUSE volumes or if the total number of the following pairs and migration plans is 500 or more in the subsystem, the History window can take some time to show the operation history.

For operations involving copying, the History window shows information about the operations only after the copying process starts.

The History window shows the following operation history information:• SI pairs• Volume Migration• HTI pairs

The following table lists descriptions for items shown for HTI pairs.


1. In SN, click Actions > Local Replications > SI > History.2. In the History window, complete the following:

To change the order in which information is shown in the list, click a column in the list. The list is sorted based on the items in the clicked column. If there are more than 16,384 records of operations, the list

Item Description

Previous button Click to open the previous page of the operation history list when the total number exceeds the limit, which is 16,384. If the number of the operation history pages is less than the limit, this button is unavailable.

Next button Click to open the next page of the operation history list when the total number exceeds 16,384. If the number of the operation history entries is less than 16,384, this button is unavailable.

Date Shows date and time of the operation in the following format:YYYY / MM / DD hh:mm:ss• YYYY: year• MM: month• DD: day• hh: hour• mm: minute• ss: second

P-VOL The operation's P-VOL, identified in the following format:LDKC:CU:LDEVA device ID ending in # (for example, 00:00:3C #), indicates that the LDEV is an external volume.For more information about UVM external volumes, see the Hitachi Universal Volume Manager User Guide.A device ID ending in X (for example, 00:00:3C X) indicates that the LDEV is a DP V-VOL.For more information about DP V-VOLs, see the Hitachi Unified Storage VM Block Module Provisioning Guide.

S-VOL The operation's S-VOL (V-VOL), identified in the following format:LDKC:CU:LDEV.A device ID ending in V (for example, 00:00:01 V) indicates that the LDEV is a V-VOL.

MU The HTI identifier.

Pool ID The identifier of the related data pool.

Code The HTI reference code, which indicates the kind of operation that you performed.For more information about the codes and descriptions of the codes, see Monitoring pair operation history on page 5-4.

Message Describes the operation. Related to the reference code.For more information about the messages and descriptions of the messages, see Monitoring pair operation history on page 5-4.



is divided into multiple pages and only the list that is showing is sorted. Click the column again to switch the sorting order (ascending or descending).

To update the list with the latest information if the list is not up to date, click File > Refresh.

If there are many records of operations, click and drag the scroll button down and up to see the complete list of operations.

To expand the display area of the list, click and drag down the frame border that divides the History window into upper and lower panes.

To show subsequent records of operations, click Next. To return to the previous page, click Previous.Note: If 16,384 or less records of operations exist, the Previous and Next are unavailable.

Monitoring licensed capacityThis topic explains how to monitor licensed capacity.

In the Storage Systems tree, select Replications. You can view the licensed capacity.

Monitoring the number of cache management devicesThis topic explains how to monitor the number of cache management devices. You can view the number of cache management devices in the View Management Resource Usage window. To open this window, click Actions > View Management Resource Usage.

Related topics• View Management Resource Usage window.

For more information about this window, see the Hitachi Unified Storage VM Block Module Provisioning Guide.

• The number of cache management devices required for Thin Image pair operations on page 2-9

Managing pools and V-VOLsThis topic explains how to manage pools and V-VOLs.

Monitoring pool informationIn the Storage Systems tree, select Pools. You can view information about a pool.

Related topics• The top window when you click Pool.


For more information, see the Hitachi Unified Storage VM Block Module Provisioning Guide.

Viewing used pool capacityYou can view used pool capacity by pool or by HTI P-VOL.

Viewing used capacity by pool1. In the Storage System tree, select Pools.2. The used capacity of the pools appears in the Used column of the Pools

tab.

Related topics• The Pools window after selecting a pool in the Hitachi Virtual Storage

Platform Provisioning Guide for Open Systems

Viewing used pool capacity by HTI P-VOL1. In the Storage System tree, select Pools.2. In the Pools table, click the name of the pool for which you want to see

the used capacity.3. Select the Primary Volumes tab.4. The used pool capacity of the HTI P-VOLs appears in the Used Pool

Capacity column.

Related topics• The top window when selecting a pool under Pools in the Hitachi Virtual

Storage Platform Provisioning Guide for Open Systems.

Pool capacity and formattingFollowing are cases that the free space of the pool is not formatted. In those cases, the free space of the pool may not increase:• Pools other than the selected pool are being formatted.• The pool usage level reaches up to the warning threshold.• The selected pool is blocked.• I/O loads to the storage system are high.• The cache memory is blocked.• Pool-VOLs in the selected pool are blocked.• Pool-VOLs which are external volumes in the selected pool are blocked.• Correction access executes to the pool-VOL in the selected pool.



• The format function for a free space of a pool is not operating.

Viewing formatted pool capacityUse the View Pool Management Status window to view formatted pool capacity.1. In the Storage Systems tree on the left pane of the top window, select

Pool.2. In the Pools window, from the Pools table on the right, click the row of

a pool you want to confirm the free pool capacity, click More Actions > View Pool Management Status.

Increasing pool capacityYou can increase the pool capacity by adding pool-VOLs to the pool. Use the following formula to calculate the pool capacity:

Pool capacity = the total capacity of pool-VOLs in the pool - the capacity of V-VOL management areas

Check the capacity of available free space in the pool and expand the pool as needed.1. In the Storage System tree, select Pools.2. In the Pools window, from the list, click the pool whose capacity you

want to increase and click Expand Pool.You cannot expand multiple pools.

3. In the Expand Pool window, click Select Pool VOLs.4. In the Select Pool VOLs window, Available Pool Volumes table,

select the LDEV you want, then click Add.The LDEV is moved to the Selected Pool Volumes table.(Optional) Complete the following: To filter rows, in the Filter component, select ON. To select all of the pool-VOLs in the list, click Select All Pages. To specify the capacity unit and the number of rows to be shown,

click Options.5. Click OK.6. In the Expand Pool window, view the number of selected pool-VOLs

and total capacity, and then click Finish.7. In the Confirm window, complete the following and then click Apply:

For Task Name, type the name for the task.Character and symbol limit: All 32 alphanumeric except \ / : , ; * ? " < > |

Note: Following are cases that the formatted pool capacity may decrease:• The storage system is allocating new pages.• The storage system is running correction copy.


Default: date-task name (Optional) For Go to tasks window for status, select to open the

Tasks window.The pool capacity is increased.

Related topics• Expand Pool wizard.

For more information about this wizard, see the Hitachi Unified Storage VM Block Module Provisioning Guide.

• Volume requirements on page 2-3.

Changing the pool thresholdUse the following procedure to change the pool threshold. Prevent the pool from reaching full capacity by monitoring the pool usage rate.

For example, when the actual pool usage rate is 50.1%, the value is rounded down to the closest integer 50, and 50% is shown on the window. If you set the pool threshold at 50%, even though the value shown on the window does not exceed the threshold, the excessive pool usage in SIM and SNMP is reported.1. In the Storage System tree, select Pools.2. In the Pools window, from the list, click the pool with the threshold that

you want to change, and then click More Actions > Edit Pools.3. In the Edit Pools window, complete the following and then click Finish:

Select Warning Threshold. For Warning Threshold, type a new threshold.

The possible range shows below the item.4. In the Confirm window, complete the following and then click Apply:

For Task Name, type the name for the task.Character and symbol limit: All 32 alphanumeric except \ / : , ; * ? " < > |Default: date-task name


The pool threshold is changed.

Related topics• Edit Pools wizard.


Changing the pool nameThis procedures explains how to change the pool name.



1. In the Storage System tree, select Pools.2. In the Pools window, click the pool whose name you want to change,

and then click More Actions > Edit Pools.3. In the Edit Pools window, complete the following and then click Finish:

Select Pool Name. For Pool Name, type a new pool name.

- For Prefix, type alphanumeric characters (case-sensitive).- For Initial Number, type a number of up to nine digits (9).

Required: YesMax. characters for the Prefix and Initial Number: 32

4. In the Confirm window, complete the following and then click Apply: For Task Name, type the name for the task.

Character and symbol limit: All 32 alphanumeric except \ / : , ; * ? " < > |Default: date-task name


The pool name is changed.

Related topics• Edit Pools wizard.


Recovering poolsPerform this operation for disaster recovery purpose. Normally, this operation should not be performed.

The recovery time for pools depends on pool or V-VOL usage. Calculate roughly 20 minutes of recovery time for every 100 TB of pool or V-VOL usage. Recovery time also depends on system workload.1. In the Storage System tree, select Pools.2. From the list, select one or more pools that you want to recover.3. In the Confirm window, complete the following and then click Apply:



The pool is recovered.


Related topics• Restore Pools window.


Deleting pools1. In the Storage System tree, select Pools.2. In the Pools window, from the list, select one or more pools that you

want to delete, and then click More Actions > Delete Pools.3. In the Delete Pools window, click Finish.4. In the Confirm window, complete the following and then click Apply:



To perform volume shredding to erase data from the volume, click Next.For more information about volume shredding operations, see the Hitachi Volume Shredder User Guide.

The pool is deleted.

Related topics• Delete Pools wizard.


Changing V-VOL namesThis procedure explains how to change a V-VOL name.1. In the Storage System tree, select Logical Devices.2. In the list, select the rows for V-VOLs you want to change, and then click

Edit LDEVs.3. In the Edit LDEVs window, for LDEV Name, type the prefix and the

initial number and then click Finish.4. In the Confirm window, complete the following and then click Apply:





The V-VOL name is changed.

Related topics• Edit LDEVs wizard.


Deleting V-VOLsThis procedure explains how to delete a V-VOL.

In most cases, you cannot delete V-VOLs and V-VOL groups that are specified for HTI S-VOLs. To delete a V-VOL and V-VOL group specified for an HTI S-VOL, first release the HTI pairs.1. In the Storage System tree, select Logical Devices.2. In the Logical Devices window, from the list, click the rows for the V-

VOLs that you want to delete, and then click More Actions > Delete LDEVs.

3. In the Delete LDEVs window, complete the following and then click Apply: For Task Name, type the name for the task.



The V-VOL is deleted.

Related topics• Delete LDEVs window.


Viewing snapshot data capacityYou can use the raidcom command to view the snapshot data capacity for each P-VOL.

This capacity indicates the pool capacity which is used as snapshot data stored from the P-VOL, but it does not include all of the information required to manage snapshot data. Although snapshot data is assigned from the pool in 42MB blocks, HTI stores snapshot data from a P-VOL in 256KB blocks. Therefore, the snapshot data capacity is not always consistent with each pool’s used capacity.

The following example shows how to use the raidcom command to view snapshot data capacity.


#raidcom get ldev -ldev_id 640Serial# : 63502LDEV : 640SL : 0CL : 0VOL_TYPE : OPEN-V-CVSVOL_Capacity(BLK) : 2181120VOL_Capacity(cyl) : 22720NUM_LDEV : 1LDEVs : 640NUM_PORT : 1

PORTs : CL2-E-0 14 Linux_X86F_POOLID : NONEVOL_ATTR : CVS : VVOL : QS:TIER_Alloc_level : HTIER#1_Alloc_rate : MAX : 50 : MIN : 30TIER#3_Alloc_rate : MAX : 50 : MIN : 30Snap_Used_Pool(MB) : 2181

For more information about the raidcom command, see Hitachi Command Control Interface Command Reference.

Maintenance requirementsThis topic explains important information regarding switching off the power when HTI is up and running. This topic also explains replacing the microcode offline.

Replacing the microcode offlineYou typically replace microcode online to preserve the pool and pair shared memory. If you replace the microcode offline (for example, when you need to change the configuration of shared memory), you must recreate the pools and pairs.

Switching off the power supply1. Stop the host I/O.2. Switch off the power supply.3. Restore the power supply.

When you restore the power, HTI's behavior depends on whether data that has been in shared memory before you switched off the power is present after you switch on the power supply.

If information in shared memory is present before switching off the power supply and after restoring the power

If information in the shared memory is present after you switch off the power supply, the pools and pairs can usually be used. However, since the storage system checks the status of the pools and the pool-VOLs, if the pool-VOLs are blocked at that moment, the pool is blocked and the status of the pairs changes to “PSUE”. If this occurs, you must recover the pools after the switch-on.



When you store snapshot data by consistency group, if you switch off the power supply before the status of all of the pairs in a consistency group has changed completely, the storing of snapshot data is resumed, and the status of some pairs may remain unchanged when the power supply is switched on again.

If information in shared memory is lost after you switch off the power supply

If you lose power and the data in SM is lost, the storage system saves the data to SSD at the time the power supply is switched off. You can still use the pool and HTI pairs, because the data is restored to SM from SSD after switching the power supply back on.

6

Troubleshooting 6–1Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Troubleshooting

This topic provides HTI troubleshooting information.

□ General troubleshooting

□ Contacting the Hitachi Data Systems Support Center


6–2 Troubleshooting

General troubleshootingThe following table lists causes and solutions to common HTI problems.

Problem Causes and solutions

Pool information is not shown.

Cause: The pool is blocked.Solution: Recover the blocked pool.For more information about recovering blocked pools, see Blocked pool recovery workflow on page 6-5.

A pool is blocked. Cause: • The pool-VOLs are blocked.• The pool reaches full capacity.Solution:1. Recover the blocked pool.

For more information about recovering blocked pools, see Blocked pool recovery workflow on page 6-5.

2. Complete the SIMs.For more information about processing pool-related SIMs, see Processing pool-related SIMs on page 6-5.

Pool usage rate exceeds the threshold.

Causes:• Too much snapshot data is stored in the pool.• There is an insufficient amount of pool capacity.• The pool threshold is too low.Solutions:1. Do one of the following:

Decrease the usage rate of the pool by deleting all snapshot data in the P-VOL.

Increase the pool capacity by adding more pool-VOLs.Note: To add the pool-VOLs, unused volumes must exist. If an unused volume does not exist, create new volumes or ask the Hitachi Data Systems Support Center to add the hard disks.

Increase the pool threshold value.2. Complete the SIMs.

or more information about completing SIMs, see Processing pool-related SIMs on page 6-5.

Cannot add pool-VOLs. Causes:• You have added the maximum amount of pool-VOLs to the pool.• Available pool management block in the V-VOL management area in the

shared memory is insufficient.• Pool-VOL requirements were not followed.Solutions:• Add pool-VOLs to another pool.• Initialize the V-VOL management area.• Check pool-VOLs requirements.


Cannot create HTI pairs. Causes:• There are not enough cache management devices.• There are not enough resources depending on cache management

devices.• The conditions to create the pair are not fulfilled.• The status of the specified volume is not shown because the system is

deleting an HTI pair.Solutions:• Make sure that there are enough cache management devices to create

the pairs.For more information, see Monitoring the number of cache management devices on page 5-8.

• If cache management devices are running out, delete unnecessary external volumes, V-VOLs, or all of the HTI pairs related to the P-VOL.

• Fulfill the conditions to create the pair and try the pair creation again.• Increase the resources depending on cache management devices by

deleting the unnecessary external volumes, V-VOLs, or all of the HTI pairs related to the P-VOL. Delete them until the following formula is satisfied:The number of external volumes + the number of V-VOLs + the number of P-VOLs of HTI pair <= 13,056When this is done, confirm that the volume status is SMPL(PD), run the CCI inqraid command to verify that the volume is not used by HTI, then recreate the pair.

HTI pairs are not shown in the volume list.

Causes:• The pairs are not created.• The filtering function prohibits the pairs from showing in the list.Solutions:• Create the pairs.• Change the settings in the Display Filter dialog box.

An error occurred while restoring the pair.

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.

A volume is blocked. Causes:• A failure occurred in two or more hard disk drives.• You turned off the breaker and then switched on the power supply.Solution: call the Support Center.

A problem occurred in the host application for monitoring the volumes.

Cause: Access to the volume is rejected.Solution:1. Stop the host application monitoring the volumes.2. Change all pair statuses to PSUS.3. Start the monitoring application on the host.For more information about host access to pair volumes, see HTI pair status on page 1-12.




Please contact the Support Center if the solutions in this table do not work, or if your problem is not included in this table.

A V-VOL cannot be recognized correctly after the host server is booted/rebooted or the command for recognizing a device is performed.

Cause: Access to the volume is rejected.Solution:1. Stop the host application monitoring the volumes.2. Change all pair statuses to PSUS.3. Reboot the host server or run a command that causes the system to

recognize the device.4. Start the monitoring application on the host.For more information about host access to pair volumes, see HTI pair status on page 1-12.

When the host computer tries to access the port, an error occurs and the host cannot access the port.

Cause: A port may go offline because access to a volume on another port is rejected.Solutions:• Wait awhile, then retry the operation.• If a host application is installed to monitor the volume, stop the

application.

SN times out frequently. Causes:• The load on SN is too heavy and it cannot respond to the SVP.• The time-out period is not long enough.Solutions:• Wait for a while, then retry the operation.• Verify the SN RMI time-out period.For information about how to set the RMI time-out period, see the Hitachi Storage Navigator User Guide.

The pair information in Local Replications window is not updated. The date and time in Last Updated is not updated.

HTI processing may be in progress. The update completes sometime after the HTI processing finishes.

By the write operation from the host, the used pool capacity shown on the summary tab in the Pool window and on the list in the Primary Volumes tab may be different.

By the write operation from the host, the storage system is running the copy processing. Wait for a while after the copy processing finishes, then the used pool capacity shown on the summary tab in the Pool window and on the list in the Primary Volumes tab matches.

You cannot resynchronize the HTI pair in “PSUE” status.

Cause:You cannot create the HTI pair because the status changed to “PSUE” during the process of creating the pair.Solution:Delete all of the HTI pairs related to the P-VOL, and then create again.



Blocked pool recovery workflowWhen a pool is blocked, recover the pool in the following order:1. Recover the blocked 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. Delete all snapshot data from the P-VOLs to increase unused

capacity.3. Recover the pair.

To recover the pair, delete the pair. When a pool is blocked, the status of all pairs with snapshot data in the pool changes to “PSUE”. To recover the “PSUE” pairs, they must be deleted.

4. Recover the V-VOLs.To recover the V-VOL, call the Support Center.

Processing pool-related SIMsCorrect pool-related Service Information Messages (SIMs) for the following, if they occur:• Reference code 601XXX: Pool usage rate exceeds the threshold.• Reference code 602XXX: Pool is blocked. (602FFE: Multiple pools are

blocked.)• Reference code 603000: Snapshot estimated manageable capacity is

less than 128TB.• Reference code 624000: The shared memory does not have space

available.

XXX indicates the pool ID. Check SIMs using the System Information/Status window in SN.

After correcting a problem related to a SIM, complete the SIM and change the SIM status to “Completed”.

After processing a pool-related SIM, you can perform volume shredding to erase data from the volume by clicking Next in the wizard.

For more information about volume shredding operations, see the Hitachi Volume Shredder User Guide.1. For reference code 601XXX or 602XXX, recover the pool in the “Normal”

status.For more information about countermeasures of these codes, see General troubleshooting on page 6-2.

2. Complete the following: (For reference code 624000):

a. Delete unused pools.



b. Delete unused HTI pairs.c. Delete the unused V-VOLs that you created using DP or HDT.d. Shrink the capacity of the DP or HDT pool.

(For reference code 603000) If some time has passed since you have completed the steps for reference code 624000 (above), reference code 624000 is reported.

3. On the Pool window, click More Actions > Complete SIM Action.4. In the Confirm window, complete the following and then click Apply:



The pool-related SIMs are processed.

Completing warning SIMs before depletion of cache management devices

The following SIM (service information message) occurs if the number of the remaining cache management devices goes below 4,096.• Reference code 670000

For more information about SIM reference codes, call the Support Center. In an SN window, you can see SIMs that occur in the storage system.

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

Calculating the number of the remaining cache management devices

Use this task to complete SIMs related to cache management devices.

Use the following formula to calculate the number of the remaining cache management devices:

number-of-cache-management-devices = 65,280 - number-of-cache-management-devices-being-used

For more information about how to confirm the number of cache management devices being used, see Monitoring the number of cache management devices on page 5-8.

If a warning SIM is issued before depletion of cache management devices, that does not mean a problem occurs immediately. However, if you continue to use the storage system and then cache management devices are depleted, the HTI pair status changes to “PSUE” and you cannot store snapshot data. Also, you cannot create additional HTI pairs using other P-VOLs. Therefore, be sure to reserve enough cache management devices.


After correcting a problem related to a SIM, complete the SIM and change the SIM status to “Completed”.1. Confirm the number of the remaining cache management devices.

For more information about how to confirm the number of the remaining cache management devices, see Calculating the number of the remaining cache management devices on page 6-6.

2. To make sure that the number of the remaining cache management devices is 4,096 or more, complete the following and then on the Pools window, click More Actions > Complete SIM Action:a. Remove unneeded V-VOLs.b. Remove all snapshots in unneeded P-VOLs.

3. In the Confirm window, complete the following and then click Apply: For Task Name, type the name for the task.



The number of the remaining cache management devices are calculated. The SIMs related to cache management devices are completed.To confirm whether a SIM has been complete normally, use the SN window. For more information about using this window, see the Hitachi Storage Navigator User Guide.

Contacting the Hitachi Data Systems Support CenterHDS customer support staff is available 24 hours a day, seven days a week. Contact the Hitachi Data Systems Support Center for technical support. Provide as much information about the problem as possible, including:• The circumstances surrounding the error or failure.• The content of any messages displayed on SN.• The SN configuration information (use the FD Dump Tool).• The service information messages (SIMs), including reference codes and

severity levels, displayed by SN.

If you need technical support, log on to HDS Support Portal for contact information: https://hdssupport.hds.com


A

Command Control Interface command reference A–1Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Command Control Interface commandreference

This appendix describes the CCI commands corresponding to actions in the SN GUI.

□ Statuses required for CCI operations

□ Troubleshooting with the Command Control Interface


A–2 Command Control Interface command reference

Statuses required for CCI operationsWhen you use the CCI, perform operations using the existing commands for pair operations or the raidcom commands.

If you store 65 or more snapshot data or use 64 or more MU numbers, use raidcom commands. You can use the existing commands for pair operations only for the pairs which have 0 to 63 MU numbers.

The following table shows the CCI commands or SN operation to perform pair operations.

You cannot use the noread mode (-m noread) for S-VOLs if you are using the CCI. When creating a pair, if you specify the noread mode for an S-VOL, the command ends normally but the noread mode does not take effect.

Pair status names in the CCIRunning the CCI commands for a pair with a status other than the one required can have mixed results. The following shows the results for operations that you run for pairs that are in statuses other than the required status.

Pair operation The CCI command SN operation

Create pair paircreate Create pairs

raidcom add snapshot

Create and split pair paircreate –split Split pairs

-

Split pair pairsplit Split pairs

raidcom modify snapshot -snapshot_data createraidcom modify snapshot -snapshot_data split

Normal Copy pairresync Resynchronize pairs

raidcom modify snapshot -snapshot_data resync

Reverse Copy pairresync -restore Resynchronize pairs

raidcom modify snapshot -snapshot_data restore

Delete pair pairsplit -S Delete pairs

raidcom delete snapshot

Pair status

The CCI command

paircreate

paircreate -split

pairsplit pairresync

pairresync -

restore

pairsplit -S

pairsplit -E

SMPL Ok Ab Ab Ab Ab Np Ab

COPY Np Ab Ab Np Np Ab Ab


When the CCI commands are rejected and end abnormally and the host is running the HP-UX operating system, sense bytes (SSB) are output to the CCI error log file. Sense bytes indicate the cause of the error.

For more information about SSB and error causes, see Troubleshooting with the Command Control Interface on page A-3.

Troubleshooting with the Command Control InterfaceIf errors occur when you are using the CCI, you can identify the cause of the error by referring to the following:• The log displayed on the CCI window• The CCI operation log file

The following table includes the SSB2 error codes.

PAIR/PFUL

Np Ok Ok Np Np Ok Ab

PSUS/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 normallyNp: the command is not performed but ends normallyAb: the command is rejected, ends abnormally

Pair status

The CCI command

paircreate

paircreate -split

pairsplit pairresync

pairresync -

restore

pairsplit -S

pairsplit -E

SSB2 CCI command Cause of error

9100 All commands You cannot run the command because the user authentication is not performed.

9685 paircreate You cannot create the pair because of a shortage of pair tables.

9700 paircreate You cannot create the pair because the pool is not available.

9702 paircreate You cannot create the pair because you specified a pool ID different from the pool ID used by existing pairs with the specified P-VOL.

9703 paircreate You cannot create the pair because the volume you specified as the P-VOL is already used by another HTI S-VOL.

9704 paircreate You cannot create the pair because the volume you specified as the S-VOL is already used by another HTI P-VOL.

9705 paircreate You cannot create the pair because the volume you specified as the S-VOL is already used by another HTI S-VOL.



9706 paircreate You cannot create the pair because the specified snapshot ID is already used by another HTI pair.

9707 paircreate You cannot create the pair because the capacity of the pair that you are trying to create exceeds the licensed capacity.

9718 All commands The command ended abnormally. You tried to use a command other than the paircreate command for the volume in the pair other than the HTI pair.This error can also occur if you run the command specifying an unsupported parameter.

9719 All commands The command ended abnormally because the pair is in a status that the command does not accept.This error can also occur if you run the command specifying an unsupported parameter.

971A paircreate You cannot create the pair because the capacity of shared memory is insufficient.

971F pairresync -restore

You cannot restore the pair because the volume you specified as the P-VOL has an S-VOL Disable attribute.

9723 All commands The command ended abnormally because there is no additional shared memory.

9724 All commands The command ended abnormally because there is no additional shared memory.

9725 All commands The command ended abnormally because the LDEV number of the volume you specified as the P-VOL is beyond the specified range.

9726 All commands The command ended abnormally because you specified the unmounted volume as the HTI P-VOL.

9727 paircreate, pairsplit, pairresync, pairresync -restore

The command ended abnormally because you specified a blocked volume as the HTI P-VOL.


The command ended abnormally because you specified a volume that is in the process of being formatted as the HTI P-VOL.


The command ended abnormally because you specified a volume as the HTI 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 HTI P-VOL has the command device setting.

972F paircreate You cannot create the pair because you specified a V-VOL as the HTI P-VOL.

9730 paircreate You cannot create the pair because you specified a pool-VOL as the HTI P-VOL.



9731 pairresync -restore

You cannot restore the pair because the HTI P-VOL and TC P-VOL share the volume, and the status of the TC pair is not “PSUS” or “PSUE”.


You cannot restore the pair because the HTI 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 HTI P-VOL and TC S-VOL share the volume.


You cannot restore the pair because the HTI P-VOL and UR S-VOL share the volume.

9735 paircreate You cannot create the pair because you specified UR's journal volume as the HTI P-VOL.

973B All commands The command ended abnormally because the LDEV number of the volume you specified as the S-VOL is beyond the specified range.

973C All commands The command ended abnormally because you specified an unmounted volume as the HTI S-VOL.

973D paircreate, pairsplit, pairresync, pairresync -restore

The command ended abnormally because you specified a blocked volume as the HTI S-VOL.

973E paircreate, pairsplit, pairresync, pairresync -restore

The command ended abnormally because you specified a volume that is in process of formatting as the HTI S-VOL.

973F paircreate, pairsplit, pairresync, pairresync -restore

The command ended abnormally because you specified a volume whose emulation type is other than OPEN-V as the HTI S-VOL.

9740 paircreate You cannot create the pair because the volume you specified as the HTI S-VOL has the command device setting.

9742 paircreate You cannot create the pair because you specified an external volume as the HTI S-VOL.

9745 paircreate You cannot create the pair because you specified a volume other than V-VOLs as the HTI S-VOL.

9746 paircreate You cannot create the pair because you specified a pool-VOL as the HTI S-VOL.

9747 paircreate You cannot create the pair because you specified a TC P-VOL as the HTI S-VOL.

9748 paircreate You cannot create the pair because you specified TC S-VOL as the HTI S-VOL.

974A paircreate You cannot create the pair because you specified a UR P-VOL as the HTI S-VOL.

974B paircreate You cannot create the pair because you specified a UR S-VOL as the HTI S-VOL.




974C paircreate You cannot create the pair because you specified a UR journal volume as the HTI S-VOL.

974F All commands The command ended abnormally because the volume you specified as the S-VOL has an S-VOL Disable attribute.


The command ended abnormally because the Max LBA size of the volumes you specified as the HTI P-VOL and S-VOL is different.


The command ended abnormally because the number of slots of the volumes you specified as the HTI P-VOL and S-VOL is different.

9754 paircreate You cannot create the pair because you specified a DP V-VOL as the HTI S-VOL.

9756 All commands The command ended abnormally because you specified a SI reserved volume as the HTI P-VOL.

9757 All commands The command ended abnormally because you specified a Volume Migration source volume as the HTI P-VOL.For information about using Volume Migration, contact the Hitachi Data Systems Support Center.

9758 All commands The command ended abnormally because you specified a Volume Migration target volume as the HTI P-VOL.For information about using Volume Migration, contact the Hitachi Data Systems Support Center.

9759 All commands The command ended abnormally because you specified a Volume Migration reserved volume as the HTI P-VOL.For information o about n using Volume Migration, contact the Hitachi Data Systems Support Center.

975A All commands The command ended abnormally because you specified a SI P-VOL as the HTI S-VOL.

975B All commands The command ended abnormally because you specified a SI S-VOL as the HTI S-VOL.

975C All commands The command ended abnormally because you specified a SI reserved volume as the HTI S-VOL.

975D All commands The command ended abnormally because you specified a Volume Migration source volume as the HTI S-VOL.For information about using Volume Migration, contact the Hitachi Data Systems Support Center.

975E All commands The command ended abnormally because you specified a Volume Migration target volume as the HTI S-VOL.For information about using Volume Migration, contact the Hitachi Data Systems Support Center.

975F All commands The command ended abnormally because you specified a Volume Migration reserved volume as the HTI S-VOL.For information about using Volume Migration, contact the Hitachi Data Systems Support Center.



976A paircreate An unavailable parameter (unsupported parameter) is specified in the command.

976C pairsplit You cannot store snapshot data because you ran the command when the status was “PSUE”.

976E pairsplit You cannot store snapshot data because the HTI P-VOL and TC S-VOL share the volume, and the TC pair is in the process of being created (“COPY” status).

976F pairsplit You cannot store snapshot data because the HTI P-VOL and UR S-VOL share the volume, and the UR pair is in the process of being created (“COPY” status).

9772 paircreate You cannot create the pair because you specified UR delta resync pair volume as the HTI S-VOL.

9774 paircreate You cannot create the pair because the HTI P-VOL and SI P-VOL share the volume, and the MU number you specified for the HTI pair is already used by the SI pair.

9777 paircreate You cannot create the pair because the HTI P-VOL and SI S-VOL share the volume, and you specified MU number zero (0) for the HTI P-VOL.

977A paircreate, pairsplit

The command ended abnormally because the HTI P-VOL and SI P-VOL share the volume, and the SI pair was in the process of resynchronization.

977B paircreate, pairsplit

The command ended abnormally because the HTI P-VOL and SI S-VOL share the volume, and SI pair status is not “PSUS”.

977C pairresync -restore

You cannot restore the HTI pair because the HTI P-VOL and SI P-VOL share the volume, and the SI pair status is not “PSUS” or “PSUE”.

977D pairresync -restore

You cannot restore the HTI pair because the HTI P-VOL and SI S-VOL share the volume, and the SI pair status is not “PSUS”.

977E pairsplit You cannot store snapshot data because the pool or the pool-VOL is blocked.


You cannot restore the pair for one of the following reasons:• Snapshot for the pair to be restored is being stored per

consistency group.• The P-VOL of the pair to be restored is used as the P-

VOL of another HTI pair, and the snapshot data of the latter pair is being stored per consistency group.


The command ended abnormally because HAM quorum disks are specified as HTI P-VOLs.


The command ended abnormally because HAM quorum disks are specified as HTI S-VOLs.




978A paircreate You cannot create the pair 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 you can create for a consistency group.

• A pair that uses the same P-VOL exists already in the specified consistency group.

978B paircreate You cannot create the pair because the consistency group number you specified is outside of the acceptable range of numbers.

9790 paircreate You cannot create the pair because the DP V-VOL, which is undergoing capacity expansion, is specified as the HTI P-VOL.

9793 paircreate You cannot create the pair because a DP V-VOL that is undergoing Unmap command operation with system option mode 905 ON is specified as the HTI P-VOL.


The command ended abnormally because a volume without path definition is specified as the HTI P-VOL


The command ended abnormally because a volume without path definition is specified as the HTI S-VOL.

97A1 paircreate If you have created the maximum number of HTI pairs, you cannot create additional pairs.

97A4 paircreate You cannot create the pair because the DP-VOL in the initialization process is specified as the HTI P-VOL.

97A5 paircreate, pairsplit, pairresync, pairresync -restore

The command ended abnormally because the external volume that is mapped for online data migration is specified as HTI P-VOL.

97A6 paircreate, pairsplit, pairresync, pairresync -restore

The command ended abnormally because the external volume that is mapped for online data migration is specified as the HTI S-VOL.

97B4 paircreate You cannot create the pair specified with a consistency group because the maximum number of the consistency groups are defined.

97B5 paircreate You cannot create the pair for the specified P-VOL because the maximum number of snapshot ID (MU number) was used.



97B6 paircreate You cannot create the pair because of one of the following reasons:• The new snapshot group was being created, but the

maximum number of snapshot groups were defined.• The maximum number of pairs are defined in the

specified snapshot group.

97B7 paircreate You cannot create the pair because the DP pool is being initialized.

97BF paircreate You cannot create the pair by using the consistency group to which the specified snapshot group belongs because of one of the following reasons:• The specified consistency group is being used for SI.• The number of pairs is more than the maximum

number of pairs that you can create for a consistency group.

• A pair that uses the same P-VOL exists already in the specified snapshot group.

97C2 All commands The command ended abnormally because the specified MU number is outside the allowable range.

97C3 paircreate, pairsplit, pairresync, or pairresync -restore

The command ended abnormally because microprograms that support HTI and other microprograms are mixed.

97C4 All commands The command ended abnormally because of one of the following reasons.• The specified pool is not an HTI.• The specified pool does not exist.

97C6 paircreate, pairsplit, pairresync, or pairresync -restore

The command ended abnormally because HTI is not installed.

97C7 paircreate You cannot create the pair because the capacity of cache management devices is insufficient.

97C8 paircreate You cannot create the pair because the capacity of the volume you specified as the primary or the S-VOL of the HTI pair is more than the supported size (4TB).

97C9 paircreate You cannot create the pair because you specified the LUSE volume for the P-VOL.

97CB All commands The command ended abnormally because the specified pool is other than a HTI pool.

97CF paircreate You cannot create the pair because the specified consistency group number is being used for a snapshot group.

B912 paircreate, pairsplit, pairresync

The pair operation failed because the specified S-VOL is wrong.




Identifying errors using the log on the CCI window1. Find the error code from the logs displayed on the CCI window.

The following figure shows an example of a log displayed 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).3. View the description of the SSB1/SSB2 error code combination.

For more information about the codes, see the table in Troubleshooting with the Command Control Interface on page A-3.For more information about the error codes not described in the table in Troubleshooting with the Command Control Interface on page A-3, contact the Hitachi Data Systems Support Center.

Identifying errors using the CCI operation log file1. Open the CCI log file from the following default location:

/HORCM/log*/curlog/horcmlog_HOST/horcm.log

where: The asterisk (*) is the instance number. HOST is the host name.

2. Find the error code. An example error code string is:11:06:03-37897-10413- SSB = 0xB901,4A96

3. Locate the SSB1 and SSB2 codes. In the example error code above: Error codes appear to the right of "SSB=". The last four digits to the left of the comma (,) are the SSB1 code

(B901). The characters to the right of the comma (,) are the SSB2 code

(4A96).4. Locate the description of the SSB1/SSB2 error code combination in the

following table.

B9A7 All commands You cannot obtain the consistency group information because HTI is not installed.



For more information about error codes for raidcom commands, see Command Control Interface User and Reference Guide.For more information about the error codes not described in the table in Troubleshooting with the Command Control Interface on page A-3, contact the Hitachi Data Systems Support Center.

B

Thin Image GUI reference B–1Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Thin Image GUI reference

This appendix describes HTI windows and dialog boxes.

□ Replications window

□ Local Replications window

□ View Pair Properties window

□ View Pair Synchronous Rate window

□ View Histories window

□ Consistency Group Properties window

□ Create Pairs wizard

□ Split Pairs wizard

□ Resync Pairs wizard

□ Delete Pairs window

□ Edit Local Replica Options wizard


B–2 Thin Image GUI reference

Replications windowThe following figure shows the Replications window.

Summary tab

Item Description

Licensed Capacity (Used/Licensed Capacity)

The used capacity and the licensed capacity of each product.

Number of Replica LDEVs The number of LDEVs used for SI and HTI pairs.

View Histories button Click to open the View History window.


Replica LDEVs tab

Only pairs that consist of the P-VOL and S-VOLs allocated to each user are shown.

Local Replications windowThe following figure shows this window.

Item Description

LDEV ID Selected LDEV's identifier

LDEV Name Selected LDEV's name

Emulation Type Selected LDEV's emulation type

Capacity Selected LDEV's capacity

Copy Type The copy typeValues:• SI-L1: SI L1 primary or S-VOL• SI-L2: SI L2 primary or S-VOL• TI: HTI pairStatus of SI and TI volumes:• Primary: P-VOL• Secondary: S-VOL

Export button Click to open a dialog for downloading table information to a file.



Summary tab

Item Description

Number of Pairs Number of pairs for each local replication software type.

Number of Reserve Volumes

The number of reserve volumes.

Number of Reserve Volumes including Secondary Volumes

The number of reserve volumes including S-VOLs.

Number of Consistency Groups

The number of consistency groups whose status is other than "Free".


Pairs tab

The Pairs tab only shows pairs that have P-VOL or S-VOLs to which you are allocated.

Snapshot Estimated Manageable Capacity *

The number of estimated manageable capacity for HTI pair. When Snapshot Estimated Manageable Capacity

is less than 128.00 TB, icon is shown.

Number of Pair Tables The number of pair tables for following combinations of software applications:• SI/Volume Migration: Number of SI and Volume

Migration pair tables in use.• TI: Number of HTI pair tables in use.

Number of Differential Tables

The number of differential tables in use.Differential tables are not used for HTI pairs. HTI pair operations does not increase or decrease the number of differential tables.

Edit Local Replica Options button

Click to open the Edit Local Replica Options window.

* Snapshot Estimated Manageable Capacity is the estimated HTI pair capacity that you can create using the remaining SM capacity. The remaining SM is calculated by subtracting the SM area used by HTI pools and HTI pairs from the whole SM capacity. Snapshot Estimated Manageable Capacity is a rough estimation, and the value does not guarantee that HTI pairs of the indicated capacity are created successfully. In case a HTI pool-VOL or a HTI pair is added or deleted, Snapshot Estimated Manageable Capacity changes.

Item Description

Item Description

Primary Volume The P-VOL.Values:• LDEV ID: The P-VOL's LDEV identifier. Click to open

the LDEV Properties dialog box, which contains additional information for the selected LDEV.

• LDEV Name: The P-VOL's LDEV name• Port ID: The P-VOL LDEV's LUN path’s port name.• Host Group Name: Host group name of the P-VOL

LDEV's LUN path• LUN ID: The P-VOL LDEV's LUN path’s LUN identifier.• Emulation Type: The P-VOL's emulation type• Capacity: The P-VOL's capacity• CLPR: The P-VOL's CLPR number

Copy Type The copy type.Values:• SI-L1: SI L1 pair• SI-L2: SI L2 pair• TI: HTI pair



Snapshot Group snapshot group name.Configure a snapshot group for an HTI pair to show information for this item.For non-HTI pairs, a hyphen (-) is shown.

Status Shows the following icons and pair.Values:(“SMPL” statuses is not shown in SN.)

• This icon indicates the SI pair or HTI pair is being deleted:Values: (SI or HTI) SMPL(PD)

• This icon indicates the following: The initial copy is in progress. The pair is being

created.Values:- (SI) COPY(PD)/COPY- (HTI) COPY

The pair is being resynchronized.Values:- (SI) COPY(RS)/COPY

The pair is being reverse resynchronized.Values:- (SI) COPY(RS-R)/RCPY- (HTI) RCPY

The pair is being split in normal mode.Value: (SI) COPY(SP)/COPY

• This icon indicates the following: The volumes are paired.

Value: SI: PAIR The pool has exceeded the threshold.

Value: TI: PFUL

Item Description


Status, continued• This icon indicates the following:

The pair is split.Value: SI: PSUS

The pair is being split in high-speed mode.Value: SI: PSUS(SP)/PSUS

The data pool threshold is exceeded in “PSUS” status.Values:- (TI) PFUS

• This icon indicates the pair is suspended:Values:- (SI) PSUE

For more information about HTI pair status, see Checking pair status on page 5-2. For more information about pair status for SI, see the user guide corresponding to the software applications.

Secondary Volume The S-VOLValues:• LDEV ID: The S-VOL's LDEV identifier. Click to open


• LDEV Name: The S-VOL's LDEV name• Port ID: The S-VOL LDEV's LUN path’s port name.• Host Group Name: Host group name of the S-VOL

LDEV's LUN path• LUN ID: The S-VOL LDEV's LUN path’s LUN identifier.• Emulation Type: The S-VOL's emulation type• Capacity: The S-VOL's capacity• CLPR: The S-VOL's CLPR number

Snapshot Date Date and time that a snapshot was acquired.For non-HTI pairs, a hyphen (-) is shown.

Pool Name (ID) Pool name and identification number.Required: YesFor non-HTI pairs, a hyphen (-) is shown.

Copy Pace The speed at which the system copies the data.Values: Faster, Medium, and LowerFor HTI, this item is blank.

CTG ID The consistency Group identifier.

Mirror Unit The mirror unit number.

Topology ID The LDEV’s topology identifier.

Create Pairs button Click to open the first window of the Create Pairs wizard.

Split Pairs button Click to open the Split Pairs window.

Resync Pairs button Click to open the Resync Pairs window.

Item Description



Reserve Volumes tab

The following image shows this tab.

The reserved volume for SI. Only LDEVs that are allocated to each user are shown.

More Actions list Shows a list of actions you can perform on the tab.Options:• View Pair Synchronous Rate: Click to open the

View Pair Synchronous Rate window.• View Pair Properties: Click to open the View Pair

Properties window.• Suspend Pairs: Click to open the Suspend Pairs

window.• Delete Pairs: Click to open the Delete Pairs window.• Export: Click to open a dialog for downloading table

information to a file.

Item Description

Item Description

LDEV ID Reserved volume LDEV's identifier

LDEV Name Reserved volume LDEV's name

Capacity Reserved volume's capacity

Number of Paths Shows number of paths to reserved volume.

Add Reserve Volumes Click to open Add Reserve Volumes window.

Remove Reserve Volumes Click to open Remove Reserve Volumes window.

Export Click to open a dialog for downloading table information to a file.


Consistency Groups tab

The following image shows this tab.

Item Description

CTG ID Consistency group identifier. Click to open the Consistency Group Properties window.

Status The statusValues:• SI Used: SI is using the consistency group.• TI Used: HTI is using the consistency group.• Free: Consistency group neither being used nor being

reserved.• (Changing...): The status of the consistency group is

changing.

Number of Pairs Number of pairs for the consistency group in use.




View Pair Properties windowThe following image shows this window.

Pair Properties tab

Pairs table

All pairs, which are related to a pair shown on the Pair Property table, are shown.

Item Description

Copy Type The copy type.Values: ShadowImage or Thin Image

Pool Name (ID) Pool name and ID.For non-HTI pairs, a hyphen (-) is shown.

Most Recent Snapshot Date

The date and time when you obtain the latest snapshot data.For non-HTI pairs, a hyphen (-) is shown.

LDEV ID Identifiers of P-VOL and S-VOL LDEVs

LDEV Name Names of P-VOL and S-VOL LDEVs


Item Description

Primary Volume The P-VOLValues:• LDEV ID: P-VOL's LDEV identifier• LDEV Name: P-VOL's LDEV name• Emulation Type: P-VOL's emulation type• Capacity: P-VOL's volume capacity• CLPR: P-VOL's CLPR number

Snapshot Group snapshot group name.Configure a snapshot group for an HTI pair to show information for this item.For non-HTI pairs, a hyphen (-) is shown.

Status Pair status.For more information about pair statuses, see Checking pair status on page 5-2.

Secondary Volume The S-VOLValues:• LDEV ID: S-VOL's LDEV identifier• LDEV name: S-VOL's LDEV name• Emulation type: S-VOL's emulation type• Capacity: S-VOL's volume capacity• CLPR: S-VOL's CLPR number• Mode: Indicates whether the S-VOL has been written

to or not. For SI, the mode also indicates whether you can read the S-VOL. W: The S-VOL has been written to. This also

indicates that the S-VOL was written to and cannot be read when its pair status is PSUS(SP)/PSUS or PSUS.

N: You cannot read the S-VOL because you specified the noread mode (-m noread) using the CCI.For more information about the noread mode (-m noread) using the CCI, see Pair status names in the CCI on page A-2.

A hyphen (-) indicates that the S-VOL has not been written to and you can read it.

Snapshot Date Date and time when a snapshot was acquired.For non-HTI pairs, hyphen (-) is shown.

CTG ID Consistency group identifier

COPY Pace Copy speed.For HTI pairs, hyphen (-) is shown.




View Pair Synchronous Rate windowThe following image shows this window.

Pairs table

Item Description

Primary Volume The P-VOLValues:• LDEV ID: P-VOL's LDEV identifier• LDEV Name: P-VOL's LDEV name• CLPR: P-VOL's CLPR number


Snapshot Group The name of the snapshot group.Configure a snapshot group for an HTI pair to show information for this item.For non-HTI pairs, a hyphen (-) is shown.


Synchronous Rate (%) Synchronous rate that the S-VOL matches the next new generation of the S-VOL. If the S-VOL is the latest one, the synchronous rate is computed by comparing the S-VOL with the P-VOL.


View Histories windowThis window includes the following section and table:• Setting items• Histories table

The following image shows the View Histories window.

Setting items

The following table lists the descriptions of the item in the View Histories window.

Secondary Volume The S-VOL• LDEV ID: S-VOL's LDEV identifier• LDEV name: S-VOL's LDEV name• CLPR: S-VOL's CLPR number



Refresh Click to update the information in the Pairs table.

Item Description



Histories table

This table shows a history of the operations that have been performed on pairs that consist of the P-VOL and S-VOLs allocated to each user. This table also includes descriptions of the operations that have run.

The following table lists the descriptions of the items on the Histories table.

Item Description

Copy Type The copy type.Values:• SI: The view history of SI pairs is shown. • TI: The view history of HTI pairs is shown.Default: TI

Item Description

Date Operation date and time

Primary Volume The P-VOLValues:• LDEV ID: P-VOL's LDEV identifier• Provisioning Type: The P-VOL’s provisioning type.

Values: Basic: Internal volume DP: DP-VOL External: External volume

Secondary Volume The S-VOLValues:• LDEV ID: S-VOL's LDEV identifier• Provisioning Type: The S-VOL’s provisioning type.

Values: Basic: Internal volume DP: DP-VOL External: External volume

This item is available only if you specify SI as the copy type.

Mirror Unit The mirror unit number.This item only shows information if you have selected TI as the copy type.

Pool ID The pool identifier.This item only shows information if you have selected TI as the copy type.

Description Code The code for the type of operation performed.


Consistency Group Properties windowThe following image shows this window.

Consistency Group Properties table

Description A description of the HTI operation.For more information about monitoring HTI pair operation history, see Monitoring pair operation history on page 5-4. For more information about monitoring the history for SI, see the user guide corresponding to the software application.


Item Description

Item Description

CTG ID Consistency group identifier

Status Consistency group status• SI Used: SI is using the consistency group• TI Used: HTI is using the consistency group.• Free: The consistency group is not being used and is

not reserved.• (Changing...): The status of the consistency group is

changing.

Number of Pairs Number of pairs assigned to the consistency group



Pairs table

The Pairs table shows pairs with P-VOL or S-VOLs to which you are allocated.

Create Pairs wizardUse the Create Pairs wizard to create pairs. This wizard includes the following windows:• Select Pair Configuration window.

Item Description

Primary Volume The P-VOLValues:• LDEV ID: P-VOL's LDEV identifier• LDEV Name: P-VOL's LDEV name• Emulation Type: P-VOL's emulation type• Capacity: P-VOL's volume capacity• CLPR: P-VOL's CLPR number


Snapshot Group Snapshot group name.Configure a snapshot group for an HTI pair to show information for this item.For non-HTI pairs, hyphen (-) is shown.


Secondary Volume • LDEV ID: S-VOL's LDEV identifier• LDEV Name: S-VOL's LDEV name• Emulation Type: S-VOL's emulation type• Capacity: S-VOL's volume capacity• CLPR: S-VOL's CLPR number

Snapshot Date Date and time that a snapshot was acquired.For non-HTI pairs, a hyphen (-) is shown.

Pool Name (ID) Pool name and identification number. For non-HTI pairs, a hyphen (-) is shown.



Detail Click to open the Pair Properties window.


• Select Primary Volumes window• Select Secondary Volumes window• Confirm window

For more information about how to create pairs, see Creating HTI pairs on page 4-2.

Select Pair Configuration windowThe Select Pair Configuration window is the first window in the Create Pairs wizard. The following image shows this window.

The following table describes the items in the Select Pair Configuration window.

Item Description

Copy Type Specifies the copy type.Values: SI or Thin Image

Pair Topology Type Specifies whether to show the pair topology type as the SI pair configuration.Values:• Cleared but available: You can set the SI pair

configuration.• Selected but unavailable: The SI pair exists.• Cleared and unavailable: You cannot set the SI pair

configuration.This item is only shown if you specify SI as the copy type.

Number of Secondary Volumes

The total number of S-VOLs assigned to the P-VOL. Includes volumes in existing pairs.For SI, this item is blank.



Select Primary Volumes windowThe Select Primary Volumes window is the second window in the Create Pairs wizard. The following image shows this window.

The following table describes the items in the Select Primary Volumes window.

Split Type Shows the split type.Values:• Non Split: The pair is not split.• Quick Split: Splits the pair immediately so that you

can continue to read or write to the S-VOL. The remaining differential data is copied to the S-VOL in the background.

• Steady Split: The pairs are split after all of the differential data is copied.

For HTI, this item is blank.


Item Description

Item Description

Use Primary Volumes of Snapshot Pairs

Specifies whether the P-VOL of a snapshot pair is used or not.Values:• Yes: shows only P-VOLs of the pair that is already

created in the Available LDEVs table.• No: shows only LDEV of the pair that is not created yet

in the Available LDEVs table.For SI, this item is blank.


Available LDEVs table

The following table shows the items in this table in the Select Primary Volumes window of the Create Pairs wizard.

Port ID list Select a port ID by which to filter the available LDEVs.

Host Group Name list Select a group name by which to filter the available LDEVs.Default: Any

Select Pool The selected pool name and identifier.This item is shown only for HTI.

Select Pool button Click to open the Select Pool window.If you select Yes for Use Primary Volumes of Snapshot Pairs, this button is unavailable.This button is shown only for HTI.

Add button Adds the selected LDEVs from the Available LDEVs table to the Selected LDEVs table.

Remove button Moves the selected LDEVs from the Selected LDEVs table back to the Available LDEVs table.

Item Description

Item Description

LDEV ID The LDEV's identifier.

LDEV Name The LDEV's name.

Port ID The LDEV's LUN path’s port name.

Host Group Name The LDEV's LUN path’s host group name.

LUN ID The LDEV's LUN path’s LUN identifier.

Provisioning Type The LDEV’s provisioning type.Values:• Basic: Internal volume• DP: DP volume• External: External volume

Emulation Type Emulation type of the LDEV.

Capacity The LDEV’s capacity.

CLPR The LDEV’s CLPR number.


Shows the number of S-VOLs. For SI, this number does not include the number of SI L2 S-VOLs.



Selected LDEVs table

Primary Volumes Shows information about the P-VOL when the LDEV is used as a S-VOL for an existing pair:• LDEV ID: The P-VOL's LDEV identifier.• LDEV Name: The P-VOL's LDEV name• Port ID: The P-VOL LDEV's LUN path’s port name.• Host Group Name: Host group name of the P-VOL

LDEV's LUN path• LUN ID: The P-VOL LDEV's LUN path’s LUN identifier.• Emulation Type: The P-VOL's emulation type• Capacity: The P-VOL's capacity• CLPR: The P-VOL's CLPR numberFor SI, this item is blank.

Mirror Unit The mirror unit number. If the pair is not an S-VOL of an existing pair, a hyphen (-) is shown.For SI, this item is blank.

Pool Name (ID) Pool name and ID number. For SI, this item is blank.

Item Description

Item Description

LDEV ID Selected P-VOL's LDEV identifier.

LDEV Name Selected P-VOL's 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.

Provisioning Type The LDEV’s provisioning type.Values:• Basic: Internal volume• DP: DP-VOL• External: External volume

Emulation Type Emulation type of LDEV.

Capacity Capacity of LDEV.

CLPR CLPR number.


Shows the number of S-VOLs. For SI, this number does not include the number of SI L2 S-VOLs.


Select Pool windowThe following image shows this window.

Primary Volume If you use the LDEV as an S-VOL for an existing pair, the P-VOL information.Values:• LDEV ID: The P-VOL's LDEV identifier. Click to open


• LDEV Name: The P-VOL's LDEV name• Port ID: The P-VOL LDEV's LUN path’s port name.• Host Group Name: Host group name of the P-VOL

LDEV's LUN path• LUN ID: The P-VOL LDEV's LUN path’s LUN identifier.• Emulation Type: The P-VOL's emulation type• Capacity: The P-VOL's capacity• CLPR: The P-VOL's CLPR numberFor SI, this item is blank.

Mirror Unit Mirror unit number. A hyphen (-) is shown if it is not an S-VOL of an existing pair.For SI, this item is blank.


Item Description



Available Pools table

The following table shows the items in this table on the Select Pool window.

Select Secondary Volumes windowThe Select Secondary Volumes window is the third window in the Create Pairs wizard. The following image shows this window.

Item Description

Pool Name (ID) The nickname and ID of the pool.

RAID Level The RAID level of the pool.If multiple RAID levels exist in the pool, Mixed is shown.If all of the pool-VOLs are external volumes, a hyphen (-) is shown.

Capacity The pool 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. Shows the number truncated to an integer.

Drive Type/RPM The hard disk drive type and RPM.When the volume is the external volume, External Storage and the value of the external LDEV tier rank.If multiple drive types, RPMs, or external LDEV tier ranks exist in the pool, Mixed is shown.

User-Defined Threshold (%)

The threshold you configure.

CLPR The ID and name of the CLPR in the CLPR-name format (ID:CLPR).

Detail button Click to open the Pool Properties window.


The following table describes the items in the Select Secondary Volumes window.

Item Description

Capacity list Select a capacity by which to filter the available LDEVs.Default: All - Remaining: 1

The remaining number you have to select

This item refers to the selected P-VOLs in the Selected Pairs table that do not have an assigned S-VOL.

Port ID list Select a port ID by which to filter the available LDEVs.

Host Group Name list Select a group name by which to filter the available LDEVs.Default: Any

Exclude Paired Volumes Select to exclude volumes that are already in a pair from the Available LDEVs table.Information is shown for this item only for SI.

Snapshot Group Select whether to create a new snapshot group or use the defined snapshot group.Values:• Create New Snapshot Group:

Select and then type the new Snapshot group name.• Use Existing Snapshot Group:

Select and then choose the desired snapshot group.Information is shown for this item only if you specify HTI as the copy type.

Detail button Click to open the LDEV Properties dialog box, which contains additional information for the selected LDEV.

Set button Click to move the selected LDEV from the Available LDEVs table to the Selected Pairs table.



Available LDEVs table

The following table describes the items in the Available LDEVs table in the Select Secondary Volumes window.

Clear button Click to move the selected S-VOL from the Selected Pairs table back to the Available LDEVs table.

Sort Pairs Sorts the Select Pairs table according to the following:• Arrange in Mirror Unit: Data is shown according to

mirror units.• Arrange in Topology: Data is shown according to its

topology. For example, SI L1 or SI L2 pairs.This item is only shown for SI.

Change Options button Click to open the Change Options window. Use this window to specify the options to apply to all new pairs.This button is only shown for SI.

Edit Mirror Units button Click to open the Edit Mirror Units window where you change mirror unit numbers, and thereby, pair topology.This button is only shown for SI.

Remove button Removes the pair from the table.For SI, if the SI L1 pair has an SI L2 pair, you cannot remove the pair.

Item Description

Item Description

LDEV ID The LDEV’s identifier.

LDEV Name The LDEV's 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 LDEV’s emulation type.

Capacity The LDEV’s capacity.

Provisioning Type The LDEV’s provisioning type.Values:• Basic: Internal volume• DP: DP-VOL• External: External volume• Snapshot: HTI volume

CLPR LDEV's CLPR number


Number of S-VOLs that the selected P-VOL has been assigned so far. For SI only, this amount can include the number of S-VOLs for an L2 pair that is already created.

Reserve Volume Indicates whether the LDEV is reserved as an S-VOL.Values: Yes or No


Selected Pairs table

The following table describes the items in the Selected Pairs table in the Select Secondary Volumes window.

Item Description

Primary Volume The P-VOLValues:• LDEV ID: The P-VOL's LDEV identifier.• LDEV Name: The P-VOL's LDEV name

A hyphen (-) is shown if the LDEV is not allocated.• Port ID: The P-VOL LDEV's LUN path’s port name.• Host Group Name: Host group name of the P-VOL

LDEV's LUN path• LUN ID: The P-VOL LDEV's LUN path’s LUN identifier.• Emulation Type: The P-VOL's emulation type• Capacity: The P-VOL's capacity

Snapshot Group The snapshot group name.For SI, this item is not shown.

New Snapshot Group Indicates whether the snapshot group is newly created.Values:• Yes: Newly created snapshot group• No: The snapshot group is not new.For SI, this item is blank.

Secondary Volume The S-VOL.Values:• LDEV ID: The S-VOL's LDEV identifier.• LDEV Name: The S-VOL's LDEV name

A hyphen (-) is shown if the LDEV is not allocated.• Port ID: The S-VOL LDEV's LUN path’s port name.• Host Group Name: Host group name of the S-VOL

LDEV's LUN path• LUN ID: The S-VOL LDEV's LUN path’s LUN identifier.• Emulation Type: The S-VOL's emulation type• Capacity: The S-VOL's capacity


Mirror Unit Mirror unit numberFor HTI, this item is blank.



Confirm windowThe Confirm window is the fourth window in the Create Pairs wizard.

The following images shows this window.

Split Type One of the following selected split types are shown:• Non Split: The pair is not split.• Quick Split: Splits the pair immediately so that you






Item Description



Item Description

Primary Volume The P-VOL.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 volume capacity• CLPR: P-VOL's CLPR number


Snapshot Group The snapshot group name.This item is shown only for HTI.

New Snapshot Group Indicates whether the snapshot group is newly created or not.• Yes: Newly created snapshot group• No: Already defined snapshot groupThis item is shown only for HTI.

Secondary Volume • LDEV ID: S-VOL's LDEV identifierA blank is shown if the LDEV is not allocated.

• LDEV Name: S-VOL's LDEV nameIf you have not allocated the LDEV, a hyphen (-) is shown.

• Port ID: Port name of the S-VOL LDEV's LUN path• Host Group Name: Host group name of the S-VOL

LDEV's LUN path• LUN ID: LUN ID of the S-VOL LDEV's LUN path• Emulation Type: S-VOL's emulation type• Capacity: S-VOL's volume capacity• CLPR: S-VOL's CLPR number




Split Pairs wizardUse the Split Pairs wizard to split pairs. This wizard includes the following windows:• Split Pairs window• Confirm window

For more information about acquiring snapshot data, see Acquiring snapshot data on page 4-5.

Split Pairs windowThe following image shows the Split Pairs window of the Split Pairs wizard.






Mirror Unit Shows the mirror unit number. For HTI, this item is blank.

Item Description



Item Description

Primary Volume The P-VOLValues:• LDEV ID: P-VOL's LDEV identifier• LDEV Name: P-VOL's LDEV name• Capacity: P-VOL's volume capacity• CLPR: P-VOL's CLPR number


Snapshot Group Snapshot group name.Configure a snapshot group for an HTI pair to show information for this item.For non-HTI pairs, a hyphen (-) is shown.




Confirm windowThe following image shows the Confirm window of the Split Pairs wizard.

Secondary Volume The S-VOL.• LDEV ID: S-VOL's LDEV identifier• LDEV Name: S-VOL's LDEV name• Capacity: S-VOL's volume capacity• CLPR: S-VOL's CLPR number

Pool Name (ID) Pool name and ID number. For non-HTI pairs, hyphen (-) is shown.

Mirror Unit Mirror unit number




For HTI, only Steady Split is an option.


Item Description



Item Description



Snapshot Group The snapshot group name.Configure a snapshot group for an HTI pair to show information for this item.For non-HTI pairs, a hyphen (-) is shown.




Resync Pairs wizardUse the Resync Pairs wizard to resynchronize pairs. This wizard includes the following windows:• Resync Pairs window• Confirm window

For more information about restoring pairs, see Restoring pairs on page 4-10.

Resync Pairs windowThe Resync Pairs window is the first window of the Resync Pairs wizard. The following image shows the window.






Secondary Volume The S-VOL.Values:• LDEV ID: S-VOL's LDEV identifier• LDEV Name: S-VOL's LDEV name• Capacity: S-VOL's volume capacity• CLPR: S-VOL's CLPR number

Pool Name (ID) Pool name and ID number.For non-HTI pairs, hyphen (-) is shown.


Item Description



Item Description



Snapshot Group Snapshot group name.Configure a snapshot group for an HTI pair to show information for this item.For non-HTI pairs, a hyphen (-) is shown.



Confirm windowThe Confirm window is the second window of the Resync Pairs wizard. The following image shows this window.


Secondary Volume • LDEV ID: S-VOL's LDEV identifier• LDEV Name: S-VOL's LDEV name• Capacity: S-VOL's volume capacity• CLPR: S-VOL's CLPR number

Snapshot Date The date and time that a snapshot was acquired.For non-HTI pairs, a hyphen (-) is shown.

Pool Name (ID) Pool name and ID number. For non-HTI pairs, a hyphen (-) is shown.


Resync Type The type of resynchronization.Values:• Normal Copy (Primary > Secondary): All

differential data is updated on the S-VOL.• Reverse Copy (Secondary > Primary): All

differential data is updated on the P-VOL. This option cannot be used for SI L2 pairs.

• Quick Resync (Primary > Secondary): Changes the pair status to “PAIR” immediately. The differential data is copied during the updating copy. You can specify this option only for SI pairs.

• Quick Restore (Secondary > Primary): Replaces the P-VOL and the S-VOL. The differential data is copied during the update copying. You can specify this option only for SI pairs. You cannot use this option for the following pairs: SI L2 pair A pair containing DP-VOL as the P-VOL or the S-

VOL SI pair containing HTI pair as the P-VOL or the S-

VOL


Item Description



Item Description






Delete Pairs windowUse the Delete Pairs window to confirm the deletion of the selected pairs.

For more information about deleting pairs, see Deleting pairs on page 4-11.

The following image shows the Delete Pairs window.


Resync Type The type of resynchronization.Values:• Normal Copy (Primary > Secondary)• Reverse Copy (Secondary > Primary)• Quick Resync (Primary > Secondary)• Quick Restore (Secondary > Primary)


Secondary Volume S-VOL information includes:• LDEV ID: S-VOL's LDEV identifier• LDEV Name: S-VOL's LDEV name• Capacity: S-VOL's volume capacity• CLPR: S-VOL's CLPR number


Pool Name (ID) Pool name and ID number. For non-HTI pairs, a hyphen (-) is shown.


Item Description



Item Description





Secondary Volume • LDEV ID: S-VOL's LDEV identifier• LDEV Name: S-VOL's LDEV name• Capacity: S-VOL's volume capacity• CLPR: S-VOL's CLPR number



Edit Local Replica Options wizardThe Edit Local Replica Options wizard includes the following windows:• Edit Local Replica Options window.• Confirm window

Edit Local Replica Options windowUse the Edit Local Replica Options window of the Edit Local Replica Options wizard to specify options that affect performance.

For more information about this window, see Hitachi ShadowImage® User Guide.

The following image shows this window.

SI/TI System Options table

The Edit Local Replica Options window includes the SI/TI System Options table.

The following table lists descriptions of the items in the SI/TI System Options table.


Pool Name (ID) Pool name and ID number.For non-HTI pairs, a hyphen (-) is shown.


Item Description


Confirm windowThe following image shows the Confirm window of the Edit Local Replica Options wizard.

Item Description

System Option The system options.Options:• Swap & Freeze: Saves the data as it is immediately

after you perform Quick Restore. If you Quick Restore with this option enabled, the copy is updated after the Quick Restore is inhibited. The paired S-VOL is not updated.

• Host I/O Performance: Gives weight to I/O response rather than the copy time. This option controls the copy operation, and improves the host I/O response.

• Copy Pace Ext. Slower1• Copy Pace Ext. Slower2• Copy Pace Ext. None: Reducing the copy volume in

the “PAIR” status curbs the influence to the I/O performance of the host server. This item is available to all pairs in “PAIR” status. The host server I/O performance is improved in the following order: Copy Pace Ext. Slower1, Copy Pace Ext. Slower2, and Copy Pace Ext. None.

Status Shows whether the option is enabled or disabled.

Enable button Click to enable the option.

Disable button Click to disable the option.



SI/TI System Options table

The Confirm window of the Edit Local Replica Options wizard includes the SI/TI System Options table.

The following table lists descriptions of the items in the SI/TI System Options table.

Item Description

System Option Shows the system options.

Status Shows whether the option is enabled or disabled.

CA KD E F G H I J L M N O P Q R S T U V W X Y# B ZA C D E F H I J L M N O P Q R S T U V W

Glossary–1Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Glossary

This glossary defines the special terms used in the Hitachi Unified Storage VM user documentation and SN online help. Click the letter links below to navigate.

A

access attributeThe setting on a logical volume that determines whether hosts can read or write to the volume.

allocated volumeA logical device (LDEV) for which one or more host paths are defined.

alternate pathA secondary path (port, target ID, LUN) to a logical volume, in addition to the primary path, that is used as a backup in case the primary path fails.

AOUallocation on use. Another name for Hitachi Dynamic Provisioning.

arrayAnother name for a RAID storage system.

at-time splitOperation in which all pairs in a consistency group are split at the same time.

audit logFiles that store a history of the operations performed from SN and the service processor (SVP) and commands that the storage system received from hosts.



Glossary–2

C

C/Tconsistency time

cache logical partition (CLPR)Virtual cache memory that you can allocate to specified hosts in contention for cache memory.

cascade configurationIn a SI cascade configuration, you can define two layers of S-VOLs for a single P-VOL. Pairs created in the first and second layer are called cascaded pairs.

CCICommand Control Interface

CGconsistency group (CG, CTG) on page Glossary-2

CLPRcache logical partition

command deviceA dedicated logical volume used only by the Command Control Interface (CCI) to interface with the storage system. Can be shared by several hosts.

configuration definition fileA text file that defines the configuration, parameters, and options of the CCI operations. It also defines the connected hosts and the volumes and groups for the CCI instance.

consistency group (CG, CTG)A group of copy pairs (local or remote) on which copy operations are performed simultaneously to maintain data consistency across all pairs in the group.

consistency time (C/T)The latest time at which the data on the S-VOL was consistent with the data on the P-VOL in a copy pair or consistency group. The C/T also refers to the time stamp of a journal group.



controllerA general term for the component in the storage system that manages all storage functions. The controller typically contains processors, I/O devices, RAM, power supplies, cooling fans, and other sub-components as needed to support the operation of the storage system.

copy pairA pair of volumes in which one volume contains original data and the other volume contains the copy of the original. Copy operations can be synchronous or asynchronous, and you can locate the volumes of the copy pair in the same storage system (local copy) or in different storage systems (remote copy).

A copy pair can also be called a volume pair, or just pair.

CRMHitachi Cache Residency Manager

CT, C/Tconsistency time

CTGconsistency group

CTLcontroller

CTQcommand tag queuing

CUcontrol unit

currency of dataThe synchronization of the volumes in a copy pair. When the data on the S-VOL is identical to the data on the P-VOL, the data on the S-VOL is current. When the data on the S-VOL is not identical to the data on the P-VOL, the data on the S-VOL is not current. See also data consistency on page Glossary-4.

custom volume (CV)A custom-size volume whose size is defined by the user using Virtual LUN.

CVcustom volume (CV) on page Glossary-3



Glossary–4

CVScustom volume size

cylinder bitmapIndicates the differential data (updated by write I/Os) in a volume of a split or suspended copy pair. In TC, the P-VOL and S-VOLs each have their own cylinder bitmap. When a TC pair is resynchronized, the cylinder bitmaps are merged, and the differential data is copied to the S-VOL (or P-VOL in the case of reverse resynchronization).

D

data consistencyThe synchronization of the volumes in a copy pair. When the data on the S-VOL of a copy pair is identical to the data on the P-VOL, the data is consistent. When the data on the S-VOL is not identical to the data on the P-VOL, the data on the S-VOL is not consistent. See also currency of data on page Glossary-3.

data driveA physical data storage device that can be either a hard disk drive (HDD) or a flash drive (also called a solid-state device).

data poolA set of logical volumes designated to temporarily store snapshot data of HTI P-VOLs. The volumes in the data pool that contain the HTI snapshot data are called pool-VOLs.

device emulationIndicates the type of logical volume. Open-systems device emulation types provide logical volumes of variable size, called logical units (LUs), that contain ASCII data in FBA format. The typical open-systems device emulation type on the Unified Storage VM is OPEN-V.

differential dataChanged data in one of the volumes of a copy pair, usually the P-VOL, that has not been reflected in the other volume of the pair. In TC, the cylinder bitmap on page Glossary-4 for the volume keeps track of the differential data, and in HTI the differential data (snapshot data) is stored on V-VOLs in the data pool on page Glossary-4.

disk arrayDisk array, or just array, is a (complete) storage system that employs RAID technology (for example, RAID1, RAID5, RAID6), including the control and logic devices, drives, connecting cables, and racks.



DKCdisk controller

DKCMAINdisk controller main. Another name for the microcode for the Unified Storage VM storage system.

DPHitachi Dynamic Provisioning

DP-VOLDynamic Provisioning-virtual volume. A V-VOL that DP is not using memory space.

DRUHitachi Data Retention Utility

dumpA set of data that is saved when an error occurs and used by support personnel to determine the cause of the error.

dynamic provisioningAn approach to managing storage. Instead of “reserving” a fixed amount of storage, it removes capacity from the available pool when data is actually written to disk. Also called thin provisioning.

E

EXGexternal volume group

Export ToolSoftware used to export monitoring data (statistics) shown in the Hitachi Performance Monitor Monitor Performance window to text files.

external portA fibre-channel port that is configured to be connected to an external storage system for UVM operations.

external volumeA volume whose data resides on data drives that are physically located outside the Unified Storage VM storage system.



Glossary–6

F

FD Dump ToolDownloads SN configuration information for backup and troubleshooting purposes.

flash driveA data drive that is a solid-state memory device instead of a rotating hard disk drive. Can also be called a solid-state drive (SSD).

H

HDDhard disk drive

HDLMHitachi Dynamic Link Manager

HDPHitachi Dynamic Provisioning

HDSHitachi Data Systems

HDTHitachi Dynamic Tiering software

HORCHitachi Open Remote Copy. Another name for Hitachi TrueCopy®.

HORCMHitachi Open Remote Copy Manager. Another name for the CCI.

host groupA group of hosts of the same operating system platform.

host modeOperational modes of the fibre-channel ports on the Unified Storage VM that provide enhanced compatibility with supported host platforms.

host mode optionAdditional options for the fibre-channel ports on the Unified Storage VM storage system that provide enhanced functionality for host software and middleware.



HURHitachi Universal Replicator

HUS VMHitachi Unified Storage VM

I

initial copyA copy operation that copies all data on the P-VOL of a copy pair to the S-VOL of the pair. An initial copy operation is performed when a copy pair is created. See also update copy on page Glossary-15.

in-system replicationThe original data volume and its copy are located in the same storage system. SI in-system replication provides duplication of logical volumes. See also remote replication on page Glossary-13.

internal volumeA logical volume whose data resides on drives that are physically located within the storage system. See also external volume on page Glossary-5.

J

JNLjournal

JNLGjournal group

journal group (JNLG)In an UR system, journal groups manage data consistency between multiple P-VOLs and S-VOLs. See also consistency group (CG, CTG) on page Glossary-2.

journal volumeA volume that records and stores a log of all events that take place in another volume. In the event of a system crash, the journal volume logs are used to restore lost data and maintain data integrity.

In UR, differential data is held in journal volumes on until it is copied to the S-VOL.



Glossary–8

L

L1 pairlayer-1 (L1) pair

L2 pairlayer-2 (L2) pair

layer-1 (L1) pairIn a SI cascade configuration, a layer-1 pair consists of a P-VOL and S-VOL in the first cascade layer. You can pair an L1 P-VOL with up to three L1 S-VOLs.

See also cascade configuration on page Glossary-2.

layer-2 (L2) pairIn a SI cascade configuration, a layer-2 (L2) pair consists of a P-VOL and S-VOL in the second cascade layer. You can pair an L2 P-VOL with up to two L2 S-VOLs.

See also cascade configuration on page Glossary-2.

LCUlogical control unit

LDEVlogical device

LDKClogical disk controller

leaf volumeA level-2 S-VOL in a SI cascade configuration. The P-VOL of a layer-2 pair is called a node volume. See also cascade configuration on page Glossary-2.

license keyA specific set of characters that unlocks an application and allows it to be used.

local copyAnother name for in-system replication on page Glossary-7.

logical device (LDEV)An individual logical data volume (on multiple drives in a RAID configuration) in the storage system. An LDEV may or may not contain



any data and may or may not be defined to any hosts. Each LDEV has a unique identifier, or address, within the storage system composed of the logical disk controller (LDKC) number, control unit (CU) number, and LDEV number. The LDEV IDs within a storage system do not change.

An LDEV formatted for use by open-systems hosts is called a logical unit (LU).

logical disk controller (LDKC)A group of control unit (CU) images in the Unified Storage VM storage system that is controlled by a virtual (logical) storage system within the single physical storage system.

logical unit (LU)A logical volume that is configured for use by open-systems hosts.

logical unit (LU) pathThe path between an open-systems host and a logical unit.

logical volumeA logical device (LDEV), or a set of concatenated LDEVs in the case of a LUSE volume, that has been defined to one or more hosts as a single data storage unit. An open-systems logical volume, or just volume, is called a logical unit (LU).

LUlogical unit

LUNlogical unit number

LUNMHitachi LUN Manager

LUSEHitachi LUN Expansion; LU size expansion

LVlogical volume

M

master journal (M-JNL)A dedicated volume that contains the differential data on the primary UR system until it is copied to the restore journal (R-JNL) on the secondary system. See also restore journal (R-JNL) on page Glossary-13.



Glossary–10

mirrorIn UR, each pair relationship in and between journal groups is called a mirror. Each pair is assigned a mirror ID when it is created. The mirror ID identifies individual pair relationships between journal groups.

M-JNLmain journal

modify modeThe mode of operation of SN that allows changes to the storage system configuration. See also view mode on page Glossary-15.

MUmirror unit

N

node volumeA level-2 P-VOL in a SI cascade configuration. The S-VOL of a layer-2 pair is called a leaf volume. See also cascade configuration on page Glossary-2.

O

OPEN-VA logical unit (LU) of user-defined size that is formatted for use by open-systems hosts.

OSoperating system

P

pairTwo logical volumes in a replication relationship in which one volume contains original data to be copied and the other volume contains the copy of the original data. The copy operations can be synchronous or asynchronous, and you can locate the pair volumes in the same storage system (in-system replication on page Glossary-7) or in different storage systems (remote replication on page Glossary-13).

pair statusIndicates the condition of a copy pair. A pair must have a specific status for specific operations. When a replication operation (such as creating or



splitting a pair) completes, the status of the pair changes to the new status.

parity groupAnother name for a RAID group on page Glossary-12.

PDLProduct Documentation Library

PFMHitachi Performance Monitor

PiTpoint-in-time

point-in-time (PiT) copyA copy or snapshot of a volume or set of volumes at a specific point in time. You can use a point-in-time copy for backup or mirroring application to run concurrently with the system.

poolA set of volumes that are reserved for storing DP or HTI write data.

pool volume (pool-VOL)A logical volume that is reserved for storing write data for DP or HTI.

Preview listThe list of requested operations on SN.

primary volume (P-VOL)The volume in a copy pair that contains the original data to be replicated. The data on the P-VOL is duplicated synchronously or asynchronously on the secondary volume (S-VOL) on page Glossary-13.

P-VOLprimary volume

Q

QSAQuery Security Attributes



Glossary–12

quick formatThe quick format feature in Virtual LUN in which the formatting of the internal volumes is done in the background. This allows system configuration (such as defining a path or creating a copy pair) before the formatting is completed. To run quick formatting, the volumes must be in blocked status.

quick restoreA reverse resynchronization in which data is not actually copied: the P-VOL and S-VOLs are swapped.

quick resyncA forward resynchronization (ShadowImage only) in which the pair status changes to “PAIR” immediately and the differential data is copied during the updating copy.

quick splitA split operation in which the pair is split immediately before the differential data is copied to the S-VOL. Any remaining differential data is copied to the S-VOL in the background. The benefit of the quick split is that the S-VOL is immediately available for read and write I/O.

R

RAID groupA set of data drives in a RAID configuration that have the same capacity and are treated as one group for data storage and recovery. A RAID group contains both user data and parity information, which allows the user data to be accessed in the event that one or more of the drives within the RAID group are not available. The RAID level of a RAID group determines the number of data drives and parity drives and how the data is striped across the drives. For RAID1, user data is duplicated within the RAID group, so RAID1 RAID groups do not have parity data.

A RAID group can also be called an array group or a parity group.

RCreference code (of a service information message)

remote console PCAnother name for the SN PC.

remote copyAnother name for remote replication on page Glossary-13.



remote replicationData replication configuration in which the storage system that contains the original data is at a local site and the storage system that contains the copy of the original data is at a remote site. TC and UR provide remote replication. See also in-system replication on page Glossary-7.

reserve volumeA volume reserved either as a S-VOL for ShadowImage or SI, or as a migration destination for a Volume Migration migration plan.

restore journal (R-JNL)Holds differential data on the secondary UR system until it is copied to the S-VOL.

resyncresynchronize

R-JNLrestore journal

root volumeA level-1 P-VOL in a SI cascade configuration. The S-VOL of a layer-1 pair is called a node volume. See also cascade configuration on page Glossary-2.

R-SIMremote service information message

S

S#, S/Nserial number

secondary volume (S-VOL)The volume in a copy pair that is the copy of the original data on the primary volume (P-VOL) on page Glossary-11.

service information message (SIM)SIMs are generated by a Unified Storage VM storage system when it detects an error or service requirement. SIMs are reported to hosts and displayed on SN.



Glossary–14

service processor (SVP)The computer inside a Unified Storage VM storage system that hosts the SN software and is used by service personnel for configuration and maintenance of the storage system.

shared volumeA volume that is being used by more than one replication function. For example, a volume that is both the P-VOL of a TC pair and the P-VOL of a SI pair.

SIHitachi ShadowImage®

sidefileAn area of cache memory that is used to store updated data for later integration into the copied data.

SIMservice information message

SMPLsimplex

SNserial number; Storage Navigator

snapshotA point-in-time copy of a data volume in a storage system.

SOMsystem option mode (SOM) on page Glossary-15

SSBsense byte

SSDsolid-state drive. Another name for a flash drive on page Glossary-6.

steady splitIn SI, a typical pair split operation in which any remaining differential data from the P-VOL is copied to the S-VOL and then the pair is split.

Storage AdministratorUser role in SN with permission to perform data encryption operations.



S-VOLsecondary volume (S-VOL) on page Glossary-13

SVPservice processor (SVP) on page Glossary-14

system option mode (SOM)Additional operational parameters for the Unified Storage VM storage systems that enable the storage system to be tailored to unique customer operating requirements. SOMs are set on the service processor.

T

TCHitachi TrueCopy®

U

update copyA copy operation that copies differential data on the P-VOL of a copy pair to the S-VOL of the pair. Update copy operations are performed in response to write I/Os on the P-VOL after the initial copy operation is complete.

URHitachi Universal Replicator

UVMHitachi Universal Volume Manager

V

Vversion

view modeThe mode of operation of SN that allows viewing only of the storage system configuration. The two SN modes are view mode and modify mode.

Virtual LUN volumeA custom-size volume whose size is defined by the user using Virtual LUN. Also called a custom volume (CV).



Glossary–16

virtual volume (V-VOL)A logical volume in a storage system that does not have physical storage space. HTI uses V-VOLs as S-VOLs of copy pairs. A V-VOL used for DP is called a DP-VOL.

volumeAnother name for a logical volume on page Glossary-9.

volume pairAnother name for a copy pair on page Glossary-3.

VPMHitachi Virtual Partition Manager

V-VOLvirtual volume

V-VOL management areaThe V-VOL management area, which is automatically created when shared memory is added, is an area used to store information for associating pool-VOLs and DP-VOLs.

W

write orderThe order of write I/Os to the P-VOL of a copy pair. The data on the S-VOL is updated in the same order as on the P-VOL, particularly when there are multiple write operations in one update cycle. This feature maintains data consistency at the S-VOL. Update records are sorted in the cache at the remote system to ensure proper write sequencing.

Index–1Hitachi Unified Storage VM Block Module Hitachi Thin Image User Guide

Index

Bblocked pool 6–2blocked pool, recovering 6–5blocked volume 6–3

CCCI

command device 3–7troubleshooting with A–3

consistency group, monitoring 5–4creating

pools 3–2

Ddeleting

V-VOLs 5–14

HHistories window B–13host access problem 6–4

Llicense information, viewing 5–2

Mmonitoring pool information 5–8

Ppair

details, viewing 5–2operations history, monitoring 5–4status definitions 5–2status for CCI operations A–2

pool information, monitoring 5–8pool threshold exceeded 6–2pools

changing the pool name 5–12changing the usage threshold 5–11creating 3–2

deleting 5–13increasing capacity 5–10

SShared Memory Requirements 2–3SIMs for pool problems 6–5Snapshot

powering off the system 5–15synchronous rate, viewing 5–3

VV-VOLs

creating 3–5Viewing free pool capacity 5–10


Index–2

MK-92HM7010-05

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0)1753 [email protected]

Asia Pacific+852 3189 [email protected]

hitachi unified storage vm block module hitachi thin image ... · product version contents getting...

Documents